grkvlt edited a comment on pull request #54:
URL: https://github.com/apache/brooklyn/pull/54#issuecomment-842311759


   The `master` build has the following output:
   ```
   Successfully tagged brooklyn:jenkins-Brooklyn-brooklyn-master-173
   [Pipeline] }
   [Pipeline] // stage
   [Pipeline] stage
   [Pipeline] { (Run tests)
   [Pipeline] isUnix
   [Pipeline] sh
   + docker inspect -f . brooklyn:jenkins-Brooklyn-brooklyn-master-173
   .
   [Pipeline] withDockerContainer
   H37 does not seem to be running inside a container
   $ docker run -t -d -u 910:910 -i --name brooklyn-${DOCKER_TAG} -v 
${WORKSPACE}/.m2:/var/maven/.m2 --mount 
type=bind,source=${HOME}/.m2/settings.xml,target=/var/maven/.m2/settings.xml,readonly
 -v ${WORKSPACE}:/usr/build -w /usr/build -w 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master -v 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master:rw,z
 -v 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master@tmp:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master@tmp:rw,z
 -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** 
brooklyn:${DOCKER_TAG} cat
   
   $ docker top 
1d835a9eedc718eecdd15d8af8dd8b88d90d9b305b3cce148380ee6f5ef26aa2 -eo pid,comm
   [Pipeline] {
   [Pipeline] sh
   + MAVEN_OPTS=-Xmx12g
   + mvn clean install -Prpm -Pdeb -Pclient -Duser.home=/var/maven 
-Duser.name=jenkins
   [INFO] Scanning for projects...
   ```
   And the pull request is the same, except the tag is different:
   ```
   Successfully tagged brooklyn:jenkins-Brooklyn-brooklyn-PR-52-4
   [Pipeline] }
   [Pipeline] // stage
   [Pipeline] stage
   [Pipeline] { (Run tests)
   [Pipeline] isUnix
   [Pipeline] sh
   + docker inspect -f . brooklyn:jenkins-Brooklyn-brooklyn-PR-52-4
   .
   [Pipeline] withDockerContainer
   H32 does not seem to be running inside a container
   $ docker run -t -d -u 910:910 -i --name brooklyn-${DOCKER_TAG} -v 
${WORKSPACE}/.m2:/var/maven/.m2 --mount 
type=bind,source=${HOME}/.m2/settings.xml,target=/var/maven/.m2/settings.xml,readonly
 -v ${WORKSPACE}:/usr/build -w /usr/build -w 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52 -v 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52:rw,z
 -v 
/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52@tmp:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52@tmp:rw,z
 -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e ******** -e 
******** -e ******** -e ******** -e ******** -e ******** -e **
 ****** -e ******** -e ******** -e ******** brooklyn:${DOCKER_TAG} cat
   $ docker top 
cb97726b257f834bde11a09a806b5fe5c49af3590d474da39cd649f89b55a0bc -eo pid,comm
   [Pipeline] {
   [Pipeline] sh
   + MAVEN_OPTS=-Xmx12g
   + mvn clean install -Prpm -Pdeb -Pclient -Duser.home=/var/maven 
-Duser.name=jenkins
   [INFO] Scanning for projects...
   ```
   Which is followed by much donloading of artifacts from Maven Central and the 
build then begins as with `master`.
   
   The console output can be seen for 
[`master`](https://ci-builds.apache.org/job/Brooklyn/job/brooklyn/job/master/173/consoleText)
 and [pull 
request](https://ci-builds.apache.org/job/Brooklyn/job/brooklyn/view/change-requests/job/PR-52/4/consoleText)
 so the difference may be down to the workspace contents here, or perhaps the 
Docker images since the `master` image is cached, but the pull-request image is 
built fresh each time...?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to