Convert Jenkins CI/CD pipelines to GitHub Actions workflows#3
Open
devin-ai-integration[bot] wants to merge 2 commits intoDevOpsfrom
Open
Convert Jenkins CI/CD pipelines to GitHub Actions workflows#3devin-ai-integration[bot] wants to merge 2 commits intoDevOpsfrom
devin-ai-integration[bot] wants to merge 2 commits intoDevOpsfrom
Conversation
- Replace Jenkins CI pipeline with GitHub Actions CI workflow (.github/workflows/ci.yml) - Replace Jenkins CD pipeline with GitHub Actions CD workflow (.github/workflows/cd.yml) - Archive legacy Jenkins files in legacy/jenkins directory - Add documentation for required GitHub Actions secrets (.github/SECRETS.md) - Update README.md and cicd.md to reflect GitHub Actions migration - Maintain all existing functionality: security scanning, code quality, Docker build/push, GitOps deployment Features: - Trivy filesystem scanning with vulnerability reporting - OWASP dependency check with artifact upload - SonarQube analysis with quality gates - Docker build and push to Docker Hub with proper authentication - GitOps workflow with automatic Kubernetes manifest updates - Email notifications matching existing Jenkins format - Repository dispatch for CI/CD pipeline coordination - Manual workflow triggers via workflow dispatch Co-Authored-By: Stephen Cornwell <stephencornwell20@gmail.com>
- Remove original Jenkins files (Jenkinsfile, GitOps/Jenkinsfile, vars/) - Update README.md with GitHub Actions migration documentation - Update cicd.md with GitHub Actions workflow information - All Jenkins functionality now replaced with GitHub Actions workflows Migration complete: - CI workflow: .github/workflows/ci.yml - CD workflow: .github/workflows/cd.yml - Secrets documentation: .github/SECRETS.md - Legacy files preserved: legacy/jenkins/ Co-Authored-By: Stephen Cornwell <stephencornwell20@gmail.com>
Author
|
Prompt hidden (unlisted session) |
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
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 CI/CD pipelines to GitHub Actions workflows
Summary
This PR completely migrates the existing Jenkins-based CI/CD system to GitHub Actions workflows while maintaining full feature parity. The migration includes:
Jenkinsfilewith.github/workflows/ci.ymlcontaining 10 stages including security scanning (Trivy, OWASP), code quality (SonarQube), and Docker operationsGitOps/Jenkinsfilewith.github/workflows/cd.ymlfor GitOps deployment with Kubernetes manifest updates and email notificationslegacy/jenkins/directory for reference.github/SECRETS.mdThe GitHub Actions workflows provide equivalent functionality to the original Jenkins pipelines with improved integration to GitHub's native CI/CD platform.
Review & Testing Checklist for Human
.github/SECRETS.md(Docker Hub, SonarQube, email SMTP credentials)gh workflow run ci.yml --ref DevOps -f docker_tag=test-v1.0kubernetes/bankapp-deployment.ymlNotes
The CD workflow modifies and commits to the DevOps branch directly - ensure this doesn't conflict with any branch protection rules.
Link to Devin run: https://app.devin.ai/sessions/deb656576f2b4c039973f44c3901fa47
Requested by: Stephen Cornwell (@stephencornwell)