Jenkins is used to automate tests and deployment tasks.
It's reachable at https://ci.nasqueron.org/
- Restart or provision a new Jenkins container:
docker restart cior
- Go to https://ci.nasqueron.org to have an idea of the slave nodes, restart them
We should at least have one slave container with
docker run -dt -P -v /data/jenkins/slave_home:/home/app nasqueron/jenkins-slave-php (from the script run-ci-slave)
The following connections are known:
- Jenkins communicates with GitHub directly through tokens and Alken-Orin SSH key
tommycontainer provides a dashboard at https://builds.nasqueron.org/
Broker and notifications center aren't currently (2016-07-21) needed by Jenkins: they currently link Docker Hub, GitHub, Phabricator, Wearg and the notification CLI client. DevCentral has the responsibility to trigger Jenkins builds when a new diff occurs while GitHub and Jenkins communicate directly without using the notifications center.
If a node is offline, but the container has been launched, go check the IP of the slave container and update on Jenkins the configuration of the node with the current IP.
When the Docker engine is restarted, /etc/hosts is fairly often lost in some containers, and so they lost container name resolution.