Deprecate build collection and test import to Galaxy GitHub Actions and shared workflows

Project Discussions
, ,
1

(This was split off from Pinning GHA actions/shared workflows to commits - #2 by felixfontein)

Regarding:

test-galaxy-import is only used by one repository: GitHub - ansible-collections/community.vmware: Ansible Collection for VMware · GitHub and action-build-collection is only used internally by test-galaxy-import from what I can see. Please correct me if I’m wrong.

Is the time and effort being spent on maintaining these actions worth it?

Furthermore, building a collection is quite simple, and both antsibull-nox and tox-ansible have ways of running Galaxy importer which I feel we could be encouraging for the other benefits for collection testing too. What are your thoughts @felixfontein?

Pinning GHA actions/shared workflows to commits
2

I’m fine with archiving both actions. They were useful when the alternative was to use Zuul (which took up to 20 minutes for what the actions were doing in a minute or so), but now that most collections moved on from them I don’t think they are needed anymore.

3

I created an issue (Shared workflow for Galaxy import might get deprecated/archived · Issue #2561 · ansible-collections/community.vmware · GitHub) in the community.vmware repository. Once they stop using the github-action-test-galaxy-import and github-action-build-collection actions/shared workflows, I’d archive these.

4

Does anyone have any examples how other collections replaced this workflow? Might be really helpful for me.

But don’t search! If you can’t name some examples just like this I’ll have to investigate myself.

5

When you use antsibull-nox, you can simply add

[sessions.build_import_check]
run_galaxy_importer = true

to your antsibull-nox.toml file. (Documenation of this session.)

If you don’t use it yet, and want to use it for that, you can create a new antsibull-nox.toml file

version = 1

[sessions]

[sessions.build_import_check]
run_galaxy_importer = true

and a noxfile.py (as in Getting started - antsibull-nox – Antsibull Nox Helper, or you can ask antsibull-nox to create it for you) and add a workflow like the one in Running nox in CI - antsibull-nox – Antsibull Nox Helper to your collection.

1 Like
6

@dbrennand I’ve started to work on replacing this workflow in community.vmware. There are some things I don’t fully understand, and I’ll have to figure out why the CI isn’t happy. But as I’ve said: I’m working on getting rid of this.

1 Like