Once snapshot publishing is verified, we'll want to also define release publishing. This will allow for better release automation of snapshot/release versions.
Waiting for https://travis-ci.org/OpenAPITools/openapi-generator/builds/390254621 https://travis-ci.org/OpenAPITools/openapi-generator/builds/390267814 to complete. The first build addresses an issue where I forgot to reference the location of the GPG secret. Second build should resolve an issue with the gpg trustdb complaining about an invalid packet.
See https://github.com/making/travis-ci-maven-deploy-skelton
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.shand./bin/security/{LANG}-petstore.shif updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\. -
Filed the PR against the correct branch: Default: master. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
(details of the change, additional tests that have been done, reference to the issue for tracking, etc)