https://github.com/informaticsmatters/squonk2-fragmenstein
https://github.com/informaticsmatters/squonk2-fragmenstein
squonk2 squonk2-jobs
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/informaticsmatters/squonk2-fragmenstein
- Owner: InformaticsMatters
- License: apache-2.0
- Created: 2023-07-04T15:34:48.000Z (almost 3 years ago)
- Default Branch: main
- Last Pushed: 2023-11-24T16:24:38.000Z (over 2 years ago)
- Last Synced: 2025-01-25T18:43:20.439Z (over 1 year ago)
- Topics: squonk2, squonk2-jobs
- Language: Python
- Homepage:
- Size: 301 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Fragmenstein workflows


[](https://github.com/InformaticsMatters/squonk2-fragmenstein/actions/workflows/publish-latest.yaml)
[](https://github.com/InformaticsMatters/squonk2-fragmenstein/actions/workflows/publish-stable.yaml)
[](https://github.com/InformaticsMatters/squonk2-fragmenstein/actions/workflows/build.yaml)
This repository is used to build the things needed to execute
the **Squonk2 Fragmenstein** jobs.
## Building the workflows
Automated GitHub CI Actions take care of official releases of these Job workflows.
Container images are built and pushed to DockerHub using the image tag `latest` for
each change on the main branch, and images built during an _official release_
will be tagged `stable`.
> To build an _official release_ create a new **Release** in GitHub,
assigning a [semver] style tag to the release, while also leaving the
**Set as a pre-release** checkbox un-ticked.
Refer to the `docker-compose.yaml` file for the details of the images that are built.
If you want to build your own (local) images you can use the docker compose file in the
repository, but **DO NOT** publish these images to DockerHub: -
python -m venv venv
source venv/bin/activate
pip install -r build-requirements.txt
docker-compose build
---
[semver]: https://semver.org