[infinispan-dev] Infinispan Managment Console versioning and releases
Vladimir Blagojevic
vblagoje at redhat.com
Thu Jan 19 09:00:06 EST 2017
Sebastian,
Seems like you solved everything already on your own. Do you still have
build issues?
Vladimir
On 2017-01-19 2:39 AM, Sebastian Laskawiec wrote:
> Just a friendly reminder...
>
> @Vladimir, @Ryan.... yes, I'm looking at YOU :)
>
> On Fri, Dec 16, 2016 at 9:22 AM, Sebastian Laskawiec
> <slaskawi at redhat.com <mailto:slaskawi at redhat.com>> wrote:
>
> Hey guys,
>
> A while ago was been talking with Ryan and Tristan about automated
> releases for Infinispan Management Console. I would like to send
> the main point for wider audience.
>
> Long story short, we were considering different versioning
> schemes, such as X.Y.Z.SHA1 or using Z as an auto-increment
> counter for console releases. The main problem we were trying to
> solve was how to release the management console more often.
>
> I would like to propose different approach - Let's stick with a
> standard versioning (X.Y.Z.[Alpha|Beta|Fina] for releases and
> X.Y.Z-SNAPSHOT for ongoing work). Then we need to embed SHA1 into
> the MANIFEST.MF to increase tracability (in other words, here I
> have an Infinispan build and I need to know which SHA1 was used to
> build the console). SNAPSHOTs will be pushed into JBoss Repository
> [1] after each commit. Infinispan master branch will have a
> SNAPSHOT dependency to the console. The tricky part are releases.
> Well, at first we need to release the console (I hope we will
> automate that in Team City). Then we can use the version plugin
> [2] to update the Infinispan source code to the latest version of
> the console. Finally, we can release the Infinispan. As a
> long-term goal, everything will happen inside a single staging
> repository in Nexus (but that's a long-term goal... first let get
> this running).
>
> If you agree to my proposal, please change the version in the
> console into 9.0.0-SNAPSHOT and retrigger [3] (automated builds
> are disabled at the moment). Next, I would kindly ask to look into
> the build logs [4][5] and give me a hint how to fix it. The NPM
> plugin is failing with some weird error. Once we are done with
> that, I will configure a Pull Request builder and release job.
>
> Thanks
> Sebastian
>
> [1]
> https://repository.jboss.org/nexus/content/repositories/snapshots/
> <https://repository.jboss.org/nexus/content/repositories/snapshots/>
> [2] http://www.mojohaus.org/versions-maven-plugin/
> <http://www.mojohaus.org/versions-maven-plugin/>
> [3]
> http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8
> <http://ci.infinispan.org/viewType.html?buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8>
> [4]
> http://ci.infinispan.org/viewLog.html?buildId=46542&buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8&tab=buildLog
> <http://ci.infinispan.org/viewLog.html?buildId=46542&buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8&tab=buildLog>
> [5]
> http://ci.infinispan.org/viewLog.html?buildId=46543&buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8&tab=buildLog
> <http://ci.infinispan.org/viewLog.html?buildId=46543&buildTypeId=Infinispan_ManagmentConsoleMasterHotspotJdk8&tab=buildLog>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20170119/11c8b5ed/attachment.html
More information about the infinispan-dev
mailing list