Commit Graph

6 Commits

Author SHA1 Message Date
84b108e154 Fix container builds on forks by using context vars
Also add conditional to only build containers on the upstream repo.
2024-01-03 20:24:55 +00:00
c1aa3e59d1 Merge pull request #3 from shymega/shymega/prs/ci
Initial version of CI for RSSingle
2023-12-29 11:54:45 +01:00
57ed8aef3a Start testing release packager 2023-12-25 20:25:23 +00:00
b526fc582f Initial version of CI for RSSingle
Hi @tanrax!

As part of our new collaboration, I've made an initial version for
automated CI for RSSingle.

It needs macOS to work first, so I've commented out a draft version of
the `pyinstaller` aspect, so I'll make this PR a draft for now when we
can discuss further, preferably in a GH issue for transparency (unless
you want it private?), but this workflow tests on PRs and pushes to any
branch, with flake8 across multiple Python versions. The pyinstaller
aspect only runs if the flake8 check passes.

What do you think?

Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
2023-12-25 20:25:23 +00:00
1f36dea889 Adjust branch, assumed the branch - use master
I didn't realise you were using `master` as the branch name, so this
wouldn't run if the PR was accepted.

Now fixed.

Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
2022-09-12 23:45:26 +01:00
daf79338b5 Add Docker support for RSSingle, and a workflow for builds
This commit adds a Dockerfile, .dockerignore, and a GH Action for
pushing container images to - and this is by default, other registries
can be used - Docker Hub (you need to generate a token and install it in
the repo), and GitHub Registry, which doesn't require a manual token.

The workflow won't build until #3 is merged, as it relies on successful
builds from that workflow before a container image is pushed. Once we use unit
tests, this will ensure container images aren't broken when pushed to a
remote registry.

I have marked this PR as draft for that reason.

Signed-off-by: Dom Rodriguez <shymega@shymega.org.uk>
2022-09-12 22:09:57 +01:00