We are trying to release to github when there is tag in git
pipeline:
compile:
image: quay.io/naveensrinivasan/sonar:0.5
commands:
- ./gradlew build
- sonar-scanner -Dsonar.analysis.mode=preview -Dsonar.github.pullRequest=$DRONE_PULL_REQUEST -Dsonar.github.repository=Revature/core -Dsonar.github.login=revaturebot -Dsonar.github.oauth=$REVATUREBOT_TOKEN -Dsonar.host.url=https://sq.com/ -Dsonar.login=abc
when:
event: [push, pull_request]
publish:
image: quay.io/naveensrinivasan/sonar:0.5
commands:
- ./gradlew zip
github_release:
api_key: $REVATUREBOT_TOKEN
files: core.zip
checksum: sha1
when:
event: tag
Here are the results from the tag
event and it is not executing any of the actions. What am I doing wrong? Thanks
mjwwit
(Michael de Wit)
December 28, 2016, 7:21am
2
Your problem is most likely in this part of your config. It’s best to use secrets for these kinds of things.
The GitHub Release plugin allows you to set the api key with this secret: GITHUB_RELEASE_API_KEY
.
You can add your secret using the Drone CLI:
drone secret add --image=quay.io/naveensrinivasan/sonar Revature/core GITHUB_RELEASE_API_KEY {your_api_key}
Then you’ll need to sign your config like this:
drone sign Revature/core
After doing this you can remove the whole api_key
part from your drone config.
The sample yaml file has a number of issues and is invalid. It seems to try to combine the 0.4 yaml and 0.5 yaml, which are not compatible formats. Please see http://readme.drone.io/0.5/usage/repository/configuration/
In addition, the github_release
is not ported to drone 0.5 yet. For a list of plugins available to drone 0.5 please see http://plugins.drone.io/
Looks like the github release plugin isn’t ready for 0.5 release which is the biggest issue.