We are using bitbucket webhooks for trigger our builds for multibranch pipeline due to some license issue we have stopped using the webhooks. Currently what we are facing is if i create a new branch or any PR if we raise manually we need to trigger the scan button in multibranch pipeline that scan button is not scanning our new branch or any PR. Usually scan button take the latest branch or any new commit or any new PR but scan is not happening.
Currently am using 2.452.1 version for my Jenkins.
Bitbucket branch scanning works for me with Jenkins 2.491 and has worked consistently with previous versions. When I click “Scan Multibranch Pipeline now”, the scan is performed and the expected actions are taken. I pushed a new branch to my git-client-plugin repository and clicked the “Scan Multibranch Pipeline now” action on the multibranch Pipeline job page.
The Scan Multibranch Pipeline Log page shows:
Started by user Mark Waite
[Thu Dec 26 07:34:23 MST 2024] Starting branch indexing...
Connecting to https://bitbucket.org using markewaite bitbucket git client poll from docker-lfs multibranch eggF8LC5KbhyyQgkmZHd
Looking up markewaite/git-client-plugin for branches
Checking branch create-ssh-dir-with-better-perms from markewaite/git-client-plugin
‘Jenkinsfile’ found
Met criteria
Scheduled build for branch: create-ssh-dir-with-better-perms
Checking branch master from markewaite/git-client-plugin
‘Jenkinsfile’ found
Met criteria
No changes detected: master (still at 6cc496b932b99c6a6303608629e7e95d263a60a6)
2 branches were processed
Skipping pull requests for markewaite/git-client-plugin (public repository)
[Thu Dec 26 07:34:25 MST 2024] Finished branch indexing. Indexing took 1.8 sec
Finished: SUCCESS
What is reported in your Scan Multibranch Pipeline Log page?
What plugin versions are you using?
Are you performing the scan from a multibranch Pipeline or from an organization folder?
Is the repository a public repository or a private repository?
Is the clock on the Jenkins controller correct? If the clock on the Jenkins controller is wrong, then many, many problems will appear.
If you click the “Scan Multibranch Pipeline Now” button and quickly check the contents of the “Scan Multibranch Pipeline Log” page, does it show that that scan is in progress or does it continue to show a completed scan from 22 July 2024?
Use “Manage Jenkins” → “Script Console” to run the system groovy script that is included in “How to report an issue”. That will list the name and version of every plugin that is installed.
Review the Jenkins system log (“Manage Jenkins” → “Logs”) immediately after you’ve clicked the “Scan now” button. Hopefully there will be some additional information written in the Jenkins system log that suggests what is happening.
Dec 30, 2024 5:54:19 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:20 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:20 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:20 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:20 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:27 PM INFO com.cloudbees.jenkins.plugins.bitbucket.BitbucketTeamMetadataAction$BitbucketAvatarCacheSource
Created: BitbucketAvatarSource(::NATURECONNECT::a33be74c-48a2-4328-b934-a0b55b70fb3d)
Dec 30, 2024 5:54:29 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:29 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Connection #249388 from /161.86.8.167:56386 failed: null
Dec 30, 2024 5:54:29 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Accepted JNLP4-connect connection #249389 from
Dec 30, 2024 5:54:29 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:29 PM WARNING jenkins.slaves.DefaultJnlpSlaveReceiver afterProperties
Rejecting connection to MG24_ChipSet_Ec2 from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56387 as an inbound agent as the launcher class hudson.plugins.sshslaves.SSHLauncher does not extend JNLPLauncher or does not implement DelegatingComputerLauncher with a delegation chain leading to a JNLPLauncher. Set system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true to allowconnections until the plugin has been fixed.
Dec 30, 2024 5:54:29 PM INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
[JNLP4-connect connection from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56387] Refusing headers from remote: MG24_ChipSet_Ec2 is not an inbound agent
Dec 30, 2024 5:54:30 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:30 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:30 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:30 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:39 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:39 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:39 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Connection #249390 from /161.86.8.167:56389 failed: null
Dec 30, 2024 5:54:39 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Accepted JNLP4-connect connection #249391 from /161.86.8.167:56390
Dec 30, 2024 5:54:40 PM WARNING jenkins.slaves.DefaultJnlpSlaveReceiver afterProperties
Rejecting connection to MG24_ChipSet_Ec2 from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56390 as an inbound agent as the launcher class hudson.plugins.sshslaves.SSHLauncher does not extend JNLPLauncher or does not implement DelegatingComputerLauncher with a delegation chain leading to a JNLPLauncher. Set system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true to allowconnections until the plugin has been fixed.
Dec 30, 2024 5:54:40 PM INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
[JNLP4-connect connection from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56390] Refusing headers from remote: MG24_ChipSet_Ec2 is not an inbound agent
Dec 30, 2024 5:54:40 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:40 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:40 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:40 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:49 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:49 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:50 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Connection #249392 from /161.86.8.167:56392 failed: null
Dec 30, 2024 5:54:50 PM INFO hudson.TcpSlaveAgentListener$ConnectionHandler run
Accepted JNLP4-connect connection #249393 from /161.86.8.167:56393
Dec 30, 2024 5:54:50 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:50 PM WARNING jenkins.slaves.DefaultJnlpSlaveReceiver afterProperties
Rejecting connection to MG24_ChipSet_Ec2 from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56393 as an inbound agent as the launcher class hudson.plugins.sshslaves.SSHLauncher does not extend JNLPLauncher or does not implement DelegatingComputerLauncher with a delegation chain leading to a JNLPLauncher. Set system property jenkins.slaves.DefaultJnlpSlaveReceiver.disableStrictVerification=true to allowconnections until the plugin has been fixed.
Dec 30, 2024 5:54:50 PM INFO org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecv
[JNLP4-connect connection from windows-template-for-jenkins-mg24chipset.rndit.intra.lighting.com/161.86.8.167:56393] Refusing headers from remote: MG24_ChipSet_Ec2 is not an inbound agent
Dec 30, 2024 5:54:50 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:50 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Dec 30, 2024 5:54:50 PM INFO com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory addProxyConfig
Configuring Proxy. Proxy Host: zscaler.proxy.Proxy Port: 9480
Do you see an error in the browser console when you click on the scan now button?
Have you configured the multibranch folder to periodically scan the repo?
Please find the attached screenshot. I have not seen any error in console output,I have clicked multiple times still scan is not happening last scan happened at 31st December today is 2nd Jan
the last execution returned an error, but other than that I have no idea.
My suspicion is that the last run is not completely finished somehow and that prevents new scans from starting. That would mean that a restart of Jenkins should at least allow you to run it once.
