| non port: Tools/portbuild/scripts/buildsuccess |
|
CVSWeb
|
Number of commits found: 13 |
|
Sun, 24 Apr 2011
|
[ 16:37 flz ] 
1.2 Tools/portbuild/conf/.cvsignore
1.2 Tools/portbuild/conf/README.dotunnel
1.7 Tools/portbuild/scripts/allgohans
1.5 Tools/portbuild/scripts/allgohans.safe
1.5 Tools/portbuild/scripts/bothlogs
1.16 Tools/portbuild/scripts/build
1.37 Tools/portbuild/scripts/buildenv
1.12 Tools/portbuild/scripts/buildfailure
1.5 Tools/portbuild/scripts/buildproxy
1.4 Tools/portbuild/scripts/buildproxy-client
(Only the first 10 of 72 ports in this commit are shown above.  )
Remove portbuild scripts from pcvs, as they now live in svn/projects.
|
|
Wed, 1 Dec 2010
|
[ 02:27 linimon ]
1.11 Tools/portbuild/scripts/buildfailure
1.12 Tools/portbuild/scripts/buildsuccess
1.14 Tools/portbuild/scripts/claim-chroot
1.18 Tools/portbuild/scripts/clean-chroot
1.27 Tools/portbuild/scripts/makeduds
1.32 Tools/portbuild/scripts/makeindex
1.12 Tools/portbuild/scripts/makerestr
1.35 Tools/portbuild/scripts/pdispatch
1.8 Tools/portbuild/scripts/prunefailure
Although I was going to try to avoid it, it turns out that it is
impossble to have merely "server.conf" and "client.conf" control
everything on a head node. Some pieces must be refactored into
"common.conf".
|
|
Fri, 25 Jun 2010
|
[ 22:49 linimon ]
1.10 Tools/portbuild/scripts/buildfailure
1.11 Tools/portbuild/scripts/buildsuccess
1.13 Tools/portbuild/scripts/claim-chroot
1.11 Tools/portbuild/scripts/cleanup-chroots
1.2 Tools/portbuild/scripts/client-metrics
1.4 Tools/portbuild/scripts/flushsquid
1.3 Tools/portbuild/scripts/keeprestr
1.25 Tools/portbuild/scripts/makeduds
1.22 Tools/portbuild/scripts/mkbindist
1.7 Tools/portbuild/scripts/prunefailure
(Only the first 10 of 11 ports in this commit are shown above. )
Generalize the packge building scripts to be able to be run on more than
one 'head' node, rather than just pointyhat itself.
Constants are factored out into installation-specific files known as
portbuild/conf/server.conf and portbuild/conf/client.conf. There is
only one server.conf file. Individual <arch> directories may have
their own client.conf files, or may symlink to ../conf/client.conf.
This first set of files only gets the *.conf files and some cleanup.
Feature safe: yes
|
|
Mon, 31 May 2010
|
[ 20:06 linimon ]
1.31 Tools/portbuild/scripts/buildenv
1.9 Tools/portbuild/scripts/buildfailure
1.10 Tools/portbuild/scripts/buildsuccess
1.24 Tools/portbuild/scripts/makeduds
1.29 Tools/portbuild/scripts/makeindex
1.8 Tools/portbuild/scripts/makerestr
Sigh. This had already been done, just not checked out on production.
Pointy hat: self
|
[ 20:01 linimon ]
1.30 Tools/portbuild/scripts/buildenv
1.8 Tools/portbuild/scripts/buildfailure
1.9 Tools/portbuild/scripts/buildsuccess
1.23 Tools/portbuild/scripts/makeduds
1.28 Tools/portbuild/scripts/makeindex
1.7 Tools/portbuild/scripts/makerestr
Get rid of the remnants of X11BASE.
|
|
Fri, 18 Dec 2009
|
[ 14:25 pav ]
1.29 Tools/portbuild/scripts/buildenv
1.7 Tools/portbuild/scripts/buildfailure
1.35 Tools/portbuild/scripts/buildscript
1.8 Tools/portbuild/scripts/buildsuccess
1.22 Tools/portbuild/scripts/makeduds
1.27 Tools/portbuild/scripts/makeindex
1.6 Tools/portbuild/scripts/makerestr
1.60 Tools/portbuild/scripts/portbuild
- Remove use of X11BASE from pointyhat scripts
|
|
Sat, 26 Jul 2008
|
[ 14:07 kris ]
1.7 Tools/portbuild/scripts/buildsuccess
* Cleanup
* Catch up to build ID directory changes
|
|
Sat, 11 Feb 2006
|
[ 09:48 kris ]
1.6 Tools/portbuild/scripts/buildsuccess
Use ${mailto} portbuild.conf variable instead of hard-coded list
Requested by: lofi
Submitted by: linimon
No more accidental portbuild spam: kris and krion
|
|
Thu, 6 Jan 2005
|
[ 23:05 kris ]
1.5 Tools/portbuild/scripts/buildsuccess
krion wants to drink from the pointyhat email firehose as well.
XXX This should be a portbuild.conf tunable
Approved by: portmgr (self)
|
|
Mon, 25 Oct 2004
|
[ 04:28 kris ]
1.4 Tools/portbuild/scripts/buildsuccess
Clean up the 'latest error log' symlink when the build is successful.
|
|
Wed, 14 Jul 2004
|
[ 09:06 kris ]
1.3 Tools/portbuild/scripts/buildsuccess
Send me mail when a previously-broken port builds successfully.
XXX Should not be a hard-coded address
|
|
Mon, 13 Oct 2003
|
[ 02:59 kris ]
1.2 Tools/portbuild/scripts/buildsuccess
The newfailure file is no longer updated by builds
|
|
Fri, 24 Jan 2003
|
[ 05:01 kris ]
1.1 Tools/portbuild/scripts/buildfailure
1.1 Tools/portbuild/scripts/buildsuccess
These scripts are run when a build completes (successfully or not). They
keep track of the number of times a port has failed to build, resetting
the counter when it builds successfully. There are still some bugs to be
worked out, but this will be used as the basis for maintainer notification
of port failures.
|
Number of commits found: 13 |
