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:
> 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
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.