|
Hi,
Any clues when jenkins will support building individual modules for maven 3 ? Currently it displays message " Building single Maven modules is not implemented for Maven 3, yet!" -Raj |
|
What's the full use case?
Also - if you're doing that - why not break them into individual repositories or modules and just rely on dependencies? Jenkins also has an option to "build just what's changed". Maybe that'd be a good compromise? On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: Hi, |
|
Scenario is this :
Lets say one maven projects has 5 modules. Developer changed only one module and committed it to Version control. Here i was looking for an option where developer and trigger build for only this particular module. As Jenkins surely understand root pom and modules in it and it even gives option to build individual modules but that doesnt work for maven 3 and gives the message " Building single Maven modules is not implemented for Maven 3, yet!" As per your suggestion i think you are refering to "poll scm" option in jenkins for building only what's changed ? So lets say if i enable this then jenkins will pull down only the files that got changed but what about the dependencies of these files which are not changed ? Will jenkins figure it self and bring those down too ? -Raj On Wed, Apr 25, 2012 at 7:19 AM, Maven User <[hidden email]> wrote: What's the full use case? |
|
Nope - expand the maven config in your project - look for the "
On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote:
On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote:
|
|
Is there any jira entry ?
I could have a look later to fix that. As *definitely* the native maven plugin is a *very* nice feature of Jenkins :P 2012/4/25 Maven User <[hidden email]>: > Nope - expand the maven config in your project - look for the "Incremental > build - only build changed modules" option. > > > > > > On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: >> >> Scenario is this : >> >> Lets say one maven projects has 5 modules. >> Developer changed only one module and committed it to Version control. >> >> Here i was looking for an option where developer and trigger build for >> only this particular module. As Jenkins surely understand root pom and >> modules in it and it even gives option to build individual modules but that >> doesnt work for maven 3 and gives the message " Building single Maven >> modules is not implemented for Maven 3, yet!" >> >> As per your suggestion i think you are refering to "poll scm" option in >> jenkins for building only what's changed ? So lets say if i enable this >> then jenkins will pull down only the files that got changed but what about >> the dependencies of these files which are not changed ? Will jenkins figure >> it self and bring those down too ? >> >> -Raj >> >> >> On Wed, Apr 25, 2012 at 7:19 AM, M >>> >>> What's the full use case? >>> >>> >>> Also - if you're doing that - why not break them into individual >>> repositories or modules and just rely on dependencies? >>> >>> Jenkins also has an option to "build just what's changed". Maybe that'd >>> be a good compromise? >>> >>> >>> >>> >>> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: >>>> >>>> Hi, >>>> >>>> Any clues when jenkins will support building individual modules for >>>> maven 3 ? >>>> >>>> Currently it displays message " Building single Maven modules is not >>>> implemented for Maven 3, yet!" >>>> >>>> -Raj >> >> > > On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: >> >> Scenario is this : >> >> Lets say one maven projects has 5 modules. >> Developer changed only one module and committed it to Version control. >> >> Here i was looking for an option where developer and trigger build for >> only this particular module. As Jenkins surely understand root pom and >> modules in it and it even gives option to build individual modules but that >> doesnt work for maven 3 and gives the message " Building single Maven >> modules is not implemented for Maven 3, yet!" >> >> As per your suggestion i think you are refering to "poll scm" option in >> jenkins for building only what's changed ? So lets say if i enable this >> then jenkins will pull down only the files that got changed but what about >> the dependencies of these files which are not changed ? Will jenkins figure >> it self and bring those down too ? >> >> -Raj >> >> >> On Wed, Apr 25, 2012 at 7:19 AM, Maven User: >> >>> What's the full use case? >>> >>> Also - if you're doing that - why not break them into individual >>> repositories or modules and just rely on dependencies? >>> >>> Jenkins also has an option to "build just what's changed". Maybe that'd >>> be a good compromise? >>> >>> >>> >>> >>> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: >>>> >>>> Hi, >>>> >>>> Any clues when jenkins will support building individual modules for >>>> maven 3 ? >>>> >>>> Currently it displays message " Building single Maven modules is not >>>> implemented for Maven 3, yet!" >>>> >>>> -Raj >> >> > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy |
|
Seems the Nabaztag site is up and running again and I was thinking of
updating the Nabaztag plugin to be compatible, would there be any interest? -- Kenneth H. Wieschhoff, Jr. NBA - Digital Turner Broadcasting Systems 404.509.0987 |
|
In reply to this post by Olivier Lamy-2
https://issues.jenkins-ci.org/browse/JENKINS-11964
-------- Original-Nachricht -------- > Datum: Thu, 26 Apr 2012 16:09:40 +0200 > Von: Olivier Lamy <[hidden email]> > An: [hidden email] > Betreff: Re: Maven 3 & modules > Is there any jira entry ? > I could have a look later to fix that. > As *definitely* the native maven plugin is a *very* nice feature of > Jenkins :P > > 2012/4/25 Maven User <[hidden email]>: > > Nope - expand the maven config in your project - look for the > "Incremental > > build - only build changed modules" option. > > > > > > > > > > > > On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: > >> > >> Scenario is this : > >> > >> Lets say one maven projects has 5 modules. > >> Developer changed only one module and committed it to Version control. > >> > >> Here i was looking for an option where developer and trigger build for > >> only this particular module. As Jenkins surely understand root pom and > >> modules in it and it even gives option to build individual modules but > that > >> doesnt work for maven 3 and gives the message " Building single Maven > >> modules is not implemented for Maven 3, yet!" > >> > >> As per your suggestion i think you are refering to "poll scm" option in > >> jenkins for building only what's changed ? So lets say if i enable > this > >> then jenkins will pull down only the files that got changed but what > about > >> the dependencies of these files which are not changed ? Will jenkins > figure > >> it self and bring those down too ? > >> > >> -Raj > >> > >> > >> On Wed, Apr 25, 2012 at 7:19 AM, M > >>> > >>> What's the full use case? > >>> > >>> > >>> Also - if you're doing that - why not break them into individual > >>> repositories or modules and just rely on dependencies? > >>> > >>> Jenkins also has an option to "build just what's changed". Maybe > that'd > >>> be a good compromise? > >>> > >>> > >>> > >>> > >>> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: > >>>> > >>>> Hi, > >>>> > >>>> Any clues when jenkins will support building individual modules for > >>>> maven 3 ? > >>>> > >>>> Currently it displays message " Building single Maven modules is not > >>>> implemented for Maven 3, yet!" > >>>> > >>>> -Raj > >> > >> > > > > On Wednesday, April 25, 2012 1:48:56 PM UTC-4, Rajwinder Makkar wrote: > >> > >> Scenario is this : > >> > >> Lets say one maven projects has 5 modules. > >> Developer changed only one module and committed it to Version control. > >> > >> Here i was looking for an option where developer and trigger build for > >> only this particular module. As Jenkins surely understand root pom and > >> modules in it and it even gives option to build individual modules but > that > >> doesnt work for maven 3 and gives the message " Building single Maven > >> modules is not implemented for Maven 3, yet!" > >> > >> As per your suggestion i think you are refering to "poll scm" option in > >> jenkins for building only what's changed ? So lets say if i enable > this > >> then jenkins will pull down only the files that got changed but what > about > >> the dependencies of these files which are not changed ? Will jenkins > figure > >> it self and bring those down too ? > >> > >> -Raj > >> > >> > >> On Wed, Apr 25, 2012 at 7:19 AM, Maven User: > >> > >>> What's the full use case? > >>> > >>> Also - if you're doing that - why not break them into individual > >>> repositories or modules and just rely on dependencies? > >>> > >>> Jenkins also has an option to "build just what's changed". Maybe > that'd > >>> be a good compromise? > >>> > >>> > >>> > >>> > >>> On Monday, April 23, 2012 11:55:31 AM UTC-4, Rajwinder Makkar wrote: > >>>> > >>>> Hi, > >>>> > >>>> Any clues when jenkins will support building individual modules for > >>>> maven 3 ? > >>>> > >>>> Currently it displays message " Building single Maven modules is not > >>>> implemented for Maven 3, yet!" > >>>> > >>>> -Raj > >> > >> > > > > > > -- > Olivier Lamy > Talend: http://coders.talend.com > http://twitter.com/olamy | http://linkedin.com/in/olamy |
|
In reply to this post by Wieschhoff, Kenneth
Am 26.04.12 16:26, schrieb Wieschhoff, Kenneth:
> Seems the Nabaztag site is up and running again and I was thinking of > updating the Nabaztag plugin to be compatible, would there be any interest? > Hi, IMO Nabaztag is totally useless as XFD. We tried it at work, but the problem is: If Network is down, or the API has a bug or something else goes wrong, the little rabbit is blinking and turning the ears and nobody knows what it means. And nobody wants to learn dozens of color and ear codes to know, if the build is brokne or only the WIFI is down. So the developers ignored the rabbit. Nabaztag is everything else, but easy to understand. IMHO an XFD consists only of a big red lamp and/or a train horn which give signal on build failure. -Sven -- "Ich habe vom Glauben zum Wissen konvertiert." (Abdel-Samad) |
|
++
On Friday, April 27, 2012 5:19:03 AM UTC-4, Sven Strittmatter wrote: Am 26.04.12 16:26, schrieb Wieschhoff, Kenneth: |
|
On 4/27/12 9:09 AM, "Maven User" <maven.2.user@...> wrote: ++ -- Kenneth H. Wieschhoff, Jr. NBA - Digital Turner Broadcasting Systems 404.509.0987 |
|
Dude, when you're done that please send me the script. I want to put that on my Jenkins server and have it play when a build fails!
Anthony On 2012-04-27, at 10:22 AM, Wieschhoff, Kenneth wrote:
|
| Powered by Nabble | Edit this page |
