Hi Franz and dear developers,

On 08/12/2014 01:16 PM, Zieris, Franz wrote:
> Dear developers,
>
> To me, the mail traffic of the last days was kind of intransparent, and I 
> guess I'm not alone.
> I understand that our CI setup has some severe problems.
> As the CI is an integral part of our development infrastructure I want 
> everyone who knows something about this issue to keep reading.
>
> So here is what I would like to see as response(s) to this e-mail:
> * What is the *current state* of our CI (is it up or down, which jobs are 
> running normally, which are not)?
All jobs are running normally, I'm expecting the Saros job to fail, 
though. That is a different problem,
but at least there is a workaround. If desired I can go into detail on this.
> * For the non-normal jobs: What exactly are the *symptoms*?
There were three problems:
1. All QA jobs didn't fail when Unit tests failed. This was due to not 
having published JUnit testresults as a
post build step. (fixed)
2. The (now again) hourly Saros-Job always built the same patchset due 
to misconfiguration. The configuration
was reverted, as is now the same as before, except that it also builds 
Intellij. (fixed)
3. Saros-Job failed when trigerred by the hourly poll. This is a 
peculiar problem. In the ant call, Gerrit parameters
are passed and parsed incorrectly. (status unknown, have to wait for a 
real change-merge, manual triggering
didn't work either).
> * What do we currently know about *possible reasons* for that? (If there is 
> more than one theory, please feel free to share it with us).
>
> Please note: The question "Who did what?" is not part of this list.
>
> As soon as we agree on the status quo, we can discuss possible ways to reach 
> the desired state -- and eventually who will carry out the necessary steps.
>
> Finally, after the CI is back to normal, I want:
> * An analysis of what happened in the first place.
>
> * Ideas to prevent this in the future.
1. Peer review Jenkins configuration changes.
2. Put effort into simplifying the configuration in Jenkins (in the vein 
of a refactoring).

LG,
Arsenij
> Cheers,
> Franz
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> DPP-Devel mailing list
> DPP-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel


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

Reply via email to