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

Set service name correctly when using Azure Pipelines urls #1846

Merged
merged 1 commit into from Sep 26, 2018

Conversation

JacobHenner
Copy link
Contributor

The previous service naming logic used the instance's subdomain. When an
Azure Pipelines url was provided, "dev" was always used. Now, the instance
name will be obtained from the url's path if an Azure Pipelines url is
provided.

Resolves #1841

@JacobHenner
Copy link
Contributor Author

JacobHenner commented Sep 24, 2018

It looks like the CI job failed on ARM due to a bug within DotNet core, rather than a bug within the PR itself.

See https://github.com/dotnet/coreclr/issues/18486 for details.

@TingluoHuang
Copy link
Contributor

@JacobHenner thanks for fixing this 👍

The previous service naming logic used the instance's subdomain. When an
Azure Pipelines url was provided, "dev" was always used. Now, the instance
name will be obtained from the url's path if an Azure Pipelines url is
provided.

Resolves microsoft#1841
@JacobHenner
Copy link
Contributor Author

This is ready for review. The CI job keeps failing for reasons unrelated to my change (different each time, oddly enough).

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.

None yet

2 participants