Hello all, We are moving jobs from one Jenkins machine to another. On the old machine we disable the job, then we copy the project in the jobs folder from the old to the new machine. In the new Jenkins I load the jobs by reloading the configuration. All copied jobs appear to the existing ones, but they are still disabled. I open each job and press the Enable button in the status view. And then my problem appears: the job is enabled, but builds nothing. When I compare the latest with the previous configuration I see that a huge block is added to the configuration with the dependency graph information. Why does Jenkins add this? Such corrupt config.xml files are more than 200k in size, were they are normally around 10k. I already did find a work around: to enable a job I open the configuration, remove the check from 'disable project' and save the configuration. After that the configuration does not get corrupt. Has anyone experienced the same issue? And perhaps has a solution? Jenkins version: 2.107.2
regards, Mark -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/eb586fe2-f9bf-4395-9913-a35ccddcd0e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
