You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2019/08/01 15:11:26 UTC
[GitHub] [incubator-openwhisk] chetanmeh opened a new pull request #4573:
Publish OpenWhisk standalone jar to Github release
chetanmeh opened a new pull request #4573: Publish OpenWhisk standalone jar to Github release
URL: https://github.com/apache/incubator-openwhisk/pull/4573
Enables publishing the `openwhisk-standalone.jar` to Github release
Closes #4525
## Description
It uses approach similar to whats being used in incubator-openwhisk-cli repo to publish the `wsk` cli
Key aspects
1. Build is published as `pre-release`
2. It tagged as `nightly` to follow convention used for Docker builds
### Steps followed
First a personal Github api token was created with commit rights to repo
Generate encrypted key via approach as demonstrated [here](https://gist.github.com/willprice/e07efd73fb7f13f917ea)
```bash
# Install travis cli
$ gem install travis
# Login via github
$ travis login
# Encrypt the github access token
$ travis encrypt <token> -r apache/incubator-openwhisk
Please add the following to your .travis.yml file:
secure: "BmUqo91TCbfhsLIIeeDPlg1501jigTOy3nmrKq13rq7lAGYU ..."
# Create encrypted env variable `API_KEY` used to create tag
# Its placed in `env` section
$ echo API_KEY=<token> | travis encrypt -r apache/incubator-openwhisk
```
## Related issue and scope
<!--- Please include a link to a related issue if there is one. -->
- [ ] I opened an issue to propose and discuss this change (#????)
## My changes affect the following components
<!--- Select below all system components are affected by your change. -->
<!--- Enter an `x` in all applicable boxes. -->
- [ ] API
- [ ] Controller
- [ ] Message Bus (e.g., Kafka)
- [ ] Loadbalancer
- [ ] Invoker
- [ ] Intrinsic actions (e.g., sequences, conductors)
- [ ] Data stores (e.g., CouchDB)
- [ ] Tests
- [ ] Deployment
- [ ] CLI
- [ ] General tooling
- [ ] Documentation
## Types of changes
<!--- What types of changes does your code introduce? Use `x` in all the boxes that apply: -->
- [ ] Bug fix (generally a non-breaking change which closes an issue).
- [ ] Enhancement or new feature (adds new functionality).
- [ ] Breaking change (a bug fix or enhancement which changes existing behavior).
## Checklist:
<!--- Please review the points below which help you make sure you've covered all aspects of the change you're making. -->
- [ ] I signed an [Apache CLA](https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md).
- [ ] I reviewed the [style guides](https://github.com/apache/incubator-openwhisk/wiki/Contributing:-Git-guidelines#code-readiness) and followed the recommendations (Travis CI will check :).
- [ ] I added tests to cover my changes.
- [ ] My changes require further changes to the documentation.
- [ ] I updated the documentation where necessary.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services