#azdo — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #azdo, aggregated by home.social.
-
Microsoft.Testing.Platform Now Fully Supported in Azure DevOps
https://devblogs.microsoft.com/dotnet/microsoft-testing-platform-azure-retry/#microsoft #NET #C #F #Visual_Basic #Announcements #azdo #Azure_DevOPs #testing
-
Microsoft.Testing.Platform Now Fully Supported in Azure DevOps
https://devblogs.microsoft.com/dotnet/microsoft-testing-platform-azure-retry/#microsoft #NET #C #F #Visual_Basic #Announcements #azdo #Azure_DevOPs #testing
-
Visual Studio Dev/Test Benefit Explained | by Jim Harrer
https://devblogs.microsoft.com/visualstudio/visual-studio-dev-test-benefit-explained/
-
Visual Studio Dev/Test Benefit Explained | by Jim Harrer
https://devblogs.microsoft.com/visualstudio/visual-studio-dev-test-benefit-explained/
-
Visual Studio Dev/Test Benefit Explained | by Jim Harrer
https://devblogs.microsoft.com/visualstudio/visual-studio-dev-test-benefit-explained/
-
Visual Studio Dev/Test Benefit Explained | by Jim Harrer
https://devblogs.microsoft.com/visualstudio/visual-studio-dev-test-benefit-explained/
-
Visual Studio Dev/Test Benefit Explained | by Jim Harrer
https://devblogs.microsoft.com/visualstudio/visual-studio-dev-test-benefit-explained/
-
Anyone know if Azure DevOps Artifacts feeds can have cycles in their upstream sources? (ie: feed A is an upstream of feed B and feed B is an upstream of feed A). I don't see any reason why it wouldn't be allowed (or at least I could see why it would be hard to catch the more general case of longer upstream paths)
-
Anyone know if Azure DevOps Artifacts feeds can have cycles in their upstream sources? (ie: feed A is an upstream of feed B and feed B is an upstream of feed A). I don't see any reason why it wouldn't be allowed (or at least I could see why it would be hard to catch the more general case of longer upstream paths)
-
Anyone know if Azure DevOps Artifacts feeds can have cycles in their upstream sources? (ie: feed A is an upstream of feed B and feed B is an upstream of feed A). I don't see any reason why it wouldn't be allowed (or at least I could see why it would be hard to catch the more general case of longer upstream paths)
-
Anyone know if Azure DevOps Artifacts feeds can have cycles in their upstream sources? (ie: feed A is an upstream of feed B and feed B is an upstream of feed A). I don't see any reason why it wouldn't be allowed (or at least I could see why it would be hard to catch the more general case of longer upstream paths)
-
Anyone know if Azure DevOps Artifacts feeds can have cycles in their upstream sources? (ie: feed A is an upstream of feed B and feed B is an upstream of feed A). I don't see any reason why it wouldn't be allowed (or at least I could see why it would be hard to catch the more general case of longer upstream paths)
-
Good luck to the #microsoft cloud teams 🍀 #azure #azdo #o365
-
Good luck to the #microsoft cloud teams 🍀 #azure #azdo #o365
-
Good luck to the #microsoft cloud teams 🍀 #azure #azdo #o365
-
Good luck to the #microsoft cloud teams 🍀 #azure #azdo #o365
-
Good luck to the #microsoft cloud teams 🍀 #azure #azdo #o365
-
out of curiousity has anyone seen data corruption issues with either Azure DevOps Repos (Git only) or #Databricks' Git provider. Specifically interested in during merge conflicts, where a file was changed and the change isn't reflected in Git history. Boosts appreciated #AzDO #azure #azuredevops #git #github
-
out of curiousity has anyone seen data corruption issues with either Azure DevOps Repos (Git only) or #Databricks' Git provider. Specifically interested in during merge conflicts, where a file was changed and the change isn't reflected in Git history. Boosts appreciated #AzDO #azure #azuredevops #git #github
-
out of curiousity has anyone seen data corruption issues with either Azure DevOps Repos (Git only) or #Databricks' Git provider. Specifically interested in during merge conflicts, where a file was changed and the change isn't reflected in Git history. Boosts appreciated #AzDO #azure #azuredevops #git #github
-
out of curiousity has anyone seen data corruption issues with either Azure DevOps Repos (Git only) or #Databricks' Git provider. Specifically interested in during merge conflicts, where a file was changed and the change isn't reflected in Git history. Boosts appreciated #AzDO #azure #azuredevops #git #github
-
out of curiousity has anyone seen data corruption issues with either Azure DevOps Repos (Git only) or #Databricks' Git provider. Specifically interested in during merge conflicts, where a file was changed and the change isn't reflected in Git history. Boosts appreciated #AzDO #azure #azuredevops #git #github
-
@rjohnston @jlaban I think #AzDO is the best AzureDevOps abbreviation. It also doesn't have this problem 😅
-
@rjohnston @jlaban I think #AzDO is the best AzureDevOps abbreviation. It also doesn't have this problem 😅
-
@rjohnston @jlaban I think #AzDO is the best AzureDevOps abbreviation. It also doesn't have this problem 😅
-
@rjohnston @jlaban I think #AzDO is the best AzureDevOps abbreviation. It also doesn't have this problem 😅
-
I need to write some #AzDO pipelines this afternoon. Joy. :revblobfoxthonking:
-
I need to write some #AzDO pipelines this afternoon. Joy. :revblobfoxthonking: