Conversation
ekohl
left a comment
ekohl
left a comment
There was a problem hiding this comment.
This is a good base. I never know how detailed it needs to be so feel free to ignore my suggestions.
|
|
||
| The packages are built by [Jenkins](jenkins.md) on a Jenkins node configured using the [`jenkins_node::packaging::rpm`](https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/jenkins_node/manifests/packaging/rpm.pp) Puppet class. | ||
|
|
||
| Jenkins prepares an SRPM and submits the build to [COPR](https://copr.fedorainfracloud.org/), which performs the actual build. |
There was a problem hiding this comment.
Would it help to mention we have https://ci.theforeman.org/job/foreman-packaging-rpm-copr-nightly-release/ for regular packages (and foreman-packaging-rpm-${release}-release for stable branches) together with ${package}-${branch}-package-release for nightly packages? Those are the actual jobs that prepare the SRPM and submit.
And then we have a similar setup for pulpcore-packaging, but candlepin-packaging is special.
| COPR publishes the built packages in own repositories, but doesn't support neither filtering nor gating of the built packages. | ||
| Instead we use a process where a staging repository is built based on the COPR content, published to `stagingyum.theforeman.org`, tests are executed and once the tests pass the repository is published to `yum.theforeman.org`. | ||
|
|
||
| For nightly, the process can be seen in [`foreman-rpm.groovy`](https://github.com/theforeman/jenkins-jobs/blob/master/theforeman.org/pipelines/release/pipelines/foreman-rpm.groovy). |
There was a problem hiding this comment.
Should we also mention the concrete pipelines? Like https://ci.theforeman.org/job/foreman-nightly-rpm-pipeline/
|
Mhh, maybe calling the PR "packaging workflows" was not the best idea 😅 Not arguing that better docs on the various jenkins jobs would be cool, just not what I wanted to work on here ;) |
evgeni
changed the title
|
@theforeman/packaging anyone has any objections to merging this? |
|
🤷♀️ |
2 participants
No description provided.