Details
-
Bug
-
Status: Open (View Workflow)
-
Blocker
-
Resolution: Unresolved
-
Cloudbees Folders Plugin 6.4
Jenkins 2.114
Ubuntu 14.04 w/ full updates
Description
The Folders Plugin is not replicating required information into the sub-jobs.
The Folders plugin is used in a Multi-Configuration project for multiple related jobs. The job configuration is specified in the folder, and prints-thru into the individual job configurations. However, the github scan time is not replicating into the jobs, and is instead defaulting to an unacceptable 1-hour for unknown reasons. It is not possible to alter the individual job configurations to compensate for plugin defects, as there is no save button on the sub-jobs. Screenshots are attached of (a) an offending folder showing the requested 5-minute scan time, and (b) a typical folder sub-job showing the misconfiguration and defaulting to 1-hour instead of the 5-minutes specified in the folder.
This error makes the jobs almost unusable for normal development purposes, as source scans only occur a few times per day. Critical error.
Attachments
Issue Links
- is related to
-
-
- Open
-
-
-
- Resolved
-
Activity
I upgraded to Jenkins 2.118 overnight, and picked up a dozen small updates to the plugins at the same time. The problem behaviour is unaltered. Attaching a slightly-redacted folder config and typical subjob config that has the problem per request. Looking back, I cannot locate a job where this is working, so I am unsure when it broke.
Ok, it looks like your parent job is an organization folder and the sub jobs are multibranch projects. I am not familiar with the plugins and APIs that provide those features, but I see what appears to be related discussion in JENKINS-47077. In particular stephenconnolly notes in a comment something that makes me think this never worked.
(ignore that you cannot configure the multibranch's period at present)
Maybe the configuration of the folder properties has never worked, but you are only noticing it now that you are experiencing JENKINS-47077?
Hypothetically, what needs updating is the number of msecs in the following stanza in the config.xml for the job:
<triggers> <com.cloudbees.hudson.plugins.folder.computed.PeriodicFolderTrigger plugin="cloudbees-folder@6.4"> <spec>H H * * *</spec> <interval>86400000</interval> </com.cloudbees.hudson.plugins.folder.computed.PeriodicFolderTrigger> </triggers>
A much more suitable interval value would be (say) 300000, or 5 minutes.
Raphael Pionke
added a comment - alt_jmellor i had the same issue and the workaround from https://issues.jenkins-ci.org/browse/JENKINS-48960?focusedCommentId=332057&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332057 worked for me
Raphael Pionke
added a comment - alt_jmellor i had the same issue and the workaround from https://issues.jenkins-ci.org/browse/JENKINS-48960?focusedCommentId=332057&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-332057 worked for me
Thanks for reporting the issue. To help figure out where things are going wrong, could you attach the config.xml of the parent folder that you are having issues with? You can get it from the UI by navigating the folder and then adding config.xml to the URL. You'll want to make sure to remove any sensitive content (I only want to see the general structure). Also, since you marked this ticket as a regression, can you list the environment in which things were previously working?