-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins 2.109
My scan organization folder is set to execute every 1 minutes. It runs fine but is not detecting code changes and building my changes. If i access the configure option and make a change to the configuration, that forces a scan, and my programs build. Worked fine in 2.79
[JENKINS-49798] Scan Organization Folder not detecting code changes
| Component/s | New: pipeline [ 21692 ] |
| Assignee | Original: Mark Waite [ markewaite ] |
| Component/s | New: scm-api-plugin [ 18054 ] | |
| Component/s | Original: git-plugin [ 15543 ] |
kford2000 I think others will need more information before they can assist with diagnosis. For example:
- Which branch source plugin are you using? GitHub, Bitbucket, Gitea, or Git
- If you're using the Git branch source, are you using modern or legacy SCM provider?
- Are there entries in the Jenkins log which might hint why the build did not run?
- Are there any reports in logs that you've exhausted your API limits with your git hosting provider?
| Attachment | New: Jenkinsfile [ 41632 ] |
- Using Bitbucket installed on local server as well as jenkins on local server, all this worked on version 2.79, all broke when i install 3.10
- Not sure what you are asking
- which log files
- attached my jenkinsfile
Definitely could webex with someone to help work through this issue ^^
The branch source provider is defined in the multi-branch job definition. Since you were willing to upload your Jenkinsfile, could you also upload the config.xml file for the multi-branch PIpeline job? I suspect that will be needed if someone investigates it.
I doubt very much that anyone will agree to a webex to investigate the issue. That's quite uncommon in open source projects.
| Attachment | New: org.config.xml [ 41633 ] |
Scan organization is set to 1 min and runs every 1 min, but does not build my changes.
This is the log
Looking up JU/jbasetraining for branches
Checking branch release/2.0.0 from JU/jbasetraining
‘Jenkinsfile’ found
Met criteria
1 branches were processed (query completed)
I did find that if I enter the configure option at the organization level, make a change to the config (any change) and save it. It automatically starts an organizational scan with this log value
Looking up JU/jbasetraining for branches
Checking branch release/2.0.0 from JU/jbasetraining
‘Jenkinsfile’ found
Met criteria
1 branches were processed (query completed)
Looks the same as the 1min scan above, but it also builds my changes.
So for some reason, the 1min checking of the code changes at the organizational level does not detect code changes, but a save to the config at the organizational level does find the changes.