Skip to content

DEVOPS: Update Workflows #330

@ZanderCowboy

Description

@ZanderCowboy
  • Update workflows to use correct semantic versioning
Image
  • Linting workflow still runs on every PR
  • Move test coverage and CodeCov to linting.
  • Develop workflow runs after a PR pointing to develop is merged.
    • A PR having either the label feature or bug is allowed to bump versioning, respectively, including build number.
    • Using feature: Bump minor
    • Using bug: Bump patch
    • A PR having any other labels should just get a build number bump
  • Staging workflow
    • Should be run when a PR with a base branch that includes rc is pointed to main. Branches pattern - "rc", "rc/N" (where N is a number), "rc-N" or "rc_N". etc.
    • We should create a new build on every push and send to internal track
    • The underlying change: Create a RC branch off of develop once a release is imminent. Create a PR pointing to main, create a new build, send to Google Play. On every push, bump build number with new build and send to track.
    • Still the usual with the "-RC" part
  • Production workflow
    • Needs to be manually dispatched
    • Looks at latest RC tag, remove rc, create new "production" tag and create release
    • Remove: No new builds should happen; we only look at the version that was merged into main and update the pubspec file.
    • For example, if we merged a RC PR into main, say the version in pubspec was 1.3.7-RC+155, then update the version to 1.3.7+155.

Refactoring:

  • Reduce code duplications by creating actions
  • Remove old workflows no longer being used.

Metadata

Metadata

Assignees

No one assigned

    Labels

    dev-opsrefactorCode refactoring without behavior changes

    Projects

    Status

    In Review

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions