openstack/openstack-zuul-jobs
Code Issues Proposed changes

Avoid moving release notes after complete execution

Browse Source 
Originally, we were moving the release notes to another folder
to make it work with the fetch-sphinx-output role.  However,
this did not always work as expected due to the fact that some
projects do not have a doc folder.

This fixes that issue and avoids the move and simply grabs the
data from the right folder.

Change-Id: If6ee519c33320db91f8a9553ed4abc099c284eec
This commit is contained in:
Mohammed Naser 2017-10-04 21:34:17 -04:00
parent 622155cda7
commit b80e33039c
No known key found for this signature in database
GPG Key ID: 481CBC90384AEC42
2 changed files with 1 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
playbooks/releasenotes/post.yaml
View File

@ -2,5 +2,5 @@
roles:
- role: fetch-tox-output
- role: fetch-sphinx-output
sphinx_output_src: "{{ zuul.project.src_dir }}/doc/build/html/"
sphinx_output_src: "{{ zuul.project.src_dir }}/releasenotes/build/html/"
zuul_executor_dest: "{{ zuul.executor.log_root }}"

5
roles/build-releasenotes/tasks/main.yaml
View File

@ -120,8 +120,3 @@
vars:
tox_constraints_file: "{{ ansible_user_dir }}/src/git.openstack.org/openstack/requirements/upper-constraints.txt"
tox_envlist: releasenotes
- name: Move build output to correct path for publishers
command: mv releasenotes/build doc
args:
chdir: "{{ zuul_work_dir }}"