[Qa-jenkins-scm] [jenkins.debian.net] 01/01: reproducble: introduce options: --notify and --artifacts

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 62f0ee6956fd0fc459355822d188b7da30460fd8
Author: Holger Levsen <holger at layer-acht.org>
Date:   Wed May 27 22:19:31 2015 +0200

    reproducble: introduce options: --notify and --artifacts
---
 README                                 |  6 +++---
 bin/reproducible_schedule_on_demand.sh | 28 +++++++++-------------------
 2 files changed, 12 insertions(+), 22 deletions(-)

diff --git a/README b/README
index d1d0b68..e94cc7a 100644
--- a/README
+++ b/README
@@ -161,11 +161,11 @@ Installation tests inside chroot environments.
 * If you are not in the reproducible team or if you want to reschedule big sets of packages please ask for a manual rescheduling in the '#debian-reproducible' IRC channel on OFTC. Those with shell access to jenkins need to run this command:
 
 ----
-jenkins at jenkins:~$ /srv/jenkins/bin/reproducible_schedule_on_demand.sh $suite $package1 $package2
+jenkins at jenkins:~$ /srv/jenkins/bin/reproducible_schedule_on_demand.sh --$option $suite $package1 $package2
 ----
 
-If $package1 is "artifacts" then the build job will preserve the produced packages and publish them under reproducible.debian.net, to allow easy+deeper investigation of reproducible issues. The URL is published in the build log and on IRC.
-The same way, if $package1 is "notify" the build job will notify the team IRC channel when a package finishes building.
+The script can be called with either one of the two options: with "--artifacts" the build job will preserve the produced packages and publish them under reproducible.debian.net, to allow easy+deeper investigation of reproducible issues. The URL is published in the build log and on IRC.
+Alternativly it's possible to use "--notify" to make the build job notify the team IRC channel when a package finishes building.
 
 * Blacklisting packages can be done similarily:
 
diff --git a/bin/reproducible_schedule_on_demand.sh b/bin/reproducible_schedule_on_demand.sh
index 6e2aca8..d9f5062 100755
--- a/bin/reproducible_schedule_on_demand.sh
+++ b/bin/reproducible_schedule_on_demand.sh
@@ -15,6 +15,15 @@ common_init "$@"
 # main
 #
 set +x
+ARTIFACTS=0
+NOTIFY=''
+if [ "$1" = "--notify" ] ; then
+	NOTIFY=true
+	shift
+elif [ "$1" = "--artifacts" ] ; then
+	ARTIFACTS=1
+	NOTIFY=true
+fi
 SUITE="$1"
 shift
 if [ "$SUITE" = "sid" ] ; then
@@ -22,25 +31,6 @@ if [ "$SUITE" = "sid" ] ; then
 	SUITE=unstable
 fi
 
-case "$1" in
-	"artifacts")
-		ARTIFACTS=1
-		NOTIFY=true
-		shift
-		printf "\nThe artifacts of the build(s) will be saved to the location mentioned at the end of the build log(s).\n\n"
-		;;
-	"notify")
-		ARTIFACTS=0
-		NOTIFY=true
-		shift
-		printf "\nThe IRC channel will be notified once the build(s) finished.\n\n"
-		;;
-	*)
-		ARTIFACTS=0
-		NOTIFY=''
-		;;
-esac
-
 CANDIDATES="$@"
 if [ ${#} -gt 50 ] && [ "$NOTIFY" = "true" ] ; then
 	echo

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git