dentaku/woodpecker-helm3
1
0
Fork 0
Code Pull requests Releases Activity

Directions on how to setup custom build of images till PR gets merged

Browse source
This commit is contained in:
Joachim Hill-Grannec 2019-12-31 14:19:56 -05:00
parent 353bd76f8f
commit 680989754a
No known key found for this signature in database
GPG key ID: 4391E44ED5D6BB46
2 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.gitignore vendored
View file

@ -5,6 +5,8 @@
*.so *.so
*.dylib *.dylib
.idea
# Test binary, built with `go test -c` # Test binary, built with `go test -c`
*.test *.test

8
README.md
View file

@ -69,3 +69,11 @@ drone-helm3 is largely backwards-compatible with drone-helm. There are some know
* `stable_repo_url` * `stable_repo_url`
Since helm 3 does not require Tiller, we also recommend switching to a service account with less-expansive permissions. Since helm 3 does not require Tiller, we also recommend switching to a service account with less-expansive permissions.
### Contribution
This repo is setup in a way that if you enable a personal drone server to build your fork it will
build and publish your image (makes it easier to test PRs and use the image till the contributions get merged)
* Build local ```DRONE_REPO_OWNER=josmo DRONE_REPO_NAME=drone-ecs drone exec```
* on your server (or cloud.drone.io) just make sure you have DOCKER_USERNAME, DOCKER_PASSWORD, and PLUGIN_REPO set as secrets