Pipeline jobs for PRs failing due to Jenkins NOT using configured account.
20 views
Skip to first unread message
Chris Funderburg
unread,
Apr 11, 2018, 1:40:40 PM4/11/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Users
Multi branch pipeline jobs are failing on Pull Request branches only. Console output shows Jenkins doing "using GIT_ASKPASS to set credentials ***" (*** = configured user name). Using folder level credentials. Other branch jobs run fine. PRs fail on the master when trying to git pull the Jenkinsfile. I did a git reset on user.name globally on the master. This job works fine on my test master. I'm not sure where to look on the production master to fix this. Any thoughts?
Manny DaSilva
unread,
Sep 28, 2018, 4:15:40 PM9/28/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Jenkins Users
I'm having a similar issue. The multi-branch pipeline uses agent label 'docker' and we only have one build agent with that label. Most builds are running correctly on the agent node labeled 'docker' BUT some of the PR builds are running directly on the master node which does NOT have 'docker' label. I'm feeling like there is bug here but can't really back that up yet.