[
https://issues.apache.org/jira/browse/MDEPLOY-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965807#comment-17965807
]
Olivier Lamy commented on MDEPLOY-199:
--------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#236|https://github.com/apache/maven-deploy-plugin/issues/236].
> Ability to set properties containing the SNAPSHOT id and hash information
> assigned by repository.
> -------------------------------------------------------------------------------------------------
>
> Key: MDEPLOY-199
> URL: https://issues.apache.org/jira/browse/MDEPLOY-199
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: New Feature
> Components: deploy:deploy
> Affects Versions: 2.8.2
> Reporter: Jeff Vincent
> Priority: Minor
>
> I'm building a continuous deployment pipeline with Jenkins and GoCD and when
> SNAPSHOT artifacts are published, I want to trigger the pipeline with the
> EXACT SNAPSHOT version generated by the deploy to Nexus (or equivalent) in
> order to make our deployment pipelines.
> In our case we are using SaltStack to provision our systems and we are
> pulling the WAR file directly from Nexus as a 'managed file' in saltstack.
> It needs the SHA1 or MD5 hash for files hosted externally to be able to
> detect changes.
> I'd like a way to be able to retrieve the SNAPSHOT version and the SHA1 (and
> maybe MD5) hash of the artifact and be able to write them to a file or set
> environment variables.
> I'm not versed in Maven to know exactly what is possible in this regard since
> things like resource filtering happens before the build and this is after the
> build has been published.
> Regardless, the hope would be to get that data as part of the build process
> to be used on steps later in the CI/CD pipeline process.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
