Pack can have errors but still pass CI
Consider the roslyn repository as an example. Clone master, run Build.cmd -restore -pack and you will get the following error:
e:\nuget\microsoft.dotnet.arcade.sdk\1.0.0-beta.19171.3\tools\BuildReleasePackages.targets(20,5): error : Multiple packages of name 'Microsoft.CodeAnalysis' specifie d [e:\nuget\microsoft.dotnet.arcade.sdk\1.0.0-beta.19171.3\tools\AfterSolutionBuild.proj]
Even so $lastExitCode is still 0 and the build passes. This should be failing our build.
Added to post preview 7
@markwilkie where can I see how the bugs are prioritized? Not judging you moving this bug just curious where the scheduling, prioritization is kept at.
We're using the ZenHub extension, and using "epics". These "epics" denote the business priority that we're classifying the bugs as. We opted for ZenHub over labels because of the handy parent/child relationship for issues, and a nice kanban board.