Now fully operational since end August.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Sep 11 2018
Jan 23 2017
- refactoring done.
- filtering partially done: only failure are reported, Jenkins notifies, we consume.
- to automate without human assertion system status isn't currently considered as valuable
Aug 23 2016
Step 4 done for B to D, but currently every failure will be reported. And we don't exploit in the artefact log what's failing.
Aug 15 2016
Aug 10 2016
Jul 31 2016
Successfully built 356c17bb34cf
Jul 29 2016
3A alternative: a cron job running the command for us and generating a report published somewhere Jenkins has access to.
We probably need two containers:
one isolated and standalone for tests
one with more privileged access for delivery
From a security point of view, to give access to a Jenkins slave node to the Docker engine means giving a root access to all the containers to the Trusted users group.
According the history of silly_bardeen, we manually installed to test new CI jobs:
Jul 28 2016
Plugin installed. We're blocked by T953 to fire them to the notifications center.
https://ci.nasqueron.org/job/test-prod-env/rssFailed shows three failure, with success the immediate next build:
Needs Docker too (see T948 roadmap)