Hi all, My name is Yiming and I'm the contributor of Jenkinsfile Runner for GitHub Actions Project <https://www.jenkins.io/projects/gsoc/2022/projects/jenkinsfile-runner-action-for-github-actions/> for GSoC 2022. As the development of my POC project <https://github.com/Cr1t-GYM/jenkins-action-poc> is nearing the end, I’d like to migrate my repository to the GitHub jenkinsci organization using the steps of opening a hosting request <http://www.jenkins.io/doc/developer/publishing/requesting-hosting/>. The idea of this project is based on jenkinsfile-runner-github-actions <https://github.com/jenkinsci/jenkinsfile-runner-github-actions> and it’s powered by jenkinsfile-runner <https://github.com/jenkinsci/jenkinsfile-runner>.
This project intends to develop some useful GitHub Actions. There are a total of 5 actions in my POC project and one demo/example project. Based on the discussion with my mentors and the rules of publishing actions in GitHub Marketplace <https://docs.github.com/en/actions/creating-actions/publishing-actions-in-github-marketplace>, I need to create different repositories for these 5 GitHub Actions. Therefore, I need 5 repositories for actions, 1 repository for the demo project and 1 repository for hosting the centralized documentation using GitHub Pages. Here is a short description for these actions. You can check the further details in the POC README <https://github.com/Cr1t-GYM/jenkins-action-poc>. Based on the difference in the running environment, I split these actions into two groups which are Runtime type actions and Container type actions. 1. Runtime type actions: These actions run the pipeline in the GitHub Actions runners host machines directly. 1. jenkins-setup <https://github.com/Cr1t-GYM/jenkins-action-poc/tree/master/jenkins-setup>: It's used to set up the Jenkins environment, including but not limited to Jenkins core, plugin installation manager and Jenkinsfile Runner. 2. jenkins-plugin-installation-action <https://github.com/Cr1t-GYM/jenkins-action-poc/tree/master/jenkins-plugin-installation-action>: Users can use it to install extra plugins. jenkins-setup needs to be run before. 3. jenkinsfile-runner-action <https://github.com/Cr1t-GYM/jenkins-action-poc/tree/master/jenkinsfile-runner-action>: It runs the Jenkins pipeline in the host machine. jenkins-setup needs to be run before. 2. Container type actions: These actions run the pipeline in the customized container. 1. jfr-container-action <https://github.com/Cr1t-GYM/jenkins-action-poc/tree/master/jfr-container-action>: It runs the Jenkins pipeline in the declared container. As the prebuilt container is declared in advance, it can integrate with other GitHub Actions theoretically. 2. jfr-static-image-action <https://github.com/Cr1t-GYM/jenkins-action-poc/tree/master/jfr-static-image-action>: It runs the Jenkins pipeline in the runtime built container. It doesn't need to declare the container in advance so users cannot use other GitHub Actions except using `actions/checkout` to set up the workspace. But the users are able to override the base image by providing the docker image URL. For instance, if users want to combine the Jenkins environment with nodejs environment, they can use `node:18.3.0` as input. Here are useful links: 1. Project page: https://www.jenkins.io/projects/gsoc/2022/projects/jenkinsfile-runner-action-for-github-actions/ 2. POC repository: https://github.com/Cr1t-GYM/jenkins-action-poc 3. Demo repository: https://github.com/Cr1t-GYM/Jenkinsfile-runner-actions-demo 4. Guide to Plugin Hosting: http://www.jenkins.io/doc/developer/publishing/requesting-hosting/ I intend to follow the official guidelines and to submit the relevant PRs to follow up on this matter, which will be subject to the usual process for Jenkins plugins hosting. This will happen over the next few weeks and I hope all relevant parties will be okay with the new arrangement. 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAOr_RqY6%2BZykk_Ydi%3D6YbhRbbe1dZT9RVgF-jQ5eznw49O4hwQ%40mail.gmail.com.
