When creating a new job from the REST API using an XML file:

curl -u <user>:<pass> \
	 -H "Content-Type:application/xml" \
	 -X POST http://jenkins.example.com/createItem?name=TEST_JOB \
	 -d @config.xml

The job is correctly created BUT the builds directory does not contains the legacyIds file. The same happens when using the create-job command with the Jenkins CLI, we see the same behavior.

When creating a job from the UI however, the legacyIds is correctly added.

Impact

The absence of the legacyIds file cause the RunIdMigrator to "migrate" that job on the next startup.

jenkins.model.RunIdMigrator#migrate: Migrating build records in <pathToJobDirectory>/builds

If many jobs are created using the REST API, this can slow down the next startup considerably. Some users that are automating the creating of items could be impacted.

Workaround

Create the job first "from scratch" then update the XML file:

# create a pipeline job from scratch
curl -X POST \
	 -u <user>:<pass> \
	 -H "Content-Type:application/x-www-form-urlencoded" \
	 "http://jenkins.example.com/createItem?name=TEST_JOB&mode=org.jenkinsci.plugins.workflow.job.WorkflowJob"

# update the job configuration by providing the XML
curl -X POST \
	 -u <user>:<pass> \
	 -H "Content-Type:application/xml" \
	 -d @config.xml \
	 "http://jenkins.example.com/job/TEST_JOB/config.xml"

Further Note

The "RunIdMigrator" is instantiated in Job and AbstractProject when the Item#onCreatedFromScratch is called. But this is not called when using the REST API to copy a job or to create an item from XML:

• https://github.com/jenkinsci/jenkins/blob/jenkins-2.269/core/src/main/java/hudson/model/ItemGroupMixIn.java#L219-L261
• https://github.com/jenkinsci/jenkins/blob/jenkins-2.269/core/src/main/java/hudson/model/ItemGroupMixIn.java#L263-L306