Are you sure this is reproducible? In which Jenkins version? It certainly should be reloading all jobs, everywhere, in any version I know about.

Loading of folder items is done by the Folders plugin.

This report needs much more information to allow investigating further.

Loading of folder items is done by the Folders plugin.

Yes, but in response to loading of the Folder itself, which should happen during a general Jenkins reload too.

Yeah, my bad, I was pretty sure I had selected the correct component for Cloudbees Folder
Will add repro steps.

Is step 3 necessary, or can it be skipped?

hello,

I have the same issue with Jenkins 1.609.2 and CloodBees folder 4.9.0. Step 3 is not necessary, you can skip it. By the way if i restart the server hosting Jenkins, jobs reflect changes.

thanks

Correct, step 3 is not a requirement, was just the use case at the time.

I can confirm this problem, restarting seems to be the only quick fix (which is a problem).

We have the same issue with Jenkins 1.636 and CloudBees Folders Plugin 5.0. The Folders plugin is great, but loosing the reload possibility is a drawback.

You know you can reload individual items rather than the whole Jenkins configuration, right? That is much safer.

Pardon my ignorance, but .. how?
Tried doing search and nothing came up.

/job/foo/reload should work.

Seems to be still occurring in 2.73.2.  Any update on this?

I used groovy script to avoid this bug, however since the scritpler plugin has been removed, this issue is getting worse: there is no way to reload a job inside a folder.

Repro:

1/ Change manually a job configuration (ex: repo1/jobA/config.xml)

2/ Reload configuration from disk

-> The job configuration is not updated

Any update on reloading the job configuration when the jobs are inside a folder?  Reloading will not load "config.xml" changes for jobs that exist in a folder.

Using:  Jenkins ver. 1.642.4.1 (CloudBees Jenkins Enterprise 15.11)

Issue still present: core version 2.190.2

Folder plugin: org.jenkins-ci.plugins:cloudbees-folder:6.9

Just created a whole load of jobs in a Folder.
Did a mass change inside the config files manually ( using a script )
Reloaded config ManageJenkins->reload configuration from disc

Jenkins updated, jobs inside folders were not updated
I'll go for the above...
*Jenkins Version 2.219 *
( tried it on an earlier version, thought I had done something wrong, only a few jobs so changed using Jenkins GUI .. and ignored it.)
All latest plugins installed

Raised it to Major
I have many jobs in folders and changing e.g. the clearcase branch in 20+ jobs using the Jenkins GUI is not amusing when a perl one liner does it almost instantly.

got caught by this again - now I have more folders and jobs.
A one line perl changes all config.xml files, expected a reload config from disk to work.
Jenkins is constantly running jobs, a new restart is not possible.
A reload config allows the jobs to continue.
( does not - my mistake, no downstream job were started, really blown my CI system )
Does raising it to critical put more emphasis on this defect ?
using Jenkins LTS 2.235.5
all plugins are up to date.

Hi, I faced same issue. I need to update job and folders config.xml files manually and then get changes reflected in Jenkins. jenkins-cli reload-configuration was not working for jobs under folders. and "Reload Configuration from Disk" (in UI) was also not working.

TEMP SOLUTION (which worked for me):

create file: reload-configuration.groovy with content

_{import jenkins.model.Jenkins;}

_{import hudson.model.AbstractItem;}

_{import java.io.InputStream;
import java.io.FileInputStream
import java.io.File;
import javax.xml.transform.stream.StreamSource;}

_{Jenkins.instance.getAllItems(AbstractItem.class).each{job ->
  def configXMLFile = job.getConfigFile();
  def file = configXMLFile.getFile();}

  _{if (file.exists()) {}

    _{InputStream is = new FileInputStream(file);}

    _{job.updateByXml(new StreamSource(is));
    job.save();}

    _{println("Config reloaded: " + job.fullName);
  }
}}

And then run it with (add your auth method if needed): 

_{java -jar jenkins-cli.jar -s https://${JENKINS_ADDRESS}/ groovy = < reload-configuration.groovy}

This script goes through all items (jobs/folders) and updates their configs.

Please let me know if something is not clear in this explanation.

Same problem here. Need this fixed, big time.

Vitalii, your solution worked great, thank you.