Skip to content
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

The branches are not triggered by the multibranch job #742

Open
criss2525 opened this issue Jul 24, 2023 · 2 comments
Open

The branches are not triggered by the multibranch job #742

criss2525 opened this issue Jul 24, 2023 · 2 comments
Labels

Comments

@criss2525
Copy link

criss2525 commented Jul 24, 2023

Jenkins and plugins versions report

Environment
Jenkins: 2.401.1
OS: Linux - 5.15.0-60-generic
Java: 11.0.19 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
bitbucket-push-and-pull-request:2.8.3
cloudbees-bitbucket-branch-source:825.va_6a_dc46a_f97d

What Operating System are you using (both controller, and any agents involved in the problem)?

Jenkins 2.401.1 - Linux - 5.15.0-60-generic.
Agent is on Windows Server 2022 Standard on the agent.

Reproduction steps

  1. Create a multibranch pipeline using the Bitbucket Server.
  2. Fill in all the details and scan the job. ( it says: Finished: NOT_BUILT)

Expected Results

The expected outcome is that the branches are getting triggered. ( The same steps are performed with git, not bitbucket plugin and everything works as expected, the jobs are automatically scanned and the branches are build)

Actual Results

The job is not scanned and not triggered. The output result of the jobs is:

Started by timer
[Mon Jul 24 13:43:09 CEST 2023] Starting branch indexing...
Connecting to <bitbucket_server>
Repository type: Git
Looking up <REPO_NAME> for branches
Checking branch jenkins_development from <REPO_NAME>
      ‘Jenkins/Jenkinsfile_Full_regression’ found
[Mon Jul 24 13:43:10 CEST 2023] Finished branch indexing. Indexing took 0.83 sec
Finished: NOT_BUILT

Anything else?

No response

@criss2525 criss2525 added the bug label Jul 24, 2023
@s7an-it-ez
Copy link

@criss2525 I am on that version and have some other bug where Organisation as some point of time get with a corrupoted index. I need to go in Jenkins global settings and clear cache and then click on scan project, can you try that to see if it will help you?

@nfalco79
Copy link
Member

I need to go in Jenkins global settings and clear cache and then click on scan project, can you try that to see if it will help you?

This was fixed by #837

Did you change the default name for Jenkinsfile? I see Jenkins/Jenkinsfile_Full_regression in the log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants