Commit b0e671f2 authored by Tails developers's avatar Tails developers
Browse files

Update roadmap.

parent 1edb6a92
......@@ -33,19 +33,14 @@ What we have
Roadmap
=======
0. Setup the SCM Sync plugin.
0. Configure a Git username and email for Jenkins.
0. Setup a few basic Jenkins jobs, e.g. simply run cucumber in Tails
source tree after every commit in `stable`, `testing`, `devel`,
`experimental`, and unmerged `feature/*` and `bugfix/*`.
[[!tag todo/sysadmin]]
0. Tell Jenkins that its public URL is https://...
0. Fix redirects to plain http://.
0. Setup a Jenkins slave on builder.lizard.
0. Setup email notifications.
0. Add more Jenkins jobs such as:
- run our various [[custom programs|contribute/git]]' test suite
(see the section about Perl projects on [[automated builds and tests]])
and build Debian packages for them
- check PO files [[validity with
i18nspector|contribute/l10n_tricks]]
- automated ISO builds
......@@ -53,12 +48,17 @@ Roadmap
[[!taglink todo/research]] if that's possible without using the
Jenkins slave/master feature.
- automated test suite
0. run our various [[custom programs|contribute/git]]' test suite
(see the section about Perl projects on [[automated builds and tests]])
and build Debian packages for them:
a. set up a `perl-tester.lizard` Jenkins slave
0. Run `jenkins-jobs update /etc/jenkins_jobs/jobs/` when the Jenkins
jobs repository gets an update.
0. Setup IRC notifications (see [[resources|automated builds and tests/jenkins]]).
0. Think through a plugins upgrade policy and possibly create the
needed tools.
0. Make our Jenkins visible and read-only on the web.
0. Start/stop `builder.lizard` before/after building an ISO.
What we need
============
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment