admin管理员组文章数量:1024666
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?
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?
本文标签： cloudbeesAPI changes after Jenkins Core Version 246222 upgradeStack Overflow
版权声明：本文标题：cloudbees - API changes after Jenkins Core Version 2.462.2.2 upgrade - Stack Overflow 内容由热心网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://it.en369.cn/questions/1745608887a2158886.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。
发表评论