open-source-mirrors
/
scrutiny
mirror of https://github.com/AnalogJ/scrutiny
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '727d5b0ace'
${ noResults }
scrutiny/docs/TROUBLESHOOTING_DOCKER.md

1.4 KiB
Raw Blame History

Docker Images master-omnibus vs latest

TL;DR; The master-omnibus and latest tags are almost semantically identical, as I follow a golden master development process. However if you want to ensure you're only using the latest release, you can change to latest

The CI script used to orchestrate the docker image builds can be found here: https://github.com/AnalogJ/scrutiny/blob/master/.github/workflows/docker-build.yaml#L166-L184

In general Scrutiny follows a golden master development process, which means that the master branch is not directly updated (unless its for documentation changes), instead development is done in a feature branch, or committed to the beta branch.

As development progresses, and we're satisfied that a feature is complete, and the quality is acceptable, I merge the changes to master and trigger the creation of a new release -- ie, when master is updated, a new release is almost immediately created (and tagged with latest)

So changing from master-omnibus -> latest will be the same thing for all intents and purposes.

NOTE: Previously, there was a automated cron build that ran on the master and beta branches. They used to trigger a nightly build, even if nothing has changed on the branch. This has a couple of benefits, but one is to ensure that there's no broken external dependencies in our (unchanged) code. This nightly build no longer updates the master-omnibus tag.