So we are making some okay momentum on getting things moved over onto
katello and i've hit a interesting point.
In our previous system we have a 'build' repository that was available to
the dev nodes. Every package was placed in that repo, but only version that
passed the testing in that environment were moved to our actual release
repository.
I'm not sure how we would do similarly in Katello. It seems like maybe
content-filters, but that seems like a very heavy way to have to always
publish packages in a repository.
> hey all,
>
>
> So we are making some okay momentum on getting things moved over onto
> katello and i've hit a interesting point.
>
> In our previous system we have a 'build' repository that was available to
> the dev nodes. Every package was placed in that repo, but only version that
> passed the testing in that environment were moved to our actual release
> repository.
>
> I'm not sure how we would do similarly in Katello. It seems like maybe
> content-filters, but that seems like a very heavy way to have to always
> publish packages in a repository.
>
As you mention, the only methods I can think to achieve what you want are:
Add filters for white-listing packages you want to make it through
Add a step in your pipeline to upload a package to the repository when
it passes testing
Push test packages into a repo on Katello, generate a CV, run tests,
when it passes, diff the "test repo" against the "release repo" and
upload/create filters only for those
Thats just off the top of my head, if you think of anything that would help
with this within Katello let us know.
Eric
···
On Tue, May 17, 2016 at 12:04 PM, Greg Swift wrote:
