Agent configuration files

You can supply your own agent configuration and have Pipelines merge it with the system config.

You can store the config:

in your repository
included into the build image
generated earlier in the step script

Referencing a config file in an agent definition

definitions:
  agents:
    my-agent:
      config:
        path: "config.yaml"   # relative to the agent’s working directory
pipelines:
  default:
    - step:
        script:
          - agent: my-agent

Overriding the config at step level

pipelines:
  default:
    - step:
        script:
          - agent: my-agent
            config:
              path: "${BITBUCKET_CLONE_DIR}/custom-config.yaml"

Key behaviours:

The config file at config.path is merged with the Pipelines system config.

この内容はお役に立ちましたか?

正確ではなかった明確ではなかった関係なかった

さらにヘルプが必要ですか?

アトラシアンコミュニティをご利用ください。

コミュニティに質問