-
Notifications
You must be signed in to change notification settings - Fork 77
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
DEVOP-53 automatically deploy main branch to devNet #975
Open
mcmillennick
wants to merge
23
commits into
main
Choose a base branch
from
DEVOPS-53-automatically-deploy-main-branch-to-dev
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
DEVOP-53 automatically deploy main branch to devNet #975
mcmillennick
wants to merge
23
commits into
main
from
DEVOPS-53-automatically-deploy-main-branch-to-dev
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mcmillennick
requested review from
l-monninger,
0xmovses and
mzabaluev
as code owners
December 20, 2024 21:34
mcmillennick
changed the title
Devops 53 automatically deploy main branch to dev
DEVOP-53 automatically deploy main branch to dev
Dec 20, 2024
mcmillennick
changed the title
DEVOP-53 automatically deploy main branch to dev
DEVOP-53 automatically deploy main branch to devNet
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
cicd
Adds workflow jobs for triggering new deployment to k8s pipeline.
Changelog
Modified the build-push-containers to trigger and check a workflow in the movement-infra org that deploys the movement-network helm chart to the kubernetes clusters in the devNet environment. This happens after the container checks so that it's guaranteed the containers are built and tested.
Testing
I've done some pretty extensive testing with triggering the workflow both in this repo and the infrastructure repo. I added error handling in the pipeline to make debugging failed deployments a easier.
But once there's a commit on main or a branch is tagged to build the containers we should see this pipeline trigger the devNet deploy.
Outstanding issues
The helm chart sometimes errors out but this shouldn't interfere with the deployment pipeline but will inform in the build-push-containers workflow that triggers the deploy.