Remote Artifacts

[otaviof]

Creating this placeholder issue to keep track of the feature #419 (Remote Artifacts).

[SaschaSchwarze0]

@otaviof is there anything remaining for this issue ?

[sbose78]

Are you tracking API improvements in this one ?

[otaviof]

@SaschaSchwarze0, @sbose78 sorry for the late reply :-) We could close this issue and open it up again later on, or even, create new issues as we need to discuss further API changes and feature enhances.

[adambkaplan]

/close

Implemented in #616

[openshift-ci-robot]

@adambkaplan: Closing this issue.

In response to this:

/close

Implemented in #616

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[qu1queee]

I would like to add that the remote artifacts is not fully implemented yet. The spec.sources does not support git at the moment, which is one of our most popular features. We should ensure that what we wrote in EP reflects our implementation.

Having all specifications implemented, will also allow us to move out of spec.source eventually. At the moment the API can be confusing when wondering about spec.source vs spec.sources , plus the current tribe knowledge, that spec.sources is half baked.

[qu1queee]

@adambkaplan @otaviof we should re-open this one, and discuss at grooming when we think we should complete it. We should not lose track of the missing features.