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
[Azure Maps] - Onboarding for Search, Route, Render SDKs. #29580
[Azure Maps] - Onboarding for Search, Route, Render SDKs. #29580
Conversation
/azp run prepare-pipelines |
/azp run java - azure-maps-route - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines failed to run 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
API change check APIView has identified API level changes in this PR and created following API reviews. azure-maps-search |
/azp run java - azure-maps-route - tests |
Azure Pipelines successfully started running 1 pipeline(s). |
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
Pull request contains merge conflicts. |
974693f
to
7db1a2c
Compare
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
/check-enforcer evaulate |
public static final MapTileSize SIZE256 = fromString("256"); | ||
|
||
/** Static value 512 for MapTileSize. */ | ||
public static final MapTileSize SIZE512 = fromString("512"); |
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.
un-resolving as this is not resolved yet.
khmic5: resolved!
sdk/maps/azure-maps-render/src/main/java/com/azure/maps/render/models/MapTileset.java
Outdated
Show resolved
Hide resolved
sdk/maps/azure-maps-render/src/main/java/com/azure/maps/render/models/MapTileset.java
Outdated
Show resolved
Hide resolved
...ps/azure-maps-render/src/main/java/com/azure/maps/render/models/RegionCopyrightsCountry.java
Outdated
Show resolved
Hide resolved
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
/check-enforcer evaluate |
/azp run prepare-pipelines |
Azure Pipelines successfully started running 1 pipeline(s). |
* Adding Azure Maps Search Route Render
* Adding Azure Maps Search Route Render
Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines