Mark Waite added a comment - 2021-11-20 21:16 Please provide enough details so that others can duplicate the problem you are trying to report. You're trying to persuade volunteers to assist you. The easier you make it for them to assist you, the more likely they are to assist you. The "How to report an issue" page describes the types of information you should include in the issue report.

Kameswara Rao Mithipati added a comment - 2021-11-22 06:51 Hi Mark, Thanks for pointing me to the link apologies for not adhering to the process, Previously we are used to get queue item number when we curl build with parameters to jenkins to invoke or initiate build on jenkins version 2.150 But recently we upgraded to 2.303 and we are not finding queu item number affter initiating/invoking build on jenkins. Because of this we don't have a handle to get build number of the job to track.

Daniel Beck added a comment - 2022-01-05 11:38 There hasn't been a change in a while this code that I could find. The difference seems to be whether the call created a queue item or didn't. Do both API calls actually result in the creation of a new queue item? I just tried it in 2.303.3 locally and it worked: $ curl -v -u admin:1139080402ef85168d6a077545e7038026 -X POST http://localhost:8080/job/fs/buildWithParameters?s=foo * Trying ::1... * TCP_NODELAY set * Connected to localhost (::1) port 8080 (#0) * Server auth using Basic with user 'admin' > POST /job/fs/buildWithParameters?s=foo HTTP/1.1 > Host: localhost:8080 > Authorization: Basic YWRtaW46MTEzOTA4MDQwMmVmODUxNjhkNmEwNzc1NDVlNzAzODAyNg== > User-Agent: curl/7.64.1 > Accept: */* > < HTTP/1.1 201 Created < Date: Wed, 05 Jan 2022 11:37:36 GMT < X-Content-Type-Options: nosniff < Location: http://localhost:8080/queue/item/1/ < Content-Length: 0 < Server: Jetty(9.4.43.v20210629) < * Connection #0 to host localhost left intact * Closing connection 0 Your user name is ssqa and your Jenkins API token is 11daadc0c0819bdf6de52e8a5f9f8d2fa2 . If you're going to redact, do it thoroughly