tracking Jenkins builds in my application using a combination of queueId and job name. Recently, restored Jenkins from a backup that is about a month old. Now, the application is experiencing conflicts because queueId values from the restored Jenkins instance are overlapping with entries already stored in database.
Is there any way to reset or configure the queueId Jenkins assigns to new build items, so that i can avoid this conflict? For example, can i set a starting point for queue IDs, or purge/reindex the queue to prevent duplication?
The queueId is stored in the file JENKINS_HOME/queue.xml. So when you restore a backup you would need to ensure that the queueId is adjusted to what you need while Jenkins i not running. BTW the queue.xml should not be taken from the backup.
The queue.xml looks like this on my machine (queue is empty)