[JIRA] (JENKINS-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title John Stephenson created an issue Jenkins / JENKINS-38092 workflow-multibranch plugin doesn't use credentials when indexing the branches Issue Type: Bug Assignee: Jesse Glick Components: workflow-multibranch-plugin Created: 2016/Sep/09 9:32 AM Environment: Jenkins is hosted in a docker container defined below: FROM jenkins:2.7.3 USER root RUN apt-get update && \ apt-get install -y ruby ruby-dev && \ apt-get -y install curl && \ curl -sL https://deb.nodesource.com/setup_6.x | bash - && \ apt-get install -y nodejs && \ apt-get install -y git && \ npm install -g jspm && \ npm install -g gulp-cli && \ apt-get install -y build-essential && \ /usr/local/bin/install-plugins.sh docker-slaves github-branch-source:1.8 \ disk-usage nested-view saferestart greenballs build-flow build-monitor build-timeout build-name-setter \ cucumber-testresult git git-client hipchat Exclusion embeddable-build-status extended-read-permission \ workflow-aggregator bitbucket Labels: pipeline git plugins Priority: Major Reporter: John Stephenson When using the mutlibranch indexing I can't connect to bitbucket due to the credentials not being used correctly. I've setup credentials for the repository and can create a single branch project that connects and pulls correctly (see the end of this description). The output from the multibranch indexing job is below. > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to https://bitbucket.org//x.git > git config remote.origin.url
[JIRA] (JENKINS-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title
John Stephenson updated an issue
Jenkins / JENKINS-38092
workflow-multibranch plugin doesn't use credentials when indexing the branches
Change By:
John Stephenson
When using the mutlibranch indexing I can't connect to bitbucket due to the credentials not being used correctly. I've setup credentials for the repository and can create a single branch project that connects and pulls correctly (see the end of this description). The output from the multibranch indexing job is below. > git rev-parse --is-inside-work-tree # timeout=10Setting origin to https://bitbucket.org//x.git > git config remote.origin.url https://bitbucket.org//x.git # timeout=10Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneFATAL: Failed to recompute children of testhudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128:stdout: stderr: remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.fatal: Authentication failed for 'https://bitbucket.org//x.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1740) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1476) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:293) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILUREAs mentioned, if I run a (different) single branch project job against the same repo on the same machine I get: {{ ln -s builds/lastSuccessfulBuild /var/jenkins_home/jobs/bosh/lastSuccessful failed: 71 Protocol errorln -s builds/lastStableBuild /var/jenkins_home/jobs/bosh/lastStable failed: 71 Protocol errorCloning the remote Git repositoryCloning repository https://bitbucket.org//x.git > git init /var/jenkins_home/workspace/bosh@script # timeout=10Fetching upstream changes from https://bitbucket.org//x.git > git --version # timeout=10* * using .gitcredentials to set credentials * > git config --local credential.username # timeout=10 > git config --local credential.helper store --file=/tmp/git7209450783850968846.credentials # timeout=10 ** > git
[JIRA] (JENKINS-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title
John Stephenson updated an issue
Jenkins / JENKINS-38092
workflow-multibranch plugin doesn't use credentials when indexing the branches
Change By:
John Stephenson
When using the mutlibranch indexing I can't connect to bitbucket due to the credentials not being used correctly. I've setup credentials for the repository and can create a single branch project that connects and pulls correctly (see the end of this description). The output from the multibranch indexing job is below. > git rev-parse --is-inside-work-tree # timeout=10Setting origin to https://bitbucket.org//x.git > git config remote.origin.url https://bitbucket.org//x.git # timeout=10Fetching & pruning origin...Fetching upstream changes from origin > git --version # timeout=10 > git -c core.askpass=true fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --pruneFATAL: Failed to recompute children of testhudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* --prune" returned status code 128:stdout: stderr: remote: Invalid username or password. If you log in via a third party service you must ensure you have an account password set in your account profile.fatal: Authentication failed for 'https://bitbucket.org//x.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1740) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1476) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:63) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:314) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:293) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILUREAs mentioned, if I run a (different) single branch project job against the same repo on the same machine I get: {{ ln -s builds/lastSuccessfulBuild /var/jenkins_home/jobs/bosh/lastSuccessful failed: 71 Protocol errorln -s builds/lastStableBuild /var/jenkins_home/jobs/bosh/lastStable failed: 71 Protocol errorCloning the remote Git repositoryCloning repository https://bitbucket.org//x.git > git init /var/jenkins_home/workspace/bosh@script # timeout=10Fetching upstream changes from https://bitbucket.org//x.git > git --version # timeout=10* * using .gitcredentials to set credentials > git config --local credential.username # timeout=10 > git config --local credential.helper store --file=/tmp/git7209450783850968846.credentials # timeout=10* * > git -c
[JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL
Title: Message Title John Stephenson commented on JENKINS-38664 Re: bitbucket source plugin fails with bad URL Thanks for your quick response. I finally got past this. Background: I'm currently setting up Jenkins in AWS and haven't setup a DNS entry for the jenkins host machine yet. I don't know if this is relevant but hey yo. For me I had : set in the Jenkins URL field for the jenkins installation but this still didn't work (I didn't change anything here). I did find that the JENKINS_URL env var should be being set. I assume it wasn't as when I explicitly added a new env var within the Jenkins web admin, this worked! The value was a copy+paste job from the Jenkins URL field that's on the same config webpage. Strange but true. Anyway, I'm now onto my next hurdle! Many thanks! John 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-38664) bitbucket source plugin fails with bad URL
Title: Message Title John Stephenson commented on JENKINS-38664 Re: bitbucket source plugin fails with bad URL Hi, I've hit this issue too. Can I can an ETA on the new version being published? You hint at a workaround with the URL being set, but I don't think I'm using any status notifications, so I don't know on what screen (bitbucket or jenkins) I should be trying to set the 'rootUrl'. Can you guide me to solution if the fix isn't going to be published soon? Many thanks! John 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-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title John Stephenson commented on JENKINS-38092 Re: workflow-multibranch plugin doesn't use credentials when indexing the branches I have done just that, with some but not complete success (not this plugin's fault). If this is a known problem perhaps some information could be added to the wiki page to let other know not to use this plugin in certain circumstances? As an aside I don't think the resolution should be 'Incomplete'. I'm happy with 'Won't fix' etc but to say Incomplete suggests that there's not enough information to fix the defect (you haven't indicated that's the case), or something else. Please don't take my comment the wrong way. I appreciate the time you have spent on this, I'm just trying to get myself and others to a more 'happy place' . 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-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title John Stephenson commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs Thanks for these responses. I'm up and running sort of. I had 2 issues: 1. I was running in AWS and forgot that I need to allow the incoming ports from bitbucket (described here 2. The polling flags where not on It's strange, as I have a 'run a build every 2 hours regardless of changes pending' setup and it's only building when a change happens. Spent so much time on this, I can't afford to invest any more effort in it ATM. FWIW, I still think the wiki needs work. 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-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title
John Stephenson commented on JENKINS-38447
Re: Bitbucket hooks don't work for Pipeline jobs
I too can't get this to work. I'm using the cloudbees-bitbucket-branch-source and can't see where I can correctly configure the triggers. From the wiki :
freeStyleJob('test-job') {
triggers {
bitbucketPush ( )
}
}
But my JenkinsFile looks like this (edited):
node {
/* triggers{
bitbucketPush()
}*/
stage('Checkout'){
checkout scm
}
stage('Build client') {
dir('./client') {
sh 'npm run build'
}
}
}
If this can't work with the cloudbees-bitbucket-branch-source plugin it would be good to know and advertise this on the wiki page. Alternative approaches would be appreciated too! Thanks, John
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
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title John Stephenson commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs And ensure you've updated your firewall as necessary (https://bitbucket.org/blog/new-ip-addresses-bitbucket-cloud?_ga=2.183187939.453555296.1545035860-2047301735.1528367903) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
