Skip to content

Support actions/cache in branch deploy workflow #11

@aaronccasanova

Description

@aaronccasanova

Description:

In a recent exploration, I was configuring GitHub actions/cache to optimize subsequent CI builds and realized our /snapit branch deploy workflow is unable to leverage that feature. However, I think there's an opportunity to slightly rework the current implementation and bring us closer to our sub-goal of keeping a majority of work in the GitHub runner.

Current branch deploy workflow:

  • User comments /snapit
  • Snapit runs changeset version --snapshot snapshot, and
  • Force pushes to another branch for Buildkite to take over the build, pack, and upload

Proposed branch deploy workflow:

  • User comments /snapit
  • Snapit runs changeset version --snapshot snapshot and the existing build_script
  • Snapit runs a new pack_script command, and
  • Force pushes the packed artifacts to another branch for Buildkite to upload

This update would allow workflows to leverage GitHub actions/cache to only build the changes between runs, and the branch deploy would only be responsible for uploading artifacts. In our case, the branch could essentially be a single .pack dir that, when pushed to, gets uploaded to Cloudsmith.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions