kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/Tools/portbuild/scripts/dopackages2

72 lines
2.1 KiB
Text
Raw Normal View History

Driver script for whole build process. It will (1) cvsup (2) run cvs update on the ports and doc trees (3) generate new index (4) generate new duds list (5) move old packages and distfiles out of the way (6) build packages (7) build packages again (to salvage those died with transient errors) (8) generate restricted list (9) generate no-cdrom list Steps (3)-(9) are repeated for 4-current and 3-stable.
1999-06-22 12:43:10 +02:00
#!/bin/sh
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
# configurable variables
Read in configuration variables from /var/portbuild/portbuild.conf.
2000-09-27 03:43:32 +02:00
pb=/var/portbuild
. ${pb}/portbuild.conf
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
lock=${pb}/lock
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
status=${pb}/status
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
date=$(date '+%Y%m%d%H')
shortdate=$(date '+%Y%m%d')
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
if [ -e ${lock} ]; then
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
# echo "Skipped package build since lock file exists" | sendmail $mailto
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
exit 1
fi
touch ${lock}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
rm -f ${status}
Put build logs in "archive/buildlogs" and make a symlink to it.
1999-09-22 02:59:47 +02:00
mkdir -p ${pb}/archive/buildlogs
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
if [ -f ${pb}/scripts/dopackages.new ]; then
mv -f ${pb}/scripts/dopackages.new ${pb}/scripts/dopackages
fi
Put build logs in "archive/buildlogs" and make a symlink to it.
1999-09-22 02:59:47 +02:00
ln -sf ${pb}/archive/buildlogs/log.4.${date} ${pb}/4/build.log
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
ln -sf log.4.${date} ${pb}/archive/buildlogs/log.4.${shortdate}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
${pb}/scripts/dopackages $@ 4 ${date} 2>&1 \
Put build logs in "archive/buildlogs" and make a symlink to it.
1999-09-22 02:59:47 +02:00
| tee ${pb}/archive/buildlogs/log.4.${date} \
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
| sendmail $mailto
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
if [ -f ${status} ]; then
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
rm -f ${lock}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
exit "$(cat ${status})"
fi
if [ -f ${pb}/scripts/dopackages.new ]; then
mv -f ${pb}/scripts/dopackages.new ${pb}/scripts/dopackages
fi
ln -sf ${pb}/archive/buildlogs/log.5.${date} ${pb}/5/build.log
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
ln -sf log.5.${date} ${pb}/archive/buildlogs/log.5.${shortdate}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
${pb}/scripts/dopackages -nocvsup $@ 5 ${date} 2>&1 \
| tee ${pb}/archive/buildlogs/log.5.${date} \
| sendmail $mailto
if [ -f ${status} ]; then
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
rm -f ${lock}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
exit "$(cat ${status})"
fi
if [ -f ${pb}/scripts/dopackages.new ]; then
mv -f ${pb}/scripts/dopackages.new ${pb}/scripts/dopackages
fi
Put build logs in "archive/buildlogs" and make a symlink to it.
1999-09-22 02:59:47 +02:00
ln -sf ${pb}/archive/buildlogs/log.3.${date} ${pb}/3/build.log
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
ln -sf log.3.${date} ${pb}/archive/buildlogs/log.3.${shortdate}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
${pb}/scripts/dopackages -nocvsup $@ 3 ${date} 2>&1 \
Put build logs in "archive/buildlogs" and make a symlink to it.
1999-09-22 02:59:47 +02:00
| tee ${pb}/archive/buildlogs/log.3.${date} \
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
| sendmail $mailto
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
if [ -f ${status} ]; then
Use YYYYMMDDHH for log files so we can have two builds on the same day. Remove lock file if package build aborts.
2000-11-08 00:40:07 +01:00
rm -f ${lock}
Run build on three branches. Check the status file filled out by dopackages and abort build if there were any errors. It intentionally leaves lock files behind in that case because it usually requires my manual intervention to fix whatever's wrong (usually a botched INDEX build due to someone forgetting to update dependency lines) and we don't want subsequent failed tries to wipe out all the good packages and distfiles we have accumulated.
2000-08-29 10:21:47 +02:00
exit "$(cat ${status})"
fi
cd ${pb}/archive/errorlogs/e.3.${date} && ${pb}/scripts/processlogs
cd ${pb}/archive/errorlogs/e.4.${date} && ${pb}/scripts/processlogs
cd ${pb}/archive/errorlogs/e.5.${date} && ${pb}/scripts/processlogs
cd ${pb}/archive/errorlogs
${pb}/scripts/comparelogs e.3.${date} e.4.${date}
${pb}/scripts/comparelogs e.4.${date} e.3.${date}
${pb}/scripts/comparelogs e.5.${date} e.4.${date}
${pb}/scripts/comparelogs e.4.${date} e.5.${date}
${pb}/scripts/bothlogs e.3.${date} e.4.${date} e.5.${date}
Create lock file so you won't have two of these running. Also, separate the report mailing address into the configurable variables section.
1999-07-30 09:19:44 +02:00
rm -f ${lock}
Reference in a new issue Copy permalink