entrypoint overrides the image’s ENTRYPOINT. The command used as executable when launching the container. The field is appropriate if you would rather have a different host name instead of localhost, for example, if you are starting multiple versions of the same service. By default, all services are exposed directly on localhost. Name defines the name for reaching the secondary service containers. The first image listed under a job defines the job’s own primary container image where all steps will run. The name of a custom docker image to use. If more than one is set you will receive an error.Ĭonfigured by docker key which takes a list of maps: Key (1) One executor type should be specified per job. See Workflows for configuring branch execution for jobs in a workflow or 2.1 config.Īmount of CPU and RAM allocated to each container in a job. Number of parallel instances of this job to run (default: 1)Ī map of environment variable names and values.Ī map defining rules to allow/block execution of specific branches for a single job that is not in a workflow or a 2.1 config (default: all allowed). working_directory will be created automatically if it doesn’t exist. Note: Paths written in your YAML configuration file will not be expanded if your store_test_results.path is $CIRCLE_WORKING_DIRECTORY/tests, then CircleCI will attempt to store the test subdirectory of the directory literally named $CIRCLE_WORKING_DIRECTORY, dollar sign $ and all. Processes run during the job can use the $CIRCLE_WORKING_DIRECTORY environment variable to refer to this directory. Default: ~/project (where project is a literal string, not the name of your specific project). Parameters for making a job explicitly configurable in a workflow.
Can be overridden by shell in each step (default: See Default Shell Options) Shell to use for execution command in all steps. The value map has the following attributes: Key A name should be case insensitive unique within a current jobs list.
0 kommentar(er)
