![]() Also available: cache:paths, cache:key, cache:untracked, and cache:policy. List of files that should be cached between subsequent runs. Also available: environment:name, environment:url, environment:on_stop, and environment:action. Name of an environment to which the job deploys. ![]() Also available: when:manual and when:delayed. Failed job doesn't contribute to commit status. List of tags which are used to select Runner.Īllow job to fail. List of conditions to evaluate and determine selected attributes of a job, and whether or not it is created. Also available: except:refs, except:kubernetes, except:variables, and except:changes. Also available: only:refs, only:kubernetes, only:variables, and only:changes. Override a set of commands that are executed after job. Override a set of commands that are executed before job. Also available: services:name, services:alias, services:entrypoint, and services:command. Also available: image:name and image:entrypoint. Shell script which is executed by Runner. The following table lists available parameters for jobs: Keyword For example, /bin/true.Ī job is defined as a list of parameters that define the job's behavior. If you get validation error when using specific values (for example, true or false), try to: Unavailable names for jobsĮach job must have a unique name, but there are a few reserved keywords that You can find the Lint under the page ci/lint of your gitlab-ci.ymlĮach instance of GitLab CI has an embedded debug tool called Lint, which validates theĬontent of your. What is important, is that each job is run Jobs are picked up by Runners and executed within theĮnvironment of the Runner. Or run a script ( test.sh) in the repository. Of course a command can execute code directly (. ![]() Jobs, where each of the jobs executes a different command. The above example is the simplest possible CI/CD configuration with two separate
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |