JFrog JIRA | Gal Raif | 3 months ago
Click on the to mark the solution that helps you, Samebug will learn from it.
As a community member, you’ll be rewarded for you help.
  1. 0

    To reproduce Jenkins's UI bug: 1. Go to "Global Tool Configuration" 2. In "Gradle" or "Maven" or "Ant" section, choose a name and Path to the HOME and press save. 3. Edit the above section. remove the path to the HOME and check "Install automatically" Result: The install version from X is not presented. This bug cause an issue when we running a job with remote agent (maybe it reproduced without remote agent). {code} Started by user admin [Pipeline] node Running on ubuntu-agent in /home/jfrog/jenkins-agent/workspace/gradle-example-pipeline [Pipeline] { [Pipeline] newArtifactoryServer [Pipeline] newGradleBuild [Pipeline] stage (Build) Using the ‘stage’ step without a block argument is deprecated Entering stage Build Proceeding [Pipeline] git > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url # timeout=10 Fetching upstream changes from > git --version # timeout=10 > git fetch --tags --progress +refs/heads/*:refs/remotes/origin/* > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 Checking out Revision 2ae1f9257afeaca893edee6c0868f2c87a75028f (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 2ae1f9257afeaca893edee6c0868f2c87a75028f > git branch -a -v --no-abbrev # timeout=10 > git branch -D master # timeout=10 > git checkout -b master 2ae1f9257afeaca893edee6c0868f2c87a75028f > git rev-list 2ae1f9257afeaca893edee6c0868f2c87a75028f # timeout=10 [Pipeline] stage (Artifactory configuration) Using the ‘stage’ step without a block argument is deprecated Entering stage Artifactory configuration Proceeding [Pipeline] withEnv [Pipeline] { [Pipeline] stage (Config Build Info) Using the ‘stage’ step without a block argument is deprecated Entering stage Config Build Info Proceeding [Pipeline] newBuildInfo [Pipeline] stage (Extra gradle configurations) Using the ‘stage’ step without a block argument is deprecated Entering stage Extra gradle configurations Proceeding [Pipeline] stage (Exec Gradle) Using the ‘stage’ step without a block argument is deprecated Entering stage Exec Gradle Proceeding [Pipeline] ArtifactoryGradleBuild ERROR: Gradle tool = T3 ERROR: In else gi is not null. ERROR: working on node: ubuntu-agent ERROR: ******************** ERROR: GradleInstallation[T3] ERROR: ******************** ERROR: T3 ERROR: GRADLE_HOME = ERROR: ARGS = ERROR: ARGS T0String = [gradle-example] $ clean artifactoryPublish -b build.gradle ERROR: Couldn't execute gradle task. Cannot run program "clean" (in directory "/home/jfrog/jenkins-agent/workspace/gradle-example-pipeline/gradle-examples/4/gradle-example"): error=2, No such file or directory [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline hudson.model.Run$RunnerAbortedException at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe( at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$ at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$ at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$ at at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$ at java.util.concurrent.Executors$ at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Finished: FAILURE {code} I reproduced this issue with Jenkinsfile from project-examples/jenkins-pipeline-examples/gradle-example/

    JFrog JIRA | 3 months ago | Gal Raif
  2. 0

    Jenkins + Gradle + Artifactory: Couldn't read generated build info

    Stack Overflow | 5 months ago | frinux
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    [JIRA] (JENKINS-41277) can't upload artifacts to artifactory

    Google Groups | 3 months ago | (JIRA) remote file operation failed: /opt/jenkins/workspace/gs-test-arti-upload/some at hudson.remoting.Channel@175e9603:linux_x86: Remote call on linux_x86 failed

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. hudson.model.Run$RunnerAbortedException

      No message provided

      at org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe()
    2. org.jfrog.hudson
      1. org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$Execution.exe(
      2. org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$
      3. org.jfrog.hudson.pipeline.steps.ArtifactoryGradleBuild$
      3 frames
    3. org.jenkinsci.plugins
      1. org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$
      1 frame
    4. Hudson
      1 frame
    5. org.jenkinsci.plugins
      1. org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$
      1 frame
    6. Java RT
      1. java.util.concurrent.Executors$
      3. java.util.concurrent.ThreadPoolExecutor.runWorker(
      4. java.util.concurrent.ThreadPoolExecutor$
      5 frames