Skip to content

artifacts: Destination for "local" artifact can be anything

Limiting the destination of a local artifact to a relative path doesn't afford any benefit and is easily circumvented (using a two step copy via a temporary variant for instance).

Remove the relativelocal validation from destination and allow users to copy directly to any path within the build container.

Merge request reports

Loading