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

Xcode Plugin fails to generate unit test report on macOS Catalina: JAXB-API issue

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • xcode-plugin
    • None
    • Jenkins 2.280
      Xcode-Plugin 2.0.14
      Xcode 12.4, Build version 12D4e
      macOS 10.15.7 Catalina
      java openjdk version "11.0.9" 2020-10-20
    • 2.0.17-565.v1c48051d46ef

      When I execute unit test in Xcode job, the test runs correctly, but the report generator fails to create the xml:

      Test Case '-[FooTests testBundle]' passed (0.001 seconds). Test Suite 'FooTests' passed at 2021-02-22 11:07:56.161.FATAL: Implementation of JAXB-API has not been found on module path or classpath.

        1. Xcode-PlugIn-Test-App.zip
          30 kB

          [JENKINS-64917] Xcode Plugin fails to generate unit test report on macOS Catalina: JAXB-API issue

          Francis Labrie created issue -
          Francis Labrie made changes -
          Description Original: When I execute unit test in Xcode job, the test runs correctly, but the report generator fails to create the xml:

          {{Test Case '-[FooTests testBundle]' passed (0.001 seconds). Test Suite '}}{{Foo}}{{Tests' passed at 2021-02-22 11:07:56.161.FATAL: Implementation of JAXB-API has not been found on module path or classpath. }}           		New: When I execute unit test in Xcode job, the test runs correctly, but the report generator fails to create the xml:

          {code}
          Test Case '-[FooTests testBundle]' passed (0.001 seconds). Test Suite 'FooTests' passed at 2021-02-22 11:07:56.161.FATAL: Implementation of JAXB-API has not been found on module path or classpath.
          {code}

          Francis Labrie added a comment - - edited

          Maybe the Xcode PlugIn just need to add the JAXB PlugIn dependancy, like described here: https://plugins.jenkins.io/jaxb/

          Francis Labrie added a comment - - edited Maybe the Xcode PlugIn just need to add the JAXB PlugIn dependancy, like described here:  https://plugins.jenkins.io/jaxb/
          Francis Labrie made changes -
          Link New: This issue is duplicated by JENKINS-62038 [ JENKINS-62038 ]
          Francis Labrie made changes -
          Assignee New: Kazuhide Takahashi [ kazuhidet ]

          Maximilian added a comment - - edited

          It's still not updated and blocking us from using Jenkins with the recommended version of Java 11.

          Simply adding the dependency for jaxb 2.3.0.1 leads to an error while compiling:
          "[WARNING] Rule 2: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:
          Found Banned Dependency: javax.xml.bind:jaxb-api:jar:2.3.0"

          Maximilian added a comment - - edited It's still not updated and blocking us from using Jenkins with the recommended version of Java 11. Simply adding the dependency for jaxb 2.3.0.1 leads to an error while compiling: " [WARNING] Rule 2: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message: Found Banned Dependency: javax.xml.bind:jaxb-api:jar:2.3.0"

          Francis Labrie added a comment - - edited

          We still have this issue using Jenkins 2.321, Xcode 13.1 and Xcode plugin 2.0.15 on macOS 11.6.1.

          This is a blocker, can it be fixed quickly, please? Thanks!

          Francis Labrie added a comment - - edited We still have this issue using Jenkins 2.321, Xcode 13.1 and Xcode plugin 2.0.15 on macOS 11.6.1. This is a blocker, can it be fixed quickly, please? Thanks!

          Mark Waite added a comment -

          flabrie as far as I can tell, there is no active development being done on the xcode plugin. I used the instructions from the DevOps World 2021 "Contributing to Open Source" workshop and made a few modernization improvements to the plugin in PR-112. I confirmed that the automated tests in the plugin repository all pass after my changes. I confirmed that I can build and test with Java 11.

          I do not have access to a macOS machine or an XCode development environment, so I have no way of knowing if the updates work when installed by a user.

          If you would like to try my changes, you could download the build from https://ci.jenkins.io/job/Plugins/job/xcode-plugin/job/PR-112/ and install it on your system. If it works, please provide feedback on PR-112.

          If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

          Mark Waite added a comment - flabrie as far as I can tell, there is no active development being done on the xcode plugin. I used the instructions from the DevOps World 2021 "Contributing to Open Source" workshop and made a few modernization improvements to the plugin in PR-112 . I confirmed that the automated tests in the plugin repository all pass after my changes. I confirmed that I can build and test with Java 11. I do not have access to a macOS machine or an XCode development environment, so I have no way of knowing if the updates work when installed by a user. If you would like to try my changes, you could download the build from https://ci.jenkins.io/job/Plugins/job/xcode-plugin/job/PR-112/ and install it on your system. If it works, please provide feedback on PR-112 . If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

          Francis Labrie added a comment -

          Thank you very much, markewaite, to work on this issue. It's very appreciated.

          Unfortunately, unit testing still fails with this PR-112: it seems the JAXB-API is not found.

          Test Case '-[CGIAccessManagerTests testServiceWithValidCredential]' passed (1.003 seconds).
Test Case '-[CGIAccessManagerTests testURL]' started.
Test Case '-[CGIAccessManagerTests testURL]' passed (0.001 seconds).
Test Suite 'CGIAccessManagerTests' passed at 2021-11-23 08:42:02.415.FATAL: Implementation of JAXB-API has not been found on module path or classpath.

          Francis Labrie added a comment - Thank you very much, markewaite , to work on this issue. It's very appreciated. Unfortunately, unit testing still fails with this PR-112: it seems the JAXB-API is not found. Test Case '-[CGIAccessManagerTests testServiceWithValidCredential]' passed (1.003 seconds). Test Case '-[CGIAccessManagerTests testURL]' started. Test Case '-[CGIAccessManagerTests testURL]' passed (0.001 seconds). Test Suite 'CGIAccessManagerTests' passed at 2021-11-23 08:42:02.415.FATAL: Implementation of JAXB-API has not been found on module path or classpath.

          Paul Jacobs added a comment -

          I also tried PR-112 and the JAXB-API issue is still there:
          Test Suite 'ADeviceSettingsTest' passed at 2022-04-25 13:31:35.892.FATAL: Implementation of JAXB-API has not been found on module path or classpath.

          Paul Jacobs added a comment - I also tried PR-112 and the JAXB-API issue is still there: Test Suite 'ADeviceSettingsTest' passed at 2022-04-25 13:31:35.892.FATAL: Implementation of JAXB-API has not been found on module path or classpath.

            kazuhidet Kazuhide Takahashi
            flabrie Francis Labrie
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: