Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I don't know how to prove or discover this, but anyway. This error happens when Jenkins job is interrupted while the P4 plugin is doing what it calls "reconcile". A "reconcile" is a special form o...
Answer
#2: Post edited
- I don't know how to prove or discover this, but anyway.
- This error happens when Jenkins job is interrupted while the P4 plugin is doing what it calls "reconcile". A "reconcile" is a special form of downloading, which is supposed to do it faster and/or more cleanly.
- P4 plugin has several bugs related to "reconcile": [1](https://issues.jenkins.io/browse/JENKINS-60430), [2](https://issues.jenkins.io/browse/JENKINS-60447). They are probably not going to be fixed. A workaround is to never do "reconcile" but to delete all files and download them by force. The job settings-page calls this "Force Clean and Sync … (Inefficient and NOT RECOMENDED)".
- I don't know how to prove or discover this, but anyway.
- This error happens when Jenkins job is interrupted while the P4 plugin is doing what it calls "reconcile". A "reconcile" is a special form of downloading, which is supposed to do it faster and/or more cleanly.
- P4 plugin has several bugs related to "reconcile": [1](https://issues.jenkins.io/browse/JENKINS-60430), [2](https://issues.jenkins.io/browse/JENKINS-60447). They are probably not going to be fixed. A workaround is to never do "reconcile" but to delete all files and download them by force. The job settings-page calls this "Force Clean and Sync … (Inefficient and NOT RECOMENDED)".
- Either that or "never stop any running job" as a policy. The latter is unintuitive and hard to enforce; in our case, some compound jobs are configured to stop all sub-jobs if one of them fails.
#1: Initial revision
I don't know how to prove or discover this, but anyway. This error happens when Jenkins job is interrupted while the P4 plugin is doing what it calls "reconcile". A "reconcile" is a special form of downloading, which is supposed to do it faster and/or more cleanly. P4 plugin has several bugs related to "reconcile": [1](https://issues.jenkins.io/browse/JENKINS-60430), [2](https://issues.jenkins.io/browse/JENKINS-60447). They are probably not going to be fixed. A workaround is to never do "reconcile" but to delete all files and download them by force. The job settings-page calls this "Force Clean and Sync … (Inefficient and NOT RECOMENDED)".