-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 2.346.2
subversion-plugin 2.16.0
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works.
Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior.
---
It was a time skew in SVN server.
[JENKINS-69295] SVN fresh checkout stopped to work
Description |
Original:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` to test, but no changes on behavior. |
New:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. |
Description |
Original:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. |
New:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. --- Log snippet: {code:java} Cleaning local Directory . Checking out https://svn.../trunk at revision '2022-08-11T14:08:40.596 -0300' Using sole credentials ... in realm ‘<https://svn..> Subversion Repository’ A ... ... U . At revision 8200 {code} Expected revision is: *8201* |
Description |
Original:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. --- Log snippet: {code:java} Cleaning local Directory . Checking out https://svn.../trunk at revision '2022-08-11T14:08:40.596 -0300' Using sole credentials ... in realm ‘<https://svn..> Subversion Repository’ A ... ... U . At revision 8200 {code} Expected revision is: *8201* |
New:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. --- Log snippet: {code:java} Cleaning local Directory . Checking out https://svn.../trunk at revision '2022-08-11T14:08:40.596 -0300' Using sole credentials ... in realm ‘<https://svn..> Subversion Repository’ A ... ... U . At revision 8200 {code} Expected revision is: *8201* Checking on SVN history: * Revision 8200: 2022-08-11T13:53:... * Revision 8201: 2022-08-11T14:08... |
Description |
Original:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. --- Log snippet: {code:java} Cleaning local Directory . Checking out https://svn.../trunk at revision '2022-08-11T14:08:40.596 -0300' Using sole credentials ... in realm ‘<https://svn..> Subversion Repository’ A ... ... U . At revision 8200 {code} Expected revision is: *8201* Checking on SVN history: * Revision 8200: 2022-08-11T13:53:... * Revision 8201: 2022-08-11T14:08... |
New:
We have a pipeline that uses subversion-plugin to do checkout.
This pipeline worked flawless until last week, when it just stopped to do a fresh checkout, and it always get history one revision behind. One example is, if a tag is created Jenkins pipeline will blame that the path doesn't exist, so we just do a replay and it works. Pipeline config was using `workspaceUpdater` with `UpdateWithCleanUpdater`, so we changed it to `UpdateWithRevertUpdater` and to `CheckoutUpdater` implementations to test, but no changes on behavior. --- It was a time skew in SVN server. |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Fixed but Unreleased [ 10203 ] |
Status | Original: Fixed but Unreleased [ 10203 ] | New: Closed [ 6 ] |