[
https://jira.codehaus.org/browse/MRELEASE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-846:
------------------------------------
Fix Version/s: (was: 2.5)
2.4.2
> m2 release plugin exposes SCM password in release.properties file
> -----------------------------------------------------------------
>
> Key: MRELEASE-846
> URL: https://jira.codehaus.org/browse/MRELEASE-846
> Project: Maven Release Plugin
> Issue Type: Bug
> Reporter: Mark Maun
> Assignee: Robert Scholte
> Fix For: 2.4.2
>
>
> When executing a maven release build using the m2 release plugin in Jenkins a
> release.properties file is created in the workspace that has the SCM
> user/password credentials in plain text. In our jenkins instance this is a
> problem since we have multiple users with access to release the same job. The
> release.properties is removed after the release build is successful. If the
> release build fails the release.properties stays in the workspace until it's
> manually deleted. This allows other users to see SCM passwords in our
> organization if they view the workspace during a release build or after one
> fails.
> 4
> If anyone has viable workarounds/solutions we can use in the meantime that
> would also be appreciated.
> Note I have a ticket open with Jenkins dev but they deferred me here:
> https://issues.jenkins-ci.org/browse/JENKINS-19416
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira