-
Notifications
You must be signed in to change notification settings - Fork 247
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
fix(ci)_: skip windows build cleanup stage #6003
Conversation
Jenkins BuildsClick to see older builds (39)
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #6003 +/- ##
===========================================
+ Coverage 60.57% 60.62% +0.04%
===========================================
Files 812 812
Lines 109328 109328
===========================================
+ Hits 66230 66275 +45
+ Misses 35337 35295 -42
+ Partials 7761 7758 -3
Flags with carried forward coverage won't be shown. Click here to find out more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you actually trying using LAUNCH_DIAGNOSTICS=true
as the error suggests?
25020e0
to
5a568e2
Compare
0a7e54b
to
88cdbe0
Compare
Windows build pipeline has errors while running: ```sh sh "rm -rf ${env.WORKSPACE}@tmp" ``` In cleanup stage: ```groovy process apparently never started in J:/Users/jenkins/workspace/_prs_windows_x86_64_main_PR-5990@tmp/durable-478fb71e (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) ``` Related with [Durable Task Plugin](https://plugins.jenkins.io/durable-task/). Signed-off-by: Jakub Sokołowski <[email protected]>
88cdbe0
to
c08e922
Compare
Windows build pipeline has errors while running:
sh "rm -rf ${env.WORKSPACE}@tmp"
In cleanup stage:
Related with Durable Task Plugin.
Quick fix would be skipping this stage on Windows due to
tmp
folder being empty, as they should be at the end of the pipeline.Opting only for
as post cleanup step.