Request to Create New Repository for GSoC 2025 Project: Jenkins Domain Specific LLM

[chiruu12]

Hi,

This request is related to the GSoC 2025 project: https://www.jenkins.io/projects/gsoc/2025/projects/domain-specific-LLM-based-on-jenkins-usage-using-ci-jenkins-io-data/

The project focuses on developing a Jenkins domain-specific Large Language Model trained on actual CI usage patterns from ci.jenkins.io. The project initially began as a standalone LLM, but has since shifted to an agentic architecture approach while retaining the same core objectives around Jenkins-aware guidance.

We would like to request the creation of a new public repository under the jenkinsci GitHub organization:

Repository Name jenkins-domain-LLM

Repository Purpose This repository will contain the implementation of the agentic Jenkins Domain system.

The repository will include:

• Data extraction and processing pipelines based on Jenkins job usage
• Tools to generate and update domain-specific knowledge artifacts
• Agentic workflow components for task planning and assistance
• Evaluation and benchmarking utilities to validate the system’s recommendations and behavior
• Interfaces intended for future integration into Jenkins user-facing experiences (e.g., CLI, web UI, or chat assistance)

The project is currently developed in a personal repository and is ready to be migrated to the official organization repository: https://github.com/chiruu12/jenkins-domain-LLM

The project is currently being developed in a personal repository and is ready to be migrated once the official repository is created.

GitHub Users to Receive Maintain Permission

• @chiruu12
• @harsh-ps-2003
• @shivaylamba
• @cnu1812
• @gounthar
• @krisstern

Permissions Needed Maintain

Secrets None required at this stage.

FYI: @jenkinsci/gsoc-mentors

[krisstern]

@dduportal Is it okay for me to add the repo to under jenkins-infra directly?

[dduportal]

@krisstern please wait for the infra team to triage the ticket and see what is needed / not needed in order to avoid too many changes. I'm asking because the initial message mentions jenkinsci and you are asking about jenkins-infra organization. These are different set of responsibilities.

On first sort (and superficial) sight, it looks like this repository should be in the jenkinsci organization as its code would benefit the Jenkins users or contributors. I don't see why it should be on the jenkins-infra as it does not seem related to any infrastructure element or service, but I might be wrong (in that case what "infrastructure" service is targeted)?

[krisstern]

@dduportal I think there is some confusion here as I told @chiruu12 to request migration to jenkins-infra and not jenkinsci. This is because this repo is similar in nature to https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge, and that it is not a plugin. What do you think?

[dduportal]

@dduportal I think there is some confusion here as I told @chiruu12 to request migration to jenkins-infra and not jenkinsci. This is because this repo is similar in nature to https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge, and that it is not a plugin. What do you think?

I see, thanks the explanation which explains your request.

However the justification for putting https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge in jenkins-infra was https://github.com/jenkins-infra/helpdesk/issues/4260#issuecomment-2315098436

The code in https://github.com/nouralmulhem/Enhancing-LLM-with-Jenkins-Knowledge is expected to produce artifacts/data consumed by the Jenkins Infra.

=> It appears it was wrong. This 2024 project never had an ounce of Jenkins related infrastructure in the end after many turn arounds. This is why I believe jenkinsci is the best home as per @timja 's message in https://github.com/jenkins-infra/helpdesk/issues/4262#issuecomment-2308948354.

Unless of course there is a really clear definition of which infrastructure is required and what problem is solves (which was never answered in last year project).

Of course, if the new 2025 GSoC project ends in a clear definition (followed by a consensus on why it would be good and useful to allocate Jenkins infrastructure budget and maintainers time), we can revisit or even better "split": having the application code and binaries hosted in jenkinsci and any infrastructural-related stuff (deployment manifest, production data, etc.) in the jenkins-infra (a 2 step processes a bit like we do with Docker images of the infra).

Does it make sense? Did I miss something?

[dduportal]

Ping @jenkins-infra/jenkinsci-admins (to create the new repository with the described elements)

[NotMyFault]

Ping @jenkins-infra/jenkinsci-admins (to create the new repository with the described elements)

I've invited @chiruu12 to https://github.com/jenkinsci-transfer. They can transfer the repository to the organization, from where we org admins can transfer it to jenkinsci, preserving the history.

[lemeurherveCB]

the justification for putting https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge in jenkins-infra was #4260 (comment)

The code in https://github.com/nouralmulhem/Enhancing-LLM-with-Jenkins-Knowledge is expected to produce artifacts/data consumed by the Jenkins Infra.

=> It appears it was wrong. This 2024 project never had an ounce of Jenkins related infrastructure in the end after many turn arounds. This is why I believe jenkinsci is the best home as per @timja 's message in #4262 (comment).

Could https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge also be moved to @jenkinsci?

[dduportal]

the justification for putting https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge in jenkins-infra was #4260 (comment)

The code in https://github.com/nouralmulhem/Enhancing-LLM-with-Jenkins-Knowledge is expected to produce artifacts/data consumed by the Jenkins Infra.

=> It appears it was wrong. This 2024 project never had an ounce of Jenkins related infrastructure in the end after many turn arounds. This is why I believe jenkinsci is the best home as per @timja 's message in #4262 (comment).

Could https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge also be moved to @jenkinsci?

Nope because it has been featured in blog post and other papers. And we don't know how much GitHub can keep the redirections links alas.

[timja]

Nope because it has been featured in blog post and other papers. And we don't know how much GitHub can keep the redirections links alas.

Transferring across orgs is fine, as long as you don't re-create the repo the redirect will work

[krisstern]

@dduportal Sounds good! Your suggestion makes perfect sense

[krisstern]

Ping @jenkins-infra/jenkinsci-admins (to create the new repository with the described elements)

I've invited @chiruu12 to https://github.com/jenkinsci-transfer. They can transfer the repository to the organization, from where we org admins can transfer it to jenkinsci, preserving the history.

c.c. @chiruu12

[chiruu12]

Ping @jenkins-infra/jenkinsci-admins (to create the new repository with the described elements)

I've invited @chiruu12 to https://github.com/jenkinsci-transfer. They can transfer the repository to the organization, from where we org admins can transfer it to jenkinsci, preserving the history.

@NotMyFault Hey can you please send the invite again! I had missed the invite earlier and was traveling after that.

[timja]

I sent you an invite

[krisstern]

@chiruu12 could you please check if you have received an invitation again?

[chiruu12]

@krisstern yes got it thx!

[lemeurherve]

Transferring across orgs is fine, as long as you don't re-create the repo the redirect will work

@timja: could you also transfert https://github.com/jenkins-infra/Enhancing-LLM-with-Jenkins-Knowledge to @jenkinsci please?

[timja]

Moved

[chiruu12]

@timja I just saw that I got removed from the jenkinsci-transfer org. We have not transferred the ownership of the repo yet.

[timja]

@NotMyFault removed you, I've readded you.

[NotMyFault]

Oh I thought this was already done after a week.

[timja]

Done: https://github.com/jenkinsci/domain-llm