This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
services:rook_jenkins [2020/12/09 18:08] akraitman created |
services:rook_jenkins [2021/02/02 11:17] akraitman [Troubleshooting] |
||
---|---|---|---|
Line 16: | Line 16: | ||
The Rook Jenkins is named "Prod-Jenkins" in the AWS console instances tab, The public IP can be seen there | The Rook Jenkins is named "Prod-Jenkins" in the AWS console instances tab, The public IP can be seen there | ||
- | In order to ssh this instance you will need to allow your public IP port 22 in the security group - "rook-jenkins-group" | + | In order to ssh this instance you will need to go the the aws dashboard and |
- | Then you will be able to ssh using the .pem key (Adam and Travis has the .pem key) | + | Allow access to your public IP, port 22 in the security group "rook-jenkins-group", Inbound rules. |
+ | Then you will be able to ssh the Prod-Jenkins using the privet key (Located in the encrypted form in https://github.com/ceph/ceph-sepia-secrets/tree/master/ansible/secrets/rook_key.yml) | ||
If the Container stopped running you can start it | If the Container stopped running you can start it | ||
sudo docker run -d --name jenkins -p 8080:8080 -p 50000:50000 -v /mnt/jenkins/jenkins:/var/jenkins_home jenkins/jenkins:2.235.5 | sudo docker run -d --name jenkins -p 8080:8080 -p 50000:50000 -v /mnt/jenkins/jenkins:/var/jenkins_home jenkins/jenkins:2.235.5 | ||
- | To watch the jenkins logs you can run this | + | To watch the jenkins logs you can run this |
sudo docker logs -f --tail=100 jenkins | sudo docker logs -f --tail=100 jenkins | ||