- Parameterized Builds for Jenkins version: 4.0.5 - latest
- Bitbucket version: 6.7.1 - latest
- Jenkins version: 2.190.1 - latest LTS
- Crowd version: 6.6.0 - latest
- Crowd-2-Jenkins-plugin version: 2.0.1 - latest
- Any Jenkins or Bitbucket settings that could be relevant
- We expreinced fail to start build from Bitbucket with the plugin.
- FACTS:
- We have used crowd to auth from the begining.
- We use the Jenkins Crowd-2 plugin (henceforward: plugin) with a technikal user (for example robot).
- We generated a token with this robot user and we used the plugin with pleasure.
- After the last upgrade, we can not start build from bitbucket. :/
- From my investigation, I came to the plugin not pushes the token to start the job, it uses the logged in username/sessionID. I though it, beacuse in the jenkins.log I found when I push on build manuially from bitbucket
`jenkins.log` : `d.t.j.c.CrowdAuthenticationManager#authenticate: Application name and/or password are not valid.`
BUT
in the crowd log, I don't see the technical user (robot) tries, just only this line:
`atlassian-crowd.log` : `[crowd.manager.application.ApplicationServiceGeneric] Invalid credentials for user zsolt.denes in directory XYZ, aborting˛`
So we connected the bitbucket to jenkins with tecnical user robot *but* it tries to login in my name to start a build.
So right now, I don't know makes the mistake. Can You check, the jenkins's token process handling not changed? Or why needs the crowd auth after the technical user token? Of course, I also wrote to the The Parameterized Builds for Jenkins plugin developers at project gitter channel Of course, if they not ansering i will put a bug report to [github|https://github.com/KyleLNicholls/parameterized-builds/issues/] Thanks a lot your energy for this work! Gr,
Zsolt |
