Travis’s encryption is done on a per-repository basis:
Encryption and decryption keys are tied to the repository. If you fork a project and add it to Travis CI, it will not have access to the encrypted variables.
The encrypted variable hashes found in
.travis.yml are intended for bonej/BoneJ2, not mdoube/BoneJ2.
The failure to decrypt the variables does not fail the build directly. Rather, the build fails because the deploy to maven.scijava.org cannot be done, due to missing credentials:
Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project pom-bonej: Failed to deploy artifacts: Could not transfer artifact org.bonej:pom-bonej:pom:6.1.2-20190819.051954-8 from/to scijava.snapshots (dav:https://maven.scijava.org/content/repositories/snapshots): Failed to transfer file: https://maven.scijava.org/content/repositories/snapshots/org/bonej/pom-bonej/6.1.2-SNAPSHOT/pom-bonej-6.1.2-20190819.051954-8.pom. Return code is: 401 -> [Help 1]
I updated the
travis-build.sh script to detect this situation, and not attempt a deploy if the current repository being built does not match what’s in the
@mdoube Please try clicking the “Restart build” button of the failed build you linked, and we’ll see if the problem goes away. What should happen is that Travis should no longer attempt to deploy your non-canonical snapshot artifacts.