That's interesting. I mistook Jenkins's grey status ball for "Deactivated", but 
obviously it also stands for "Pending".

The job is *active*, but for some reason the previous builds are not listed 
(they were meant to be discarded after 30 days). However, there are no pending 
changes in the repository for build scripts, so the job has nothing to do 
anyway. 

Long story short: Never mind :)

Franz

-----Original Message-----
From: Zieris, Franz [mailto:franz.zie...@fu-berlin.de] 
Sent: Tuesday, July 09, 2013 11:02 AM
To: dpp-devel@lists.sourceforge.net
Subject: Re: [DPP-Devel] Two changes in our CI infrastructure

Dear developers,

as it seems, the new Jenkins jobs "CI-Script-Deploy" has been deactivated (and 
apparently the job doesn't even "remember" when it last ran/failed/succeeded).

I assume this was a deliberate action. Could the one who did this please 
enlighten us?

Franz

-----Original Message-----
From: Zieris, Franz [mailto:franz.zie...@fu-berlin.de] 
Sent: Friday, July 05, 2013 7:51 PM
To: dpp-devel@lists.sourceforge.net
Subject: [DPP-Devel] Two changes in our CI infrastructure

Dear developers,

I just performed two maintenance tasks on our Jenkins system.

Task 1: Job configuration history.

I installed the plugin "JobConfigHistory" [1] which keeps track of all changes 
to the configuration of Jenkins's jobs. From now on, we can view, compare, and 
restore older versions. I performed a "Save" on all jobs (without any changes, 
of course) in order create the first version of each configuration as a 
baseline for the next actual changes.

Task 2: Jenkins scripts under version control.

I created a new repository named "saros-ci-scripts" [2] which, as of now, 
contains Jenkins's "scripts" folder. Changes will go through Gerrit. There is 
also a new job called "CI-Script-Deploy" which monitors the Git repository for 
changes and replaces the scripts if need be.
I used the two locks PLUGIN_BUILD and STF_RUN in this job to make sure that the 
scripts won't get changed while another job accesses them.

Feel free to give feedback or take action. Everything is a bit safer from now 
on :)

Best Regards,
Franz

[1] https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin
[2] git clone http://saros-build.imp.fu-berlin.de/gerrit/saros-ci-scripts.git

_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel


------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel

Reply via email to