summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorjosch <j.schauer@email.de>2015-06-17 18:59:41 +0200
committerHolger Levsen <holger@layer-acht.org>2015-06-17 19:02:01 +0200
commit1e44dc0cc5eca0c42701719ff9ca53ec2f2527da (patch)
treec7bbc9c7a8f368b10c9b608b9b97f9090c64f9e1
parent36295d2ee4a0d78834bf0d60bd2dd1c2fe92afdd (diff)
downloadjenkins.debian.net-1e44dc0cc5eca0c42701719ff9ca53ec2f2527da.tar.xz
README: clarify to log into alioth via ssh
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 7b111727..ec72e86a 100644
--- a/README
+++ b/README
@@ -161,7 +161,7 @@ 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.
* 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.
+** log into alioth.debian.org via ssh, 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 can bypass the limitations imposed to remote calls (and e.g. schedule a lot of packages (remotes are limited at 50 per day) without notifications at the end).