-
Notifications
You must be signed in to change notification settings - Fork 410
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
ci: add graph building workflow #1468
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CHANGELOG.md entries missing. |
TheGreatRefrigerator
force-pushed
the
ci/automated-graph-building
branch
from
June 13, 2023 13:02
88a779a
to
8e194b2
Compare
TheGreatRefrigerator
force-pushed
the
ci/automated-graph-building
branch
from
June 13, 2023 13:49
d4ff573
to
5b5f0f1
Compare
Done |
koebi
approved these changes
Jun 13, 2023
The workflow can only be run on workflow_dispatch from the GitHub UI by ors team members. Inputs are: - `osm_file_url`: Download URL to the OSM pbf file (best use geofabrik) - `environment`: GitHub environment to use - `config_in_war`: whether the war file should include the config Check how to create an environment on: https://heigit.atlassian.net/wiki/spaces/openrouteservice/pages/129695876/Graph+Builder+Usage Outputs graphs, logs, elevation_cache, PBF, war and config to the `<gh_runner_ors_repo_dir>/envs/ENV_NAME` folder on the server the GitHub runner is on. Detailed changes in #1468 Co-authored-by: Amandus Butzer <amandus.butzer@heigit.org>
the following env vars are now available for configuring paths: - 'GRAPHS_FOLDER': overrides 'ors.services.routing.profiles.default_params.graphs_root_path' config value - 'ELEVATION_CACHE_FOLDER': overrides 'ors.services.routing.profiles.default_params.elevation_cache_path' config value - 'PBF_FILE_PATH': overrides the first array entry of 'ors.services.routing.sources' config value - 'LOGS_FOLDER': overrides 'ors.logging.location' config value Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
report_every takes the number of execution iterations on which it should output the log entry. Co-authored-by: Amandus Butzer <amandus.butzer@heigit.org>
Co-authored-by: Jakob Schnell <jakob.schnell@heigit.org>
TheGreatRefrigerator
force-pushed
the
ci/automated-graph-building
branch
from
June 13, 2023 14:16
5b5f0f1
to
5f1f5a7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Checklist
have been resolved.
[Unreleased] heading.
along with a short description of what it is for, and documented this in the Pull Request (below).
(at least Germany), and the graphs build without problems (i.e. no out-of-memory errors).
importer etc.), I have generated longer distance routes for the affected profiles with different options
(avoid features, max weight etc.) and compared these with the routes of the same parameters and start/end
points generated from the current live ORS.
If there are differences then the reasoning for these MUST be documented in the pull request.
and why the change was needed.
Information about the changes