[JIRA] (JENKINS-50814) provide a way to keep git credentials
Title: Message Title Dominik Bartholdi assigned an issue to rsandell Jenkins / JENKINS-50814 provide a way to keep git credentials Change By: Dominik Bartholdi Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50814) provide a way to keep git credentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-50814 provide a way to keep git credentials Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-04-16 08:19 Priority: Minor Reporter: Dominik Bartholdi This is an enhancement request to support some kind of way to tell the plugin not to delete the git credentials after the checkout. Today when ever I want to pull or push some changes from/to the remote git repository, I have to explicitly set the following configuration in may pipeline: sh "git config --global user.name 'myuser'" sh "git config --global user.email 'myu...@mycomp.com'" # no pull/push works sh "git push ..." This has the major drawback, that now my pipeline script is bound to the credentials configured in my jenkins job. I therefore request a flag/option which I can enable so this information is set (or not removed after the checkout) by the bitbucket multibranch plugin.
