Bug #685

Move jenkins instance to one of the internal nyc tech ops servers

Added by Sam Boyer about 1 year ago. Updated 12 months ago.

Status:In Progress Start date:05/13/2012
Priority:Normal Due date:
Assignee:Sam Kottler % Done:

50%
Category:-
Target version:devops phase 1

Description

we need to get jenkins off of kottler's little linode and into something that's part of the core occupy.net infra. web-etc makes sense to me.

History

#1
Updated by Sam Kottler about 1 year ago

  • Assignee set to Sam Kottler

#2
Updated by Sam Kottler about 1 year ago

Host fga-jenkins
HostName 166.84.136.91
User [your user]
LocalForward localhost:8080 166.84.136.91:8080
StrictHostKeyChecking no
ServerAliveInterval 2
LogLevel QUIET
ExitOnForwardFailure yes
IdentityFile ~/.ssh/id_rsa

#3
Updated by Sam Kottler about 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

The server is running on web-etc. I am going to do some work around security on that machine since it's completely open right now and that poses some amount of risk. Jenkins itself will be available solely via SSH tunnel. You can add the snippet above to ~/.ssh/config and then access Jenkins by running `ssh fga-jenkins` and then `open http://localhost:8080`.

#4
Updated by Sam Boyer 12 months ago

Seems that Jenkins instance is a bit unstable - i just had to restart it. not quite sure why, from a brief perusal of the logs.

what'd we do for managing accounts, again?

Also available in: Atom PDF