project-config/playbooks/publish/static.yaml
Andreas Jaeger d719449ed1 Rework base-publish-static jobs using protected
The new protected attribute means that only jobs in the same repo can
inherit from it. Use that on base-publish-static and move the secrets
from the inherited job to it now, it's now safe to have them here.

Since the secrets need to be available to the post-job and are not
available to post-jobs of inheried jobs, use a common post job for all
of these. Move static-special.yaml to static.yaml and set the location
for the publish location for the single previous user of static.yaml.

Change-Id: I3d749adf242eb87895ad10b6f9c4d12859882ac9
2018-02-17 17:51:27 +01:00

21 lines
578 B
YAML

- hosts: all
roles:
- fetch-tox-output
- role: fetch-sphinx-output
sphinx_output_src: "src/{{ zuul.project.canonical_name }}/doc/build/html/"
zuul_executor_dest: "{{ zuul.executor.work_root }}/artifacts"
when: zuul_success | bool
- hosts: localhost
roles:
- add-fileserver
- hosts: "{{ fileserver.fqdn }}"
gather_facts: False
tasks:
- name: Upload docs to static site
synchronize:
src: "{{ zuul.executor.work_root }}/artifacts/"
dest: "{{ fileserver.path }}/{{ static_target }}/"
when: zuul_success | bool