-
Notifications
You must be signed in to change notification settings - Fork 95
Register AWS GCE instance to jenkins
Amos Kong edited this page Mar 6, 2018
·
5 revisions
AWS instace:
- upload a pem key as credential, create a jenkins user in instance, and setup ~/.ssh/authorized_keys (add public key of jenkins server)
- Replace Defaults requiretty by Defaults !requiretty in your /etc/sudoers. This will impact your global sudo configuration. Reference: https://www.shell-tips.com/2014/09/08/sudo-sorry-you-must-have-a-tty-to-run-sudo/
- create ~/.aws/config & ~/.aws/credentials chmod 400 ~/.aws/*
GCE instance:
we already has a global key in GCE, just choose in credentials list (jenkins(New RSA key for slave)
).
General setup in instance:
[scylla-cluster-tests]# sudo yum update
[scylla-cluster-tests]# sudo pip install -f requirements.txt
[jenkins@public-jenkins-builder1-qavpc scylla-cluster-tests]$ sudo pip install requests --upgrade --force-reinstall
Branches that we keep sending backports from master
- branch-4.0
- branch-4.1
- branch-2019.1
- branch-perf-v9
- manager-2.1
Branches that we are sending critical backports from master only
- branch-3.3
- branch-2019.1
- manager-2.0
a branch that we still have jobs for, and using, but can't get backports from master anymore
- manager-v1.2
- manager-v1.3
- manager-v1.3.1
- manager-v1.4
Older unused branches will be deleted on a regular basis.