when i was working on this a few months ago, I had to turn the nighties off because the `sign` goal needed a new setup for the gpg keys, IIRC. I think we needed to configure Jenkins with an `ENV` var for signing keys, something simikar to what is in your `~/.m2.settings.xml` if you're releasing. so it was failing on `deploy` ; Maybe you guys already fixed that already?
Here though it seems like its loking for a `master` branch: https://builds.apache.org/job/mahout-nightly/2536/consoleText ``` Started by timer Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on H36 (ubuntu) in workspace /home/jenkins/jenkins-slave/workspace/mahout-nightly No credentials specified Cloning the remote Git repository Cloning repository https://git-wip-us.apache.org/repos/asf/mahout.git > git init /home/jenkins/jenkins-slave/workspace/mahout-nightly # timeout=10 Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/mahout.git > git --version # timeout=10 > git fetch --tags --progress -- > https://git-wip-us.apache.org/repos/asf/mahout.git > +refs/heads/**:refs/remotes/origin/** > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/mahout.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/**:refs/remotes/origin/** # > timeout=10 > git config remote.origin.url > https://git-wip-us.apache.org/repos/asf/mahout.git # timeout=10 Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/mahout.git > git fetch --tags --progress -- > https://git-wip-us.apache.org/repos/asf/mahout.git > +refs/heads/**:refs/remotes/origin/** > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 > git rev-parse origin/master^{commit} # timeout=10 ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.``` quick search of https://github.com/apache/mahout/blob/14.1/pom.xml#L951 for the term `master` doent reveal anything maybe the jenkins cofig job needs a `scm` block config update to build from `trunk` ?
