Skip to content

trigger CI for track2 when tools is changed - #9699

Merged
Praveen Kuttappan (praveenkuttappan) merged 2 commits into
Azure:masterfrom
praveenkuttappan:toolsci
Feb 3, 2020
Merged

trigger CI for track2 when tools is changed#9699
Praveen Kuttappan (praveenkuttappan) merged 2 commits into
Azure:masterfrom
praveenkuttappan:toolsci

Conversation

@praveenkuttappan

Copy link
Copy Markdown
Member

Trigger CI for core and track2 packages when tools is changed.

Comment thread sdk/appconfiguration/ci.yml
@weshaggard

Copy link
Copy Markdown
Member

Praveen Kuttappan (@praveenkuttappan) Scott Beddall (@scbedd) is there a reason we want to trigger ci for all these pipelines if anything under eng changes? We generally use one pipeline like core as a proxy for those changes to prevent all pipelines from triggering. I noticed while merging #10761 that we ran a lot more ci pipelines then I expected to see which is what triggered me to find this PR.

@praveenkuttappan

Copy link
Copy Markdown
Member Author

I believe it as per the discussion with Laurent we made change to trigger all track2 pipelines when anything inside eng is changed. I am trying to find that discussion thread. But we should probably add more granular control so it wont trigger all when anything in eng is changed. for e.g. eng/common.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants