Skip to content
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

CI: Fix triggers for pipeline changes #76594

Merged
merged 2 commits into from
Oct 4, 2022
Merged

Conversation

radical
Copy link
Member

@radical radical commented Oct 4, 2022

Revert to the earlier triggers which excluded coreclr, installer, or
mono ymls, for the relevant subsets. For example:

    subset: coreclr
    exclude:
      - eng/pipelines/installer/*
      - eng/pipelines/mono/*
      - eng/pipelines/libraries/*

Prompted by #76057 (comment)

Revert to the earlier triggers which excluded coreclr, installer, or
mono ymls, for the relevant subsets. For example:

```yml
    subset: coreclr
    exclude:
      - eng/pipelines/installer/*
      - eng/pipelines/mono/*
      - eng/pipelines/libraries/*
```

Prompted by dotnet#76057 (comment)
@ghost
Copy link

ghost commented Oct 4, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Revert to the earlier triggers which excluded coreclr, installer, or
mono ymls, for the relevant subsets. For example:

    subset: coreclr
    exclude:
      - eng/pipelines/installer/*
      - eng/pipelines/mono/*
      - eng/pipelines/libraries/*

Prompted by #76057 (comment)

Author: radical
Assignees: -
Labels:

area-Infrastructure

Milestone: -

@ghost ghost assigned radical Oct 4, 2022
@radical radical merged commit 6224223 into dotnet:main Oct 4, 2022
@radical radical deleted the ci-pipelines branch October 4, 2022 15:59
@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants