Skip to content

[WIP] Make generate-ansible-collection die on version mismatch#442

Open
felixfontein wants to merge 1 commit intoansible:masterfrom
felixfontein:die-on-wrong-version
Open

[WIP] Make generate-ansible-collection die on version mismatch#442
felixfontein wants to merge 1 commit intoansible:masterfrom
felixfontein:die-on-wrong-version

Conversation

@felixfontein
Copy link
Copy Markdown
Contributor

This depends on ansible-network/releases#23.

@softwarefactory-project-zuul
Copy link
Copy Markdown
Contributor

Build succeeded.

✔️ config-check SUCCESS in 33s
✔️ refresh-automation-hub-token SUCCESS in 16s
✔️ validate-ansible-galaxy-token SUCCESS in 19s

args:
chdir: "~/{{ item.src_dir }}"
shell: "if test -f 'galaxy.yml'; then ~/.local/bin/generate-ansible-collection; fi"
shell: "if test -f 'galaxy.yml'; then ~/.local/bin/generate-ansible-collection --for-release; fi"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

build-ansible-collection is also run for 'normal' CI jobs, not just for the 'release' job, I think the --for-release flag should only be run if we're running because someone triggered a the job by pushing a tag

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, that totally makes sense, but I have no idea how to detect that situation :)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I'd need to copy this directory to a new one build-ansible-collection-for-release and do the change there. Or is there a cleaner way to do this @goneri?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants