-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to create cache java.lang.InterruptedException #334
Comments
@dragenet it seems that the exception is thrown exactly after 5 minutes, according to the log of my job. However, I could not find where the timeout is set. |
Not on this plugin for sure It's cause by There is an hardcoded timeout for CPS Thread : https://github.com/jenkinsci/workflow-cps-plugin/blob/5b32b1a2e5b83a23354bbc147037cbdbc9d9061f/plugin/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThread.java#L176 Normally for long operation (like 'sh') Jenkins use the durable task. But for other step there seems to have this hardcoded timeout. I don't know if we can bypass it to be honnest. Probably the plugin need to implement in some way: https://github.com/jenkinsci/durable-task-plugin to allow the I never did anything like this to be honnest, so if anyone want to give some helps, I'm more than happy to review any pull request |
Similar error here: jenkinsci/bom#4351 (comment) |
@jglick got any advice on a good approach here? |
Hmm its already using that: jobcacher-plugin/src/main/java/jenkins/plugins/jobcacher/pipeline/CacheStepExecution.java Line 18 in 1b30b69
but its times out at 5 mins. |
edit hmm not sure I think maybe not |
I believe the issue is not the |
Actually is it even documented to be used like this: Initiate background work that should not block the CPS VM thread. Call this from a CPS VM thread, such as from start or BodyExecutionCallback. onSuccess |
I created a commit with this change. Probably it would make sense to checkout the implementation of |
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
I'm using Jenkins on Kubernetes:
Reproduction steps
Expected Results
Cache created
Actual Results
Anything else?
It happens not for each execution but often no matter which compression implementation was selected
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: