Hi all, What time would be good (UTC) for starting a new daily build for trunk? The current solution has enough compute power to do one build per day for trunk in about 1.5hrs. Perhaps someone finds it fun to make a graph of average commit activity versus time of the day that I can use to decide when to bzr up and start the build. :-)
cheers, Johan
On 9-10-2014 10:43, jbc.engelen@...2592... wrote:
Hi all, I have set up a daily build system that checks if trunk still builds (on Ubuntu) and, more importantly, runs clang's static analyzer using scan-build. You can find the results here: http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/ After some clicking, you will find these interesting pages (links may become obsolete after a new build) http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_tr... and http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape%20...
As you can see, there are still some nasty bugs in trunk. For example http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_tr...
-Johan
(currently I run Jenkins on free-tier EC2, but we are working on getting something more permanent. Expect a longer email with plans in the near future)
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.cl... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel