OilfieldToolsNet/opm-simulators
4
0
Fork 0
mirror of https://github.com/OPM/opm-simulators.git synced 2024-11-25 02:30:18 -06:00
Code Issues Packages Projects Releases Wiki Activity
71e2d63a6e
opm-simulators/jenkins
History
babrodtk 9b91e2f20b Added script to update opm-data references
2017-01-16 08:06:26 +01:00
..
build.sh Added script to update opm-data references 2017-01-16 08:06:26 +01:00
README.md add multiconfiguration support to jenkins build script 2016-08-23 14:26:06 +02:00
run-norne.sh changed: use a separate output dir for each simulator in norne integration test 2016-11-28 10:15:21 +01:00
run-polymer.sh changed: drop usage of python based comparison script in polymer integration test 2016-11-03 09:10:08 +01:00
run-spe.sh changed: drop usage of python based comparison script in spe integration tests 2016-11-03 09:10:26 +01:00

README.md

opm-simulators jenkins build scripts:

build.sh: This script will build dependencies, then build opm-simulators and execute its tests. It also inspects the $ghbPrBuildComment environmental variable and builds downstreams if requested. It inspects the $ghbPrBuildComment environmental variable to obtain a pull request to use for the modules.

It is intended for pre-merge builds of pull requests.

To specify a given pull request to use for upstreams and downstreams, trigger line needs to contain <module-name>=<pull request number>.

To build with downstreams the trigger line needs to contain 'with downstreams'.

run-spe.sh: This script will execute the SPE1, SPE3 and SPE9 cases, then compare against OPM and Eclipse reference results. It is meant to be executed after a build. The binary used used is from the build identified by the configuration environment variable.

run-norne.sh: This script will execute the Norne case, and generate a document with plots of the results. It is meant to be executed after a build. The binary used used is from the build identified by the configuration environment variable.

run-polymer.sh: This script will execute the simple2D polymer case, then compare against Eclipse reference results. It is meant to be executed after a build. The binary used used is from the build identified by the configuration environment variable.