Decouple implicit build → test relationship

[TomasTomecek]

As we are heading in the direction of having multiple jobs that can consume artifacts from other (hello vm-image-build), we should decouple the implicit relationship of copr_build and tests jobs.

The expectation here is that:

• tests job needs a copr_build job if RPMs are consumed there: Require copr build job definition for running tests #1775
• /packit copr_build doesn't trigger tests
• the relationship needs to be explicitly referenced: SPIKE: jobs referencing #1773

[lachmanfrantisek]

+1 for the decoupling, it will make the code really simpler!

• /packit copr_build doesn't trigger tests

Hmm, I am wondering how to do this. And if this is really needed. (Test submission is done when we receive a build result.)

[TomasTomecek]

+1 for the decoupling, it will make the code really simpler!

• /packit copr_build doesn't trigger tests

Hmm, I am wondering how to do this. And if this is really needed. (Test submission is done when we receive a build result.)

You are right! The point is, it should be configurable :) The "jobs referencing" should solve it.

[mfocko]

+1 for the decoupling, it will make the code really simpler!

• /packit copr_build doesn't trigger tests

Hmm, I am wondering how to do this. And if this is really needed. (Test submission is done when we receive a build result.)

Maybe we're getting to the point where job trigger is not actually a job trigger and we want job trigger and job source 😄 /s

ps: 🗡️ sounds good

[lachmanfrantisek]

Maybe we're getting to the point where job trigger is not actually a job trigger and we want job trigger and job source smile /s

Exactly!
Do we want to solve that here? Or do this separately? (Since it's valid to all the downstream jobs as well.

[lachmanfrantisek]

Still relevant but low prio.