[JIRA] (JENKINS-56239) Gradle cache locked

[jed.jacobs@prudential.com (JIRA)]

Jed Jacobs created an issue

Jenkins / JENKINS-56239 Gradle cache locked Issue Type: Bug Assignee: Stefan Wolf Attachments: log Components: gradle-plugin Created: 2019-02-21 21:18 Environment: Jenkins 2.150.2 Gradle Plugin version 1.28 Gradle version 4.2.1 on Linux server Priority: Major Reporter: Jed Jacobs Locks are not being released on the Gradle cache so other jobs are failing waiting for the locks to be released. Debug message from Jenkins log:  [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] The file lock is held by a different Gradle process (pid: 3265, operation: ). Will attempt to ping owner at port 42238   The lock file is not being deleted after builds complete. Full log attached. Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[stefan.wolf.phd@gmail.com (JIRA)]

Stefan Wolf commented on JENKINS-56239

Re: Gradle cache locked Jed Jacobs: I don't think this has anything to do with the Gradle plugin. This is an issue with Gradle or the usage of Gradle. Do you have two Gradle build run in parallel on the same machine? Do your Gradle builds share the same user home? What is the other process which is noted in the log doing?

Add Comment

[jed.jacobs@prudential.com (JIRA)]

Jed Jacobs commented on JENKINS-56239

Re: Gradle cache locked Hi Stefan.  We have more than one build on the same machine but they were not running concurrently. The Gradle builds all run with the same account so yes, they share the same user home and Gradle cache then, by default. The only other process is the git plugin get the files from BitBucket. I should mention, this is a scripted pipeline.

Add Comment

[jed.jacobs@prudential.com (JIRA)]

Jed Jacobs updated an issue

Jenkins / JENKINS-56239 Gradle cache locked

Change By: Jed Jacobs Priority: Major Trivial

Add Comment

[jed.jacobs@prudential.com (JIRA)]

Jed Jacobs updated JENKINS-56239

Issue not caused by the Gradle Plugin.  We found a rogue process on the server that had not released locks on over 1000 dependencies.  Killing the process and deleting the locks resolved the issue.

Jenkins / JENKINS-56239 Gradle cache locked

Change By: Jed Jacobs Status: Open Fixed but Unreleased Assignee: Stefan Wolf Resolution: Not A Defect

Add Comment

[stefan.wolf.phd@gmail.com (JIRA)]

Stefan Wolf updated JENKINS-56239

Jenkins / JENKINS-56239 Gradle cache locked

Change By: Stefan Wolf Status: Fixed but Unreleased Closed

Add Comment

[jed.jacobs@prudential.com (JIRA)]

Jed Jacobs updated an issue

Jenkins / JENKINS-56239 Gradle cache locked

Change By: Jed Jacobs Attachment: log

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)