Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1964

Incrementals generation and deployment failing

    Details

    • Similar Issues:

      Description

      Whenever a new Jenkins Infrastructure CI build of pull-requests of either of the following is run:

      An incremental build version and artifact fails to generate. This is observed as an "Internal Server Error" during the "deploy" phase of the CI build.

       

      Examples of this CI build-'server error' observed are found in the attached 'Server Error Example' links.

      In the linked examples of pull requests to Jenkins-core, at the time of starting those CI builds, their branches were up-to-date with the Jenkins base branch. Yet an incremental version (and its artifacts) of Jenkins still failed to be generated by the Azure incremental-deployment/publisher server.

        Attachments

          Activity

          Hide
          jvz Matt Sicker added a comment -

          I'll note that this seems to be failing due to the automatic Maven module "jenkins-test-jdk8" which is only activated for Java 8. A PR to clean up some deprecated remoting over CLI code will remove the need for that automatic Maven module which may end up fixing this particular issue for now: https://github.com/jenkinsci/jenkins/pull/3838

          Show
          jvz Matt Sicker added a comment - I'll note that this seems to be failing due to the automatic Maven module "jenkins-test-jdk8" which is only activated for Java 8. A PR to clean up some deprecated remoting over CLI code will remove the need for that automatic Maven module which may end up fixing this particular issue for now: https://github.com/jenkinsci/jenkins/pull/3838
          Hide
          batmat Baptiste Mathus added a comment -

          I confirm this really looks like this issue got introduced with https://github.com/jenkinsci/jenkins/pull/3759.

          Any hint what would be happening Jesse Glick? Do we have any way to get more logs than the current HTTP 500 we see? Thanks

          Show
          batmat Baptiste Mathus added a comment - I confirm this really looks like this issue got introduced with https://github.com/jenkinsci/jenkins/pull/3759 . Any hint what would be happening Jesse Glick ? Do we have any way to get more logs than the current HTTP 500 we see? Thanks
          Hide
          jglick Jesse Glick added a comment -

          Those console links are dead now (I guess since PRs have been merged and the orphaned item strategy kicks in). This however does show it.

          I note that  build artifacts include some JARs from test modules, which is senseless, I think because this was not updated with an extra * wildcard, though AFAIK those artifacts ought to be harmless. Of course my proposed removal of Remoting-based CLI would also suffice.

          The only way to get at the details behind the 500 errors is to look at the Azure Functions logs directly. I do not have access to those. R. Tyler Croy at least used to. Olivier Vernin do you? For security reasons, the function currently sends back detailed messages in HTTP responses only in cases of known expected issues.

          Show
          jglick Jesse Glick added a comment - Those console links are dead now (I guess since PRs have been merged and the orphaned item strategy kicks in). This however does show it. I note that   build artifacts include some JARs from test modules, which is senseless, I think because this was not updated with an extra * wildcard, though AFAIK those artifacts ought to be harmless. Of course my proposed removal of Remoting-based CLI would also suffice. The only way to get at the details behind the 500 errors is to look at the Azure Functions logs directly. I do not have access to those. R. Tyler Croy at least used to. Olivier Vernin do you? For security reasons, the function currently sends back detailed messages in HTTP responses only in cases of known expected issues.
          Hide
          jglick Jesse Glick added a comment -

          Baptiste Mathus claims this is fixed at least for Jenkins core. Is there still a problem somewhere?

          Show
          jglick Jesse Glick added a comment - Baptiste Mathus claims this is fixed at least for Jenkins core. Is there still a problem somewhere?
          Hide
          mide David Olorundare added a comment - - edited

          I've confirmed incrementals is working now for our plugin.

          Example here- https://github.com/jenkinsci/audit-log-plugin/pull/15

           

          Hence, will be closing this Jira issue.

          Show
          mide David Olorundare added a comment - - edited I've confirmed incrementals is working now for our plugin. Example here- https://github.com/jenkinsci/audit-log-plugin/pull/15   Hence, will be closing this Jira issue.
          Hide
          mide David Olorundare added a comment -

          Incrementals is now working.

          Show
          mide David Olorundare added a comment - Incrementals is now working.

            People

            • Assignee:
              rtyler R. Tyler Croy
              Reporter:
              mide David Olorundare
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: