"trigger" keyword and failing strategy

Summary

Use the trigger keyword as defined here and also set strategy: depend.

This MR implements caosdb/internal/all#650 and caosdb/internal/all#526.

Focus

Is the old functionality reproduced?

Test Environment

Watch the pipelines.

Check List for the Author

Please, prepare your MR for a review. Be sure to write a summary and a focus and create gitlab comments for the reviewer. They should guide the reviewer through the changes, explain your changes and also point out open questions. For further good practices have a look at our review guidelines

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Annotations in code (Gitlab comments)
  • Intent of new code
  • Problems with old code
  • Why this implementation?

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

For further good practices have a look at our review guidelines.

assigned to @daniel

added 1 commit

• 9840ab94 - FIX: DEPLOY_REF variable is needed.

Compare with previous version

added 1 commit

• caa70bd3 - DOC: Added comment to .gitlab-ci.yml

Compare with previous version

mentioned in issue caosdb-julialib#8 (closed)

mentioned in issue caosdb-octavelib#12 (closed)

mentioned in issue caosdb-pylib#127 (closed)

mentioned in issue caosdb-cpplib#44 (closed)

mentioned in issue caosdb-webui#281 (closed)

mentioned in issue caosdb-server#238 (closed)

marked the checklist item All automated tests pass as completed

marked the checklist item Reference related issues as completed

marked the checklist item Annotations in code (Gitlab comments) as completed

assigned to @timm