/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
To: jenkinsci-users@googlegroups.com
Cc: Jeff , Jeremy
ting use cases.
>
> what do you think?
>
> Andrei.
>
>
> On Tuesday, February 26, 2013 12:06:16 AM UTC-6,
> Andrei Pozolotin wrote:
>
> Hello, there!
>
>
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
;>
>>>> *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 us
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.
>>>
>>
cases.
>>
>> what do you think?
>>
>> Andrei.
>>
>>
>> On Tuesday, February 26, 2013 12:06:16 AM UTC-6, Andrei Pozolotin wrote:
>>>
>>>Hello, there!
>>>
tories 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 be
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
>
> most-dependent module (i.e. the webapp or application you want to release),
>> and then calculated what upstream dependencies needed to be released, that
>> would be ideal. Just because I've released some base library upon which 20
>> apps depend does not mean I want to cut a release of tho
upstream dependencies needed to be released, that
> would be ideal. Just because I've released some base library upon which 20
> apps depend does not mean I want to cut a release of those 20 apps.
>
>
>
>
>
>
> On Tuesday, February 26, 2013 1:06:16 AM
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
use I've released some base library upon which 20
apps depend does not mean I want to cut a release of those 20 apps.
On Tuesday, February 26, 2013 1:06:16 AM UTC-5, Andrei Pozolotin wrote:
>
> Hello, there!
>
> I am curious : "How to better manage casca
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 AP
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 a
17 matches
Mail list logo
