summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMattia Rizzolo <mattia@mapreri.org>2015-05-04 18:14:46 +0200
committerHolger Levsen <holger@layer-acht.org>2015-05-04 18:31:41 +0200
commit7a381a6fe6f017260bc3c1fb6487d2b4047dd1ec (patch)
treeb6f5e018184cba4f79cdae2863248474c1986263
parent12c04491ccb8ea8570a39595f6b06f5a61e3c97d (diff)
downloadjenkins.debian.net-7a381a6fe6f017260bc3c1fb6487d2b4047dd1ec.tar.xz
add the alioth.d.o rescheduling script for the reproducible team and document it in the README
-rw-r--r--README6
-rwxr-xr-xalioth-scripts/reproducible-reschedule.sh9
2 files changed, 14 insertions, 1 deletions
diff --git a/README b/README
index 8f24f631..a9296ad9 100644
--- a/README
+++ b/README
@@ -154,7 +154,11 @@ Installation tests inside chroot environments.
* The jenkins job overview at https://jenkins.debian.net/view/reproducible/ probably makes it clearer how the job scheduling works in practice.
-* Plase ask for manual rescheduling of packages in the '#debian-reproducible' IRC channel on OFTC. Those with shell access to jenkins need to run this command:
+* If you are in the reproducible team you can reschedule packages by yourself:
+** log into alioth.debian.org, in the team home (/home/groups/reproducible/) there is a reschedule.sh script you can call. Use the --help switch to get the online help.
+** The team IRC channel will get a notification both when the scheduling is done and once the build finishes.
+
+* 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@jenkins:~$ /srv/jenkins/bin/reproducible_schedule_on_demand.sh $suite $package1 $package2
diff --git a/alioth-scripts/reproducible-reschedule.sh b/alioth-scripts/reproducible-reschedule.sh
new file mode 100755
index 00000000..ee6b9c1f
--- /dev/null
+++ b/alioth-scripts/reproducible-reschedule.sh
@@ -0,0 +1,9 @@
+#!/bin/bash
+
+SSH_KEY="/home/groups/reproducible/private/jenkins-key"
+SSH_KNOWN_HOSTS="/home/groups/reproducible/private/ssh_known_hosts"
+
+# "dummy" is discarded by the server ssh (jenkins.debian.net in this case) and
+# it's there because otherwise the client ssh (this) tries to parse the options
+# for the remote command
+LC_USER="$USER" ssh -i "$SSH_KEY" -o GlobalKnownHostsFile="$SSH_KNOWN_HOSTS" jenkins@jenkins.debian.net dummy "$@"