-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
on-tag dynamic continuations should compare against the last tag #83
Comments
This warrants more discussion @Benjythebee. As I mentioned above, how I presently organize my configs, including this project's , is to keep tag-specific jobs separate from branch-specific jobs, by placing the former in my main config, But it does increase code duplication as well, which is why I've spun off yet another orb, a general orb, with all the typical jobs I'll use in my pipelines. Any ideas for how we could organize this differently? I've been thinking about it for a while and haven't come up with a better solution. |
Thank you for your response and for dealing with my ignorant ass....
Thank you for your time! |
No problem at all! Enjoy 👍 |
I tend to keep tag-specific jobs in my main config, but the functionality could be the same for tags as well, but instead of comparing two commits, we compare two tags (the current, and the last).
Another argument I could add is to optionally run all workflows on tag, say, and not just rely on changes between tags to kick off workflows. E.g., say you want a new docker image and helm chart (with corresponding image tag) on tag, but you've only changed
src/
(granted this could also be accomplished with ignore-includes).The text was updated successfully, but these errors were encountered: