You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we push a new branch/create a new PR to Bitbucket Cloud, Jenkins does not run the build unless the branch/PR has been discovered by a Branch Indexing. Once a branch has been discovered by Branch Indexing, subsequent pushes to the branch/PR trigger an immediate build.
We have a large number of repositories so this causes a lot of lag when pushing new branches. We set all jobs to scan periodically but rate limiting from Bitbucket means that developers typically have to wait 20-30 minutes before a new branch is detected.
Is this something that can be fixed by configuration ?
Upstream changes
No response
The text was updated successfully, but these errors were encountered:
I use Bitbucket server, not cloud but I created a token with write permissions and enabled hooks in the configuration and new PRs and new commits in existing PRs are detected automatically.
What feature do you want to see added?
When we push a new branch/create a new PR to Bitbucket Cloud, Jenkins does not run the build unless the branch/PR has been discovered by a Branch Indexing. Once a branch has been discovered by Branch Indexing, subsequent pushes to the branch/PR trigger an immediate build.
We have a large number of repositories so this causes a lot of lag when pushing new branches. We set all jobs to scan periodically but rate limiting from Bitbucket means that developers typically have to wait 20-30 minutes before a new branch is detected.
Is this something that can be fixed by configuration ?
Upstream changes
No response
The text was updated successfully, but these errors were encountered: