ok can you explain the ant/ivy build pipeline implementing promotion you did with the help of my team mates?
(notice I won't be here for 1 week, so won't be able to continue the discussion for the moment, but the topic is worth more discussion) Regards, Hervé Le jeudi 20 décembre 2012 12:12:22 Gábor Guta a écrit : > Yes, I want to start the build of other projects if new version of the > promoted artifact is available. > > Imagine a larger project in which 15-50 modules exists. Top level > module build is triggered by the available new modules with a specific > status i.e. performance tests run when new version of the dependencies > with integration status available, but installer generation needs new > artifact with milestone quality. Developers also prefer to work with > milestone artifacts as they need something which is more stable than > snapshot, but newer than the latest release. I hope this helped to > clarify the role of module statuses. > > Regards, Gabor > > On Thu, Dec 20, 2012 at 8:35 AM, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > > ok, I see the workflow for single artifact promotion > > > > Once this artifact is promoted, you want to update another project's > > dependency to rebuild using this (now promoted) artifact? > > Or your wish is about not rebuilding the other project but promoting its > > built result and modifying dependency to let think it was built with the > > promoted artifact? > > > > > > (notice I'm going to my day work: I won't be able to continue this > > discussion before the end of the day...) > > > > Regards, > > > > Hervé > > > > Le jeudi 20 décembre 2012 07:51:08 Gábor Guta a écrit : > >> We make the promotion of the already built artifact and we update the > >> metadata. e.g.: if the corresponding integration tests are fine, the > >> status of the artifact change to milestone. > >> > >> Regards, Gabor. > >> > >> On Thu, Dec 20, 2012 at 7:17 AM, Hervé BOUTEMY <herve.bout...@free.fr> > > > > wrote: > >> > in your ideas, do you intend to rebuild the artifact at each promotion, > >> > or > >> > make promotion of the already built artifact (then without rebuilding > >> > it), > >> > only changing its status metatada? > >> > > >> > Regards, > >> > > >> > Hervé > >> > > >> > Le mercredi 19 décembre 2012 15:37:18 Gábor Guta a écrit : > >> >> Can you give me feedback feedback / recommendation about how can I > >> >> write extensions for Maven to support a build pipeline and artifact > >> >> promotion in a "standard" way. As far as understand these issues are > >> >> common problems, because I have found many blogs describing hacks and > >> >> workarounds. I also have to mention that nexus and artifactory provide > >> >> custom fixes for these problems, but I would prefer not to be locked > >> >> to a specific vendor. I built an ant/ivy build pipeline implementing > >> >> promotion with the help of my team mates. My primary motivation is to > >> >> enable the mixing of artifacts from ant and maven builds through a > >> >> central maven repository. > >> >> > >> >> I have two main issues with the current Maven model: > >> >> - no standard way to handle traceable snapshot i.e. snapshots are > >> >> temporary and I can't push them through on the testing pipeline by > >> >> referencing to them by a unique id (build number); > >> >> - no standard way to reference to staged/promoted artifact in the > >> >> dynamic version number i.e. I can't specify in a standard way that I > >> >> want the latest artifact which passed the integration test and has > >> >> version from a specific branch. > >> >> > >> >> Proposal for promotion model: > >> >> - store status information in a POM property (introducing standard > >> >> meta data in the POM would be much nicer) e.g. integration, milestone > >> >> - write an extension which can interpret and resolve "3.3.? > >> >> latest.milestone" like notation in the version number > >> >> > >> >> Proposal for staging model: > >> >> - status information is identified by the repository location, so I > >> >> have to be able to add multiple repositories with meta data about the > >> >> status of the stored artifacts > >> >> - write an extension which can interpret and resolve "3.3.?, > >> >> latest.milestone" like notation in the version number > >> >> > >> >> > >> >> Gabor > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org
