F linkahead rename

Summary

LinkAhead rename

Test Environment

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)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
  • How do I use the software? Assume "stupid" users.
  • How do I develop or debug the software? Assume novice developers.
• 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)
• Appropriate user and developer documentation (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.

.gitlab-ci.yml

@@ -27,7 +27,8 @@ variables:
   # TODO Rename to linkahead
   CI_REGISTRY_IMAGE: $CI_REGISTRY/caosdb/src/caosdb-webui/testenv
 
-image: $CI_REGISTRY_IMAGE:latest
+# TODO Rename back to "latest"
+image: $CI_REGISTRY_IMAGE:f-linkahead-rename
 
 
 stages:
@@ -82,8 +83,8 @@ build-testenv:
       # use here general latest or specific branch latest...
     - docker build 
       --pull
-      -t $CI_REGISTRY_IMAGE:latest .
-    - docker push $CI_REGISTRY_IMAGE:latest
+      -t $CI_REGISTRY_IMAGE:f-linkahead-rename .
+    - docker push $CI_REGISTRY_IMAGE:f-linkahead-rename
 
 # Build the sphinx documentation and make it ready for deployment by Gitlab Pages
 # documentation: