Skip to content

WIP: Initial workflows to support a release process - #73

Draft
wwsean08 wants to merge 21 commits into
Team-TAU:mainfrom
wwsean08:feat/71
Draft

WIP: Initial workflows to support a release process#73
wwsean08 wants to merge 21 commits into
Team-TAU:mainfrom
wwsean08:feat/71

Conversation

@wwsean08

@wwsean08 wwsean08 commented Jul 12, 2021

Copy link
Copy Markdown
Contributor

Currently a WIP/Draft PR to allow for ample input along the way for the process of creating an automated release workflow and the infrastructure around it (#71).

Changes

  • Nightly build workflow - Runs once a night to update the helix_endpoints.json and if there is a change automatically opens a PR. See Updated helix endpoint data wwsean08/tau#1 as an example of the auto-pull request working.
    • Could support more things down the line
  • Develop build workflow - Automatically updates a draft change log based on PRs merged into main
  • Pull Request workflow - Lint/License checks and (once tests exists) runs unit tests.
    • TODO: Hopefully some sort of SAST like sonar cloud, as well as vulnerability scanning like snyk (see issue).
    • Also technically the current lint job failure is valid as it's finding lint issues, whether they are issues that we care about I don't know enough about python to know, but they seem easy enough to fix
  • Release Workflow - At this point it's basically the same as the pull request workflow, but if we wanted to publish docker images, I would see it going here.

@wwsean08 wwsean08 changed the title WIP: Intiial workflows to support a release process WIP: Initial workflows to support a release process Jul 12, 2021
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

Successfully merging this pull request may close these issues.

1 participant