You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by Dale LaBossiere <dm...@gmail.com> on 2017/10/23 20:48:15 UTC

Jenkinsfile changes not getting used by Jenkins?

Chris, I’ve made a change to the Jenkinsfile and committed to PR-309 but when Jenkins runs the build it doesn’t seem to be using that version of the file.  It also doesn’t seem to be using the ${mavenLocalRepo} stuff in the Jenkinsfile, and the “echo” cmds in the Jenkinsfile don’t seem to be getting captured in the output???

I expected to see “—fail-at-end -Dmaven.repo.local=.repository” before the “-Pplatform-android…” below (and where’s the “-f pom.xml” coming from?)

e.g., from the plain text output https://builds.apache.org/view/E-G/view/Edgent/job/edgent-dev/108/consoleText <https://builds.apache.org/view/E-G/view/Edgent/job/edgent-dev/108/consoleText>

Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on beam8 (beam) in workspace /home/jenkins/jenkins-slave/workspace/edgent-dev
...
[edgent-dev] $ /home/jenkins/tools/maven/apache-maven-3.5.0/bin/mvn -f pom.xml -Pplatform-android,platform-java7,distribution,toolchain -Djava8.home=/home/jenkins/tools/java/latest1.8/ -Dedgent.build.ci=true clean install sonar:sonar site:site