diff options
| author | Holger Levsen <holger@layer-acht.org> | 2015-05-02 12:09:39 +0200 |
|---|---|---|
| committer | Holger Levsen <holger@layer-acht.org> | 2015-05-02 12:09:39 +0200 |
| commit | 60abf477fcecbb47f0d050f4678ee5e6321783a8 (patch) | |
| tree | 6cfce3622471b0410e2546572d45fa4dd64b3026 | |
| parent | 0d6f44a57099597c51a065901e6553b5efdc557c (diff) | |
| download | jenkins.debian.net-60abf477fcecbb47f0d050f4678ee5e6321783a8.tar.xz | |
improve language
| -rw-r--r-- | README | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -156,8 +156,8 @@ Installation tests inside chroot environments. jenkins@jenkins:~$ /srv/jenkins/bin/reproducible_schedule_on_demand.sh $suite $package1 $package2 ---- -If $package1 is "artifacts" then the build job will preserv 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. -The same way, if $package1 is "notify" the build job will notify the team IRC channel, to be aware when a package finish building. +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. * Blacklisting packages can be done similarily: |