Sync release-next at the start of release period #36918
Labels
DevOps
Issues and pull requests related to DevOps
ISIS Team: Core
Issue and pull requests managed by the Core subteam at ISIS
Maintenance
Unassigned issues to be addressed in the next maintenance period.
Milestone
Describe the outcome that is desired.
Currently the Jenkins job that updates release-next so that it's pointing to the head of main is not working. This is because the linux nodes don't have
jq
installed by default (it used to run on a different docker container). We need a reliable way to perform this task at the start of the release period.Describe any solutions you are considering
Move the script to the mantid repo and make use of the mamba utilities to install
jq
.It would be nice to be able to specify a branch or a tag to update to.
The text was updated successfully, but these errors were encountered: