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

Deployment Updates - CI #202

Merged
merged 3 commits into from
Jun 18, 2023
Merged

Deployment Updates - CI #202

merged 3 commits into from
Jun 18, 2023

Conversation

GrantBirki
Copy link
Member

Deployment Updates - CI

This pull request updates our Actions workflows to incorporate two new "alternate" workflow types that I recently bundled into the branch deploy Action:

  • merge commit workflow: This workflow type checks merge commits to prevent re-running a deployment when a PR is merged to main if its SHA matches the latest deployment
  • unlock on merge workflow: This workflow type releases any sticky locks that are associated to a pull request when that pull request is merged

I also figured out why CI is failing but only on dependabot PRs. So I created a new .md file to document this.

@GrantBirki GrantBirki added documentation Improvements or additions to documentation github_actions Pull requests that update GitHub Actions code labels Jun 18, 2023
@GrantBirki GrantBirki requested a review from a team as a code owner June 18, 2023 04:18
@github-actions
Copy link
Contributor

👋 Thanks for opening a pull request!

If you are new, please check out the trimmed down summary of our deployment process below:

  1. 👀 Observe the CI jobs and tests to ensure they are passing

  2. ✔️ Obtain an approval/review on this pull request

  3. 🚀 Deploy your pull request to the development environment with .deploy to development

  4. 🚀 Deploy your pull request to the production environment with .deploy

    If anything goes wrong, rollback with .deploy main

  5. 🎉 Merge!

Need help? Type .help as a comment or visit the usage guide for more details

Please note, if you have a more complex change, it is advised to claim a deployment lock with .lock <environment> --reason <reason> to prevent other deployments from happening while you are working on your change.

Once your PR has been merged, you can remove the lock with .unlock <environment>.

@GrantBirki
Copy link
Member Author

.lock --reason testing sticky locks

@github-actions
Copy link
Contributor

🔒 Deployment Lock Claimed

You are now the only user that can trigger deployments to the production environment until the deployment lock is removed

This lock is sticky and will persist until someone runs .unlock production

@GrantBirki
Copy link
Member Author

.deploy

@github-actions
Copy link
Contributor

Deployment Triggered 🚀

GrantBirki, started a branch deployment to production

You can watch the progress here 🔗

Branch: ci-deployment-updates

@github-actions github-actions bot temporarily deployed to production June 18, 2023 04:21 Inactive
@github-actions
Copy link
Contributor

API Deployment - Production 🌔

The API has been deployed to the production environment 🚀

Pusher: @GrantBirki, Action: issue_comment, Workflow: branch-deploy;

@github-actions
Copy link
Contributor

Deployment Results ✅

GrantBirki successfully deployed branch ci-deployment-updates to production

Environment URL: api.tarkov.dev/graphql

@GrantBirki GrantBirki merged commit adc0d6d into main Jun 18, 2023
@GrantBirki GrantBirki deleted the ci-deployment-updates branch June 18, 2023 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation github_actions Pull requests that update GitHub Actions code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants