[GSOC] Interested in Improving Jenkinsfile Runner abilities and GitHub Actions

Hello,

My name is Yongjun Hong, and I have contributed to over 20 Java-based open-source projects, including JUnit5, Spring Boot, and Naver’s Fixture Monkey and various apache projects.

One of the most meaningful contributions I’ve made was implementing parallel execution in JUnit5’s Vintage Engine. Originally, test executions were strictly sequential, but I enhanced performance by enabling parallel execution at both the class and method levels. During this process, I also identified and resolved a deadlock issue, which further deepened my understanding of concurrency and strengthened my Java expertise.

Currently, I’m particularly interested in enhancing the functionality of Jenkinsfile Runner and integrating it with GitHub Actions. I believe this project offers a practical solution to common CI/CD automation challenges, especially as teams transition to modern Jenkins tech stacks. With my experience in Java and Docker, I’m confident I can help modernize Jenkinsfile Runner and reinforce its integration with GitHub Actions.

As part of a formal proposal, I’m planning to prepare a basic architectural document for the project. Would you happen to have any specific directions or considerations you’d like me to keep in mind?

You can find a summary of my past contributions on my GitHub profile below

Thank you for your time, and I look forward to hearing your thoughts.

Best regards,

Yongjun Hong

Hello and welcome to this community, @YongGoose. :waving_hand:

I’m afraid the project you chose is still in the draft ideas, as we don’t have a lead mentor to offer guidance to a mentee. :person_shrugging:

That doesn’t mean your help is not welcome, far from it.

To start interacting with the project, I’ll quote Mark Waite:

The project overview page includes the code card with links to two of the GitHub organizations we use. Many Jenkins components track their issues in GitHub. Good first issues are a great place to start.
The Hacktoberfest 2024 blog post includes a link to the Hacktoberfest events page. That page includes a link to the Jenkins Jira issue tracker and its friendly issues report. They are also a good place to start.

1 Like

Thank you for your response!
I’ll take a positive look at other ideas as well.

1 Like

@poddingue

If I want to participate as a mentor for a draft idea, should I also write a draft and submit it via Google Form?

No, you don’t have to.
Let @krisstern know about that, and they will tell you what to do. :+1:

2 Likes

Hi @YongGoose I don’t think it would be a good idea for us to add new project ideas now as Google has already reviewed our project ideas. But could you please tell us more about your background if you are interested in joining us as a GSoC mentor for the existing project ideas so we could consider your case?

1 Like

@krisstern

Sure! :slight_smile:

I am a backend developer who graduated this February with a degree in Computer Science. During my college years, I naturally developed an interest in web development and CI/CD. Initially, I gained hands-on experience by implementing CI/CD through GitHub Actions, and more recently, I have been focusing on learning Jenkins in depth.

I also worked on a 4-month contract with IT companie in Korea, where I built CI/CD pipelines using Jenkins. Through this role, I gained practical experience handling Jenkins Pipelines and developing essential technical and problem-solving skills. Since my contract ended on March 31, there is no issue regarding my eligibility for GSoC.

In addition, I have actively contributed to the open-source community. I have participated in projects such as JUnit5, Naver’s Fixture-Monkey, and various Apache projects(e.g seata), providing code reviews and technical support. Beyond simply contributing new features, I have taken the initiative to propose enhancements. For example, while working on an issue related to introducing parallelization in JUnit5’s Vintage Test Engine, I noticed that class-level parallelization offered minimal performance benefits when running a single class. Therefore, I proposed and implemented method-level parallelization, during which I also identified and resolved a deadlock issue. [1]

Furthermore, I have improved my mentoring skills by teaching Spring Boot to 20 college students over the course of a year [2], which allowed me to develop effective knowledge-sharing and mentoring techniques.

Although my professional experience may be relatively short, I believe my greatest strengths are persistence and passion. I am confident that these qualities will enable me to make a positive contribution to the GSoC mentor team. I look forward to the opportunity to help advance the project and drive innovation within the Jenkins ecosystem.

Thank you.

Yongjun Hong

P.S. If you need more information, I would be happy to send you my resume and portfolio via email.

[1] : Support parallelization in junit-vintage-engine by YongGoose · Pull Request #4135 · junit-team/junit5 · GitHub
[2] : Hong Yong Jun, Son, java developer, open source enthusiast

1 Like

Hi @YongGoose it sounds like you are more suitable to be a GSoC contributor then a mentor.

I feel the same way.
Thank you for your comment.

@krisstern

I noticed on the page that it’s possible to give feedback on project idea drafts and even participate as a mentor. That’s why I was asking about the possibility of joining as a mentor!

I have a few questions regarding this.
It looks like you’re listed as a potential mentor for the mission below.

I’m really interested in working on this mission, and I’d love to know how I can apply and get started. :rocket:

It would be great to have the opportunity to work with you! :eyes:

Hi @YongGoose I do not think you have the required experiences to serve as a mentor at this time. Also, the project idea you are intesrested in is not going to go ahead, so if you are interested in applying as a contributor we would advice you to choose another project idea from the accepted list instead.

Got it! I’ll check the accepted project list and look for another project to contribute to.

Thanks for letting me know!