During the last PR, the step to add nuget sources was moved out of the setup task and into its own step. Random failures were occurring when autorest would build and test individual SDKs if the code artifact repository was set in the build server. It was not necessary to add the nuget sources until the Pack and Deploy to Code Artifact step. The add nuget sources step should have also been added back into the Pack and Deploy to PowerShell Gallery step. This PR address this oversight and was something we couldn't easily see when the CI tasks ran during testing.
In addition several filters were added to remove unnecessary tasks from the merge back to main branch ci workflow. These tasks include testing the dev SDKs against the prod PowerShell module and deploying back to code artifact again.
add nuget sources to Pack & Deploy PSGallery step
Issues
What does this solve?
During the last PR, the step to add nuget sources was moved out of the setup task and into its own step. Random failures were occurring when autorest would build and test individual SDKs if the code artifact repository was set in the build server. It was not necessary to add the nuget sources until the Pack and Deploy to Code Artifact step. The add nuget sources step should have also been added back into the Pack and Deploy to PowerShell Gallery step. This PR address this oversight and was something we couldn't easily see when the CI tasks ran during testing.
In addition several filters were added to remove unnecessary tasks from the merge back to main branch ci workflow. These tasks include testing the dev SDKs against the prod PowerShell module and deploying back to code artifact again.
Is there anything particularly tricky?
No
How should this be tested?
N/A