Closed Bug 691952 Opened 13 years ago Closed 13 years ago

jenkins.mozilla.org, migration

Categories

(Infrastructure & Operations Graveyard :: WebOps: Labs, task, P1)

x86
macOS

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: onecyrenus, Unassigned)

Details

Looking to migrate a jenkins job i have running on a qa server  http://10.8.73.228:8080/job/webapps/lastBuild/

Basic instructions on what needs to be installed on the machine is below. 

https://github.com/mozilla/openwebapps/blob/develop/site/tests/scripts/jenkins_install.txt

Basically nodejs, npm a few other requirements, please use the version i have written in the file, and not what is in apt-get.
(In reply to dclarke@mozilla.com from comment #0)
> Looking to migrate a jenkins job i have running on a qa server 
> http://10.8.73.228:8080/job/webapps/lastBuild/

So you are looking for a dedicated jenkins server for openwebapps ? Or are you looking for
a dedicated slave that can be hooked up to jenkins.mozilla.org ?

> Basic instructions on what needs to be installed on the machine is below. 
> 
> https://github.com/mozilla/openwebapps/blob/develop/site/tests/scripts/
> jenkins_install.txt
> 
> Basically nodejs, npm a few other requirements, please use the version i
> have written in the file, and not what is in apt-get.

Does this need to be publicly accessible at all, or is behind the VPN good enough ?
Status: NEW → ASSIGNED
Philippe, 
    I am looking to run my tests on jenkins.mozilla.org, if that means it runs on a dedicated slave, or locally that is up to you. It does need to be publicly accessible. 

Thanks
I should modify that last statement to say the results should be publicly accessible.
openwebapps-test1.vm1.labs.sjc1.mozilla.com is up and running, and I installed the requirements you highlighted.

You can login to that VM via the VPN. Your LDAP credentials should let you in via ssh, and you have sudo access to that box.

Not sure what/who is involved in getting this hooked into jenkins, however.

But for now, I'd make sure your test job can successfully run on that VM, that there are no missing dependencies, etc.
Assignee: server-ops-labs → dclarke
So i don't think this is good enough.  The reason i got the other staging server
openwebapps-jenkins.qa.phx1.mozilla.com 


i can take a permanent machine, openwebapps.vm1.labs.. but don't want to go through the hassle of setting up a second instance just to tear it down in the future.
slightly disjointed statement, the reason i got the previous staging server was to iron out the kinks.  

Requirements are changing, so setting up a slave which connects in is the right way to go.  But I don't want to do that just to have it get torn down, and a new configuration needed.
(In reply to dclarke@mozilla.com from comment #6)
> slightly disjointed statement, the reason i got the previous staging server
> was to iron out the kinks.  
> 
> Requirements are changing, so setting up a slave which connects in is the
> right way to go.  But I don't want to do that just to have it get torn down,
> and a new configuration needed.

Not sure what you mean here. Looks like openwebapps-jenkins.qa.phx1.mozilla.com is down at the moment, and I don't know if there is a bug open for tracking that.

Not sure if you need a VM in the labs cluster then, but if you do want it, it's not temporary, and wouldn't be torn down.

Just let me know what you want to do.
ok i'm using it, what is the backup procedure for this machine btw. ? 

Can i have regular snapshots made ?
btw it looks like the virtual machine is not able to connect to the outside world ? 

is this to be expected.. you can login via ldap.. try ping www.yahoo.com or something.. not dns related, possibly routes ? 

netstat -arn reveals routing is fairly ugly .. any thoughts ?
ignore last comment about netstat -arn.. i can reach gateway.. just installed traceroute
Priority: -- → P1
traceroute was a no go btw..  Networking connectivity to the internet is down.. unsure why.. no one has told me anything ?
Zandr's time shifted.  Pushing queues around in case someone in server-ops can handle this before he gets online.
Assignee: dclarke → server-ops
Component: Server Operations: Labs → Server Operations
QA Contact: zandr → cshields
Assignee: server-ops → gozer
Should work now, firewall needed some kicking.
Assignee: gozer → server-ops-labs
Component: Server Operations → Server Operations: Labs
QA Contact: cshields → zandr
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.