Run e2e/upgrades test on nightly
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Currently [`e2e/upgrades`](https://github.com/hashicorp/nomad/tree/master/e2e/upgrades) isn't being run on nightly, because we weren't able to update Nomad in-place in the e2e infra. Now that we have the `e2e/framework/provisioning` tooling, we can do so. Because this tests upgrade safety it'd be a good idea to make sure we're running it on a nightly basis.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the e2e/upgrades test and the e2e/framework/provisioning tooling mentioned in the issue, then inspect the repository's existing nightly test configuration. Connect the upgrade test to that nightly run using the provisioning support, and verify that the upgrade suite executes successfully on the nightly schedule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100