[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis When performing a release to Artifactory with Bitbucket source - I noticed on Linux that I had to add a username and email with permissions to the repository. Don't know if this is the Artifactory plugin's or git client plugin's fault, but I didn't have to do this when releasing the same project on Windows. The error and solution I found are here:http://stackoverflow.com/questions/41288988/jenkins-artifactory-release-plugin-unable-to-commit-tag-windows-host-machineThe problem that appears to be related the Artifactory plugin is that after adding this global config, the "Override Git credentials" option that's available in the Artifactory Release Staging screen when performing a release appears to be being ignored at the end of the release process when updated poms are given their new release and snapshot versions and checked back into the repository.We provided specific user credentials with write permissions to our Bitbucket repository (say User A), but the user that ended up checking in the updated poms for the release was the user we had to configure in the Global System Config area (Say User B). This is undesirable since User A actually works on the project and is performing the release, while User B, is a Bitbucket Admin, but isn't associated with any real work on the project. In the screenshots below, it shows Jason performed the commit back to bitbucket during the release, but the user that actually peformed the release was different and had provided his credentials in the Override Git credentials section. If we don't provide a global config, then the plugin fails to commit the final changed poms back to the repository as per the stackoverflow url proided above. Add Comment
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis Attachment: globaluser_didthecommit.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis updated an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Change By: Jason Davis Attachment: global_config.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41706) "Override Git Credentials" Value Ignored During Release
Title: Message Title Jason Davis created an issue Jenkins / JENKINS-41706 "Override Git Credentials" Value Ignored During Release Issue Type: Bug Assignee: Eyal Ben Moshe Attachments: global_config.png Components: artifactory-plugin Created: 2017/Feb/03 2:12 PM Environment: git client 2.10 - linux Build agent performing the release - linux centos 6.8 jenkins 2.31 - windows 2008 R2 artifactory plugin 2.90 bitbucket.org repository Priority: Major Reporter: Jason Davis When performing a release to Artifactory with Bitbucket source - I noticed on Linux that I had to add a username and email with permissions to the repository. Don't know if this is the Artifactory plugin's or git client plugin's fault, but I didn't have to do this when releasing the same project on Windows. The error and solution I found are here: http://stackoverflow.com/questions/41288988/jenkins-artifactory-release-plugin-unable-to-commit-tag-windows-host-machine The problem that appears to be related the Artifactory plugin is that after adding this global config, the "Override Git credentials" option that's available in the Artifactory Release Staging screen when performing a release appears to be being ignored at the end of the release process when updated poms are given their new release and snapshot versions and checked back into the repository. We provided specific user credentials with write permissions to our Bitbucket repository (say User A), but the user that ended up checking in the updated poms for the release was the user we had to configure in the Global System Config area (Say Us
