tox-dev / tox-gh Goto Github PK

I understand that Python 2.7 is dead and Python 3 < 3.7 has been retired.

Tox is for test automation, though, and sometimes developers want to verify that their software continues to work even with outdated versions of Python.

The code base of this plugin is so small that it could do without features that require Python 3.7+ and even support Python 2.7 with rather little effort, no need even for six and friends. This would help!

Hello! With other CI providers, I like to define one CI check/job per tox environment, for example one for each of py38, py39, py310-coverage, lint. For github actions, I understand that it’s easy to use python version as an axis, so that the values generate combinations and can be used as parameter for the python install action. But having to run multiple jobs (e.g. py310 and lint / type check / doc check/etc) in one check feels backward to me: it’s driven by what the tool can do rather than what I want to see.
It doesn’t make sense to have one check that runs tests with latest python and lint, these should be separate jobs with separate success status.

Inspired by a comment somewhere, I ditched tox-gh-actions, used tox-env as matrix axis and used an external config file to map tox-env value to python install parameter: https://github.com/caravancoop/configstore/blob/main/.github/workflows/configstore.yml#L11
(I tried to configure all in the yaml file at first with complicated expressions but that was not worth it)

It would be great to have native support for this!

I don’t really have implementation suggestion. If we can add arbitrary config in the actions config file, maybe a mapping could be defined there? If not, it might have to be a job with outputs and that could be heavy (if it needs to call tox or use a shell).

jobs:
  test:
    name: test ${{ matrix.tox-env }}
    strategy:
      fail-fast: false
      matrix:
        tox-env:
          - "3.10"
          - "3.9"
          - "3.8"
          - "lint"
          - "pkg"

    steps:
      - uses: actions/setup-python@v2
        with:
          python-version: ${{ some-expression-to-get-version }}

Not an issue but a question: How is this project different from https://github.com/ymyzk/tox-gh-actions?

Right now the other project has a lot more stars and forks than this one.

What would be the upside to using this GitHub action rather than tox-gh-actions?

When I look at my Action results now, I open the step and see this:

All of the details of the package installations and other preliminaries are visible, but I have one more twisty to click open to see what actually happened with my tests. I almost never want to see the stuff that is first visible, and always want to see the stuff that is hidden until I click.

Can we add another group so that at least the preliminaries are initially hidden? It would reduce the visual clutter, and put them on an even footing with the test running.

It would be nice if we could optionally set the report that tox prints out to be the step summary in GitHub.

It looks like this might require a new API hook in tox to make it happen, but that hook could probably be of general benefit too.

#63 added a summary for each job, but if only one tox environment is run, the summaries simply duplicate information that is already available:

Can we have a way to turn these off?

I notice the last release is almost a year ago, predated the actual release of tox 4.0, and the only commits to this repository since January appear to be automated or semi-automated dependency bumps.

I also notice that the plugin does not appear to work at the moment -- this GitHub Actions config and this tox config yielded a CI run that appears to have tried to run every environment on every Python version, rather than only the specified environments for each Python version.