Přemek Vysoký
Přemek Vysoký
> This is an issue for tracking an IcM we opened with the Guardian team: https://portal.microsofticm.com/imp/v3/incidents/incident/499541728/summary The auto-injected Guardian step SpotBugs started to fail this week and is consistently failing....
Custom configurations need to be added via this. We should also make `Pipeline.Validations` public and not internal.
## Problem [This test](https://github.com/dotnet/arcade-services/blob/d0bfa2fa0228c96a1a84c3d76747dc04b528aeba/test/Maestro.ScenarioTests/ScenarioTests_Clone.cs#L20) runs for 9-10 minutes. It clones repos based on `Version.Details.xml` dependencies and verifies the right set of repos was cloned. Additionally to this taking quite long,...
The tests will start to run in the pipeline soon, let's make them green
Re-write the deployment as it will become more difficult when the service has many containers.
If we have a code flow PR branch, we always need to fetch it from the remote to make sure there's no new updates. If we have one and the...
We need to be able to run several replicas so that the throughput of the service is better. We need to be able to safely deploy new revision in this...
### Context Before, Maestro would call PCS when a code flow subscription was triggered. Now we can call the code flow logic directly and perform the update. However, because we...
## Motivation The Maestro++ and PCS services are similar in what they're doing: - Both have the same connectivity (GitHub, AzDO, BAR, ..) - Both have similar capabilities (opening PRs,...
### Release Note Category - [ ] Feature changes/additions - [ ] Bug fixes - [x] Internal Infrastructure Improvements ### Release Note Description Assign failed VMR sync build failure issues...