https://github.com/metwork-framework/docker-drone-downstream-specific-image

A specific downstream plugin for drone for our use case and our CI hardware
https://github.com/metwork-framework/docker-drone-downstream-specific-image

autoreadme docker-image drone-ci integration-level-3 internal

Last synced: 18 days ago
JSON representation

A specific downstream plugin for drone for our use case and our CI hardware

• Host: GitHub
• URL: https://github.com/metwork-framework/docker-drone-downstream-specific-image
• Owner: metwork-framework
• License: bsd-3-clause
• Created: 2018-10-02T15:09:55.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2025-05-15T06:26:45.000Z (about 1 year ago)
• Last Synced: 2026-02-15T17:40:14.684Z (4 months ago)
• Topics: autoreadme, docker-image, drone-ci, integration-level-3, internal
• Language: Shell
• Size: 37.1 KB
• Stars: 0
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE
  • Code of conduct: CODE_OF_CONDUCT.md

Awesome Lists containing this project

README

          
# docker-drone-downstream-specific-image

[//]: # (automatically generated from https://github.com/metwork-framework/github_organization_management/blob/master/common_files/README.md)

**Status (master branch)**

[![GitHub CI](https://github.com/metwork-framework/docker-drone-downstream-specific-image/actions/workflows/ci.yml/badge.svg?branch=master)](https://github.com/metwork-framework/docker-drone-downstream-specific-image/actions?query=workflow%3ACI+branch%3Amaster)

[![DockerHub](https://github.com/metwork-framework/resources/blob/master/badges/dockerhub_link.svg)](https://hub.docker.com/r/metwork/drone-downstream-specific-image/)

[![Maintenance](https://raw.githubusercontent.com/metwork-framework/resources/master/badges/maintained.svg)](https://github.com/metwork-framework/resources/blob/master/badges/maintained.svg)

## What is it ?

This is a custom drone "downstream" plugin for our use case and our CI hardware.

The idea is to get a conditional "downstream" plugin. If there is a `.drone_downstream_bypass`

file in the working directory, the step is bypassed.

## Configuration example

```

pipeline:

  step:

    image: metwork/drone-downstream-specific-image:latest

    pull: true

    secrets: [ drone_server, drone_token ]

    repositories:

      - metwork-framework/mfserv

      - metwork-framework/mfbase@integration

    params:

      - foo1=bar1

      - foo2=bar2

    when:

      branch: master

      event: push

      status: success

```

## Contributing guide

See [CONTRIBUTING.md](CONTRIBUTING.md) file.

## Code of Conduct

See [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) file.

## Sponsors

*(If you are officially paid to work on MetWork Framework, please contact us to add your company logo here!)*

[![logo](https://raw.githubusercontent.com/metwork-framework/resources/master/sponsors/meteofrance-small.jpeg)](http://www.meteofrance.com)