devops: od-website deployment - #5
Merged
Merged
Conversation
added 4 commits
March 15, 2026 10:57
In a familiar fashion to od-official-server, this pipeline seeks to build a new docker image based on the newest tag and push it to our registry which in turn will get deployed by k8s.
od-website1 omegalul
Job needs npm i to run successfully...
Replacing original Jenkinsfile with this one which interacts with kubernetes, avoiding manual intervention for deployment process. When a new release of the website is to be shipped, the developer should create a new tag corresponding to our versioning standard which will be automatically deployed on our infrastructure.
OllieOlafsson
requested review from
Doru991,
ValentinNimigean,
catyuzu23 and
kickhead13
March 15, 2026 11:42
catyuzu23
approved these changes
Mar 16, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
I've updated our Jenkins pipeline to automatically deploy our website.
Relevant for frontend devs!
When shipping a new version of our website, one should create a tag corresponding to our versioning standard. Ideally, with changes from our main branch.