http://192.168.180.206:8001/ 2026-05-13T08:10:03+00:00 http://192.168.180.206:8001/ http://192.168.180.206:8001/_media/wiki:dokuwiki.svg text/html 2025-06-18T13:45:33+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/git:gitlab:ci:yaml:dynamic_tags?rev=1750254333&do=diff dynamic runner tag Variable expansion in tags works. Simple runner tag can be set as shown: variables: RUNNER_TAG: "staging" job: tags: - $RUNNER_TAG tags: - ${CI_COMMIT_BRANCH} Not possible to define array of strings as variable: text/html 2025-07-30T08:42:07+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/git:gitlab:ci:yaml:inputs?rev=1753864927&do=diff pipeline inputs Note: spec keywords must be defined in “header” - before YAML's end of directives marker ---. spec: inputs: nproc: default: $(nproc) description: "Value passed as -j to make" --- build: stage: build script: - m -j$[[ inputs.nproc ]] text/html 2024-02-13T11:15:07+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/git:gitlab:ci:yaml:needs?rev=1707822907&do=diff needs OR-ed needs Not possible * Is there a way to use OR condition with needs in GitLab CI job * Is there a way to use OR condition with needs in GitLab CI job Workaround: * duplicate all jobs chain (use hidden job as template and change only relevant parts) * Do not use needs, but simple stage ordering. * use optional (but it is not the same like OR: sideffect: possible to start job wihtout needed artifacts) text/html 2025-01-03T13:06:25+00:00 Anonymous (anonymous@undisclosed.example.com) http://192.168.180.206:8001/git:gitlab:ci:yaml:rules?rev=1735909585&do=diff rules rules:if Use rules:if clauses to specify when to add a job to a pipeline: If an if statement is true, add the job to the pipeline. If an if statement is true, but it’s combined with when: never, do not add the job to the pipeline. If no if statements are true, do not add the job to the pipeline.