Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improving success criteria for war package deployment . #7063

Merged
merged 1 commit into from
Apr 24, 2018

Conversation

hiyadav
Copy link
Contributor

@hiyadav hiyadav commented Apr 24, 2018

No description provided.

@hiyadav hiyadav requested review from sachinma and vincent1173 April 24, 2018 11:28
@@ -10,6 +10,7 @@ var msDeploy = require('webdeployment-common/deployusingmsdeploy.js');

export async function DeployWar(webPackage, taskParams: TaskParameters, msDeployPublishingProfile, kuduService: Kudu, appServiceUtility: AzureAppServiceUtility): Promise<void> {
// get list of files before deploying to the web app.
await appServiceUtility.pingApplication();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why ping required here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We observed minor difference in "MTime" of the "root" folder just after we first ping or fetch the file directory, to counter this we are pinging the application once before fetching the file directory.
The intention is to reduce the number of cases where there is a minor change in the modified time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants