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.

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

ci(cloude-release): add repository workflow for cloud release #372

Merged
merged 5 commits into from
Sep 30, 2024

Conversation

jerensl
Copy link
Contributor

@jerensl jerensl commented Sep 16, 2024

Notes for Reviewers

Signed commits

  • Yes, I signed my commits.

Copy link

netlify bot commented Sep 16, 2024

Deploy Preview for bejewelled-pegasus-b0ce81 ready!

Name Link
🔨 Latest commit 4c81b93
🔍 Latest deploy log https://app.netlify.com/sites/bejewelled-pegasus-b0ce81/deploys/66fa99a953765e000870b69c
😎 Deploy Preview https://deploy-preview-372--bejewelled-pegasus-b0ce81.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -0,0 +1,94 @@
name: Publish Version Dispatcher
on:
repository_dispatch:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jerensl can we use a workflow_dispatch instead?

run: |
release_tag=$(curl -sL -H "Authorization: token $ACCESS_TOKEN" -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/layer5io/meshery-cloud/releases/latest | jq -r ".tag_name")
echo "release_tag=$release_tag" >> $GITHUB_OUTPUT
current_tag=$(<build/meshery-cloud.version)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jerensl Can you explain this line?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MUzairS15 This will load the last tags update in the local filesystem, and do some check if it matches with the current tags update it will not do the other step, if so it also will record the version and commit it to the repo.

Wdyt, this is relevant with corn jobs also when an event got triggered more than one time but not sure

@jerensl jerensl merged commit b6473c2 into layer5io:master Sep 30, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants