Skip to content

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

@cailafinn

Description

@cailafinn

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions