diff options
| -rwxr-xr-x | bin/reproducible_build_service.sh | 12 |
1 files changed, 5 insertions, 7 deletions
diff --git a/bin/reproducible_build_service.sh b/bin/reproducible_build_service.sh index 51cf88b3..82a96c7d 100755 --- a/bin/reproducible_build_service.sh +++ b/bin/reproducible_build_service.sh @@ -10,13 +10,14 @@ export sleep 3 +sleep 5m +exit 0 + BUILD_ID=$1 BUILD_URL=https://jenkins.debian.net/userContent/build_service/$BUILD_ID case $BUILD_ID in - arm64_builder1) NODE1=codethink-sled12-arm64 - NODE2=codethink-sled15-arm64 - ;; + arm64_builder1) NODE1=codethink-sled12-arm64 NODE2=codethink-sled15-arm64 ;; *) echo "Sleeping 60min" sleep 60m exit 0 @@ -28,10 +29,7 @@ mkdir -p $BS_BASE /srv/jenkins/bin/reproducible_build.sh $NODE1 $NODE2 >$BS_BASE/$BUILD_ID 2>&1 -#script translates "arm64 builder12" to "arm64 builder12 sled3 sled 4" -# < h01ger> | but then its really simple: have a script, jenkins_build_cron_runner.sh or such, and start this with 4 params, eg, arm64, builder_12, codethink_sled11, codethink_sled14. the cron_runner script simple needs to set some variables like jenkins would do, redirect output -# to a directory which is accessable to the webserver and run reproducible_build.sh. voila. # < h01ger> | we could still make the logs accessable to browsers # < h01ger> | and we need maintenance to cleanup the log files eventually # < h01ger> | and translate that yaml to crontab entries - +# a logic for real build_ids to have several logs |