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

Add publishing for .NET 6.0.3xx SDK channels #8390

Closed
1 of 2 tasks
riarenas opened this issue Jan 25, 2022 · 6 comments
Closed
1 of 2 tasks

Add publishing for .NET 6.0.3xx SDK channels #8390

riarenas opened this issue Jan 25, 2022 · 6 comments
Assignees

Comments

@riarenas
Copy link
Member

  • This issue is blocking

Installer repo is trying to publish to this channel

  • This issue is causing unreasonable pain

Add publishing configuration for the .NET 6.0.3xx SDK and internal channels.

@riarenas
Copy link
Member Author

#8391 has been merged. Once arcade self-updates through dependency flow it will be possible to publish to the 6.0.3xx SDK channels

@TanayParikh
Copy link

Once arcade self-updates through dependency flow it will be possible to publish to the 6.0.3xx SDK channels

@riarenas when would that be / is there a way I can check if it has happened? Just tried triggering an arcade update to dotnet/razor-compiler without much luck.

@riarenas
Copy link
Member Author

I will update this issue when we have received the correct update.

@riarenas
Copy link
Member Author

I can probably trigger an update manually in the next few minutes as it looks like we have a good window to promote arcade right now.

@riarenas
Copy link
Member Author

Once #8398 is merged and mirrored to the internal repo this should be unblocked

@riarenas
Copy link
Member Author

This should be working now, already verified with the installer build that first saw the issue: https://dev.azure.com/dnceng/internal/_build/results?buildId=1566018&view=results. @TanayParikh you should be able to retry any builds that saw the issue now. You don't need to wait for any arcade updates as the publishing pipeline only depends on the arcade repo itself.

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

No branches or pull requests

2 participants