Provide example .gitlab-ci.yml extending the AutoDevOps Pipeline

[j-bauer]

It's been asked repeatedly if it is possible to run own CI-Jobs without loosing the AutoDevOps features. This example shows how:

include:
    - template: Auto-DevOps.gitlab-ci.yml

stages:
    - arc_json
    - quality_report_generator
    - quality_report
    - generate_metadata
    - my_own_ci_stuff

My own stuff:
    stage: my_own_ci_stuff
    script:
        - echo "doing things..."

Maybe we want to include this in the ARC template repo? Or at least create a KB article for this.

Opinions? @Brilator @kMutagene @muehlhaus @HLWeil

[kMutagene]

I do not think that such an advanced usecase should be in the go-to arc template repo. I'd vote for a kb entry only.

[j-bauer]

That would probably suffice. All in favor?

[Brilator]

Note to self:
Extend with ARC summary as example:

include:
    - template: Auto-DevOps.gitlab-ci.yml

stages:
    - arc_json
    - quality_report_generator
    - quality_report
    - generate_metadata
    - arc-summary

summary:
  stage: arc-summary
  image:
    name: ghcr.io/nfdi4plants/arc-summary:main
    entrypoint: [""]
  script:
    - /tool/ARCSummary summary -d .
  artifacts:
      paths:
        - README.md
      expire_in: 1 week
  only:
    - main

[Brilator]

@j-bauer or @kMutagene, can you do me the favor and double check this? I would then add this as one example to the knowledge base.

This examples creates uses https://github.com/nfdi4plants/ARCSummary#download-and-run-docker-image and creates a README.md as artifact.

There might be an easier / more efficient way with a docker runner?

[Brilator]

Added examples here:

Please check, if that makes sense:
https://nfdi4plants.github.io/nfdi4plants.knowledgebase/datahub/features/gitlab-ci-jobs/