We are storing queueId from Jenkins API as integer as it used to be. However after Jenkins version upgrade to CloudBees CI Version 2.462.2.2, this queueId becomes a really big number like 59214986632345984610 which is exceed the integer size and caused an error. Is it an expected change in this particular version? My understanding is queueId is a regular primary key, why it setup as a large number in this new version?
We are storing queueId from Jenkins API as integer as it used to be. However after Jenkins version upgrade to CloudBees CI Version 2.462.2.2, this queueId becomes a really big number like 59214986632345984610 which is exceed the integer size and caused an error. Is it an expected change in this particular version? My understanding is queueId is a regular primary key, why it setup as a large number in this new version?
Share Improve this question edited Nov 18, 2024 at 16:14 MLlamas xWF 473 bronze badges asked Nov 18, 2024 at 16:10 HannahHannah 851 silver badge11 bronze badges1 Answer
Reset to default 1queueId has always been long, check git blame here, for example. So it should be between -9,223,372,036,854,775,808 and 9,223,372,036,854,775,808. I am going to assume the example you provided is a bit of an exaggeration. If not - could you provide the API endpoint that returned it?