Skip to content

Instantly share code, notes, and snippets.

@WeldJenkins
Created October 9, 2020 07:16
Show Gist options
  • Save WeldJenkins/a8e13571f25b68bf0070a4674f217d2d to your computer and use it in GitHub Desktop.
Save WeldJenkins/a8e13571f25b68bf0070a4674f217d2d to your computer and use it in GitHub Desktop.
GitHub pull request #2157 of commit 3606da76d7e688bfbf96da166497f63e91db4246, no merge conflicts.
Setting status of 3606da76d7e688bfbf96da166497f63e91db4246 to PENDING with url https://weld-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Weld-pull-request-executor-jdk11/802/ and message: 'Build started for merge commit.'
Using context: Weld CI - JDK 11
[EnvInject] - Loading node environment variables.
Building remotely on Dedicated PR Executor-4350 (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/2157/merge^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/pr/2157/merge^{commit} # timeout=10
Checking out Revision 307c1dae18ed56c5c44f1934c8eeb3cda9a39f32 (refs/remotes/origin/pr/2157/merge)
> git config core.sparsecheckout # timeout=10
> git checkout -f 307c1dae18ed56c5c44f1934c8eeb3cda9a39f32
Commit message: "Merge 3606da76d7e688bfbf96da166497f63e91db4246 into a285514e01f1c1f71fc84e7f7e7e1bc673bc7cde"
First time build. Skipping changelog.
[EnvInject] - Executing scripts and injecting environment variables after the SCM step.
[Weld-pull-request-executor-jdk11] $ bash -xe /tmp/jenkins4448769884120354152.sh
+ source /home/hudson/weld-jenkins/scripts/common-osprey.sh
/tmp/jenkins4448769884120354152.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/jenkins7087532555966690706.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/802/\n'
+ echo -e 'PR_SHA=3606da76d7e688bfbf96da166497f63e91db4246\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/jenkins4763374653304161090.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 3606da76d7e688bfbf96da166497f63e91db4246 to FAILURE with url https://weld-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/Weld-pull-request-executor-jdk11/802/ and message: 'Build finished. '
Using context: Weld CI - JDK 11
Returning node parameter for Dedicated PR Executor-4350
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