Further automate build and release process
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 61
- Forks
- 48
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 4
Description
We also have partially automated the release process in GitHub Actions but haven't reached the level of automation that we have for Windows and Azure Pipelines.
Currently run_release requires humans to click around in the GitHub UI to manually execute the GitHub workflow, which wasn't the case before. We also lost the automatic local testing step in favor of testing on GitHub Actions, but local assurance is good to have for RMs.
- Further automate kicking off the build and release workflows on GitHub Actions.
- Automatically detect workflow completion and download artifacts from GitHub Actions.
- Add back local testing to
run_release.pyscript once artifacts are automatically downloaded.
cc @ambv
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the run_release.py script and the GitHub Actions workflows involved in build and release. Trace how workflow completion and artifacts are currently handled, then determine the local testing step that was removed. Done means workflows can be detected and artifacts downloaded automatically, with local testing restored in run_release.py.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- build-system, ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100