Migration of Jenkins Pipeline to GitHub Actions

Author(s)	Vidhi Khubchandani
Country	India
Abstract	Moving your continuous integration and continuous deployment (CI/CD) pipelines from Jenkins to GitHub Actions offers several benefits, including savings and a more flexible and secure hybrid model. Jenkins installations usually use servers hosted in their own data centers, while GitHub operations offer a hybrid model where DevSecOps self-hosted runners can be used for secure workflows and open runners for other common workflows that handle less sensitive data/code. GitHub Actions and Jenkins share some similarities, making the transition to GitHub Actions relatively easy.
Field	Computer > Design
Published In	Volume 5, Issue 6, November-December 2023
Published On	2023-11-27
Cite This	Migration of Jenkins Pipeline to GitHub Actions - Vidhi Khubchandani - IJFMR Volume 5, Issue 6, November-December 2023. DOI 10.36948/ijfmr.2023.v05i06.8905
DOI	https://doi.org/10.36948/ijfmr.2023.v05i06.8905
Short DOI	https://doi.org/gs632n

About IJFMR Fees & Payment Current Issue Publication Archive	Submit Research Paper Track Submission Status Publication Guidelines Publication Ethics Peer Review & Plagiarism	Join as a Reviewer Editors & Reviewers Reviewer Referral Program Get Reviewer Membership Certi.	Website/Journal Policies Usage Policy Content Policies Privacy Policy

Contact Us		+91-9898-5948-55	editor@ijfmr.com

International Journal For Multidisciplinary Research