-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
- Loading branch information
There are no files selected for viewing
7 comments
on commit b933b51
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 is now running
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 is now running
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 is now running
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 outcome was FAILURE
Summary: Exit code 1 Build time: 0:0:0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 outcome was FAILURE
Summary: Exit code 1 Build time: 0:0:0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 outcome was FAILURE
Summary: Exit code 1 Build time: 0:0:0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TeamCity AzureWebFarm :: Continuous Integration Build 61 outcome was FAILURE
Summary: Exit code 1 Build time: 0:0:0
@robdmoore In the new SDK you don't have to use configuration publishing anymore, you instead use CloudConfigurationManager.GetSetting().
I've added back restarting on configuration changes - but using what's now considered a better approach.