Skip to content

Instantly share code, notes, and snippets.

@WeldJenkins
Created October 14, 2020 07:26
Show Gist options
  • Save WeldJenkins/3aa55e63a16b0888874db6cb9fda21dc to your computer and use it in GitHub Desktop.
Save WeldJenkins/3aa55e63a16b0888874db6cb9fda21dc to your computer and use it in GitHub Desktop.
GitHub pull request #2164 of commit e92de8ec51acdd11f37cbcff00777c59e37f0e2e, no merge conflicts.
Setting status of e92de8ec51acdd11f37cbcff00777c59e37f0e2e to PENDING with url https://weld-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Weld-pull-request-executor-jdk11/808/ and message: 'Build started for merge commit.'
Using context: Weld CI - JDK 11
[EnvInject] - Loading node environment variables.
Building remotely on Dedicated PR Executor-4397 (static RHEL_pull_request) in workspace /mnt/hudson_workspace/workspace/Weld-pull-request-executor-jdk11
No credentials specified
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://github.com/weld/core.git # timeout=10
Fetching upstream changes from https://github.com/weld/core.git
> git --version # timeout=10
> git fetch --tags --progress -- https://github.com/weld/core.git +refs/pull/*:refs/remotes/origin/pr/*
> git rev-parse refs/remotes/origin/pr/2164/merge^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/pr/2164/merge^{commit} # timeout=10
Checking out Revision 14dda2a9213ddad56036819adb52e4b7b16f4123 (refs/remotes/origin/pr/2164/merge)
> git config core.sparsecheckout # timeout=10
> git checkout -f 14dda2a9213ddad56036819adb52e4b7b16f4123
Commit message: "Merge e92de8ec51acdd11f37cbcff00777c59e37f0e2e into 733cf6d2154194ab761fefcda2d37611ffaf89f8"
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[Weld-pull-request-executor-jdk11] $ bash -xe /tmp/jenkins3499539514718996476.sh
+ source /home/hudson/weld-jenkins/scripts/common-osprey.sh
/tmp/jenkins3499539514718996476.sh: line 2: /home/hudson/weld-jenkins/scripts/common-osprey.sh: No such file or directory
Build step 'Execute shell' marked build as failure
Archiving artifacts
[PostBuildScript] - Executing post build scripts.
[Weld-pull-request-executor-jdk11] $ bash -xe /tmp/jenkins1979032192372965763.sh
+ touch ./variables.properties
+ echo -e 'BUILD_LOG_URL=https://weld-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Weld-pull-request-executor-jdk11/808/\n'
+ echo -e 'PR_SHA=e92de8ec51acdd11f37cbcff00777c59e37f0e2e\n'
+ echo -e 'JDK=11\n'
[Current build status] check if current [FAILURE] is worse or equals then [SUCCESS] and better or equals then [SUCCESS]
Run condition [Current build status] preventing perform for step [Execute shell]
[Current build status] check if current [FAILURE] is worse or equals then [FAILURE] and better or equals then [FAILURE]
Run condition [Current build status] enabling perform for step [Execute shell]
[Weld-pull-request-executor-jdk11] $ bash -xe /tmp/jenkins5359487804858394491.sh
+ echo -e 'BUILD_STATUS=failure\n'
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Setting status of e92de8ec51acdd11f37cbcff00777c59e37f0e2e to FAILURE with url https://weld-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Weld-pull-request-executor-jdk11/808/ and message: 'Build finished. '
Using context: Weld CI - JDK 11
Returning node parameter for Dedicated PR Executor-4397
Triggering a new build of Weld-pull-request-updater
Finished: FAILURE
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment