Operations grimoire/Jenkins: Difference between revisions
From Nasqueron Agora
No edit summary |
|||
| Line 1: | Line 1: | ||
Jenkins is used to automate tests and deployment tasks. | Jenkins is used to automate tests and deployment tasks. | ||
It's reachable at https://ci.nasqueron.org/ | |||
== Restart Jenkins == | == Restart Jenkins == | ||
Revision as of 20:22, 21 July 2016
Jenkins is used to automate tests and deployment tasks.
It's reachable at https://ci.nasqueron.org/
Restart Jenkins
- Restart or provision a new Jenkins container:
docker restart ciorrun-ci - 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)
Jenkins interactions
The following connections are known:
- Jenkins communicates with GitHub directly through tokens and Alken-Orin SSH key
- The
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.
