- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Aug 1 2016
Jul 31 2016
Successfully built 356c17bb34cf
We had acme 0.8.1, letsencrypt client wanted 0.5.0
Jul 30 2016
Moved to new repository.
Move to rTESTSPRODENV.
non → not
Jul 29 2016
3A alternative: a cron job running the command for us and generating a report published somewhere Jenkins has access to.
. └── public_html ├── noautoindex ├── status.html ├── test.cgi └── test.php
We probably need two containers:
one isolated and standalone for tests
one with more privileged access for delivery
Misspelling for putloglev actually.
Tweak open proxy checker to parse hosts with IP in cloaks
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:
Build is green https://ci.nasqueron.org/job/test-notifications-phab/142/ for more details.
Jul 28 2016
@Sandlayth happy with the plan?
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:
We could replace that by putdebug provided by our core for the same purpose.