Update: Tuesday, June 13th 2017 16:52 UTC
We have identified a bug that was introduced in the recent deployment that went in yesterday. This only impacts users who use custom task conditions in their build definitions and have recently updated their build definition after 6/12/2017 16:50 UTC. A fix is being rolled out has already been rolled-out to the affected regions and it should complete in the next 1-2 hours.
- Work Around: Don’t update build definition till the fix is deployed.
- Next Update: Before Tuesday, June 13th 2017 19:00 UTC
Sincerely,
Arvin
Initial Update: Tuesday, June 13th 2017 15:06 UTC
A potentially customer impacting issue is being investigated. Customers hosted in Multiple US Regions, West Europe, East Australia, South India regions may experience issue while saving custom conditions in their build definitions.
- Next Update: Before Tuesday, June 13th 2017 17:00 UTC
Sincerely,
Rakesh Reddy