Jenkins administration
Hi all, Jenkins, our CI system, has been down for more than a month. It looks like the disk has filled up, and we need to do clean up / the build tasks should clean up after themselves better (I suspect it has to do with storing the results of too many older builds instead of just the current one plus a few recent builds).
We need an administrator for Jenkins. Currently, I think only me and Bryce have access, which is not good enough.
Who is interested in maintaining the automatic build/testing system?
Of course, you can tailor the system to your own likes; there is much to be improved and I think all are open to whatever crazy plans you may have :-)
regards, Johan
Hi Johan,
I noticed that Jenkins was down and was going to ping you about that now that I am back from a month-long vacation (maybe Jenkins' was on vacation too?).
I think this system is pretty important for Inkscape. I would like to help keep it running but am not sure I will have much time to work on it in the next month as I am already over-committed. Having said that, I might be able to take a quick look. Is there any kind of documentations on how things are set up? What about asking Joakim for some help?
Tav
On Wed, 2015-08-19 at 23:27 +0200, Johan Engelen wrote:
Hi all, Jenkins, our CI system, has been down for more than a month. It looks like the disk has filled up, and we need to do clean up / the build tasks should clean up after themselves better (I suspect it has to do with storing the results of too many older builds instead of just the current one plus a few recent builds).
We need an administrator for Jenkins. Currently, I think only me and Bryce have access, which is not good enough.
Who is interested in maintaining the automatic build/testing system?
Of course, you can tailor the system to your own likes; there is much to be improved and I think all are open to whatever crazy plans you may have :-)
regards, Johan
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Tav, There's some text here: http://wiki.inkscape.org/wiki/index.php/Jenkins_server_setup
The jobs are set up pretty straightforward, I think. The bzr_up job runs first (every day, if bzr has a new commit), and then the other jobs trigger when bzr up finishes. The Jenkins admin will need an ssh login to the server. Bryce can help arrange that.
I can help get things running next week somewhere. And I can come to IRC to help out whoever wants to take up the task. The task is low-effort I think. Perhaps Joakim is interested.
regards, Johan
On 20-8-2015 16:12, Tavmjong Bah wrote:
Hi Johan,
I noticed that Jenkins was down and was going to ping you about that now that I am back from a month-long vacation (maybe Jenkins' was on vacation too?).
I think this system is pretty important for Inkscape. I would like to help keep it running but am not sure I will have much time to work on it in the next month as I am already over-committed. Having said that, I might be able to take a quick look. Is there any kind of documentations on how things are set up? What about asking Joakim for some help?
Tav
On Wed, 2015-08-19 at 23:27 +0200, Johan Engelen wrote:
Hi all, Jenkins, our CI system, has been down for more than a month. It looks like the disk has filled up, and we need to do clean up / the build tasks should clean up after themselves better (I suspect it has to do with storing the results of too many older builds instead of just the current one plus a few recent builds).
We need an administrator for Jenkins. Currently, I think only me and Bryce have access, which is not good enough.
Who is interested in maintaining the automatic build/testing system?
Of course, you can tailor the system to your own likes; there is much to be improved and I think all are open to whatever crazy plans you may have :-)
regards, Johan
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Thu, Aug 20, 2015 at 09:32:13PM +0200, Johan Engelen wrote:
Hi Tav, There's some text here: http://wiki.inkscape.org/wiki/index.php/Jenkins_server_setup
The jobs are set up pretty straightforward, I think. The bzr_up job runs first (every day, if bzr has a new commit), and then the other jobs trigger when bzr up finishes. The Jenkins admin will need an ssh login to the server. Bryce can help arrange that.
I can help get things running next week somewhere. And I can come to IRC to help out whoever wants to take up the task. The task is low-effort I think. Perhaps Joakim is interested.
I obtained a big space upgrade from OSUOSL last month. I had started experimenting with getting coverity on it, but there wasn't adequate space, and couldn't actually add it. But I notice all that space is filled up again already, so presumably other stuff needs better gargage collection done.
Would love it if someone else could assist on this; my time has been rather fragmented lately.
Bryce
regards, Johan
On 20-8-2015 16:12, Tavmjong Bah wrote:
Hi Johan,
I noticed that Jenkins was down and was going to ping you about that now that I am back from a month-long vacation (maybe Jenkins' was on vacation too?).
I think this system is pretty important for Inkscape. I would like to help keep it running but am not sure I will have much time to work on it in the next month as I am already over-committed. Having said that, I might be able to take a quick look. Is there any kind of documentations on how things are set up? What about asking Joakim for some help?
Tav
On Wed, 2015-08-19 at 23:27 +0200, Johan Engelen wrote:
Hi all, Jenkins, our CI system, has been down for more than a month. It looks like the disk has filled up, and we need to do clean up / the build tasks should clean up after themselves better (I suspect it has to do with storing the results of too many older builds instead of just the current one plus a few recent builds).
We need an administrator for Jenkins. Currently, I think only me and Bryce have access, which is not good enough.
Who is interested in maintaining the automatic build/testing system?
Of course, you can tailor the system to your own likes; there is much to be improved and I think all are open to whatever crazy plans you may have :-)
regards, Johan
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 21-8-2015 1:52, Bryce Harrington wrote:
On Thu, Aug 20, 2015 at 09:32:13PM +0200, Johan Engelen wrote:
Hi Tav, There's some text here: http://wiki.inkscape.org/wiki/index.php/Jenkins_server_setup
The jobs are set up pretty straightforward, I think. The bzr_up job runs first (every day, if bzr has a new commit), and then the other jobs trigger when bzr up finishes. The Jenkins admin will need an ssh login to the server. Bryce can help arrange that.
I can help get things running next week somewhere. And I can come to IRC to help out whoever wants to take up the task. The task is low-effort I think. Perhaps Joakim is interested.
I obtained a big space upgrade from OSUOSL last month. I had started experimenting with getting coverity on it, but there wasn't adequate space, and couldn't actually add it. But I notice all that space is filled up again already, so presumably other stuff needs better gargage collection done.
I've fixed the space issue. Jenkins is up and running again. Now (most) jobs will only retain the results and artifacts of the last 20 builds (increase when you need more).
I also upgraded to clang-3.6, for perhaps improved static analysis results. The number of bugs dramatically reduced since last build. Either because of great work on the code, or because of clang3.6.
cheers, Johan
2015-09-13 19:34 GMT+02:00 Johan Engelen <jbc.engelen@...2592...>:
On 21-8-2015 1:52, Bryce Harrington wrote:
On Thu, Aug 20, 2015 at 09:32:13PM +0200, Johan Engelen wrote:
Hi Tav, There's some text here: http://wiki.inkscape.org/wiki/index.php/Jenkins_server_setup
The jobs are set up pretty straightforward, I think. The bzr_up job runs first (every day, if bzr has a new commit), and then the other jobs trigger when bzr up finishes. The Jenkins admin will need an ssh login to the server. Bryce can help arrange that.
I can help get things running next week somewhere. And I can come to IRC to help out whoever wants to take up the task. The task is low-effort I think. Perhaps Joakim is interested.
I obtained a big space upgrade from OSUOSL last month. I had started experimenting with getting coverity on it, but there wasn't adequate space, and couldn't actually add it. But I notice all that space is filled up again already, so presumably other stuff needs better gargage collection done.
I've fixed the space issue. Jenkins is up and running again. Now (most) jobs will only retain the results and artifacts of the last 20 builds (increase when you need more).
I also upgraded to clang-3.6, for perhaps improved static analysis results. The number of bugs dramatically reduced since last build. Either because of great work on the code, or because of clang3.6.
cheers, Johan
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Does anyone have any plans for Jenkins within Inkscape project right now?
I've tried out Jenkins and jenkins-workflow plugin last week in another project and it might be a good path to take with Inkscape as well. Two main benefits as I see it; (1) move job specification to Groovy script located in the Inkscape source and (2) be able to reduce the number of jobs in Jenkins (easier management). Following the Jenkins development the "Workflow" mindset seems to be the big thing looking forward, especially for Jenkins 2.0.
Shared workspaces are used for the jobs currently defined. Is it to only have to checkout one copy of the Inkscape source?
I would like to help out with Jenkins/build server administration, my jenkins user id is "christoffer".
Regards
2015-11-21 19:57 GMT+01:00 Christoffer Holmstedt < christoffer.holmstedt@...400...>:
2015-09-13 19:34 GMT+02:00 Johan Engelen <jbc.engelen@...2592...>:
On 21-8-2015 1:52, Bryce Harrington wrote:
On Thu, Aug 20, 2015 at 09:32:13PM +0200, Johan Engelen wrote:
Hi Tav, There's some text here: http://wiki.inkscape.org/wiki/index.php/Jenkins_server_setup
The jobs are set up pretty straightforward, I think. The bzr_up job
runs
first (every day, if bzr has a new commit), and then the other jobs trigger when bzr up finishes. The Jenkins admin will need an ssh login to the server. Bryce can help arrange that.
I can help get things running next week somewhere. And I can come to
IRC
to help out whoever wants to take up the task. The task is low-effort I think. Perhaps Joakim is interested.
I obtained a big space upgrade from OSUOSL last month. I had started experimenting with getting coverity on it, but there wasn't adequate space, and couldn't actually add it. But I notice all that space is filled up again already, so presumably other stuff needs better gargage collection done.
I've fixed the space issue. Jenkins is up and running again. Now (most) jobs will only retain the results and artifacts of the last 20 builds (increase when you need more).
I also upgraded to clang-3.6, for perhaps improved static analysis results. The number of bugs dramatically reduced since last build. Either because of great work on the code, or because of clang3.6.
cheers, Johan
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Does anyone have any plans for Jenkins within Inkscape project right now?
I've tried out Jenkins and jenkins-workflow plugin last week in another project and it might be a good path to take with Inkscape as well. Two main benefits as I see it; (1) move job specification to Groovy script located in the Inkscape source and (2) be able to reduce the number of jobs in Jenkins (easier management). Following the Jenkins development the "Workflow" mindset seems to be the big thing looking forward, especially for Jenkins 2.0.
Shared workspaces are used for the jobs currently defined. Is it to only have to checkout one copy of the Inkscape source?
I would like to help out with Jenkins/build server administration, my jenkins user id is "christoffer".
Regards
Christoffer Holmstedt
Hello again This is bump to my previous question from the 21st of November. Anyone?
Regards
On Wed, 2015-12-09 at 19:01 +0100, Christoffer Holmstedt wrote:
Hello again
This is bump to my previous question from the 21st of November. Anyone?
Hi Christoffer,
The existing Jenkins server is operational, but I'm not sure why there haven't been any comment from the people who were involved more directly in setting up that machine.
We should try and get you access from osuosl so you can have a look around.
Martin,
On Wed, 2015-12-09 at 13:36 -0500, Martin Owens wrote:
On Wed, 2015-12-09 at 19:01 +0100, Christoffer Holmstedt wrote:
Hello again
This is bump to my previous question from the 21st of November. Anyone?
Hi Christoffer,
The existing Jenkins server is operational, but I'm not sure why there haven't been any comment from the people who were involved more directly in setting up that machine.
We should try and get you access from osuosl so you can have a look around.
Martin,
Sorry, I meant to reply to you (Christoffer) earlier. Anything you can do to help us out with Jenkins would be fantastic. Johann, who was the primary driver in getting it setup, has moved onto a different project and is no longer active in Inkscape. He had help from Joakim Verona who does this kind of stuff for his day job and would probably respond if emailed.
I intended to get more involved but have been swamped by other commitments.
Tav
On Wed, Dec 09, 2015 at 08:50:24PM +0100, Tavmjong Bah wrote:
On Wed, 2015-12-09 at 13:36 -0500, Martin Owens wrote:
On Wed, 2015-12-09 at 19:01 +0100, Christoffer Holmstedt wrote:
Hello again
This is bump to my previous question from the 21st of November. Anyone?
Hi Christoffer,
The existing Jenkins server is operational, but I'm not sure why there haven't been any comment from the people who were involved more directly in setting up that machine.
We should try and get you access from osuosl so you can have a look around.
Martin,
Sorry, I meant to reply to you (Christoffer) earlier. Anything you can do to help us out with Jenkins would be fantastic. Johann, who was the primary driver in getting it setup, has moved onto a different project and is no longer active in Inkscape. He had help from Joakim Verona who does this kind of stuff for his day job and would probably respond if emailed.
I intended to get more involved but have been swamped by other commitments.
Ditto with me. I think I have the administrative credentials and probably can help get you set up if I figure out how.
Bryce
2015-12-10 6:45 GMT+01:00 Bryce Harrington <bryce@...961...>:
On Wed, Dec 09, 2015 at 08:50:24PM +0100, Tavmjong Bah wrote:
On Wed, 2015-12-09 at 13:36 -0500, Martin Owens wrote:
On Wed, 2015-12-09 at 19:01 +0100, Christoffer Holmstedt wrote:
Hello again
This is bump to my previous question from the 21st of November. Anyone?
Hi Christoffer,
The existing Jenkins server is operational, but I'm not sure why there haven't been any comment from the people who were involved more directly in setting up that machine.
We should try and get you access from osuosl so you can have a look around.
Martin,
Sorry, I meant to reply to you (Christoffer) earlier. Anything you can do to help us out with Jenkins would be fantastic. Johann, who was the primary driver in getting it setup, has moved onto a different project and is no longer active in Inkscape. He had help from Joakim Verona who does this kind of stuff for his day job and would probably respond if emailed.
I intended to get more involved but have been swamped by other commitments.
Ditto with me. I think I have the administrative credentials and probably can help get you set up if I figure out how.
Bryce
Thanks for the information, sounds good if I can get access to the machine to get started, or at least admin rights to Jenkins. Though if an update/change fails through Jenkins web interface it will be hard to fix anything without access to the machine in the end.
I'm away during the holidays but will take a look at it in January so no rush.
Merry Christmas and a happy New Year
participants (5)
-
Bryce Harrington -
Christoffer Holmstedt -
Johan Engelen -
Martin Owens -
Tavmjong Bah