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: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
