Learn more about these different git repos.
Other Git URLs
Context
@merlinm and I have been working on Compose Configuration Compare and Check tool (CCCC) tool (https://pagure.io/fedora-ci/cccc). The idea is that for every PR against pungi-fedora, fedora-comps or fedora-module-defaults, there will be a Jenkins job executed which will build two ODCS composes - one "with" the PR applied and one "without" the PR.
This ensures that the PR does not break the compose. The tool will then compare these two composes and report the result back to PR as a comment.
We are now in a phase when we have the Jenkins job running and we can execute it manually.
Request
We would like to start testing this for real PRs against pungi-fedora and limited only to "eln" branch. We would therefore like to configure Jenkins CI in the pungi-fedora repository like showed in the attached image:
<img alt="cccc.png" src="/releng/issue/raw/files/230d489b948aafc2ec38373c914fdeea75d7aa156811d6ce2147fd3b68a1c681-cccc.png" />
I will then need the token Pagure generates and configure it in the https://jenkins-fedora-infra.apps.ci.centos.org/job/cccc. After that, every PR against "eln" branch will be tested as described.
@jkaluza +1 to do this, although I dont know how to restrict it to just eln branch. And I think you should have the permissions to do so, if not I can make the necessary changes.
eln
Metadata Update from @mohanboddu: - Issue tagged with: groomed, low-trouble, medium-gain
Restriction to "eln" branch is done on Jenkins side. But maybe it will also show dummy "test passed" flag for other branches. I will have to test it. Not matter how it works, it should not break any existing workflow.
It's done.
Closing this as the work is done.
Metadata Update from @mohanboddu: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.