Hudson dependencies

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Hudson dependencies

Plante, David
Message
Hi,
 
I have a question about the management dependencies of Hudson.
 
I currently have a Maven  project with many dependencies. Now, when I build, Hudson will get the latest version of the project dependencies in the repository.
Problem is that I would like Hudson to check the version of the dependencies with the repository and build them if theres a difference. Is that possible ?
 
For example :
 
If we have 2 projects named A and B.
B have a dependency on A.
 
If I make a manual build of B, i would like Hudson to go check if any changes were made in A and build it if yes instead of just getting the latest version on A in the repository.
 
Thanks for your help.
 
David P.
 
 
 

"Ce message est confidentiel, a l'usage exclusif du destinataire ci-dessus et son contenu ne represente en aucun cas un engagement de la part de AXA, sauf en cas de stipulation expresse et par ecrit de la part de AXA. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur."

"This e-mail message is confidential, for the exclusive use of the addressee and its contents shall not constitute a commitment by AXA, except as otherwise specifically provided in writing by AXA. Any unauthorized disclosure, use or dissemination, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender immediately."
Reply | Threaded
Open this post in threaded view
|

Hudson dependencies

Plante, David
Message
Hi,
 
I have a question about the management dependencies of Hudson.
 
I currently have a Maven  project with many dependencies. Now, when I build, Hudson will get the latest version of the project dependencies in the repository.
Problem is that I would like Hudson to check the version of the dependencies with the repository and build them if theres a difference. Is that possible ?
 
For example :
 
If we have 2 projects named A and B.
B have a dependency on A.
 
If I make a manual build of B, i would like Hudson to go check if any changes were made in A and build it if yes instead of just getting the latest version on A in the repository.
 
Thanks for your help.
 
David P.
 
 
 

"Ce message est confidentiel, a l'usage exclusif du destinataire ci-dessus et son contenu ne represente en aucun cas un engagement de la part de AXA, sauf en cas de stipulation expresse et par ecrit de la part de AXA. Toute publication, utilisation ou diffusion, meme partielle, doit etre autorisee prealablement. Si vous n'etes pas destinataire de ce message, merci d'en avertir immediatement l'expediteur."

"This e-mail message is confidential, for the exclusive use of the addressee and its contents shall not constitute a commitment by AXA, except as otherwise specifically provided in writing by AXA. Any unauthorized disclosure, use or dissemination, either whole or partial, is prohibited. If you are not the intended recipient of the message, please notify the sender immediately."
Reply | Threaded
Open this post in threaded view
|

Re: Hudson dependencies

Kohsuke Kawaguchi
Administrator
In reply to this post by Plante, David
Plante, David wrote:

> Hi,
>  
> I have a question about the management dependencies of Hudson.
>  
> I currently have a Maven  project with many dependencies. Now, when I
> build, Hudson will get the latest version of the project dependencies in
> the repository.
> Problem is that I would like Hudson to check the version of the
> dependencies with the repository and build them if theres a difference.
> Is that possible ?
>  
> For example :
>  
> If we have 2 projects named A and B.
> B have a dependency on A.
>  
> If I make a manual build of B, i would like Hudson to go check if any
> changes were made in A and build it if yes instead of just getting the
> latest version on A in the repository.
Is this just a matter of adding "-U" to maven options? Or is there more
to it?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

RE : Re: Hudson dependencies

Plante, David
In reply to this post by Plante, David

Hi,

The problem is not in maven.

Here the situation again, more clearly I wish :

For example :
 
We have 2 maven projects named A and B.
Project B depends on project A.

I want to be sure that before Hudson builds B, it tries to build A so
that B will be build against the latest checked-in revision of A.


Thanks.


-----Message d'origine-----
De : Kohsuke Kawaguchi [mailto:[hidden email]]
Envoyé : vendredi, novembre 2, 2007 20:18
À : [hidden email]
Objet : Re: Hudson dependencies


Plante, David wrote:

> Hi,
>  
> I have a question about the management dependencies of Hudson.
>  
> I currently have a Maven  project with many dependencies. Now, when I
> build, Hudson will get the latest version of the project dependencies
> in the repository. Problem is that I would like Hudson to check the
> version of the dependencies with the repository and build them if
> theres a difference. Is that possible ?
>  
> For example :
>  
> If we have 2 projects named A and B.
> B have a dependency on A.
>  
> If I make a manual build of B, i would like Hudson to go check if any
> changes were made in A and build it if yes instead of just getting the
> latest version on A in the repository.

Is this just a matter of adding "-U" to maven options? Or is there more
to it?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]
  _____  

"Ce message est confidentiel, à l'usage exclusif du destinataire
ci-dessus et son contenu ne représente en aucun cas un engagement de la
part de AXA, sauf en cas de stipulation expresse et par écrit de la part
de AXA. Toute publication, utilisation ou diffusion, même partielle,
doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
message, merci d'en avertir immédiatement l'expéditeur."

"This e-mail message is confidential, for the exclusive use of the
addressee and its contents shall not constitute a commitment by AXA,
except as otherwise specifically provided in writing by AXA. Any
unauthorized disclosure, use or dissemination, either whole or partial,
is prohibited. If you are not the intended recipient of the message,
please notify the sender immediately."

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: RE : Re: Hudson dependencies

jblack
This could be setup in hudson, but I think this is better solved in your maven setup.

So in maven, if you have two projects that are interrelated, make them both <module>s of a parent project build.  Then, maven will figure out the correct build order.  Point hudson at the parent and all is well.

If your projects cannot be nested modules as above, make project A install or deploy a SNAPSHOT version that project B consumes.  In hudson, it would not matter if B was built without A first, because B would consume the latest SNAPSHOT artifact anyway.

If you must orchestrate this in hudson, both jobs must (currently) be freestyle jobs.  In the job configs, you will see a checkbox to add inter-job dependencies.  Check it and add the hudson job A as a prerequisite for job B.


Jeff

Plante, David wrote
Hi,

The problem is not in maven.

Here the situation again, more clearly I wish :

For example :
 
We have 2 maven projects named A and B.
Project B depends on project A.

I want to be sure that before Hudson builds B, it tries to build A so
that B will be build against the latest checked-in revision of A.


Thanks.


-----Message d'origine-----
De : Kohsuke Kawaguchi [mailto:Kohsuke.Kawaguchi@Sun.COM]
Envoyé : vendredi, novembre 2, 2007 20:18
À : users@hudson.dev.java.net
Objet : Re: Hudson dependencies


Plante, David wrote:
> Hi,
>  
> I have a question about the management dependencies of Hudson.
>  
> I currently have a Maven  project with many dependencies. Now, when I
> build, Hudson will get the latest version of the project dependencies
> in the repository. Problem is that I would like Hudson to check the
> version of the dependencies with the repository and build them if
> theres a difference. Is that possible ?
>  
> For example :
>  
> If we have 2 projects named A and B.
> B have a dependency on A.
>  
> If I make a manual build of B, i would like Hudson to go check if any
> changes were made in A and build it if yes instead of just getting the
> latest version on A in the repository.

Is this just a matter of adding "-U" to maven options? Or is there more
to it?

--
Kohsuke Kawaguchi
Sun Microsystems                   kohsuke.kawaguchi@sun.com
  _____  

"Ce message est confidentiel, à l'usage exclusif du destinataire
ci-dessus et son contenu ne représente en aucun cas un engagement de la
part de AXA, sauf en cas de stipulation expresse et par écrit de la part
de AXA. Toute publication, utilisation ou diffusion, même partielle,
doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
message, merci d'en avertir immédiatement l'expéditeur."

"This e-mail message is confidential, for the exclusive use of the
addressee and its contents shall not constitute a commitment by AXA,
except as otherwise specifically provided in writing by AXA. Any
unauthorized disclosure, use or dissemination, either whole or partial,
is prohibited. If you are not the intended recipient of the message,
please notify the sender immediately."

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@hudson.dev.java.net
For additional commands, e-mail: users-help@hudson.dev.java.net
Reply | Threaded
Open this post in threaded view
|

Re: RE : Re: Hudson dependencies

Péter Kovács
Sorry for the newbie question, but is SNAPSHOT a Hudson concept/notion?

Thanks
Peter

On 11/5/07, jblack <[hidden email]> wrote:

>
> This could be setup in hudson, but I think this is better solved in your
> maven setup.
>
> So in maven, if you have two projects that are interrelated, make them both
> <module>s of a parent project build.  Then, maven will figure out the
> correct build order.  Point hudson at the parent and all is well.
>
> If your projects cannot be nested modules as above, make project A install
> or deploy a SNAPSHOT version that project B consumes.  In hudson, it would
> not matter if B was built without A first, because B would consume the
> latest SNAPSHOT artifact anyway.
>
> If you must orchestrate this in hudson, both jobs must (currently) be
> freestyle jobs.  In the job configs, you will see a checkbox to add
> inter-job dependencies.  Check it and add the hudson job A as a prerequisite
> for job B.
>
>
> Jeff
>
>
> Plante, David wrote:
> >
> >
> > Hi,
> >
> > The problem is not in maven.
> >
> > Here the situation again, more clearly I wish :
> >
> > For example :
> >
> > We have 2 maven projects named A and B.
> > Project B depends on project A.
> >
> > I want to be sure that before Hudson builds B, it tries to build A so
> > that B will be build against the latest checked-in revision of A.
> >
> >
> > Thanks.
> >
> >
> > -----Message d'origine-----
> > De : Kohsuke Kawaguchi [mailto:[hidden email]]
> > Envoyé : vendredi, novembre 2, 2007 20:18
> > À : [hidden email]
> > Objet : Re: Hudson dependencies
> >
> >
> > Plante, David wrote:
> >> Hi,
> >>
> >> I have a question about the management dependencies of Hudson.
> >>
> >> I currently have a Maven  project with many dependencies. Now, when I
> >> build, Hudson will get the latest version of the project dependencies
> >> in the repository. Problem is that I would like Hudson to check the
> >> version of the dependencies with the repository and build them if
> >> theres a difference. Is that possible ?
> >>
> >> For example :
> >>
> >> If we have 2 projects named A and B.
> >> B have a dependency on A.
> >>
> >> If I make a manual build of B, i would like Hudson to go check if any
> >> changes were made in A and build it if yes instead of just getting the
> >> latest version on A in the repository.
> >
> > Is this just a matter of adding "-U" to maven options? Or is there more
> > to it?
> >
> > --
> > Kohsuke Kawaguchi
> > Sun Microsystems                   [hidden email]
> >   _____
> >
> > "Ce message est confidentiel, à l'usage exclusif du destinataire
> > ci-dessus et son contenu ne représente en aucun cas un engagement de la
> > part de AXA, sauf en cas de stipulation expresse et par écrit de la part
> > de AXA. Toute publication, utilisation ou diffusion, même partielle,
> > doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
> > message, merci d'en avertir immédiatement l'expéditeur."
> >
> > "This e-mail message is confidential, for the exclusive use of the
> > addressee and its contents shall not constitute a commitment by AXA,
> > except as otherwise specifically provided in writing by AXA. Any
> > unauthorized disclosure, use or dissemination, either whole or partial,
> > is prohibited. If you are not the intended recipient of the message,
> > please notify the sender immediately."
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Hudson-dependencies-tf4738912.html#a13589917
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Re: RE : Re: Hudson dependencies

ruel loehr
No.   Standard build/release notation.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Peter Kovacs
Sent: Wednesday, November 07, 2007 1:30 PM
To: [hidden email]
Subject: Re: RE : Re: Hudson dependencies

Sorry for the newbie question, but is SNAPSHOT a Hudson concept/notion?

Thanks
Peter

On 11/5/07, jblack <[hidden email]> wrote:

>
> This could be setup in hudson, but I think this is better solved in your
> maven setup.
>
> So in maven, if you have two projects that are interrelated, make them both
> <module>s of a parent project build.  Then, maven will figure out the
> correct build order.  Point hudson at the parent and all is well.
>
> If your projects cannot be nested modules as above, make project A install
> or deploy a SNAPSHOT version that project B consumes.  In hudson, it would
> not matter if B was built without A first, because B would consume the
> latest SNAPSHOT artifact anyway.
>
> If you must orchestrate this in hudson, both jobs must (currently) be
> freestyle jobs.  In the job configs, you will see a checkbox to add
> inter-job dependencies.  Check it and add the hudson job A as a prerequisite
> for job B.
>
>
> Jeff
>
>
> Plante, David wrote:
> >
> >
> > Hi,
> >
> > The problem is not in maven.
> >
> > Here the situation again, more clearly I wish :
> >
> > For example :
> >
> > We have 2 maven projects named A and B.
> > Project B depends on project A.
> >
> > I want to be sure that before Hudson builds B, it tries to build A so
> > that B will be build against the latest checked-in revision of A.
> >
> >
> > Thanks.
> >
> >
> > -----Message d'origine-----
> > De : Kohsuke Kawaguchi [mailto:[hidden email]]
> > Envoyé : vendredi, novembre 2, 2007 20:18
> > À : [hidden email]
> > Objet : Re: Hudson dependencies
> >
> >
> > Plante, David wrote:
> >> Hi,
> >>
> >> I have a question about the management dependencies of Hudson.
> >>
> >> I currently have a Maven  project with many dependencies. Now, when I
> >> build, Hudson will get the latest version of the project dependencies
> >> in the repository. Problem is that I would like Hudson to check the
> >> version of the dependencies with the repository and build them if
> >> theres a difference. Is that possible ?
> >>
> >> For example :
> >>
> >> If we have 2 projects named A and B.
> >> B have a dependency on A.
> >>
> >> If I make a manual build of B, i would like Hudson to go check if any
> >> changes were made in A and build it if yes instead of just getting the
> >> latest version on A in the repository.
> >
> > Is this just a matter of adding "-U" to maven options? Or is there more
> > to it?
> >
> > --
> > Kohsuke Kawaguchi
> > Sun Microsystems                   [hidden email]
> >   _____
> >
> > "Ce message est confidentiel, à l'usage exclusif du destinataire
> > ci-dessus et son contenu ne représente en aucun cas un engagement de la
> > part de AXA, sauf en cas de stipulation expresse et par écrit de la part
> > de AXA. Toute publication, utilisation ou diffusion, même partielle,
> > doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce
> > message, merci d'en avertir immédiatement l'expéditeur."
> >
> > "This e-mail message is confidential, for the exclusive use of the
> > addressee and its contents shall not constitute a commitment by AXA,
> > except as otherwise specifically provided in writing by AXA. Any
> > unauthorized disclosure, use or dissemination, either whole or partial,
> > is prohibited. If you are not the intended recipient of the message,
> > please notify the sender immediately."
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Hudson-dependencies-tf4738912.html#a13589917
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE : RE: Re: RE : Re: Hudson dependencies

Plante, David
In reply to this post by Plante, David




No its just a terminology used to indicate a development version.

In development.
Version = 1.0 SNAPSHOT.

In Prod
Version = 1.0



-----Message d'origine-----
De : Loehr, Ruel [mailto:[hidden email]]
Envoyé : mercredi, novembre 7, 2007 14:52
À : [hidden email]
Objet : RE: Re: RE : Re: Hudson dependencies


No.   Standard build/release notation.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Peter Kovacs
Sent: Wednesday, November 07, 2007 1:30 PM
To: [hidden email]
Subject: Re: RE : Re: Hudson dependencies

Sorry for the newbie question, but is SNAPSHOT a Hudson concept/notion?

Thanks
Peter

On 11/5/07, jblack <[hidden email]> wrote:

>
> This could be setup in hudson, but I think this is better solved in
> your maven setup.
>
> So in maven, if you have two projects that are interrelated, make them
> both <module>s of a parent project build.  Then, maven will figure out
> the correct build order.  Point hudson at the parent and all is well.
>
> If your projects cannot be nested modules as above, make project A
> install or deploy a SNAPSHOT version that project B consumes.  In
> hudson, it would not matter if B was built without A first, because B
> would consume the latest SNAPSHOT artifact anyway.
>
> If you must orchestrate this in hudson, both jobs must (currently) be
> freestyle jobs.  In the job configs, you will see a checkbox to add
> inter-job dependencies.  Check it and add the hudson job A as a
> prerequisite for job B.
>
>
> Jeff
>
>
> Plante, David wrote:
> >
> >
> > Hi,
> >
> > The problem is not in maven.
> >
> > Here the situation again, more clearly I wish :
> >
> > For example :
> >
> > We have 2 maven projects named A and B.
> > Project B depends on project A.
> >
> > I want to be sure that before Hudson builds B, it tries to build A
> > so that B will be build against the latest checked-in revision of A.
> >
> >
> > Thanks.
> >
> >
> > -----Message d'origine-----
> > De : Kohsuke Kawaguchi [mailto:[hidden email]]
> > Envoyé : vendredi, novembre 2, 2007 20:18
> > À : [hidden email]
> > Objet : Re: Hudson dependencies
> >
> >
> > Plante, David wrote:
> >> Hi,
> >>
> >> I have a question about the management dependencies of Hudson.
> >>
> >> I currently have a Maven  project with many dependencies. Now, when
> >> I build, Hudson will get the latest version of the project
> >> dependencies in the repository. Problem is that I would like Hudson
> >> to check the version of the dependencies with the repository and
> >> build them if theres a difference. Is that possible ?
> >>
> >> For example :
> >>
> >> If we have 2 projects named A and B.
> >> B have a dependency on A.
> >>
> >> If I make a manual build of B, i would like Hudson to go check if
> >> any changes were made in A and build it if yes instead of just
> >> getting the latest version on A in the repository.
> >
> > Is this just a matter of adding "-U" to maven options? Or is there
> > more to it?
> >
> > --
> > Kohsuke Kawaguchi
> > Sun Microsystems                   [hidden email]
> >   _____
> >
> > "Ce message est confidentiel, à l'usage exclusif du destinataire
> > ci-dessus et son contenu ne représente en aucun cas un engagement de
> > la part de AXA, sauf en cas de stipulation expresse et par écrit de
> > la part de AXA. Toute publication, utilisation ou diffusion, même
> > partielle, doit être autorisée préalablement. Si vous n'êtes pas
> > destinataire de ce message, merci d'en avertir immédiatement
> > l'expéditeur."
> >
> > "This e-mail message is confidential, for the exclusive use of the
> > addressee and its contents shall not constitute a commitment by AXA,
> > except as otherwise specifically provided in writing by AXA. Any
> > unauthorized disclosure, use or dissemination, either whole or
> > partial, is prohibited. If you are not the intended recipient of the
> > message, please notify the sender immediately."
> >
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Hudson-dependencies-tf4738912.html#a13589917
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: RE : Re: Hudson dependencies

Jean-Baptiste Quenot
In reply to this post by Plante, David
Dear David,

How are your builds triggered?  Are you using SCMTrigger (builds
triggered by commits) or only manual builds?

I also faced this problem when using SCMTrigger and finally implement
an experimental feature to do synchronous polling in the order of
dependencies, see
http://caraldi.com/jbq/blog/2007/10/10/Better-SCM-polling-for-Hudson/
--
Jean-Baptiste Quenot
http://caraldi.com/jbq/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]