[JIRA] (JENKINS-60015) Sporadic failure recoding revisions of previous build

[jenk...@mockies.de (JIRA)]

Title: Message Title

Christoph Vogtländer created an issue   Jenkins / JENKINS-60015 Sporadic failure recoding revisions of previous build Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: pipeline, subversion-plugin Created: 2019-11-01 10:11 Environment: Jenkins ver. 2.190.1 Pipeline: SCM Step 2.9 Subversion Plug-in 2.12.2 Priority: Major Reporter: Christoph Vogtländer Sometimes a build is not able to create a changelog because the previous build did not record any revisions. A Subversion post-commit hook is used to trigger the build. I use the "checkout" step with "poll: true" and "changelog: true" on one of the nodes. Normally, the polling log states something like: Started on Nov 1, 2019 9:06:07 AM no polling baseline in D:\Jenkins\jobs\JOB\jobs\trunk\jobs\CI\workspace@libs\sharedLibs on Received SCM poll call on master for CI on Nov 1, 2019 9:06:07 AM Using sole credentials jenkins/****** (<https://server:443> VisualSVN Server) in realm ‘<https://server:443> VisualSVN Server’ https://server/svn/JenkinsWorkflow/JOB/trunk is at revision 971 Received SCM poll call on master for CI on Nov 1, 2019 9:06:07 AM Found credentials jenkins/****** (<https://server:443> VisualSVN Server) in realm ‘<https://server:443> VisualSVN Server’ https://server/svn/Repo/trunk/Project is at revision 33,308 ... Done. Took 8.2 sec Changes found Sporadically, this fails with: Started on Nov 1, 2019 9:08:05 AM no polling baseline in D:\Jenkins\jobs\JOB\jobs\trunk\jobs\CI\workspace@libs\sharedLibs on Received SCM poll call on master for CI on Nov 1, 2019 9:08:05 AM Using sole credentials jenkins/****** (<https://server:443> VisualSVN Server) in realm ‘<https://server:443> VisualSVN Server’ https://server/svn/JenkinsWorkflow/JOB/trunk is at revision 971 Workspace doesn't contain https://server/svn/Repo/Project/trunk. Need a new build. Workspace doesn't contain https://server/svn/Repo/Project/trunk. Need a new build. Workspace doesn't contain https://server/svn/Repo/Project/trunk. Need a new build. Done. Took 36 ms Changes found Note that there is no second "Received SCM poll call on master for CI" in the second, failing, log. I don't know where this comes from, the SVN post-commit hook only sends the commit notification once. The node that holds the working copy that is used for creating the changelog and for polling is not "master" but another windows agent. During the build, the checkout step normally states: Updating https://server/svn/Repo/Project/trunk@HEAD at revision HEAD --quiet ... No changes for https://sssdesvn/svn/Repo/Project/trunk since the previous build (is it normal that no changes can be seen here? Because the poll already updated the working copy?) In case the polling failed, the checkout step reports: Updating https://server/svn/Repo/Project/trunk@HEAD at revision HEAD --quiet ... No revision recorded for https://sssdesvn/svn/Repo/Project/trunk in the previous build As already said, this is sporadically. About 1 out of 10 builds. But, sometimes 3 builds in a row will fail to record a changelog. I don't see any differences between the commits that could be causing this. During the tests I did the exact same commits (commit -> revert -> commit -> ...) and most of the time creating the changelog/polling works but fails eventually. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202837.1572603091000.6734.1572603120298%40Atlassian.JIRA.