Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jenkins nodes should be able to disconnect themselves if they are not ready to run jobs. #102

Open
4 tasks
cailafinn opened this issue Nov 21, 2024 · 0 comments

Comments

@cailafinn
Copy link
Collaborator

Contribution to Target

A node that is certain it cannot pass a job is not useful. A node should only be available to jenkins if it knows it is able to pass jobs.

Things a node needs:

  • Up-to-date testing data
  • Connection to anaconda
  • Connection to GitHub
  • The ability to stop itself running builds.
    • This can be done using the Jenkins HTTP API:
    • curl -X POST https://<USER>:<TOKEN>@builds.mantidproject.org/computer/<NODE>/toggleOffline?offlineMessage=<REASON_FOR_DISCONNECT>
    • builds.mantidproject.org/computer/isis-ndw1170/api/json can be used to get json including the temporarilyOffline status of the node.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant