You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been testing the go pipeline and I witnessed a strange behaviour that seems to be caused by the trigger: true for the version resource on the RC step.
Basically for every git commit the test step runs, that eventually triggers the rc step and because rc bumps the version it seems like it runs twice. Later down the road when the bump-patch runs it looks like another rc is run again.
Is there something that I am doing wrong?
The text was updated successfully, but these errors were encountered:
Hi @drnic , I have seen that behaviour with the go pipeline but I could see it happen with other ones too since the version -> rc -> version followed by shipit -> patch bump -> version pattern also exists elsewhere. Is it something you have seen?
Good afternoon,
I've been testing the go pipeline and I witnessed a strange behaviour that seems to be caused by the
trigger: true
for the version resource on the RC step.Basically for every git commit the
test
step runs, that eventually triggers therc
step and becauserc
bumps the version it seems like it runs twice. Later down the road when thebump-patch
runs it looks like anotherrc
is run again.Is there something that I am doing wrong?
The text was updated successfully, but these errors were encountered: