[Piuparts-devel] [Git][debian/piuparts][develop] 2 commits: Shuffle some entries on index.html.
Holger Levsen
gitlab at salsa.debian.org
Mon Oct 15 16:58:46 BST 2018
Holger Levsen pushed to branch develop at Debian / piuparts
Commits:
34d335ed by Holger Levsen at 2018-10-15T15:54:53Z
Shuffle some entries on index.html.
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
1ea47ce5 by Holger Levsen at 2018-10-15T15:58:29Z
explain that piuparts.debian.org exists since 2009
Signed-off-by: Holger Levsen <holger at layer-acht.org>
- - - - -
2 changed files:
- debian/changelog
- htdocs/index.tpl
Changes:
=====================================
debian/changelog
=====================================
@@ -31,6 +31,8 @@ piuparts (0.93) UNRELEASED; urgency=medium
* piuparts-report.py:
- Add new page: overview.html
- Split index.html into about (index.html) and news.html.
+ - Shuffle some entries on index.html, explain that piuparts.debian.org
+ exists since 2009.
- Minor cleanups.
* Use the new debhelper-compat(=11) notation and drop d/compat.
=====================================
htdocs/index.tpl
=====================================
@@ -25,22 +25,6 @@
A quick introduction is available in the <a href="/doc/README.html" target="_blank">piuparts README</a>, and all the options are listed on the <a href="/doc/piuparts.1.html" target="_blank">piuparts manpage</a>.
</td>
</tr>
- <tr class="normalrow">
- <td class="contentcell2">
- To make sure piuparts is run on all packages in Debian, piuparts.debian.org has been set up to run piuparts in <a href="/doc/README_server.html" target="_blank">master/slave mode</a>. This setup currently consists of three hosts: <a href="https://db.debian.org/machines.cgi?host=pejacevic" target="_blank">pejacevic.debian.org</a> and <a href="https://db.debian.org/machines.cgi?host=piu-slave-bm-a" target="_blank">piu-slave-bm-a.debian.org</a> and <a href="https://db.debian.org/machines.cgi?host=piu-slave-ubc-01" target="_blank">piu-slave-ubc-01.debian.org</a>:
- <ul>
- <li> pejacevic acts as the piuparts-master, which is responsible for scheduling test jobs to the slaves. The other main task is to generate the reports which are served via https://piuparts.debian.org.</li>
- <li> piu-slave-bm-a runs four piuparts-slave instances, which then run piuparts itself.</li>
- <li> piu-slave-ubc-01 also runs four piuparts-slave instances.</li>
- </ul>
- The first two of these hosts run as virtualized hardware on <a href="http://bits.debian.org/2013/04/bytemark-donation.html" target="_blank">a nice cluster</a> hosted at <a href="http://www.bytemark.co.uk" target="_blank">Bytemark</a> and the last one runs virtualised at the University of British Columbia.
- </td>
- </tr>
- <tr class="normalrow">
- <td class="contentcell2">
- To learn more about this setup, follow the <em>"Documentation"</em> links in the navigation menu on the left. Read those READMEs. The piuparts configuration for all the different suite(-combination)s that are currently being tested is also linked there.
- </td>
- </tr>
<tr class="normalrow">
<td class="contentcell2">
Besides all the information provided here, there is some more information available on wiki.debian.org:
@@ -57,6 +41,22 @@
You can talk to us on #debian-qa on irc.debian.org (OFTC) or send an email on the <a href="https://lists.alioth.debian.org/mailman/listinfo/piuparts-devel" target="_blank">piuparts development mailinglist</a>. The best ways to <a href="https://salsa.debian.org/debian/piuparts/blob/develop/CONTRIBUTING">contribute</a> are to provide patches via GIT pull requests and/or to file bugs based on piuparts runs.
</td>
</tr>
+ <tr class="normalrow">
+ <td class="contentcell2">
+ To make sure piuparts is run on all packages in Debian, since 2009 there is piuparts.debian.org which has been set up to run piuparts in <a href="/doc/README_server.html" target="_blank">master/slave mode</a>. This setup currently consists of three hosts: <a href="https://db.debian.org/machines.cgi?host=pejacevic" target="_blank">pejacevic.debian.org</a> and <a href="https://db.debian.org/machines.cgi?host=piu-slave-bm-a" target="_blank">piu-slave-bm-a.debian.org</a> and <a href="https://db.debian.org/machines.cgi?host=piu-slave-ubc-01" target="_blank">piu-slave-ubc-01.debian.org</a>:
+ <ul>
+ <li> pejacevic acts as the piuparts-master, which is responsible for scheduling test jobs to the slaves. The other main task is to generate the reports which are served via https://piuparts.debian.org.</li>
+ <li> piu-slave-bm-a runs four piuparts-slave instances, which then run piuparts itself.</li>
+ <li> piu-slave-ubc-01 also runs four piuparts-slave instances.</li>
+ </ul>
+ The first two of these hosts run as virtualized hardware on <a href="http://bits.debian.org/2013/04/bytemark-donation.html" target="_blank">a nice cluster</a> hosted at <a href="http://www.bytemark.co.uk" target="_blank">Bytemark</a> and the last one runs virtualised at the University of British Columbia.
+ </td>
+ </tr>
+ <tr class="normalrow">
+ <td class="contentcell2">
+ To learn more about this setup, follow the <em>"Documentation"</em> links in the navigation menu on the left. Read those READMEs. The piuparts configuration for all the different suite(-combination)s that are currently being tested is also linked there.
+ </td>
+ </tr>
<tr class="normalrow">
<td class="contentcell2">
These pages are updated twice a day.
View it on GitLab: https://salsa.debian.org/debian/piuparts/compare/0ff3fc19ad09e2cc26b7dc8b516924672fad4838...1ea47ce5a603f6137c6de89ea57aa93e7dbb498d
--
View it on GitLab: https://salsa.debian.org/debian/piuparts/compare/0ff3fc19ad09e2cc26b7dc8b516924672fad4838...1ea47ce5a603f6137c6de89ea57aa93e7dbb498d
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/piuparts-devel/attachments/20181015/eb895839/attachment-0001.html>
More information about the Piuparts-devel
mailing list