[csw-devel] SF.net SVN: gar:[6054] csw/mgar/pkg/buildbot/trunk/Makefile

wahwah at users.sourceforge.net wahwah at users.sourceforge.net
Wed Aug 19 13:34:29 CEST 2009


Revision: 6054
          http://gar.svn.sourceforge.net/gar/?rev=6054&view=rev
Author:   wahwah
Date:     2009-08-19 11:34:29 +0000 (Wed, 19 Aug 2009)

Log Message:
-----------
buildbot: cleaning up BLURB

Modified Paths:
--------------
    csw/mgar/pkg/buildbot/trunk/Makefile

Modified: csw/mgar/pkg/buildbot/trunk/Makefile
===================================================================
--- csw/mgar/pkg/buildbot/trunk/Makefile	2009-08-19 11:28:47 UTC (rev 6053)
+++ csw/mgar/pkg/buildbot/trunk/Makefile	2009-08-19 11:34:29 UTC (rev 6054)
@@ -11,14 +11,15 @@
 define BLURB
   The BuildBot is a system to automate the compile/test cycle required by most
   software projects to validate code changes. By automatically rebuilding and
-  testing the tree each time something has changed, build problems are pinpointed
-  quickly, before other developers are inconvenienced by the failure. The guilty
-  developer can be identified and harassed without human intervention. By running
-  the builds on a variety of platforms, developers who do not have the facilities
-  to test their changes everywhere before checkin will at least know shortly
-  afterwards whether they have broken the build or not. Warning counts, lint
-  checks, image size, compile time, and other build parameters can be tracked
-  over time, are more visible, and are therefore easier to improve.
+  testing the tree each time something has changed, build problems are
+  pinpointed quickly, before other developers are inconvenienced by the
+  failure. The guilty developer can be identified and harassed without human
+  intervention. By running the builds on a variety of platforms, developers who
+  do not have the facilities to test their changes everywhere before checkin
+  will at least know shortly afterwards whether they have broken the build or
+  not. Warning counts, lint checks, image size, compile time, and other build
+  parameters can be tracked over time, are more visible, and are therefore
+  easier to improve. 
 endef
 
 MASTER_SITES = $(SF_MIRROR)
@@ -26,7 +27,6 @@
 PATCHFILES += debug-$(GARVERSION)$(PATCHLEVEL).patch
 DISTFILES  = $(GARNAME)-$(GARVERSION)$(PATCHLEVEL).tar.gz $(PATCHFILES)
 
-# We define upstream file regex so we can be notifed of new upstream software release
 UFILES_REGEX = $(GARNAME)-(\d+(?:\.\d+)*).tar.gz
 
 SPKG_CLASSES = none cswpycompile


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.



More information about the devel mailing list