Verified Commit 8f98c00d authored by Lars Bilke's avatar Lars Bilke

[web] Fixed links.

parent 8e26951c
......@@ -12,7 +12,7 @@ web url checker:
- >
urlchecker check --retry-count 5 --file-types .pandoc,.md
--white-listed-files releases/*
--white-listed-urls https://jenkins.opengeosys.org/job/ufz/job/ogs-container-maker/job/master/build,http://yourproxy.example.com,https://apt.kitware.com/ubuntu/,https://github.com/YOUR-USERNAME/ogs,https://jenkins.opengeosys.org/github-webhook/,http://localhost:1313,https://github.com/ufz/ogs/pull/\$1,http://www.opengeosys.org/images/xsd/OpenGeoSysXXX.xsd,https://\`-protocol
--white-listed-urls https://jenkins.opengeosys.org/job/ufz/job/ogs-container-maker/job/master/build,http://yourproxy.example.com,https://apt.kitware.com/ubuntu/,https://github.com/YOUR-USERNAME/ogs,https://jenkins.opengeosys.org/github-webhook/,http://localhost:1313,https://github.com/ufz/ogs/pull/\$1,http://www.opengeosys.org/images/xsd/OpenGeoSysXXX.xsd,https://\`-protocol,https://gitlab.opengeosys.org/ogs/ogs/-/merge_requests/new,https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images?job=container
content
preview web site:
......
......@@ -107,7 +107,7 @@ features:
Implement your new feature and [let the CI system](/docs/devguide/development-workflows/continuous-integration) run sophisticated tests automatically for you incorporating multiple computing platforms, a magnitude of software configurations and a whole array of CPU intensive complex test simulation runs.
- headline: Get help from core developers
textline: |
Once your feature is ready the [code review process](/docs/devguide/development-workflows/code-reviews/) starts. A helpful [core developer](https://gitlab.opengeosys.org/ogs/ogs/-/graphs/gitlab-ci) checks the proposed change for general acceptance and may give hints for improvement (of e.g. the computational performance or the code structure). Once the iterative feedback loop between you, code reviewer(s) and the automated test system satisfies all aspects the proposed change is merged into the main development line.
Once your feature is ready the [code review process](/docs/devguide/development-workflows/code-reviews/) starts. A helpful [core developer](https://gitlab.opengeosys.org/ogs/ogs/-/graphs/master) checks the proposed change for general acceptance and may give hints for improvement (of e.g. the computational performance or the code structure). Once the iterative feedback loop between you, code reviewer(s) and the automated test system satisfies all aspects the proposed change is merged into the main development line.
visual:
permalink: "/features/OGS-Software-Engineering-Small.png"
alt: Dev workflow
......
......@@ -89,7 +89,7 @@ The pressure buildup test is comparable to a pumping recovery test as
the extraction rate is first kept constant at $Q$, and then becomes zero
at $t=t_p$. This benchmark then adopts the same assumptions as in the
[Theis'
problem](https://benchmarks.opengeosys.org/docs/benchmarks/liquid-flow/liquid-flow-theis-problem/).
problem](https://www.opengeosys.org/docs/benchmarks/liquid-flow/liquid-flow-theis-problem/).
The analytical solution of the pressure difference $\Delta p$ with
respect to the initial pressure $p_0$ is the sum of two Theis curves:
one starting at $t=0$ and another starting at $t=t_p$ but with an
......
......@@ -13,7 +13,7 @@ weight = 1022
[GitLab CI](https://docs.gitlab.com/ee/ci/) is a powerful [Continuous Integration](../../development-workflows/continuous-integration) system integrated into GitLab.
The tasks of the CI system are configured in [scripts inside the OGS source code](https://gitlab.opengeosys.org/ogs/ogs/-/tree/gitlab-ci/scripts/ci). The entrypoint is defined in [.gitlab-ci.yml](https://gitlab.opengeosys.org/ogs/ogs/-/blob/gitlab-ci/.gitlab-ci.yml). Scripting and versioning the configuration together with the source code is very powerful, e.g. if you introduce a new OGS CMake configuration in a merge request even the change of the CI jobs configuration or jobs environment (Docker container definition) can be part of the merge request.
The tasks of the CI system are configured in [scripts inside the OGS source code](https://gitlab.opengeosys.org/ogs/ogs/-/tree/master/scripts/ci). The entrypoint is defined in [.gitlab-ci.yml](https://gitlab.opengeosys.org/ogs/ogs/-/blob/master/.gitlab-ci.yml). Scripting and versioning the configuration together with the source code is very powerful, e.g. if you introduce a new OGS CMake configuration in a merge request even the change of the CI jobs configuration or jobs environment (Docker container definition) can be part of the merge request.
## GitLab Pipeline
......
......@@ -25,7 +25,7 @@ Simply download an image from the [releases]({{< ref "/releases" >}}) page.
#### Option: Download image from the latest master-branch build
Simply download an image from the [latest master-branch build](https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images/?job=images) page.
Simply download an image from the [latest master-branch build](https://gitlab.opengeosys.org/ogs/ogs/-/jobs/artifacts/master/browse/_out/images?job=container) page.
### Run OGS inside a Container (called from outside)
......
......@@ -37,7 +37,7 @@ On Windows you may have to install the appropriate Visual Studio Redistributable
### Development builds
You can get the latest OpenGeoSys-5 (with recent bug-fixes) version from our [Jenkins CI system](https://jenkins.opengeosys.org/job/ufz/job/ogs5/job/master/). Binaries for Windows (64-Bit) and Linux are provided for the OGS FEM-simulator under *"Last successful Artifacts"*.
TODO: You can get the latest OpenGeoSys-5 (with recent bug-fixes) version from the CI system. Binaries for Windows (64-Bit) and Linux are provided for the OGS FEM-simulator under *"Last successful Artifacts"*.
### Source code
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment