Merge remote-tracking branch 'origin/master' into multi-pipeline

* origin/master:
  Bump version
  Updating the UI: matrix-reloaded
  Usage
  Some info on the project
This commit is contained in:
Laszlo Fogas 2019-06-05 08:03:22 +02:00
commit 302f07da3c
4 changed files with 827 additions and 956 deletions

View file

@ -109,7 +109,7 @@ pipeline:
repo: laszlocloud/drone-oss-08-server
dockerfile: Dockerfile.alpine
secrets: [ docker_username, docker_password ]
tag: [ 0.8.94-alpine ]
tag: [ 0.8.95-alpine ]
when:
event: tag
@ -118,7 +118,7 @@ pipeline:
repo: laszlocloud/drone-oss-08-agent
dockerfile: Dockerfile.agent.alpine
secrets: [ docker_username, docker_password ]
tag: [ 0.8.94-alpine ]
tag: [ 0.8.95-alpine ]
when:
event: tag
@ -126,7 +126,7 @@ pipeline:
image: plugins/docker
repo: laszlocloud/drone-oss-08-server
secrets: [ docker_username, docker_password ]
tag: [ 0.8.94 ]
tag: [ 0.8.95 ]
when:
event: tag
@ -135,7 +135,7 @@ pipeline:
repo: laszlocloud/drone-oss-08-agent
dockerfile: Dockerfile.agent
secrets: [ docker_username, docker_password ]
tag: [ 0.8.94 ]
tag: [ 0.8.95 ]
when:
event: tag

View file

@ -1,41 +1,31 @@
Drone is a Continuous Delivery system built on container technology. Drone uses a simple YAML configuration file, a superset of docker-compose, to define and execute Pipelines inside Docker containers.
## Yes, it's a fork
<br/>
This repository is a hard fork of the Drone CI system.
<img src="https://github.com/drone/brand/blob/master/screenshots/screenshot_build_success.png" style="max-width:100px;" />
Forked at the `0.8.9` version https://github.com/drone/drone/commit/768ed784bd74b0e0c2d8d49c4c8b6dca99b25e96
Sample Pipeline Configuration:
## Why fork?
```yaml
pipeline:
backend:
image: golang
commands:
- go get
- go build
- go test
Drone has been an open-core project since many prior versions. With each source file indicating whether it is part of the Apache 2.0 licensed or the propritary enterprise license. In the 0.8 line the enterprise features were limited to features like autoscaling and secret vaults.
frontend:
image: node:6
commands:
- npm install
- npm test
However in the 1.0 line, databases other than SQLite, TLS support and agent based horizontal scaling were also moved under the enterprise license. Limiting the open source version to single node, hobbyist deployments.
publish:
image: plugins/docker
repo: octocat/hello-world
tags: [ 1, 1.1, latest ]
registry: index.docker.io
The above feature reductions and the lack of clear communication of what is part of the open-source version led to this fork.
notify:
image: plugins/slack
channel: developers
username: drone
```
## The focus of this fork
Documentation and Other Links:
The focus of this fork is
* Setup Documentation [docs.drone.io/installation](http://docs.drone.io/installation/)
* Usage Documentation [docs.drone.io/getting-started](http://docs.drone.io/getting-started/)
* Plugin Index [plugins.drone.io](http://plugins.drone.io/)
* Getting Help [docs.drone.io/getting-help](http://docs.drone.io/getting-help/)
- Github
- Kubernetes and VM based backends
- Linux/amd64
- Some really good features that Drone 1.0 introduced: multiple pipelines, cron triggers
## Why should you use this fork?
you shouldn't necessarily. Paying for Drone 1.0 is a fine choice.
Check the issues and releases of this project if you are evaluating this project.
Also you can check the devlog to get the nuances: https://laszlo.cloud/drone-oss-08-devlog-1
The project is currently used by one user, with 50+ repos and 500+ builds a week.

File diff suppressed because one or more lines are too long

6
vendor/vendor.json vendored
View file

@ -425,10 +425,10 @@
"revisionTime": "2016-05-04T02:26:26Z"
},
{
"checksumSHA1": "rwUvdtx1kZz5wYyDLp/hpZJMrIw=",
"checksumSHA1": "hmMnLbqq5stRt+XMnqnVglxk8pg=",
"path": "github.com/laszlocph/drone-ui/dist",
"revision": "181e328effb3aeb4c044caa76d8e005d563632a1",
"revisionTime": "2019-05-27T09:07:09Z"
"revision": "0dbf167b5c9efd822bbdf2723bdfa5b8499992ba",
"revisionTime": "2019-06-05T04:37:12Z"
},
{
"path": "github.com/lib/pq",