[Qa-jenkins-scm] [Git][qa/jenkins.debian.net][master] reproducible debian: update documentation about manual scheduling builds to...

[Mattia Rizzolo (@mattia)]

Mattia Rizzolo pushed to branch master at Debian QA / jenkins.debian.net


Commits:
7a500fe1 by Mattia Rizzolo at 2021-06-24T17:35:55+02:00
reproducible debian: update documentation about manual scheduling builds to drop some old references to alioth

Closes: #990096
Signed-off-by: Mattia Rizzolo <mattia at debian.org>

- - - - -


1 changed file:

- README


Changes:

=====================================
README
=====================================
@@ -139,6 +139,9 @@ Installation tests inside chroot environments.
 ** old versions, already tested (at least two weeks ago)
 ** and also some old versions which failed to build (at least ten days ago), if no bug has been filed.
 
+* To manually schedule a package build, you need a link:https://sso.debian.org/[Debian SSO] SSL client certificate.  Then you can navigate to each package page (i.e. https://tests.reproducible-builds.org/debian/linux) and click on the recycling icon `♻`.  The called CGI script can do more with special options, but those feature are not currently documented.
+** If you do not have a Debian SSO certificate 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, which are limited to 500 schedulings per day, which should be plenty for normal usage.
+
 * Several other jobs exist to build the HTML pages and to create two JSON files which can be downloaded from https://tests.reproducible-builds.org/reproducible.json and https://tests.reproducible-builds.org/reproducible-tracker.json. The 1st one has all the data (except history) and the 2nd has all the data we consider relevant to bother maintainers with, that is, some ftbfs isses are excluded.
 
 * Information from https://salsa.debian.org/reproducible-builds/reproducible-notes is incorporated on pushes to that git repo.
@@ -151,13 +154,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 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 about the scheduling and optionally when the build finishes too.
-
-* 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, which are limited to 500 schedulings per day, which should be plenty for normal usage.
-
-* Blacklisting packages can be done similarly (as user "jenkins"):
+* Blacklisting packages from building can be done by those with shell access (as user "jenkins"):
 
 ----
 jenkins at jenkins:~$ /srv/jenkins/bin/reproducible_blacklist.sh $arch $suite $package1 $package2 ...



View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/7a500fe1057b68959ffbbadde291d12f495c1383

-- 
View it on GitLab: https://salsa.debian.org/qa/jenkins.debian.net/-/commit/7a500fe1057b68959ffbbadde291d12f495c1383
You're receiving this email because of your account on salsa.debian.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/qa-jenkins-scm/attachments/20210624/a0732169/attachment-0001.htm>