search

timja / jenkins-gh-issues-poc-06-18

0 stars 0 forks source link

[JENKINS-47644] Jenkins Remote API - Queue API returning 404 (wasn't before) #9445

Open timja opened 7 years ago

timja commented 7 years ago

This may be related to JENKINS-27256.

We use the remote API to trigger a build. We then get the queue ID from the response of said trigger call and then query the queue API to determine the build number of the created build.

This worked perfectly until yesterday (2017-10-24) when calls to the queue API started returning a 404. I think on this day we also updated Jenkins as we ran our Ansible playbook at our server, which starts with an `apt-get update && apt-get upgrade`.

Code execution wise, our script is written in Node.js and we're using the "jenkins-api" package as an API client. We call `jenkins.build_with_params()`, and then immediately after we get a response we hit `jenkins.queue_item()` until we find "executable" in the data. Under the hood, the 404 is coming from "/jenkins/queue/item//api/json". Calling the specific URL with a small delay yields the same result.

Apologies I don't have anymore information than this as I'm not entirely sure what to provide.

Originally reported by stephenmelrose, imported from: Jenkins Remote API - Queue API returning 404 (wasn't before)
  • status: Open
  • priority: Major
  • resolution: Unresolved
  • imported: 2022/01/10
timja commented 6 years ago

danielbeck:

wasn't before

What are the current and previous versions of Jenkins?

Could https://jenkins.io/security/advisory/2017-10-11/#queue-item-remote-api-disclosed-information-about-inaccessible-jobs explain it, i.e. if the authentication for the API request is different than for the build request?

timja commented 6 years ago

jeffhube:

[EDIT] Disregard that, it was not a Jenkins problem.