Commit 1d766c3d authored by Thomas Beermann's avatar Thomas Beermann
Browse files

Extend logs with automatic MR deployment descriptions

parent 00590b52
Pipeline #92258 passed with stages
in 14 minutes and 44 seconds
......@@ -80,6 +80,7 @@ trigger_deploy_mr:
- apk add curl
- 'curl -X POST -F token=$GITLAB_DESY_TOKEN -F ref=main --form "variables[CI_COMMIT_REF_NAME]=$CI_COMMIT_REF_NAME" --form "variables[CI_MERGE_REQUEST_IID]=$CI_MERGE_REQUEST_IID" --form "variables[CP_COMPONENT]=webapp" $GITLAB_DESY_URL'
- echo "Application will be automatically deployed. After a couple of minutes you can find it at http://webapp-`echo $CI_COMMIT_REF_NAME | tr _ -`"
......@@ -4,6 +4,10 @@ Helmholtz Marketplace Web App
An entry point web application for scientific related services from various vendors.
### Automatic deployments of Merge Requests
Each Merge Request will be automatically deployed to a Kubernetes test cluster so that you can directly see your changes in a live deployment. It will be set up together with the Cerebrum backend with its own database. For Cerebrum the code from its current master branch will be taken. A dynamic URL based on the branch name of the MR will be created. You can find the URL in the output of the last job in the CI/CD pipeline (`trigger_deploy_mr`). When you push new commits to the MR the application will be redeployed.
### Running the CI in your fork
If you want to run the SonarQube tests in your fork, you will have to create a GitHub secret with the name `SONAR_AUTH_TOKEN` in your repository. You can get the necessary token in SonarQube via "My Account" -> "Security" -> "Tokens".
Supports Markdown
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