Re: Pipeline jobs for PRs failing due to Jenkins NOT using configured account.

2018-09-28 Thread Manny DaSilva
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.

On Wednesday, April 11, 2018 at 1:40:40 PM UTC-4, Chris Funderburg wrote:
>
> 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? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5459d010-4fd3-4610-a810-49145cdd8119%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Pipeline jobs for PRs failing due to Jenkins NOT using configured account.

2018-04-11 Thread Chris Funderburg
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? 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d2b77a49-38e7-4ed5-8a07-d8a85b929ca7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.