Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(ci): Upload halconfigs to GCS on Tag push (backport #274) #275

Open
wants to merge 1 commit into
base: release-1.27.x
Choose a base branch
from
Open

chore(ci): Upload halconfigs to GCS on Tag push (backport #274) #275

wants to merge 1 commit into from

Commits on Apr 26, 2022

  1. chore(ci): Upload halconfigs to GCS on Tag push (#274) 

    * chore(ci): Upload halconfigs to GCS on Tag push

Previous release tools would publish basic halconfig profiles to GCS
bucket: [https://console.cloud.google.com/storage/browser/halconfig/`<service>`/`<version>`/*](https://console.cloud.google.com/storage/browser/halconfig/%60%3Cservice%3E%60/%60%3Cversion%3E%60/*)

Where `<service>` might be `rosco` and `<version>` is our git tag, eg: `v1.2.3`.

Halyard downloads these profiles during `hal deploy apply`.
As the profiles are deprecated it would be ideal to remove from Halyard
but it may break users workflows.

For now we can upload the files as part of our regular service 'release'
flow (git tag <version> && git push) using GHA.

* chore(ci): Add Mergify config used in other services

(cherry picked from commit 96d510c)

# Conflicts:
#	.github/workflows/release.yml
    @kskewes-sf
    kskewes-sf authored and mergify-bot committed Apr 26, 2022
    Configuration menu
    Copy the full SHA
    6e944d4 View commit details
    Browse the repository at this point in the history