Hi.
I'd like to see Jenkins moved away from control. It causes random CPU spikes and as we already know control is a busy place. Could we spawn a VM (if that's stable enough already) solely for running it and remove the parts that currently run on control?
ZK
Hi Zygmunt,
Cloud isn't ready yet. Had a major step back and not sure why. Working with openstack people to resolve.
Thanks
Dave
On 9 Feb 2012, at 06:48, Zygmunt Krynicki wrote:
Hi.
I'd like to see Jenkins moved away from control. It causes random CPU spikes and as we already know control is a busy place. Could we spawn a VM (if that's stable enough already) solely for running it and remove the parts that currently run on control?
ZK
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
On Thu, Feb 9, 2012 at 7:19 PM, Dave Pigott dave.pigott@linaro.org wrote:
Hi Zygmunt,
Cloud isn't ready yet. Had a major step back and not sure why. Working with openstack people to resolve.
Thanks
Thank's for the update. I hope it goes well
ZK
Dave
On 9 Feb 2012, at 06:48, Zygmunt Krynicki wrote:
Hi.
I'd like to see Jenkins moved away from control. It causes random CPU spikes and as we already know control is a busy place. Could we spawn a VM (if that's stable enough already) solely for running it and remove the parts that currently run on control?
ZK
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Is there any reason why we shouldn't target running the few things done in jenkins on v.l.o on ci.linaro.org instead? ci.linaro.org didn't exist when we first started this, but it would make sense to consolidate our jenkins instances. At the beginning, we were using jenkins for scheduling jobs, but we don't use that any longer. Implementing the qemu testing on top of that was just for convenience because we didn't have another jenkins at the time.
Thanks, Paul Larson
I now have what looks like a stable cloud up and running. Last problem is that I have an instance running, but can't seem to attach to it. I've got a question into #openstack, so hopefully we'll be running on full steam soon.
Thanks
Dave
On 9 Feb 2012, at 12:08, Paul Larson wrote:
Is there any reason why we shouldn't target running the few things done in jenkins on v.l.o on ci.linaro.org instead? ci.linaro.org didn't exist when we first started this, but it would make sense to consolidate our jenkins instances. At the beginning, we were using jenkins for scheduling jobs, but we don't use that any longer. Implementing the qemu testing on top of that was just for convenience because we didn't have another jenkins at the time.
Thanks, Paul Larson
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
On Thu, Feb 9, 2012 at 12:08 PM, Paul Larson paul.larson@linaro.org wrote:
Is there any reason why we shouldn't target running the few things done in jenkins on v.l.o on ci.linaro.org instead? ci.linaro.org didn't exist when we first started this, but it would make sense to consolidate our jenkins instances. At the beginning, we were using jenkins for scheduling jobs, but we don't use that any longer. Implementing the qemu testing on top of that was just for convenience because we didn't have another jenkins at the time.
Thanks, Paul Larson
Actually, let me amend this slightly - Peter! It seems the qemu job hasn't run in over 2 months. Is this even interesting to run any more? Is the tree inactive?
On Fri, Feb 10, 2012 at 10:42 PM, Paul Larson paul.larson@linaro.orgwrote:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
On Thu, Feb 9, 2012 at 12:08 PM, Paul Larson paul.larson@linaro.orgwrote:
Is there any reason why we shouldn't target running the few things done in jenkins on v.l.o on ci.linaro.org instead? ci.linaro.org didn't exist when we first started this, but it would make sense to consolidate our jenkins instances. At the beginning, we were using jenkins for scheduling jobs, but we don't use that any longer. Implementing the qemu testing on top of that was just for convenience because we didn't have another jenkins at the time.
Thanks, Paul Larson
On 11 February 2012 06:44, Paul Larson paul.larson@linaro.org wrote:
Actually, let me amend this slightly - Peter! It seems the qemu job hasn't run in over 2 months. Is this even interesting to run any more? Is the tree inactive?
The tree is active but I think the job is busted (not monitoring the right branch? I think we did a config tweak which maybe wasn't the right thing...)
I'd like to increase the amount of CI we do on qemu-linaro, not decrease it, but I'm not wedded to using jenkins for it...
-- PMM
On 11 February 2012 17:39, Peter Maydell peter.maydell@linaro.org wrote:
On 11 February 2012 06:44, Paul Larson paul.larson@linaro.org wrote:
Actually, let me amend this slightly - Peter! It seems the qemu job hasn't run in over 2 months. Is this even interesting to run any more? Is the tree inactive?
The tree is active but I think the job is busted (not monitoring the right branch? I think we did a config tweak which maybe wasn't the right thing...)
I had a look to see if I could find out what was going wrong here, but as far as I can see I don't have enough permissions on this jenkins instance to even look at the config for this job, so I don't have any way to investigate the problem. Can somebody else look at it? It should be monitoring the 'master' branch of git://git.linaro.org/qemu/qemu-linaro.git but as you can see from the log at http://validation.linaro.org/jenkins/job/qemu-build/scmPollLog/? it doesn't seem to have actually polled the git server since November...
thanks -- PMM
On Fri, 17 Feb 2012 11:58:59 +0000, Peter Maydell peter.maydell@linaro.org wrote:
On 11 February 2012 17:39, Peter Maydell peter.maydell@linaro.org wrote:
On 11 February 2012 06:44, Paul Larson paul.larson@linaro.org wrote:
Actually, let me amend this slightly - Peter! It seems the qemu job hasn't run in over 2 months. Is this even interesting to run any more? Is the tree inactive?
The tree is active but I think the job is busted (not monitoring the right branch? I think we did a config tweak which maybe wasn't the right thing...)
I had a look to see if I could find out what was going wrong here, but as far as I can see I don't have enough permissions on this jenkins instance to even look at the config for this job, so I don't have any way to investigate the problem. Can somebody else look at it? It should be monitoring the 'master' branch of git://git.linaro.org/qemu/qemu-linaro.git but as you can see from the log at http://validation.linaro.org/jenkins/job/qemu-build/scmPollLog/? it doesn't seem to have actually polled the git server since November...
The branch name was ** -- having no idea what that would mean, I changed it to master. Let's see what happens next :-)
Cheers, mwh
On 20 February 2012 04:14, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
The branch name was ** -- having no idea what that would mean, I changed it to master. Let's see what happens next :-)
"**" is the default, which I think results in it building all branches (a bad idea for us since eg the 'upstream' branch won't pass tests for qemu-linaro specific features). I thought we'd fixed that problem -- I have an email conversation with Paul from last September where I asked him to change the branch specifier to 'master' and I'm sure I remember it happening. Maybe it got reset somehow.
-- PMM
On Mon, 20 Feb 2012 10:31:56 +0000, Peter Maydell peter.maydell@linaro.org wrote:
On 20 February 2012 04:14, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
The branch name was ** -- having no idea what that would mean, I changed it to master. Let's see what happens next :-)
"**" is the default, which I think results in it building all branches (a bad idea for us since eg the 'upstream' branch won't pass tests for qemu-linaro specific features). I thought we'd fixed that problem -- I have an email conversation with Paul from last September where I asked him to change the branch specifier to 'master' and I'm sure I remember it happening. Maybe it got reset somehow.
Hah, I found the problem: the git fetch from November 20 had got stuck somehow and was still running! So I killed it and requested a build and things seem to be happening now.
Cheers, mwh
On 20 February 2012 19:14, Michael Hudson-Doyle michael.hudson@linaro.org wrote:
Hah, I found the problem: the git fetch from November 20 had got stuck somehow and was still running! So I killed it and requested a build and things seem to be happening now.
And indeed we seem to have done a successful qemu-build and run the qemu-boot-images tests.
Incidentally, I'm not sure what the "Build qemu images and extract filesystems" and "QEMU Daily Headless Image Boot" jenkins projects are, so as far as I'm concerned they could go.
Thanks! -- PMM
On Sat, Feb 11, 2012 at 12:12 PM, Paul Larson paul.larson@linaro.orgwrote:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
If you are interested in using ci.linaro.org please do let me know.
On Thu, Feb 9, 2012 at 12:08 PM, Paul Larson paul.larson@linaro.orgwrote:
Is there any reason why we shouldn't target running the few things done in jenkins on v.l.o on ci.linaro.org instead? ci.linaro.org didn't exist when we first started this, but it would make sense to consolidate our jenkins instances. At the beginning, we were using jenkins for scheduling jobs, but we don't use that any longer. Implementing the qemu testing on top of that was just for convenience because we didn't have another jenkins at the time.
Thanks, Paul Larson
Hi Paul,
У пет, 10. 02 2012. у 22:42 -0800, Paul Larson пише:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
Prepare the requirements for the jobs (eg. jenkins plugins, job configs, deps for the server and such) and we can set ci.linaro.org up for what you need to do. Let's chat about this this week.
(As a side-note, we are moving this instance to the Canonical DC, so do not expect to have full admin privs on it)
Cheers, Danilo
How will you get around needing root for things like lmc? On Feb 13, 2012 4:06 AM, "Danilo Šegan" danilo.segan@linaro.org wrote:
Hi Paul,
У пет, 10. 02 2012. у 22:42 -0800, Paul Larson пише:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
Prepare the requirements for the jobs (eg. jenkins plugins, job configs, deps for the server and such) and we can set ci.linaro.org up for what you need to do. Let's chat about this this week.
(As a side-note, we are moving this instance to the Canonical DC, so do not expect to have full admin privs on it)
Cheers, Danilo
On 13 February 2012 20:59, Paul Larson paul.larson@linaro.org wrote:
How will you get around needing root for things like lmc?
feature that is also needed to run live-build to genera.
On Feb 13, 2012 4:06 AM, "Danilo Šegan" danilo.segan@linaro.org wrote:
Hi Paul,
У пет, 10. 02 2012. у 22:42 -0800, Paul Larson пише:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
Prepare the requirements for the jobs (eg. jenkins plugins, job configs, deps for the server and such) and we can set ci.linaro.org up for what you need to do. Let's chat about this this week.
(As a side-note, we are moving this instance to the Canonical DC, so do not expect to have full admin privs on it)
Cheers, Danilo
On 14 February 2012 12:28, Fathi Boudra fathi.boudra@linaro.org wrote:
On 13 February 2012 20:59, Paul Larson paul.larson@linaro.org wrote:
How will you get around needing root for things like lmc?
feature that is also needed to run live-build to genera.
sorry sent prematurely. We need to run live-build to generate images with Jenkins.
On Feb 13, 2012 4:06 AM, "Danilo Šegan" danilo.segan@linaro.org wrote:
Hi Paul,
У пет, 10. 02 2012. у 22:42 -0800, Paul Larson пише:
Hi Danilo, I'd like to see about what we can do to take the few things we are running in our old jenkins instance on the validation server, and move it into the official linaro jenkins server. Where should we start?
Prepare the requirements for the jobs (eg. jenkins plugins, job configs, deps for the server and such) and we can set ci.linaro.org up for what you need to do. Let's chat about this this week.
(As a side-note, we are moving this instance to the Canonical DC, so do not expect to have full admin privs on it)
Cheers, Danilo
-- Fathi Boudra Linaro Release Manager | Validation Project Manager Linaro.org | Open source software for ARM SoCs
У пон, 13. 02 2012. у 10:59 -0800, Paul Larson пише:
How will you get around needing root for things like lmc?
That means scripts on the slave will need root access, but for the master, we'll have nothing like that if we can be helped.
(also, if we can properly sandbox the environment, scripts might get sudo root access on the master if really necessary, but none of us would have the direct access either)
Cheers, Danilo
Oh, and btw, I am off Wed-Fri because of national holidays in Serbia.
Cheers, Danilo
linaro-validation@lists.linaro.org
-
Danilo Šegan -
Dave Pigott -
Deepti Kalakeri -
Fathi Boudra -
Michael Hudson-Doyle -
Paul Larson -
Peter Maydell -
Zygmunt Krynicki