-
Notifications
You must be signed in to change notification settings - Fork 351
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not capturing commits with bitbucket branch source plugin with OAuth credentials #747
Comments
Is this not supposed to work with Outh Consumers? |
My organization is experiencing this (or a very similar issue) as well. We are migrating from Bitbucket Server to Bitbucket Cloud and aside from migrating repositories and configuring an OAuth Consumer in Bitbucket Cloud and Jenkins we have not changed/updated Jenkins components. Our Environment
Reproduction Steps
Expected Results
Actual Results
WorkaroundWe have a temporary workaround which is to remove all when conditions that use the changeset condition. Therefor all our stages are built on any commit. However, this is not workable for all situations. Anything ElseAs noted our when conditions work fine with Bitbucket Server, Jenkins is picking up the list of changes upon each push when they come from Bitbucket Server. We are migrating all repos to Bitbucket Cloud and discovered that our stages with when conditions were not executing. Upon further investigation we noticed that while Jenkins is notified of a push no changes are ever detected. |
@lifeofguenter are you the primary maintainer of this repository? I might be able to assist fixing this if you could point me in the general direction as to where this issue may arise. |
Just hit this one myself. To be clear for those looking for a workaround; if you switch to a username/password combo in the interim it works correctly. The problem is specific to using OAuth credentials. |
I have replaced Oauth credentials with Bitbucket APP password which works fine |
Any progress on this? It's good to hear that an app password works, but those are still tied to a specific user, which is what we'd like to avoid in our CI/CD pipeline. |
Likewise, any updates? I am willing to put in the work for a patch if the owner can point me in the general direction for where this issue could be cropping up. |
I'm not sure what the etiquette is for tagging folks, my apologies in advance if this is not the recommended approach. @lifeofguenter, I see that you are a recent contributor. Are you the right point of contact for this plugin? Would you be able to point me in the right direction for resolving this, whether that be redirecting to the maintainer, or providing a general direction for resolving this myself and submitting a PR? |
Hi, Any updates on this bug? Is there any intention to fix it? |
Still hoping for an update on this bug. Willing to help if someone could point me in the general direction of a fix. I am unfamiliar with Jenkins plugin development. |
Still hoping for a fix to this bug. As before I am willing to assist if someone can point me in the right direction. |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Amazon Linux 2
OS: Linux - 6.1.25-37.47.amzn2023.x86_64
Reproduction steps
But still no changes are logged.
Expected Results
Commits should be captured.
Actual Results
No changes logged even when build is triggered due to branch event of commit.
Anything else?
No response
The text was updated successfully, but these errors were encountered: