Jobs created via CLI fail to get started by a timer trigger

[Chris]

Hello!

So we have the following setup:

1) We have a view that contains several job templates, i.e. jobs that are preconfigured with placeholders like '%application_x_version%'.

2) We have a Java application that reads the concrete parameters from an excel sheet, downloads the job template's config.xml, replaces the placeholders with the concrete parameters and sends the resulting string via the Jenkins CLI to creates a new job.

Now the problem: Some of those job templates contain timer triggers (e.g. 'H H(4-5) * * *' to start every night between 4 and 5). Jobs automatically created from those templates do not start automatically triggered by time as they should. And we are currently clueless as to why that would be. We already checked the config.xml's of the created jobs but they look perfectly fine. No weird characters or other malformations at all, no difference from one created by hand.

We also found, that when we edited the configuration of the automatically generated job by hand, e.g. change the timer trigger to something else and back and then save the job, the triggering works as intended. So we assume there must be a difference somewhere between the saving when doing it by CLI and doing it by hand, but we cant figure out what, why and how to fix it.

And ideas or other insights?

Thanks,

Chris