I'm sorry for the potential confusion in my email: I meant to say, please sign up for inkscape-tester@...233... You can also register yourself for jenkins.inkscape.org, but that is only needed when you want to help maintain and improve the Jenkins setup.
cheers, Johan
----- Reply message ----- From: "Christoffer Holmstedt" <christoffer.holmstedt@...400...> To: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net, inkscape-tester@lists.sourceforge.net Subject: [Inkscape-devel] Jenkins Date: Sat, Jan 31, 2015 06:13
Thanks for the information about that tester mailing list, I've signed up. I'm interested in testing and verification so this could perhaps be a good way into the core of inkscape source code. -- Christoffer Holmstedt
2015-01-30 23:44 GMT+01:00 Johan Engelen <jbc.engelen@...2592...>:
Hi all, Our "continuous integration" system, Jenkins, is up and running. It does automated builds, checks for bugs, runs the unittests, generates documentation with doxygen and will publish it online, and in future will also run rendertests. Currently it does those things for Inkscape trunk and 0.91.x branches; and also runs some jobs for lib2geom trunk. If some job fails (i.e. build is broken, a test no longer passes, or clang scanbuild discovers a new potential bug), Jenkins will send a notification email to the inkscape-tester SF maillist. If you are an active developer, please sign up for that maillist if you have not already.
You do not need to sign up, unless you want to help maintaining and improving the system. All help is welcome. If you want to help, sign up, and let us know so we can give you more rights. Currently, only I and Martin Owens have full access. That is definitely not enough, so let yourself be known if you are interested!
Have a look here: http://jenkins.inkscape.org
cheers, Johan
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Thanks for the clarification, I signed up there as well.
After browsing through the different build jobs I see that they are run in order so only one or two are initiated by SCM update...and if it is successfull it will start some other jobs. Do we have a wiki page where the thoughtprocess and structure of this is documented?
I've found the jenkins set up process on the wiki but no details on the "job structure". What is the goal of each job? (for those familiar with CI it's pretty clear from the name of it but for new developers it could be helpful). -- Christoffer Holmstedt
2015-01-31 8:18 GMT+01:00 Johan Engelen <jbc.engelen@...2592...>:
I'm sorry for the potential confusion in my email: I meant to say, please sign up for inkscape-tester@...233... You can also register yourself for jenkins.inkscape.org, but that is only needed when you want to help maintain and improve the Jenkins setup.
cheers, Johan
----- Reply message ----- From: "Christoffer Holmstedt" <christoffer.holmstedt@...400...> To: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net, inkscape-tester@lists.sourceforge.net Subject: [Inkscape-devel] Jenkins Date: Sat, Jan 31, 2015 06:13
Thanks for the information about that tester mailing list, I've signed up. I'm interested in testing and verification so this could perhaps be a good way into the core of inkscape source code. -- Christoffer Holmstedt
2015-01-30 23:44 GMT+01:00 Johan Engelen <jbc.engelen@...2592...>:
Hi all, Our "continuous integration" system, Jenkins, is up and running. It does automated builds, checks for bugs, runs the unittests, generates documentation with doxygen and will publish it online, and in future will also run rendertests. Currently it does those things for Inkscape trunk and 0.91.x branches; and also runs some jobs for lib2geom trunk. If some job fails (i.e. build is broken, a test no longer passes, or clang scanbuild discovers a new potential bug), Jenkins will send a notification email to the inkscape-tester SF maillist. If you are an active developer, please sign up for that maillist if you have not already.
You do not need to sign up, unless you want to help maintaining and improving the system. All help is welcome. If you want to help, sign up, and let us know so we can give you more rights. Currently, only I and Martin Owens have full access. That is definitely not enough, so let yourself be known if you are interested!
Have a look here: http://jenkins.inkscape.org
cheers, Johan
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Hi Christoffer, I assigned you the role "maintainer" meaning you can do pretty much anything on Jenkins.
You are very welcome to help join the testing effort! I am alone at the moment. Now that we've released 0.91, I hope more people join.
There is no documentation on the job structure. My thinking was to have these jobs in succession. 1. bzr update and make (using clang-scanbuild) 2. unittests (only if job 1 succeeded) 3. rendertests (only if job 2 succeeds) 4. doxygen (only if job 1? succeeds) and publish the HTML if successful
1 issue that needs be solved: - the bzr updating mechanism (it seems a bit weird the way jenkins plugin tries to update the workspace) sometimes breaks, complaining that bzr is not stable and may have crashed. Then, the workspace is emptied and the build fails. This then looks like a failed "make". If this happens, we have to simply restart the job; unfortunately i have not figured out a way to have jenkins do that itself, and not complain about the failed bzr-update with an email... So I think we should split job 1 into an update job and a make job.
Just now we had a unittest failure for 0.91.x because the workspace is empty. I do not know how this happened. :( Simply had to restart the full job chain. Don't know the cause for this problem.
cheers, Johan
On 31 Jan 2015, at 09:12, Christoffer Holmstedt <christoffer.holmstedt@...1857...00...> wrote:
Thanks for the clarification, I signed up there as well.
After browsing through the different build jobs I see that they are run in order so only one or two are initiated by SCM update...and if it is successfull it will start some other jobs. Do we have a wiki page where the thoughtprocess and structure of this is documented?
I've found the jenkins set up process on the wiki but no details on the "job structure". What is the goal of each job? (for those familiar with CI it's pretty clear from the name of it but for new developers it could be helpful). -- Christoffer Holmstedt
2015-01-31 8:18 GMT+01:00 Johan Engelen <jbc.engelen@...2592...>:
I'm sorry for the potential confusion in my email: I meant to say, please sign up for inkscape-tester@...233... You can also register yourself for jenkins.inkscape.org, but that is only needed when you want to help maintain and improve the Jenkins setup.
cheers, Johan
----- Reply message ----- From: "Christoffer Holmstedt" <christoffer.holmstedt@...400...> To: "Inkscape Devel List" inkscape-devel@lists.sourceforge.net, inkscape-tester@lists.sourceforge.net Subject: [Inkscape-devel] Jenkins Date: Sat, Jan 31, 2015 06:13
Thanks for the information about that tester mailing list, I've signed up. I'm interested in testing and verification so this could perhaps be a good way into the core of inkscape source code. -- Christoffer Holmstedt
2015-01-30 23:44 GMT+01:00 Johan Engelen <jbc.engelen@...2592...>:
Hi all, Our "continuous integration" system, Jenkins, is up and running. It does automated builds, checks for bugs, runs the unittests, generates documentation with doxygen and will publish it online, and in future will also run rendertests. Currently it does those things for Inkscape trunk and 0.91.x branches; and also runs some jobs for lib2geom trunk. If some job fails (i.e. build is broken, a test no longer passes, or clang scanbuild discovers a new potential bug), Jenkins will send a notification email to the inkscape-tester SF maillist. If you are an active developer, please sign up for that maillist if you have not already.
You do not need to sign up, unless you want to help maintaining and improving the system. All help is welcome. If you want to help, sign up, and let us know so we can give you more rights. Currently, only I and Martin Owens have full access. That is definitely not enough, so let yourself be known if you are interested!
Have a look here: http://jenkins.inkscape.org
cheers, Johan
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 01 Feb 2015, at 16:55, Johan Engelen <jbc.engelen@...2592...> wrote:
Just now we had a unittest failure for 0.91.x because the workspace is empty. I do not know how this happened. :( Simply had to restart the full job chain. Don't know the cause for this problem.
Found the cause and fixed it. The shared workspace was not properly set up (not set up at all) for Inkscape_latest_release.
cheers, Johan
participants (2)
-
Christoffer Holmstedt -
Johan Engelen