Update base-test jobs to publish artifacts too

If the job succeeded and doesn't have a zuul.change, it means it's
operating on landed code. That means anything on the executor in the
artifacts directory should be published to tarballs.o.o/{project}.

Change-Id: Ia6add476b7b1933353f1bc4736ff07ff1083857b
This commit is contained in:
Monty Taylor 2019-01-15 18:28:45 +00:00
parent e4b44ada5e
commit 257740e1f8
No known key found for this signature in database
GPG Key ID: 7BAE94BC7141A594
2 changed files with 17 additions and 0 deletions

View File

@ -3,6 +3,21 @@
- fetch-output
- merge-output-to-logs
- hosts: localhost
roles:
- role: add-fileserver
when:
- zuul_success | bool
- zuul.change is not defined
- hosts: "{{ fileserver.fqdn }}"
gather_facts: False
roles:
- role: publish-artifacts-to-fileserver
when:
- zuul_success | bool
- zuul.change is not defined
- hosts: all
# NOTE(pabelanger): We ignore_errors for the following tasks as not to fail
# successful jobs.

View File

@ -127,6 +127,8 @@
label: ubuntu-xenial
secrets:
- site_logs
- secret: site_tarballs
name: fileserver
# NOTE(corvus): A short-term test job
- job: