Here's a snippet from the console log. The gradle build is run from within a Docker container using the Docker pipeline plugin.
Download https:Download https:Download https:Download https:Download https:[Pipeline] }
[Pipeline] [Pipeline] }
[Pipeline] [Pipeline] }
$ docker stop --time=1 bc401b3124b5997f5c8a254b525737b1629050fb9058ba2e68741a5d4ee14a2e
[Pipeline] [Pipeline] }
[Pipeline] [Pipeline] }
[Pipeline] [Pipeline] End of Pipeline
hudson.model.Run$RunnerAbortedException
at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe(ArtifactoryGradleBuild.java:193)
at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:119)
at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.run(ArtifactoryGradleBuild.java:80)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
at hudson.security.ACL.impersonate(ACL.java:290)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Finished: FAILURE
When we change the job to publish using Gradle directly instead of the plugin, we get an error from Gradle itself telling us what the problem is, namely that it's looking for a JAR file that doesn't exist:
> Task :bootJar
> Task :jar SKIPPED
> Task :assemble
> Task :check
> Task :build
> Task :uploadArchives FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':uploadArchives'.
> Could not publish configuration 'archives'
> Cannot publish artifact 'sanitized.jar' (/path/to/sanitized.jar) as it does not exist.
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https:
BUILD FAILED in 2m 37s
5 actionable tasks: 4 executed, 1 up-to-date
Here's a snippet from the console log. The gradle build is run from within a Docker container using the Docker pipeline plugin.
When we change the job to publish using Gradle directly instead of the plugin, we get an error from Gradle itself telling us what the problem is, namely that it's looking for a JAR file that doesn't exist: