starter-workflows | Accelerating new GitHub Actions workflows | BPM library

The "package under test", potion in your case, should not be part of the requirements.txt. Instead, simply add your line

The beauty of tox is that you can run it both locally and on CI.

You have a high chance of a successful CI when it passes locally, and also you only need to define the test requirements and the test setup once, in one file.

To do so, I recommend using the mentioned tox-gh-actions.

I applied this pattern to dozens of repositories with success.

I recommend the following blog post which gives a great introduction to this setup:

https://hynek.me/articles/python-github-actions/

You can have a look at the tox.ini and the gh action config file for e.g. Flask-Reuploaded.

As to your question about running pytest in every matrix... the drawback here is that you need to take care of the test setup yourself, and you have to define everything at two places, tox.ini for local testing and in the yaml config for gh actions.

How is the deployment performed?

To know how to deploy or run this workflow please refer this documentation

What is kustomize for?

kustomize is a configuration mangement for application configuration

Do I have to configure on gcloud anything else than GKE key / token

You don't have to unless you are adding additional layer of security for authenticating the workflow.

Suppose I want to update multiple docker images. Will it suffice to build multiple images and push them? Like below (a little bit simplified for clarity), or do I have to also modify the Deploy job

I think no need for modification of deploy job. It is enough to build multiple images and push them into the GCR

Node.js versions 8, 10 and 12 are commonly used versions of Node.js. Versions 9 and 11 are considered experimental, since they are odd numbers, and therefore do not get LTS (Long Term Support). On the other hand, versions 8, 10 and 12 are stable.

Firebase cloud functions require either Node.js version 8 or 10, showing that versions 8 and 10 are still quite widely used.

Node.js version 14 was released a few months ago, but I doubt people will move to it until a while later when most of the bugs have been fixed, so it is not entirely necessary to test it, but you can if you want.

As you can see, Node.js versions 8, 10 and 12 are the most widely used versions of Node.js and therefore, it would be a good idea to make sure that your JavaScript code works with those 3 versions to ensure a lot of people can use your code.

If you want to ensure complete compatibility, you can test with even more versions of Node.js, but I doubt you would need to, as Node.js is usually quite backwards-compatible.

If you want to see which versions of Node.js are currently being supported, visit the Node.js releases page.

We have verified that the daemon.json file is properly updated

It looks like it's not properly updated, based on your error message:

/home/runner/work/_temp/59d363d1-0231-4d54-bffe-1e3205bf6bf3.sh: line 3: /etc/docker/daemon.json: Permission denied

What's going on here? Well, the sudo command will run the given command as root. But you're doing a shell redirect, which is handled by the shell itself, not by sudo. In other words, you're redirecting the output of sudo.

If you want to write to a file as root then you'll need to actually run a command that writes the file, and then run that using sudo. For example:

As far as I can tell, the CI variable is there for compatibility with other CI systems. Here are the facts as I know them:

1. GitHub Actions itself, does not have any use or need for the CI variable.
2. Other CI systems - like Travis and CircleCI - always set CI=1.
3. Unlike other systems, GitHub Actions does not set CI=true, since it is not intended for CI only. Instead, it sets GITHUB_ACTIONS=true.
4. The conventional use for the CI variable, is so that your tests and app configuration can check for its existence, and do something differently if they need to (for example, skip certain tests on CI, or configure a different setting when on CI).

If your code and test code do not have the CI variable in them, then you can probably omit this setting and have the same result.