Create app-tag script to help generate git tags for apps #120
Labels
No Label
breaking-change
bug
CI/CD
design
documentation
duplicate
enhancement
help wanted
invalid
plugin
question
secrets
shell-completion
versioning
wontfix
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/abra#120
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of coop-cloud/organising#51.
Reading over the notes again, I think (!) we finished up with the idea that the version of the app is derived from the
app
service version.So, for
gitea
right now (e.g.03c48f99de/compose.yml (L6)
), we'd publish the1.13.4
tag. So,app-tag.sh gitea
would produce1.13.4
.Now, if we happen to update an underlying service like the
db
(e.g.03c48f99de/compose.yml (L62)
) to10.6
but the mainapp
service remains on1.13.4
thenapp-tag.sh gitea
would produce1.13.4~1
.An example of the resulting
abra-apps.json
is then:app-tag.sh
should just read the latest HEAD of the gitea app repo, look at the existing git tags, look at the currentcompose.yml
contained tags and then generate the correct tag.Fuck it actually, we can do this manually for now!
42d7213e12
Testing with https://git.autonomic.zone/coop-cloud/gitea/src/tag/1.13.6