Re: Dependencies in Jenkins Jobs

[Robert Munteanu]

On Wed, 2017-03-29 at 13:44 +0200, Konrad Windszus wrote:
> I think the solution is the configuration option "Block build when
> upstream project is building"[0], which should be IMHO enabled on all
> Jenkins Jobs for Sling. 
> WDYT?
> @Robert: Can you change the seed job accordingly?
> Konrad

Sure, done in https://svn.apache.org/r1789342

Robert

> 
> [0] - http://blogs.wandisco.com/2012/07/26/bringing-order-your-jenkin
> s-jobs/
> 
> > On 29 Mar 2017, at 13:34, Konrad Windszus  > ic.biz> wrote:
> > 
> > I just ran into a Jenkins Build Failure in https://builds.apache.or
> > g/job/sling-bundles-extensions-validation-core-1.8/80/.
> > Although this does have a dependency on Validation API in 1.0.0-
> > SNAPSHOT the according API build job (https://builds.apache.org/job
> > /sling-bundles-extensions-validation-api-1.8/) has not been
> > triggered prior to build 80 of validation core. Therefore an older
> > version of the API bundle has been used, which is incompatible. Is
> > there anything we can tweak here on the Jenkins side to make sure
> > that the upstream jobs are triggered first (if they are affected by
> > the same commit)?
> > Thanks,
> > Konrad
> 
> 

Re: Dependencies in Jenkins Jobs

[Konrad Windszus]

I think the solution is the configuration option "Block build when upstream 
project is building"[0], which should be IMHO enabled on all Jenkins Jobs for 
Sling. 
WDYT?
@Robert: Can you change the seed job accordingly?
Konrad

[0] - http://blogs.wandisco.com/2012/07/26/bringing-order-your-jenkins-jobs/

> On 29 Mar 2017, at 13:34, Konrad Windszus  
> wrote:
> 
> I just ran into a Jenkins Build Failure in 
> https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/80/.
> Although this does have a dependency on Validation API in 1.0.0-SNAPSHOT the 
> according API build job 
> (https://builds.apache.org/job/sling-bundles-extensions-validation-api-1.8/) 
> has not been triggered prior to build 80 of validation core. Therefore an 
> older version of the API bundle has been used, which is incompatible. Is 
> there anything we can tweak here on the Jenkins side to make sure that the 
> upstream jobs are triggered first (if they are affected by the same commit)?
> Thanks,
> Konrad

Dependencies in Jenkins Jobs

[Konrad Windszus]

I just ran into a Jenkins Build Failure in 
https://builds.apache.org/job/sling-bundles-extensions-validation-core-1.8/80/.
Although this does have a dependency on Validation API in 1.0.0-SNAPSHOT the 
according API build job 
(https://builds.apache.org/job/sling-bundles-extensions-validation-api-1.8/) 
has not been triggered prior to build 80 of validation core. Therefore an older 
version of the API bundle has been used, which is incompatible. Is there 
anything we can tweak here on the Jenkins side to make sure that the upstream 
jobs are triggered first (if they are affected by the same commit)?
Thanks,
Konrad