I'm prototyping a software promotion process in Artifactory. I'm using different repositories to represent each software state (e.g. pre-release, release candidate, release, deprecated, suspended, retired). These repositories are in a single Artifactory instance. I'm using the Move feature as the promotion method.
I need to be able to perform different processing before and after the promotion depending on the source and target promotion states. For example: Promotion: release-candidate to release Before promotion: Verify that all dependencies are in release status. If not reject the promotion. Post-Processing: Notify consumers of prior version that a new version is available Has anyone used the User Plugin's beforeMove and afterMove events to handle this? Has anyone patched Artifactory to allow for custom functionality to be wrapped around the move transaction or a similar storage transaction? Are there any other suggestions? -- View this message in context: http://forums.jfrog.org/Implementing-custom-promotion-move-processing-tp5725226p5725226.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
