Should be because mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -V needs a GPG key installed in the testing machine, but it is actually not. Should not be necessarily to be the same GPG key I used in my local machine.
gpg: no default secret key: secret key not available
gpg: signing failed: secret key not available
Solution include setup the GPG key right in Travis CI (https://github.com/making/travis-ci-maven-deploy-skelton). However, since we are not really using travis CI for deployment, this seems cause unnecessary complicity.
Another possibility is to follow https://github.com/computology/java-test-package and customize command. Not sure how much it helps.
CircleCI may have the same problem. Just it is now using caching packages.
Should be because
mvn install -DskipTests=true -Dmaven.javadoc.skip=true -B -Vneeds a GPG key installed in the testing machine, but it is actually not. Should not be necessarily to be the same GPG key I used in my local machine.Solution include setup the GPG key right in Travis CI (https://github.com/making/travis-ci-maven-deploy-skelton). However, since we are not really using travis CI for deployment, this seems cause unnecessary complicity.
Another possibility is to follow https://github.com/computology/java-test-package and customize command. Not sure how much it helps.
CircleCI may have the same problem. Just it is now using caching packages.