On 04/23/2018 02:57 PM, Patrick Creech wrote: > On Mon, 2018-04-23 at 14:01 -0400, Robin Chan wrote: >> I feel like the Travis change is recent enough that I'm not exactly sure how >> they differ from the Jenkins jobs. Are we all clear on these terminology? >> Aren't there multiple jobs running at different >> times? I am not comfortable enough without the assurance that we are all >> talking about the same things to say we don't need "the Jenkins jobs". I >> would like for some of these discussions around >> release process and where (and what and when) different tests are run be a >> little bit more collaborative from the beginning rather than reactive >> post-change happening. >> >> I'm all for making quick incremental changes. I'm happy that there are test >> results that are accessible to everyone. I don't want us to over thinking >> these, but are we sure we don't have any tests >> that need to stay private (do we test for any security type things that >> might need to be embargoed before reported)? I want to make sure we think >> thing through before we start tearing stuff down. >> > The build team, for one, has not had time yet to do an assessment on if > travis will be able to provide all the packaging related items needed to > generate RPMs. There are also infrastructure security > implications we have yet to analyze as well. So, at least for rpm packaging > requirements, these are still a big ? till we have time to evaluate. >
Can someone summarize for me what there is Yet Another Process? -- bk
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pulp-dev mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-dev
