[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-34368) Add Support for OAuth Key
Title: Message Title Luís Duarte created an issue Jenkins / JENKINS-34368 Add Support for OAuth Key Issue Type: Improvement Assignee: Unassigned Components: bitbucket-pullrequest-builder-plugin Created: 2016/Apr/21 9:56 AM Labels: plugin oauth credentials Priority: Major Reporter: Luís Duarte We would like to have the possibility of using an OAuth Key for integration with our BitBucket Repositories, as similar to GitHub PR Builder Plugin. e.g.: https://github.com/janinko/ghprb/blob/master/src/main/java/org/jenkinsci/plugins/ghprb/GhprbGitHubAuth.java#L156 Thanks Add Comment
[JIRA] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Luís Duarte commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Mark Waite What i'm trying to explain is that the git clone is executed with the Credentials, but the git submodule update --recursive doesn't use Credentials, therefore causing our builds to fail. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Luís Duarte edited a comment on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I was just making a suggestion to add the "--recursive" checkbox below the Repository URL so that the SubModules are cloned recursively on the first update inital clone and not a Post-Action.You have any ETA on the Git Plugin 2.5.0 Final and Git Client Plugin 1.20.0 Final ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Luís Duarte commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated I was just making a suggestion to add the "--recursive" checkbox below the Repository URL so that the SubModules are cloned recursively on the first update and not a Post-Action. You have any ETA on the Git Plugin 2.5.0 Final and Git Client Plugin 1.20.0 Final ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Luís Duarte commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Mark Waite Output 18:08:03 > git submodule update --init --recursive 18:08:09 FATAL: Command "git submodule update --init --recursive" returned status code 1: 18:08:09 stdout: 18:08:09 stderr: Cloning into 'plugins/ruby-build'... 18:08:09 Permission denied (publickey). 18:08:09 fatal: Could not read from remote repository. 18:08:09 18:08:09 Please make sure you have the correct access rights 18:08:09 and the repository exists. 18:08:09 Clone of 'git@:/.git' into submodule path 'plugins/ruby-build' failed 18:08:09 18:08:09 hudson.plugins.git.GitException: Command "git submodule update --init --recursive" returned status code 1: 18:08:09 stdout: 18:08:09 stderr: Cloning into 'plugins/ruby-build'... 18:08:09 Permission denied (publickey). 18:08:09 fatal: Could not read from remote repository. 18:08:09 18:08:09 Please make sure you have the correct access rights 18:08:09 and the repository exists. 18:08:09 Clone of 'git@:/.git' into submodule path 'plugins/ruby-build' failed The problem is that the "Advanced submodule behaviours" is not integrating properly with the Credentials Plugin, meaning it does not use the Credentials for the --recursive update modules. And we don't upload Private Keys to Slave machines. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Luís Duarte commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated Why not add a Checkbox on Repository Clone config asking if we want a recursive clone? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
