Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update Ansible yang push-to-ah job #394

Conversation

rohitthakur2590
Copy link
Contributor

Signed-off-by: Rohit Thakur [email protected]

Signed-off-by: Rohit Thakur <[email protected]>
@rohitthakur2590 rohitthakur2590 changed the title update AH job update Ansible yang push-to-ah job May 2, 2022
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

@softwarefactory-project-zuul
Copy link
Contributor

Zuul encountered a syntax error while parsing its configuration in the
repo ansible/zuul-config on branch master. The error was:

expected a dictionary for dictionary value @ data['merge-failure']

The error appears in the following pipeline stanza:

pipeline:
name: third-party-check
description: |
Newly uploaded patchsets to projects that are external to OpenStack
enter this pipeline to receive an initial +/-1 Verified vote.
success-message: Build succeeded (third-party-check pipeline).
# TODO(mordred) We should write a document for non-OpenStack developers
failure-message: |
Build failed (third-party-check pipeline) integration testing with
OpenStack. For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing
manager: independent
trigger:
github.com:
- event: pull_request
action:
- opened
- changed
- reopened
- event: pull_request
action: comment
comment: (?i)^\srecheck\s$
start:
github.com:
status: 'pending'
status-url: 'https://ansible.softwarefactory-project.io/zuul/status.html'
comment: false
success:
github.com:
status: 'success'
comment: false
failure:
github.com:
status: 'failure'
comment: false
# Don't report merge-failures to github
merge-failure:

in "ansible/zuul-config/zuul.d/pipelines.yaml@master", line 303, column 3

@softwarefactory-project-zuul
Copy link
Contributor

Zuul encountered a syntax error while parsing its configuration in the
repo ansible/zuul-config on branch master. The error was:

expected a dictionary for dictionary value @ data['merge-failure']

The error appears in the following pipeline stanza:

pipeline:
name: third-party-check
description: |
Newly uploaded patchsets to projects that are external to OpenStack
enter this pipeline to receive an initial +/-1 Verified vote.
success-message: Build succeeded (third-party-check pipeline).
# TODO(mordred) We should write a document for non-OpenStack developers
failure-message: |
Build failed (third-party-check pipeline) integration testing with
OpenStack. For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing
manager: independent
trigger:
github.com:
- event: pull_request
action:
- opened
- changed
- reopened
- event: pull_request
action: comment
comment: (?i)^\srecheck\s$
start:
github.com:
status: 'pending'
status-url: 'https://ansible.softwarefactory-project.io/zuul/status.html'
comment: false
success:
github.com:
status: 'success'
comment: false
failure:
github.com:
status: 'failure'
comment: false
# Don't report merge-failures to github
merge-failure:

in "ansible/zuul-config/zuul.d/pipelines.yaml@master", line 303, column 3

@softwarefactory-project-zuul
Copy link
Contributor

Zuul encountered a syntax error while parsing its configuration in the
repo ansible/zuul-config on branch master. The error was:

expected a dictionary for dictionary value @ data['merge-failure']

The error appears in the following pipeline stanza:

pipeline:
name: third-party-check
description: |
Newly uploaded patchsets to projects that are external to OpenStack
enter this pipeline to receive an initial +/-1 Verified vote.
success-message: Build succeeded (third-party-check pipeline).
# TODO(mordred) We should write a document for non-OpenStack developers
failure-message: |
Build failed (third-party-check pipeline) integration testing with
OpenStack. For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing
manager: independent
trigger:
github.com:
- event: pull_request
action:
- opened
- changed
- reopened
- event: pull_request
action: comment
comment: (?i)^\srecheck\s$
start:
github.com:
status: 'pending'
status-url: 'https://ansible.softwarefactory-project.io/zuul/status.html'
comment: false
success:
github.com:
status: 'success'
comment: false
failure:
github.com:
status: 'failure'
comment: false
# Don't report merge-failures to github
merge-failure:

in "ansible/zuul-config/zuul.d/pipelines.yaml@master", line 303, column 3

@rohitthakur2590
Copy link
Contributor Author

regate

@softwarefactory-project-zuul
Copy link
Contributor

Zuul encountered a syntax error while parsing its configuration in the
repo ansible/zuul-config on branch master. The error was:

expected a dictionary for dictionary value @ data['merge-failure']

The error appears in the following pipeline stanza:

pipeline:
name: third-party-check
description: |
Newly uploaded patchsets to projects that are external to OpenStack
enter this pipeline to receive an initial +/-1 Verified vote.
success-message: Build succeeded (third-party-check pipeline).
# TODO(mordred) We should write a document for non-OpenStack developers
failure-message: |
Build failed (third-party-check pipeline) integration testing with
OpenStack. For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing
manager: independent
trigger:
github.com:
- event: pull_request
action:
- opened
- changed
- reopened
- event: pull_request
action: comment
comment: (?i)^\srecheck\s$
start:
github.com:
status: 'pending'
status-url: 'https://ansible.softwarefactory-project.io/zuul/status.html'
comment: false
success:
github.com:
status: 'success'
comment: false
failure:
github.com:
status: 'failure'
comment: false
# Don't report merge-failures to github
merge-failure:

in "ansible/zuul-config/zuul.d/pipelines.yaml@master", line 303, column 3

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

regate

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (gate pipeline). For information on how to proceed, see
http://docs.openstack.org/infra/manual/developers.html#automated-testing

config-check POST_FAILURE in 59s

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

config-check POST_FAILURE in 25s
refresh-automation-hub-token POST_FAILURE in 11s
validate-ansible-galaxy-token POST_FAILURE in 10s

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

config-check POST_FAILURE in 24s
refresh-automation-hub-token POST_FAILURE in 11s
validate-ansible-galaxy-token POST_FAILURE in 11s

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

config-check POST_FAILURE in 26s
refresh-automation-hub-token POST_FAILURE in 12s
validate-ansible-galaxy-token POST_FAILURE in 12s

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

config-check POST_FAILURE in 26s
refresh-automation-hub-token POST_FAILURE in 20s
validate-ansible-galaxy-token POST_FAILURE in 12s

@goneri
Copy link
Collaborator

goneri commented May 5, 2022

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

✔️ config-check SUCCESS in 35s
✔️ refresh-automation-hub-token SUCCESS in 21s
✔️ validate-ansible-galaxy-token SUCCESS in 21s

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded (gate pipeline).

✔️ config-check SUCCESS in 34s

@softwarefactory-project-zuul softwarefactory-project-zuul bot merged commit 581046d into ansible:master May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants