0405ec9f76
The in-tree job definition did not pass the legacy ZUUL environment
into sudo or dump the ZUUL_ prefixed vars into zuul.env, so the
get-ansible-role-requirements script did not detect that it should
use Zuul provided sources when available.
This fixes the job definition in several ways:
1) The job definition no longer calls gate-check-commit using the
sudo command. Instead become/become_user are placed on the task
so ansible will handle the sudoing and we just call
gate-check-commit directly now.
2) The zuul legacy environment is removed from the job environment.
Only ZUUL_PROJECT is used in the integrated repo[1], so that is
the only var we define now, and we do not need anything special to
pass it into gate-check-commit since it is no longer running in
a sudo wrapper.
As a result of these changes, the zuul.env loading code is removed
from gate-check-commit.
[1] c3ce038737/tests/get-ansible-role-requirements.yml (L57)
Change-Id: Id0fb8502029e3f996d2557bc09c3314cc884bba8
13 lines
454 B
YAML
13 lines
454 B
YAML
- hosts: all
|
|
tasks:
|
|
- name: Run gate-check-commit.sh script
|
|
become: yes
|
|
become_user: root
|
|
command: "scripts/gate-check-commit.sh {{ scenario }} {{ action }}"
|
|
args:
|
|
chdir: "src/{{ zuul.project.canonical_name }}"
|
|
environment:
|
|
# ZUUL_PROJECT is used by tests/get-ansible-role-requirements to
|
|
# determine when CI provided repos should be used.
|
|
ZUUL_PROJECT: "{{ zuul.project.short_name }}"
|