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

Remove pr: none clause from several CoreCLR pipelines #42933

Merged
merged 2 commits into from
Oct 6, 2020

Conversation

trylek
Copy link
Member

@trylek trylek commented Sep 30, 2020

I have updated the AzDO UI properties per Viktor's advice to enable these runs for /asp run runs. After verifying they work as expected we can expand the pipeline set. For now I have skipped the various stress runs that would be the most detrimental if they unexpectedly started to run as part of PR's as an unforeseen effect of the changes.

Thanks

Tomas

/cc @dotnet/runtime-infrastructure

@ViktorHofer
Copy link
Member

ViktorHofer commented Oct 1, 2020

It looks like you missed runtime-coreclr outerloop? (just fixed that in AzDO)

@@ -24,9 +24,6 @@ trigger:
- eng/pipelines/libraries/*
- eng/pipelines/runtime.yml


pr: none
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we ever want this pipeline to be triggerable?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or is that the outerloop pipeline?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, ci.yml corresponds to the "runtime-coreclr outerloop" pipeline. I think we should rename the YAML script to "outerloop.yml", this is an endless cause of confusion.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I proposed to rename it before as well. However, if we rename it now, we will need to port that to release/5.0 and release/5.0-rc2 branch.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it's just busywork. I would say let's leave this for a more suitable time when there are no porting concerns.

@ViktorHofer ViktorHofer closed this Oct 1, 2020
@ViktorHofer ViktorHofer reopened this Oct 1, 2020
@ViktorHofer
Copy link
Member

Hmm would be great if you could amend your commit or do something so that CI is retriggered.

@trylek trylek closed this Oct 1, 2020
@trylek trylek reopened this Oct 1, 2020
@trylek
Copy link
Member Author

trylek commented Oct 1, 2020

Good, I think the outerloop is no longer automatically triggered upon the PR, I fixed the pipeline parameters in the AzDO UI editor.

@trylek
Copy link
Member Author

trylek commented Oct 1, 2020

/azp:run runtime-coreclr crossgen2

@trylek
Copy link
Member Author

trylek commented Oct 1, 2020

/azp run runtime-coreclr crossgen2

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@trylek
Copy link
Member Author

trylek commented Oct 6, 2020

@ViktorHofer - any additional feedback on this change you asked me to make? Or is there some remaining feedback from you I haven't yet addressed?

@ViktorHofer
Copy link
Member

Hmm wasn't there an issue that was tracking this work?

@ViktorHofer
Copy link
Member

Thanks Tomas!

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@trylek trylek merged commit 642b7cb into dotnet:master Oct 6, 2020
@trylek trylek deleted the PrNone branch October 6, 2020 17:51
@ghost ghost locked as resolved and limited conversation to collaborators Dec 7, 2020
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