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

Fix random JCasC build failures on ci.jenkins.io

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      There are random build failures for CasC main project. We should understand/fix this.

        Attachments

          Activity

          Hide
          batmat Baptiste Mathus added a comment -
          15:55:51 [INFO] 
          15:55:51 [INFO] -----------< io.jenkins.configuration-as-code:integrations >------------
          15:55:51 [INFO] Building Configuration as Code Integration tests 1.1-rc507.df56469e0d56 [6/5]
          15:55:51 [INFO] --------------------------------[ jar ]---------------------------------
          16:00:13 [INFO] 
          16:00:13 [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ integrations ---
          16:00:13 [INFO] 
          16:00:13 [INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ integrations ---
          16:00:13 [INFO] Maven Version: 3.5.4
          16:00:13 [INFO] JDK Version: 1.8.0_162 normalized as: 1.8.0-162
          16:00:13 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 4.15.0-1023-azure
          16:00:13 [INFO] 
          16:00:13 [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ integrations ---
          16:00:13 [INFO] artifact junit:junit-dep: checking for updates from azure-incrementals
          16:00:13 [INFO] artifact junit:junit-dep: checking for updates from azure
          16:00:13 [INFO] artifact junit:junit-dep: checking for updates from central
          16:53:44 Sending interrupt signal to process
          16:53:46 Sending interrupt signal to process
          16:53:53 Terminated
          

          So it seems like it's failing during enforcer plugin step. For some reason, it gets stuck forever. Need to understand what it's doing.

          I've checked many failures on the master branch, and it always seems to be coming from this.

          Show
          batmat Baptiste Mathus added a comment - 15:55:51 [INFO] 15:55:51 [INFO] -----------< io.jenkins.configuration-as-code:integrations >------------ 15:55:51 [INFO] Building Configuration as Code Integration tests 1.1-rc507.df56469e0d56 [6/5] 15:55:51 [INFO] --------------------------------[ jar ]--------------------------------- 16:00:13 [INFO] 16:00:13 [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ integrations --- 16:00:13 [INFO] 16:00:13 [INFO] --- maven-enforcer-plugin:3.0.0-M1:display-info (display-info) @ integrations --- 16:00:13 [INFO] Maven Version: 3.5.4 16:00:13 [INFO] JDK Version: 1.8.0_162 normalized as: 1.8.0-162 16:00:13 [INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 4.15.0-1023-azure 16:00:13 [INFO] 16:00:13 [INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ integrations --- 16:00:13 [INFO] artifact junit:junit-dep: checking for updates from azure-incrementals 16:00:13 [INFO] artifact junit:junit-dep: checking for updates from azure 16:00:13 [INFO] artifact junit:junit-dep: checking for updates from central 16:53:44 Sending interrupt signal to process 16:53:46 Sending interrupt signal to process 16:53:53 Terminated So it seems like it's failing during enforcer plugin step. For some reason, it gets stuck forever. Need to understand what it's doing. I've checked many failures on the master branch, and it always seems to be coming from this.

            People

            • Assignee:
              batmat Baptiste Mathus
              Reporter:
              batmat Baptiste Mathus
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: