Stephen
OK! We won't! :-) Thank you,
Andrei
Original Message
Subject: Re: maven-release-plugin : How to better manage cascading releases
From: Stephen Connolly
To: jenkinsci-users@googlegroups.com
Date: Thu 28 Feb 2013 10:54:54 AM CST
> https://docs.sona
ttings.xml
alternatively, we can setup shared maven repo on Amazon S3 or
CloudBees@DEV
Thank you,
Andrei
Original Message
Subject: Re: maven-release-plugin : How to better manage cascading releases
From: Jeff
To: jenkinsci-users@googlegroups.com
Date: Thu 28 Feb
I would guess we would likely want/need both, unless there is a way to tell
Maven to "deploy" snapshot or release artifacts only to the local
repository. If it is possible, I don't know how to do that.
On Thu, Feb 28, 2013 at 11:14 AM, Jeremy Jongsma wrote:
> I assume he is referring to Git rep
I assume he is referring to Git repositories, not Maven repositories, for
hosting a set of mock projects with inter-dependencies that are
representative of our use cases.
Andrei, if you have a repository available, please grant me access and I'll
be happy to contribute a use case example.
-j
On
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
Please don't host your own maven repositories on an SCM
On 28 February 2013 16:50, Jeff wrote:
> Does github have a maven repository?
>
>
> On Thu, Feb 28, 2013 at 7:17 AM, Andrei Pozolotin <
> andrei.pozolo
Does github have a maven repository?
On Thu, Feb 28, 2013 at 7:17 AM, Andrei Pozolotin <
andrei.pozolo...@gmail.com> wrote:
> *Jeff, Keith, Jeremy:*
>
> so it seems we have few different use cases in mind between us.
>
> it would probably help if we create 2-3 mock repositories on github
> to em
*Jeff, Keith, Jeremy:*
so it seems we have few different use cases in mind between us.
it would probably help if we create 2-3 mock repositories on github
to emulate our most interesting use cases.
what do you think?
Andrei.
On Tuesday, February 26, 2013 12:06:16 AM UTC-6, Andrei Pozolotin wr
https://github.com/barchart/barchart-jenkins-m2release-plugin/wiki/Algorithm-Flow---Brain-Dump
This brain dump now has me thinking that cascade releasing from the highest
level project instead of lowest would be a cleaner and less "magical"
solution; when triggering a release of a leaf project,
Adding those two goals is a good idea, Keith - I should add them to our
builds as well. Although, I would still have to kick off 15-20 sequential
releases after a core project is updated with a new API I need access to.
The two use cases we have right now involve single, large parent projects
t
Jeff, Keith: would you be interested in collaborating on a jenkins
plugin for this? Andrei.
Original Message
Subject: Re: maven-release-plugin : How to better manage cascading releases
From: Keith Collison
To: jenkinsci-users@googlegroups.com
Date: Tue 26 Feb 2013 09:40:59 PM
Keith: very good points, thank you very much for sharing. Andrei.
Original Message
Subject: Re: maven-release-plugin : How to better manage cascading releases
From: Keith Collison
To: jenkinsci-users@googlegroups.com
Date: Tue 26 Feb 2013 09:40:59 PM CST
> We've put
Jeff: thanks for the feedback. Andrei.
Original Message
Subject: Re: maven-release-plugin : How to better manage cascading releases
From: Jeff
To: jenkinsci-users@googlegroups.com
Date: Tue 26 Feb 2013 12:14:07 AM CST
> I've thought about this too, there could be a l
We've put in place the first half of this by adding these goals to our
maven builds:
versions:use-releases scm:checkin
The former will update a pom to use released versions of snapshot
dependencies. The latter commits any resulting changes to the pom.xml. We
also use the "includesList" param
I've thought about this too, there could be a logistics issues with
how/where to find the dependent projects unless you have a multi-module POM
(parent + children) or some other way to either tell it where to find the
dependencies or impose a rigid project/folder structure.
I wonder if this type o
14 matches
Mail list logo
