Just a brief update on this thread.

I have installed pulp 2.10.0-0.4.beta.el7 on a clean development environment and have run both the runcible and katello test suites.

The results were:
    runcible: 252 tests, 632 assertions, 0 failures, 0 errors, 3 skips
    katello: 1832 runs, 4448 assertions, 0 failures, 0 errors, 8 skips

I plan to run manual tests with katello, but so far it is looking good. That said, we'll want/need to run through them again once pulp 2.10 is no longer in beta.

thanks,
Brad

On 08/24/2016 05:33 PM, Tom McKay wrote:
Katello and foreman are nearing dev freeze in early September but there are a few features centered around Atomic Host and Atomic Registry that will need changes introduced in pulp-2.10. While I understand pulp-2.10 is currently still in beta, I was hoping we could bring it into katello now ahead of dev freeze so the dependent integration could be completed.

If we did bring in pulp-2.10, it would have to be with the understanding that breakages on both sides would need to be fixed prior to katello releasing. I know this is usually how things go anyways but I just wanted to state it up front.

Also, are there resources to do this work? If I understand things correctly, it's not just as simple as updating a repo file to point to pulp-2.10, but that changes to runcible would also need to be made? Is this something that could be done ASAP? Sooner means more time to shake out issues.

Thoughts?
--
You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected] <mailto:[email protected]>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to