Automatic PR to migrate frontend pipelines from Jenkins to DK CI/CD #88
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
![dk-cicd[bot]](https://avatars.githubusercontent.com/in/305893?s=60&v=4){kind=small}
jeffersontuc
force-pushed
the
setup/dk-cicd
branch
from
a497019
to
04d2f11
Compare
jeffersontuc
approved these changes
Feb 26, 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.
This PR is part of the process of migrating pipelines from Jenkins to DK CI/CD + DK IaC. It migrates the
frontendpipelines (CI and Deploy) from Jenkins to DK CI/CD.Main Changes
We have configured two pipelines within the DK CI/CD UI for each project containing Frontend applications.
The
node-ci-v1pipeline is responsible for building and testing each new push that reaches the repo. Is it possible to activate lint and sonar, removing "skipLint" and "skipScan" respectively.The
build-node-app-and-upload-artifacts-v1Is responsible for building and uploading the project in S3 when any tag is created.Before merging this PR, it is recommended that you review the DK CI/CD pipeline configurations by comparing them with the current setup.
Usage
The usage remains the same as before: pushing a new tag will build the project, followed by uploading the artifacts in S3.
Contact
If you have doubts about configuring the pipelines, you can reach us via the #jenkins-0 Slack channel.