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 have a pattern where I'll have a pipeline run testing against every git repo commit, and then conditionally perform a task if that testing passed and certain files have changed. The example below is this pattern for setting another pipeline, i.e. "Test the repo, and if the pipeline's files have changed, set it."
I have a similar pattern for "Test the repo, if the Dockerfile changed, build the image." I cannot seem to get this duality of "need to look at and test the entire repo" but "only execute some type of build operation on certain changed files."
I've tried adding repo-self-pipeline-1 to the testing job without a trigger, but that doesn't ensure that it has the same git commit sha. Any ideas here?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a pattern where I'll have a pipeline run testing against every git repo commit, and then conditionally perform a task if that testing passed and certain files have changed. The example below is this pattern for setting another pipeline, i.e. "Test the repo, and if the pipeline's files have changed, set it."
I have a similar pattern for "Test the repo, if the Dockerfile changed, build the image." I cannot seem to get this duality of "need to look at and test the entire repo" but "only execute some type of build operation on certain changed files."
I've tried adding
repo-self-pipeline-1
to thetesting
job without a trigger, but that doesn't ensure that it has the same git commit sha. Any ideas here?Beta Was this translation helpful? Give feedback.
All reactions