>So what about disabling all jobs on Jenkins, and enable just one and
>try
>to get that one running clean, then we can enable the next one etc.?

yes, this would be a way. perhaps start with a main build job that builds all 
projects, runs all unit tests, but without any integration tests. then add 
integration tests one after another.
i've no overview how the jobs on Jenkins are currently structured (and who has 
the rights to change them).

stefan

Reply via email to