The schema validator for zuul.artifacts returned via zuul_return
did not allow for extra return data (outside of the zuul hierarchy).
Correct the validator to allow that, and update the test to exercise
it.
Change-Id: Ia8d7ed212b03d978bec1a7de1a2647b0c87b7cf9
In order to make it simple for multiple independent playbooks to return
artifacts, append the values of zuul.artifacts in zuul_return rather than
the usual method of overwriting lists.
Change-Id: I09e6076b4bb354023c5414d149d9bfa59fb3ea4b
The plan for the idea of a "promote" pipeline is to fetch
previously uploaded artifacts from the build log server
and move them to the final publication location. However,
jobs which store data (such as documentation builds,
tarballs, or container images) on the log server should not
need to know the configuration of the log server in order
to return the artifact URL to zuul. To support this, if
the job returns a relative URL for an artifact, assume it
is relative to the log URL for the build and combine the
two when storing the artifact info.
Change-Id: I4bce2401c9e59fd469e3b3da2973514c07faecf2
Add an artifact table to the SQL reporter, and allow builds to store
artifact URLs using zuul_return. The web API will return the urls.
Change-Id: I8adfc25cc93327ca73c98bbe170e8f39a0864f7f
James E. Blair