Multiple drone files?

Is there a possibility for multiple .drone.yml file. Similar to how you can can configure a specific pipeline file that you wish to you in a Jenkins pipeline.

In our development, we have different pipelines for each phase of development. For example, our pull request pipeline performs quick validation, where as when we wish to release, we go through more intense testing including integration testing.

Thoughts?

Thanks,
Dave

In this case you would use step conditions to limit which steps were executed for pull request vs push events. Below is an example to illustrate how this would work, and here is a link to the docs
http://docs.drone.io/step-conditions/

pipeline:

  # execute short tests for push events
  short:
    image: golang:1.8
    commands:
      - go test -short
    when:
      event: push

  # execute verbose tests for pull request events
  verbose:
    image: golang:1.8
    commands:
      - go test -v
    when:
      event: pull_request

  # build the binary if not a pull_request
  build:
    image: golang:1.8
    commands:
      - go build -o <binary>
    when:
      event:
        excludes: pull_request

  # publish to dockerhub for push events to master only
  publish:
    image: plugins/docker
    repo: drone/cli
    secrets: [docker_username, docker_password]
    when:
      branch: master
      event: push

Hi, I’ve a similar question to this topic.

Is it possible to have multiple drone files in a repo? My respository contains multiple different modules (with different technologies) which should be build separately (if possible: the single build should only be triggered if something has changed in a particular module or directory).

Thanks!