Arcade SDK

[jcagme]

Holding bag for issues not meant to be worked on going forward.

Recently Triaged Issues

All issues in this section should be triaged by the v-team into one of their business objectives or features.

• Use shproj for shared code #17
• Explicitly define powershell dependency #43
• Package generation should support embedding common files #65
• Create sdk to create sdk's #69
• Create guidance: how to develop and run a C# build task with source in the local repo #97
• build.ps1 'projects' variable resolution issues #1255
• Allow artifacts and dotnet installation directory to be overridden #1293
• Long running tasks should support cancellation #107
• Need support for custom build triggers that can set properties #143
• CodeCoverage comment in PRs #191
• Missing [assembly: AssemblyMetadata("Serviceable", "True")] #1526
• Telemetry seems flaky #1887
• Add DllSafeSearchPathAttribute by default to all .NET Core assemblies #1888
• Document bootstrapper extensibility #1456
• Migrate all repos to .snupkg #1959
• Implement targets that enable long paths for .exes targeting .NET Framework 4.6.2+ by default #2090
• ILProj + Signing with open key is broken #2117
• Finding a build error from PR validation is a harrowing experience #2142
• Remove GenerateBuildManifest Sdk Task when everyone is building with Arcade #2157
• Arcade OSX CI builds don't use local .NET Core SDK #2184
• Need retry on Http Client timeouts for Helix Arcade SDK (waiting for jobs to finish) #2202
• Testing documentation #2212
• Split resource assemblies into their own VSIXs automatically #2250
• DeployToSymStore failure won't always fail the build #2267
• Arcade targets override AssemblyOriginatorKeyFile #2321
• Test the argument parsing scripts against special characters #2497
• Use something (anything but bash) for bash json parsing #2510
• project.restore.configFilePaths differs between Visual Studio and command line #2352
• Pack can have errors but still pass CI  #2366
• Warn if a build is using a package with a bug #2373
• Add local internal tools restore target #2416
• Require all projects participating in the build to import Common targets #2676
• Make $LogDir build-architecture specific  #2561
• Change Warning to Information in Azure Helper retry code. #2611
• Yaml analyzer task #2743
• Automatically set test run title and log zip file to useful values #2758
• Packaging tasks should avoid using Newtonsoft.Json #2763
• Handle HTTPClient Timeout (TaskCancelledException) in Arcade Helix SDKs #2826
• SymStore.targets mistakenly assumes that PDB's are always named as $(TargetName).pdb #2874
• [Publishing] Simplify discovery of packages built from a given repository #414
• macOS should be added to arcade-validation builds #3406
• Bring all of our powershell scripts into compliance with our best practices #3502
• Incorrect SDK version used when multiple SDKs are installed #3764
• NuGetRepack tests are flaky #3794
• Linux build scripts don't properly parse multiple projects #3913
• Add retry to VSWhere.exe download / consider sourcing from owned storage #4179
• Cleanup eng/common #4187
• [QCR][Final] Clean up eng/common/templates/post-build folder #4347
• VersionTools CreateOrUpdateAsync doesn't support PullRequestOptions.ForceCreate = true #4442
• Remove GenerateInternalsVisibleTo.targets #4658
• ProjectDefaults.props shouldn't set DebugType for C++ projects #5214
• Publishing tests #5708
• Remove Helix telemetry API usage from Arcade Yaml templates #5780
• In ARM64, fallback to ARM32/x86 if SDK installer is not found #5885
• State of dotnet/arcade's NuGet dependencies: how to use NuGet.Packaging in a new build task #6014
• Add Support For .exe Packages #6120
• Tests fail for Linux local build on latest commits: "The framework 'Microsoft.NETCore.App', version '2.1.0' was not found." #6126
• Arcade overrides globalPackagesFolder to corrupt the shared NuGet cache #6720
• SignCheckTask Returns False Without Logging an Error #6734
• Arcade templates assume _BuildConfig is set #6972
• Arcade build infra gives an ambiguous error message with invalid solution filter files #7395
• https://github.com/dotnet/core-eng/issues/13334
• eng/common/cross/toolchain.cmake incorrect default compiler options. #7607
• Remove NuGet.Packaging.Core references from arcade tasks. #12906
• Rename useInstalledDotNetCli to use_installed_dotnet_cli bootstrapper Bash variable #1468
• Need tests for SignCheck - part I (Post Build Signing changes) #6326
• Exercise ExecWithRetries MSBuild task in Arcade Validation #6339
• Use Factory pattern for BatchSignUtil #6747
• MSBuildTaskBase Enhancements #6772
• https://github.com/dotnet/core-eng/issues/11895
• Make Arcade's Helix builds use VSTest #6858
• https://github.com/dotnet/core-eng/issues/12401
• Arcade PR pipeline uploads GBs of pipeline artifacts unnecessarily #7979
• Can't override jobs.yml parameters like disableComponentGovernance from job #8440

[ChadNedzlek]

If this epic is for stuff "not meant to be worked on"... what is this epic for? Would we ever prioritize this? Should we close it (and all the issues in it)? @markwilkie @Chrisboh @shawnro

[ChadNedzlek]

It sort of feels like it might be the tech-debt pit for arcade. Maybe we could/should morph it in to that?

[markwilkie]

I think the basic idea is that there's a bunch of stuff we could/should do with the Arcade SDK. On the one hand this epic is a "grab bag" of things that others could contribute. Also, at some point it'll likely be a business priority to focus on Arcade again. At that time, it'll be important to triage these issues (again) to get the priority.

It is true though, the longer these issues go w/o needing to be addressed, the less likely they are to be addressed ever says history.

[ChadNedzlek]

There are some impressive ones in here, including arcade#17. There are some things hiding in here that haven't had a comment since 2018. I'm a bit worried when we actually look at them, no one is going to understand the context from so long ago (also makes the epic sort of hard to judge... what is it when it comes to triaging things into/out-of it).

[markwilkie]

I'm a bit worried when we actually look at them, no one is going to understand the context from so long ago (also makes the epic sort of hard to judge...

Yea, you're undoubtably right. In a "perfect" world, the Arcade guardian group would triage this epic soon. Also, as I look at the comparative priorities, I don't realistically see that happening in the next short while.

Interestingly enough, I think #6560 has looked in this epic for issues related to native builds which does help justify keeping the issues around. As specific business priorities come up, we can look at this epic for what we thought we wanted to do in the past.