From 046ba4df7f7c779ea63ca1a47c9203bb32bc93fb Mon Sep 17 00:00:00 2001 From: Snir Sheriber Date: Tue, 31 May 2022 15:28:05 +0300 Subject: [PATCH 1/3] workflows: add workflow_dispatch triggering to test-kata-deploy This will allow to trigger the test-kata-deploy workflow manually from any branch instead of using always the one that is defined on main See: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/ Fixes: #4349 Signed-off-by: Snir Sheriber --- .github/workflows/kata-deploy-test.yaml | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/workflows/kata-deploy-test.yaml b/.github/workflows/kata-deploy-test.yaml index c0a9b98b38..a623900992 100644 --- a/.github/workflows/kata-deploy-test.yaml +++ b/.github/workflows/kata-deploy-test.yaml @@ -1,4 +1,5 @@ on: + workflow_dispatch: # this is used to trigger the workflow on non-main branches issue_comment: types: [created, edited] From e938ce443c1fa5f9eb13cb46fe302f838e2451dd Mon Sep 17 00:00:00 2001 From: Snir Sheriber Date: Tue, 31 May 2022 15:44:12 +0300 Subject: [PATCH 2/3] docs: update release process with latest workflow triggering instructions Signed-off-by: Snir Sheriber --- docs/Release-Process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index 9dfc37041a..7e8dfe3290 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -48,7 +48,7 @@ ### Merge all bump version Pull requests - The above step will create a GitHub pull request in the Kata projects. Trigger the CI using `/test` command on each bump Pull request. - - Trigger the test-kata-deploy workflow on the kata-containers repository bump Pull request using `/test_kata_deploy` (monitor under the "action" tab). + - Trigger the `test-kata-deploy` workflow which is under the `Actions` tab on the repository GitHub page (make sure to select the correct branch and validate it passes). - Check any failures and fix if needed. - Work with the Kata approvers to verify that the CI works and the pull requests are merged. From b75d5cee7487837a9a4e4ea5bca54d29b2d1ab33 Mon Sep 17 00:00:00 2001 From: Snir Sheriber Date: Tue, 31 May 2022 15:46:17 +0300 Subject: [PATCH 3/3] docs: update release process github token instructions and fix the gpg generating key url Signed-off-by: Snir Sheriber --- docs/Release-Process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Release-Process.md b/docs/Release-Process.md index 7e8dfe3290..7dcfb84a30 100644 --- a/docs/Release-Process.md +++ b/docs/Release-Process.md @@ -4,11 +4,11 @@ ## Requirements - [hub](https://github.com/github/hub) - * Using an [application token](https://github.com/settings/tokens) is required for hub. + * Using an [application token](https://github.com/settings/tokens) is required for hub (set to a GITHUB_TOKEN environment variable). - GitHub permissions to push tags and create releases in Kata repositories. -- GPG configured to sign git tags. https://help.github.com/articles/generating-a-new-gpg-key/ +- GPG configured to sign git tags. https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key - You should configure your GitHub to use your ssh keys (to push to branches). See https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/. * As an alternative, configure hub to push and fork with HTTPS, `git config --global hub.protocol https` (Not tested yet) *