Convert Jenkins Pipelines to GitHub Actions Workflows #2
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.
Convert Jenkins Pipelines to GitHub Actions Workflows
Summary
This PR converts the existing Jenkins CI/CD pipelines to GitHub Actions workflows while maintaining the same DevSecOps approach. The conversion includes:
CI Pipeline (
.github/workflows/ci.yml):CD Pipeline (
.github/workflows/cd.yml):Review & Testing Checklist for Human
This is a high-risk change that replaces the entire CI/CD system. Please verify the following 5 critical items:
madhupdevops/bankappbut CD updatestrainwithshubham/bankapp-eksin the manifest - verify this is intentional or needs alignmenthttps://your-sonarqube-server.comto actual SonarQube server and verify scanner installation worksSONAR_TOKEN,DOCKERHUB_TOKEN,EMAIL_PASSWORDbefore testingtrainwithshubham@gmail.com) are appropriate for notificationsNotes
DevOpsbranch and maintain the same security scanning sequence as Jenkins