Refactor using multiple build artifacts as arbitrary pipeline results
The following discussion from !5773 (merged) should be addressed:
-
@grzesiek started a discussion: (+2 comments) I have a feeling that we reached maximum amount of technical debt and duplication related to
has_artifact?
andexpose_*?
, scopes, delegated methods, head/base pipelines etc. I think it deserves building a carefully crafted abstraction for that, maybe encapsulating this inside a concern or a separate class. Should we refactor this? /cc @dzaporozhets
/cc @dzaporozhets