Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53140

Intermittent Random Stage Failures - No Changes Detected - Parallel Stages

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

      We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 

      Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml

      If you click the Stage Log it says: 

      No changes for <my_scm_url> since the previous build`

      This can happen when the build is triggered by either of the following means:

      • From an upstream job
      • Manually by clicking "build now"

       

      Of note, we use SVN as our SCM with the following configuration:

      We use "Jenkinsfile from SCM", using URL like

      http://myserver/myrepo/_automation

      In the GUI, we do not configure SCM polling 

      In the Jenkinsfile, we configure SCM polling, every 2 minutes

      In the Jenkinsfile, we configure SCM checkout of 

      http://myserver/myrepo`|http://myserver/myrepo

       

      The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

      For each SCM polling period, the Subversion Polling Log show approximately multiple entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

      http://myserver/myrepo

      and 

      http://myserver/myrepo/_automation

      Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 entry checking

      http://myserver/myrepo/_automation

      for changes for each stage in the build for the ". So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries" for

      http://myserver/myrepo/_automation

      . Not sure if this is by design or not.

       

       

       

       

       

      We have the latest versions of all plugins. 

        Attachments

          Issue Links

            Activity

            solvingj jerry wiltse created issue -
            solvingj jerry wiltse made changes -
            Field Original Value New Value
            Description On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 

            `Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml`

            If you click the Stage Log it says: 

            `No changes for <my_scm_url> since the previous build`

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like `http://myserver/myrepo/_automation`

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  `[http://myserver/myrepo`|http://myserver/myrepo]

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately 4-8 entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            `http://myserver/myrepo` and  `http://myserver/myrepo/_automation`

             

             

             

             

             

            We have the latest versions of all plugins. 
            On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 
            {code:java}
            Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}
            If you click the Stage Log it says: 

            {code:java}No changes for <my_scm_url> since the previous build`{code}

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  {code:java}http://myserver/myrepo`|http://myserver/myrepo{code}

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately 4-8 entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            {code:java}http://myserver/myrepo{code} and  http://myserver/myrepo/_automation{code}

             

             

             

             

             

            We have the latest versions of all plugins. 
            solvingj jerry wiltse made changes -
            Description On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 
            {code:java}
            Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}
            If you click the Stage Log it says: 

            {code:java}No changes for <my_scm_url> since the previous build`{code}

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  {code:java}http://myserver/myrepo`|http://myserver/myrepo{code}

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately 4-8 entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            {code:java}http://myserver/myrepo{code} and  http://myserver/myrepo/_automation{code}

             

             

             

             

             

            We have the latest versions of all plugins. 
            On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 
            {code:java}
            Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}
            If you click the Stage Log it says: 

            {code:java}No changes for <my_scm_url> since the previous build`{code}

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  {code:java}http://myserver/myrepo`|http://myserver/myrepo{code}

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately multiple entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            {code:java}http://myserver/myrepo{code} and  http://myserver/myrepo/_automation{code}

            Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 for each stage in the build. So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries". Not sure if this is by design or not.


             

             

             

             

             

            We have the latest versions of all plugins. 
            solvingj jerry wiltse made changes -
            Description On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 
            {code:java}
            Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}
            If you click the Stage Log it says: 

            {code:java}No changes for <my_scm_url> since the previous build`{code}

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  {code:java}http://myserver/myrepo`|http://myserver/myrepo{code}

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately multiple entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            {code:java}http://myserver/myrepo{code} and  http://myserver/myrepo/_automation{code}

            Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 for each stage in the build. So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries". Not sure if this is by design or not.


             

             

             

             

             

            We have the latest versions of all plugins. 
            On a new Jenkins server, we're setting up new Jenkinsfiles from scratch.  We're using parallel stages, which seems like it might be a factor based on searches for related issues. 

            We have about 15 of these jobs with 4 parallel stages.  For about 1 in 10 jobs, a stage will randomly fail in 1 second or less.  If you hover over the stage it shows: 
            {code:java}
            Failed to parse /var/lib/jenkins/jobs/MyOrg/jobs/Projects/jobs/myProject/builds/252/changelog3.xml{code}
            If you click the Stage Log it says: 

            {code:java}No changes for <my_scm_url> since the previous build`{code}

            This can happen when the build is triggered by either of the following means:
             * From an upstream job
             * Manually by clicking "build now"

             

            Of note, we use SVN as our SCM with the following configuration:

            We use "Jenkinsfile from SCM", using URL like {code:java}http://myserver/myrepo/_automation{code}

            In the GUI, we do not configure SCM polling 

            In the Jenkinsfile, we configure SCM polling, every 2 minutes

            In the Jenkinsfile, we configure SCM checkout of  {code:java}http://myserver/myrepo`|http://myserver/myrepo{code}

             

            The reason I include our SVN/SCM backstory is because we're also seeing another anomaly related to SCM which might be relevant. . 

            For each SCM polling period, the Subversion Polling Log show approximately multiple entries all at the same timestamp.   These entries are some randomized mix of polling the two relevant URL's :

            {code:java}http://myserver/myrepo{code} and  {code:java}http://myserver/myrepo/_automation{code}

            Interestingly, we've figured something out about these duplicate "Subversion Polling Entries" . There is 1 entry checking {code:java}http://myserver/myrepo/_automation{code} for changes for each stage in the build for the ". So, if we have 1 "Checkout Stage", 1 "Parallel Stages" block, and 3 "Parallel Stages", we see 5 total "Subversion Polling Entries" for {code:java}http://myserver/myrepo/_automation{code}. Not sure if this is by design or not.


             

             

             

             

             

            We have the latest versions of all plugins. 
            solvingj jerry wiltse made changes -
            abayer Andrew Bayer made changes -
            Component/s subversion-plugin [ 15485 ]
            Component/s pipeline [ 21692 ]
            abayer Andrew Bayer made changes -
            Link This issue relates to JENKINS-34313 [ JENKINS-34313 ]
            solvingj jerry wiltse made changes -
            Link This issue duplicates JENKINS-34313 [ JENKINS-34313 ]
            solvingj jerry wiltse made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Fixed but Unreleased [ 10203 ]

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              solvingj jerry wiltse
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: