-
Notifications
You must be signed in to change notification settings - Fork 319
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
Enable dependency flow #1941
Comments
/cc: @cltshivash @PBoraMSFT We would need to plan this work. |
Any update on this? |
@chcosta This work is planned for this quarter. Will update once, we pick this. |
@singhsarab , am I to take "this quarter" as meaning, "it will be done by June"? The last day for .NET Core 3.0 support in Jenkins is May 3rd. |
@chcosta How is this related to Jenkins ? |
Ack, you're right, my bad. I crossed streams. |
@chcosta fixed the issue hit while trying to generate manifest. Refer dotnet/arcade#3080 (review) |
Dependencies which are a part of source build, but do not publish using dependency flow end up causing incoherent builds. Source build is not able to determine which version of the asset is needed because it is not reported to BAR and then someone must manually go to a repo (like core-sdk) and trace back to find which version of the dependency is needed so that it can be built.
https://github.com/dotnet/arcade/blob/master/Documentation/DependencyFlowOnboardingWithoutArcade.md
The text was updated successfully, but these errors were encountered: