You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by James Russo <jr...@halo3.net> on 2009/09/10 22:20:14 UTC
question re: CI builds and maven.
Hello,
This is likely more of a software engineering related maven
question. With the concept of snapshots and versioned artifacts where
would a continuous build system come into place? How do others use it? I
guess you really have two options, the CI system can produce snapshots
or it can produce version'd releases. I would imagine that you would
want to have the CI server publish these artifacts back to your local
internal repository..
So, how do others use continuous integration servers like hudson in
their maven environment?
thanks!
-jr
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: question re: CI builds and maven.
Posted by Todd Thiessen <th...@nortel.com>.
SNAPSHOTS are a very similar concept. You work toward a 2.0.1 release,
so your development builds have a version of 2.0.1-SNAPSHOT as you work
toward a final release.
The concept of "release" typcically means more than just a CI build. A
released artifact on a repo generally never gets deleted but a developer
CI build you typically do want to purge at some point. SNAPSHOTs work
with this in mind.
---
Todd Thiessen
> -----Original Message-----
> From: James Russo [mailto:jr@halo3.net]
> Sent: Thursday, September 10, 2009 4:32 PM
> To: Maven Users List
> Subject: Re: question re: CI builds and maven.
>
> Thanks, I guess it really could work either way.
>
> I've normally used to having some type of automated build
> which eventually gets released as you move it forward (ie:
> v2.0.1.xyz, the xyz build of 2.0.1 is what ships), but what
> you are saying is just get things tested/integrated/refined
> by way of the snapshot artifacts from CI and then perform the
> release what that is all good.
>
> I still need to read-up on the standard way of doing maven releases.
> Haven't gotten that far yet..
>
> -jr
>
>
> Todd Thiessen wrote:
> > CI I believe would use SNAPSHOTS. CI and SNAPSHOTs are a
> great match.
> > It would be somewhat more complicated to use releases. And
> you would
> > deploy to your maven repository so anyone else could then
> download to
> > their local.
> >
> > ---
> > Todd Thiessen
> >
> >
> >
> >> -----Original Message-----
> >> From: James Russo [mailto:jr@halo3.net]
> >> Sent: Thursday, September 10, 2009 4:20 PM
> >> To: Maven Users List
> >> Subject: question re: CI builds and maven.
> >>
> >> Hello,
> >>
> >> This is likely more of a software engineering related maven
> >> question. With the concept of snapshots and versioned
> artifacts where
> >> would a continuous build system come into place? How do others use
> >> it? I guess you really have two options, the CI system can produce
> >> snapshots or it can produce version'd releases. I would
> imagine that
> >> you would want to have the CI server publish these
> artifacts back to
> >> your local internal repository..
> >>
> >> So, how do others use continuous integration servers like
> hudson in
> >> their maven environment?
> >>
> >> thanks!
> >> -jr
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: question re: CI builds and maven.
Posted by James Russo <jr...@halo3.net>.
Thanks, I guess it really could work either way.
I've normally used to having some type of automated build which
eventually gets released as you move it forward (ie: v2.0.1.xyz, the xyz
build of 2.0.1 is what ships), but what you are saying is just get
things tested/integrated/refined by way of the snapshot artifacts from
CI and then perform the release what that is all good.
I still need to read-up on the standard way of doing maven releases.
Haven't gotten that far yet..
-jr
Todd Thiessen wrote:
> CI I believe would use SNAPSHOTS. CI and SNAPSHOTs are a great match. It
> would be somewhat more complicated to use releases. And you would deploy
> to your maven repository so anyone else could then download to their
> local.
>
> ---
> Todd Thiessen
>
>
>
>> -----Original Message-----
>> From: James Russo [mailto:jr@halo3.net]
>> Sent: Thursday, September 10, 2009 4:20 PM
>> To: Maven Users List
>> Subject: question re: CI builds and maven.
>>
>> Hello,
>>
>> This is likely more of a software engineering related
>> maven question. With the concept of snapshots and versioned
>> artifacts where would a continuous build system come into
>> place? How do others use it? I guess you really have two
>> options, the CI system can produce snapshots or it can
>> produce version'd releases. I would imagine that you would
>> want to have the CI server publish these artifacts back to
>> your local internal repository..
>>
>> So, how do others use continuous integration servers like
>> hudson in their maven environment?
>>
>> thanks!
>> -jr
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: question re: CI builds and maven.
Posted by Todd Thiessen <th...@nortel.com>.
CI I believe would use SNAPSHOTS. CI and SNAPSHOTs are a great match. It
would be somewhat more complicated to use releases. And you would deploy
to your maven repository so anyone else could then download to their
local.
---
Todd Thiessen
> -----Original Message-----
> From: James Russo [mailto:jr@halo3.net]
> Sent: Thursday, September 10, 2009 4:20 PM
> To: Maven Users List
> Subject: question re: CI builds and maven.
>
> Hello,
>
> This is likely more of a software engineering related
> maven question. With the concept of snapshots and versioned
> artifacts where would a continuous build system come into
> place? How do others use it? I guess you really have two
> options, the CI system can produce snapshots or it can
> produce version'd releases. I would imagine that you would
> want to have the CI server publish these artifacts back to
> your local internal repository..
>
> So, how do others use continuous integration servers like
> hudson in their maven environment?
>
> thanks!
> -jr
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: question re: CI builds and maven.
Posted by Stephen Connolly <st...@gmail.com>.
The Sonatype book
2009/9/10 James Russo <jr...@halo3.net>:
> Thanks Wes,
>
> I understand. I guess for me, I'm really looking to automate the release
> portion of things. So, when I fix something or commit a change (to a version
> already released and deployed), I can just wait at the end of this big
> machine (build server) for a new release to be created with a new build
> number on it ready to go.
>
> I would think you would want to post snapshots from the CI server to the
> repo so that all other developers would be constantly getting the snapshots
> of dependent artifacts without someone having to do a deploy. The CI server
> is doing the deploy each time there is a SCM change.
>
> Any good place to read more about this stuff? Like how to organize svn in a
> way which permits you to fix bugs and create features at the same time..What
> version do you leave on the trunk, are you working on new versions/features
> in branches, etc. I'd be interested in hearing about what convention and
> assumptions maven uses in this regard with the release module.
>
> thanks,
>
> -jr
>
> Wes Wannemacher wrote:
>>
>> I use CI to make sure that unit tests all still pass in other
>> artifacts. For instance, I make changes in artifactA and somewhere
>> down a dependency chain, artifactB is affected... I may not realize
>> that my change breaks artifactB, I may not even know that artifactB
>> exists, but if the CI build shows test failures, someone knows where
>> to start looking (the changes the initiated the build?).
>>
>> The CI does push to our nexus repo, but to me the fact that it can do
>> that is irrelevant.
>>
>> -Wes
>>
>> On Thu, Sep 10, 2009 at 4:20 PM, James Russo <jr...@halo3.net> wrote:
>>
>>>
>>> Hello,
>>>
>>> This is likely more of a software engineering related maven question.
>>> With
>>> the concept of snapshots and versioned artifacts where would a continuous
>>> build system come into place? How do others use it? I guess you really
>>> have
>>> two options, the CI system can produce snapshots or it can produce
>>> version'd
>>> releases. I would imagine that you would want to have the CI server
>>> publish
>>> these artifacts back to your local internal repository..
>>>
>>> So, how do others use continuous integration servers like hudson in their
>>> maven environment?
>>>
>>> thanks!
>>> -jr
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>
>>
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: question re: CI builds and maven.
Posted by James Russo <jr...@halo3.net>.
Thanks Wes,
I understand. I guess for me, I'm really looking to automate the
release portion of things. So, when I fix something or commit a change
(to a version already released and deployed), I can just wait at the end
of this big machine (build server) for a new release to be created with
a new build number on it ready to go.
I would think you would want to post snapshots from the CI server to the
repo so that all other developers would be constantly getting the
snapshots of dependent artifacts without someone having to do a deploy.
The CI server is doing the deploy each time there is a SCM change.
Any good place to read more about this stuff? Like how to organize svn
in a way which permits you to fix bugs and create features at the same
time..What version do you leave on the trunk, are you working on new
versions/features in branches, etc. I'd be interested in hearing about
what convention and assumptions maven uses in this regard with the
release module.
thanks,
-jr
Wes Wannemacher wrote:
> I use CI to make sure that unit tests all still pass in other
> artifacts. For instance, I make changes in artifactA and somewhere
> down a dependency chain, artifactB is affected... I may not realize
> that my change breaks artifactB, I may not even know that artifactB
> exists, but if the CI build shows test failures, someone knows where
> to start looking (the changes the initiated the build?).
>
> The CI does push to our nexus repo, but to me the fact that it can do
> that is irrelevant.
>
> -Wes
>
> On Thu, Sep 10, 2009 at 4:20 PM, James Russo <jr...@halo3.net> wrote:
>
>> Hello,
>>
>> This is likely more of a software engineering related maven question. With
>> the concept of snapshots and versioned artifacts where would a continuous
>> build system come into place? How do others use it? I guess you really have
>> two options, the CI system can produce snapshots or it can produce version'd
>> releases. I would imagine that you would want to have the CI server publish
>> these artifacts back to your local internal repository..
>>
>> So, how do others use continuous integration servers like hudson in their
>> maven environment?
>>
>> thanks!
>> -jr
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>
>
>
>
Re: question re: CI builds and maven.
Posted by Wes Wannemacher <we...@wantii.com>.
I use CI to make sure that unit tests all still pass in other
artifacts. For instance, I make changes in artifactA and somewhere
down a dependency chain, artifactB is affected... I may not realize
that my change breaks artifactB, I may not even know that artifactB
exists, but if the CI build shows test failures, someone knows where
to start looking (the changes the initiated the build?).
The CI does push to our nexus repo, but to me the fact that it can do
that is irrelevant.
-Wes
On Thu, Sep 10, 2009 at 4:20 PM, James Russo <jr...@halo3.net> wrote:
> Hello,
>
> This is likely more of a software engineering related maven question. With
> the concept of snapshots and versioned artifacts where would a continuous
> build system come into place? How do others use it? I guess you really have
> two options, the CI system can produce snapshots or it can produce version'd
> releases. I would imagine that you would want to have the CI server publish
> these artifacts back to your local internal repository..
>
> So, how do others use continuous integration servers like hudson in their
> maven environment?
>
> thanks!
> -jr
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Wes Wannemacher
Head Engineer, WanTii, Inc.
Need Training? Struts, Spring, Maven, Tomcat...
Ask me for a quote!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org