This document is specific to the London RedCentric lab, but should evolve to a more generic setup once we have more labs. For now, there are some hard-coded logic in the wiki as well as the scripts, to make sure we can reproduce at least the one lab we have. Once we have more labs, we'll work to automate that using configuration files, command line options, etc.
...
You may get two warnings when you log in to Jenkins, which can be corrected on the Global Security screen:
- Agent to master security subsystem is currently off: Check the box saying "Enable Agent → Master Access Control"
- Jenkins instance uses deprecated protocols: JNLP3-connect: Uncheck the box "Java Web Start Agent Protocol/3" in "Agent Protocols"
Save the configuration and you should be all set.
Installing the Jenkins Jobs
...
| No Format |
|---|
user: user@linaro.org
password: APITOKEN
url: http://10.40.0.12:8080 |
...
: |
...
| No Format |
|---|
[jenkins] user=user@linaro.org password=APITOKEN url=http://10.40.0.12:8080 |
NOTE: The APITOKEN API TOKEN is the one from the admin user, not regular users.
...
The file server VM setup job handles the user creation + SSH keys copy, but this will move to the hpc_lab_jenkins repo.
Updating Jenkins Jobs
Once the jobs are installed and working, on every change pertaining the Jenkins configuration, you just need to update the repo and run the same playbook again:
| Code Block | ||||
|---|---|---|---|---|
| ||||
root@hpc-admin # cd hpc_lab_jenkins root@hpc-admin # git fetch -a & git pull root@hpc-admin # ansible-playbook -vvv -u root hpc_jobs_deploy.yml |
...