Hello, I have a scenario where I want to promote a build which include [SKIP CI] in the commit message.
The background is:
There is a pipeline with push to main trigger which creates a new release, the release commit also trigers the pipeline and creates an endless loop.
To solve this, I changed the release commit message to include [SKIP CI] and it ended up fine.
But now, I have a scenario where I want to promote the build created from tag event but it does not execute.
Is there something can be done to enforce the following pipeline promote execution?
If you have any ideas/ encountered a similar situation I would appreciate for some help.
Perhaps the problem is not related to [CI SKIP] but something in your yaml? I recommend taking a look at this comprehensive thread that will walk you through all possible reasons a pipeline will not execute. If you are still unable to resolve, the last section of the thread includes a list of items that you can provide us if further analysis is required.
Hey Brad, thank you!
I made some changes in my pipeline to match the scenario I had, but I still want to make sure for later situations.
The changes that have been done for [CI SKIP] are also relevant for [SKIP CI]?
I ran the same pipeline twice on two similar commits where the only change between them is [SKIP CI].
Plus, the following log shows skipping hook: