Hi all, My name is Yiming and I'm the contributor of Jenkinsfile Runner for GitHub Actions Project in GSoC-2022. As my project begins, I need the advice from the Jenkins community to make it more useful to the users.
The Jenkinsfile Runner for GitHub Actions Project in GSoC-2022 intends to build useful GitHub Actions for Jenkinsfile-runner and Plugin Installation Manager Tool. The users can utilize these GitHub Actions for their own workflow definitions. Therefore, running the Jenkins pipeline inside the GitHub Actions becomes available. You can find our project plan, POC project and demo project here. The POC project and project plan doc are still in update so it can be different by day: 1. Proof of concept about these Jenkins Actions: https://github.com/Cr1t-GYM/jenkins-action-poc 2. A demo about applying these Jenkins Actions in a small SpringBoot project: https://github.com/Cr1t-GYM/JekinsTest 3. A demo action log for these Jenkins Actions: https://github.com/Cr1t-GYM/JekinsTest/actions/runs/2518717187 4. Project Plan: https://docs.google.com/document/d/154a7pZbLaZqGYpgsefohDHU2uueYypVNJJ_aBEyPHFY/edit# 5. Original idea about Jenkins Actions: https://github.com/jenkinsci/jenkinsfile-runner-github-actions 6. Jenkinsfile-runner project: https://github.com/jenkinsci/jenkinsfile-runner 7. An example workflow definition about how to use these actions: https://github.com/Cr1t-GYM/JekinsTest/blob/master/.github/workflows/ci.yml We give three common cases about how to play with these actions: 1. jenkins-plugin-installation-action + jenkinsfile-runner-action: Download all the dependencies and run the pipeline at the runtime. 2. jfr-container-action: Use the jenkinsfile-runner vanilla distribution in the jenkins/jenkinsfile-runner repository. All the actions will be run in this container. 3. jfr-static-image-action: Create a Docker action for Jenkins pipeline. This action has its own working environment. It won't have an extra environment relationship with the on demand VM outside unless the user mounts other directories to the container (For example, checkout action if it exists). After the docker action ends, this container will be deleted. Although we didn't release these actions yet, you can reference these actions URI in your workflow definitions: 1. Cr1t-GYM/jenkins-action-poc/jenkins-plugin-installation-action@master 2. Cr1t-GYM/jenkins-action-poc/jenkinsfile-runner-action@master 3. Cr1t-GYM/jenkins-action-poc/jfr-container-action@master 4. Cr1t-GYM/jenkins-action-poc/jfr-static-image-action@master We appreciate any feedback on this proposal along the lines of the following questions: 1. Which actions do you prefer and why? 2. Do the current actions meet your project needs? 3. What kind of enhanced functionality do you look for in these actions? 4. Etc. Your opinions about our project are valuable. Thanks for your prompt attention! Sincerely, Yiming Gong GSoC 2022 Contributor -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOr_RqbiWrZELt907n7_SNyUpC-VdpFGbAEMXQBg_VJVPo99JQ%40mail.gmail.com.
