.NET Interactive combines the power of .NET with many other languages to create notebooks, REPLs, and embedded coding experiences. Share code, explore data, write, and learn across your apps in ways you couldn't before.
MIT License
2.8k
stars
374
forks
source link
Adding in a separate pipeline just for our internal signed builds on top of Compliant templates #3501
A separate pipeline is what is being recommended centrally. Here is a PR that diffs the contents of the official yml file with what we have in our repo yml today: https://dev.azure.com/dnceng/internal/_git/dotnet-interactive/pullrequest/38525?_a=files&path=/azure-pipelines.yml.
Here is a signed build that I used to validate that this is actually going to work: https://dev.azure.com/dnceng/internal/_build/results?buildId=2414181&view=results. I'll wait for this to be complete before considering merging this PR in. Here's an older build before the latest iteration which succeeded: https://dev.azure.com/dnceng/internal/_build/results?buildId=2413293&view=results
Post merge: