*Jeff, Jeremy:**
*
update:
1) I released first version of the the plugin.
https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
2) see if you can make sense out of it.
3) please file issues
https://github.com/barchart/barchart-jenkins-cascade-plugin/issues
and improve documentation
https://github.com/barchart/barchart-jenkins-cascade-plugin/wiki
Thank you,
Andrei
-------- Original Message --------
Subject: How to better manage cascading releases.
From: Andrei Pozolotin <[email protected]>
To: [email protected]
Cc: Jeff <[email protected]>, Jeremy Jongsma <[email protected]>
Date: Mon 04 Mar 2013 08:26:14 AM CST
> update:
>
> 1) extending maven-release-plugin / jenkins m2release by itself,
> http://maven.apache.org/maven-release/maven-release-plugin/
> https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin
> will not work - need orchestration plugin.
>
> 2) cascade orchestration plugin is here, 30% done:
> https://github.com/barchart/barchart-jenkins-cascade-plugin
>
> 3) proposed target project family repository layout is here
> https://github.com/barchart/barchart-jenkins-tester
>
> feedback & code review is appreciated.
>
> -------- Original Message --------
> Subject: Re: maven-release-plugin : How to better manage cascading
> releases
> From: Jeff <[email protected]>
> To: [email protected]
> Date: Thu 28 Feb 2013 12:20:14 PM CST
>> 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 <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> 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 Thu, Feb 28, 2013 at 10:54 AM, Stephen Connolly
>> <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>
>> 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 <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Does github have a maven repository?
>>
>>
>> On Thu, Feb 28, 2013 at 7:17 AM, Andrei Pozolotin
>> <[email protected]
>> <mailto:[email protected]>> 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 emulate our most interesting use cases.
>>
>> what do you think?
>>
>> Andrei.
>>
>>
>> On Tuesday, February 26, 2013 12:06:16 AM UTC-6,
>> Andrei Pozolotin wrote:
>>
>> Hello, there!
>>
>> I am curious : "How to better manage
>> cascading releases"
>> for the following use case and what you think
>> about possible solution:
>>
>> #################################
>>
>>
>> Releasing core bundles and dependent bundles
>>
>> Changing the API of a core bundle for an
>> application requires a rebuild of everything
>> down the line in order to use the new
>> feature. For projects with large numbers of
>> modules (platform, news) this is a very
>> lengthy process of splitting the bundles into
>> dependency phases, then for each phase,
>> releasing a new version of each bundle,
>> updating the next phase's bundles with the
>> newly released versions, and then releasing
>> next phase's bundles, etc, etc. This can be a
>> multiple hour process with Jenkins,
>> compounded by the fact that you can only
>> release one sub-project at a time in a Git
>> repository to avoid push conflicts causing
>> the build to fail. This process occurs much
>> more frequently than I would have originally
>> assumed. Right now I have a bash script that
>> attempts to automate this for news with a
>> combination of the maven release and version
>> plugins, but a better generic solution would
>> be very welcome.
>>
>> *Proposal: Modify Jenkins maven release
>> plugin with the following behavior:*
>>
>> 1.
>>
>> Add a "Cascade release dependent
>> projects" checkbox on release page
>>
>> 2.
>>
>> After the release completes, look for
>> jobs that are explicitly dependent on the
>> pre-release snapshot version
>>
>> 3.
>>
>> Update these dependent modules with the
>> newly release version, and trigger a
>> Maven release on them as well
>>
>> 4.
>>
>> Failing releases should be skipped, and
>> then trigger a build failure at the very
>> end, with clearly noted messages as to
>> which sub-tree failed so the user can
>> check the logs and manually cascade
>> release the subtree
>>
>> Step c) would need some cycle detection to
>> support scenarios where B and C depend on A,
>> but C also depends on B - both A and B would
>> have to be released before C could be released.
>>
>> #################################
>>
>> Thank you,
>>
>> Andrei
>>
>> --
>> You received this message because you are subscribed
>> to the Google Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving
>> emails from it, send an email to
>> [email protected]
>> <mailto:jenkinsci-users%[email protected]>.
>> For more options, visit
>> https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>>
>>
>> --
>> Jeff Vincent
>>
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/rjeffreyvincent
>> I ♥ DropBox <http://db.tt/9O6LfBX> !!
>> --
>> You received this message because you are subscribed to
>> the Google Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails
>> from it, send an email to
>> [email protected]
>> <mailto:jenkinsci-users%[email protected]>.
>> For more options, visit
>> https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to a
>> topic in the Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>>
>> https://groups.google.com/d/topic/jenkinsci-users/4OZsB9LV6nE/unsubscribe?hl=en.
>> To unsubscribe from this group and all its topics, send an
>> email to [email protected]
>> <mailto:jenkinsci-users%[email protected]>.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to [email protected]
>> <mailto:jenkinsci-users%[email protected]>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>>
>>
>>
>> --
>> Jeff Vincent
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/rjeffreyvincent
>> I ♥ DropBox <http://db.tt/9O6LfBX> !!
>> --
>> You received this message because you are subscribed to a topic in
>> the Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/4OZsB9LV6nE/unsubscribe?hl=en.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
