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

Could not initialize class com.hp.octane.integrations.OctaneSDK

XMLWordPrintable

      When the plugin is enabled on the latest jenkins/jenkins:lts-jdk11 image from Docker hub, it's breaking the Jenkins views with the following failure:

      The actual error is:

      2024-08-15 15:28:00.058+0000 [id=253]    SEVERE    h.triggers.SCMTrigger$Runner#runPolling: Failed to record SCM polling for org.jenkinsci.plugins.workflow.job.WorkflowJob@6830f7c4[<scrubbed for privacy>]
      java.lang.NoClassDefFoundError: Could not initialize class com.hp.octane.integrations.OctaneSDK
          at PluginClassLoader for hp-application-automation-tools-plugin//com.microfocus.application.automation.tools.octane.executor.CheckOutSubDirEnvContributor.buildEnvironmentFor(CheckOutSubDirEnvContributor.java:61)
          at hudson.model.Job.getEnvironment(Job.java:406)
          at hudson.model.Run.getEnvironment(Run.java:2427)
          at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowRun.getEnvironment(WorkflowRun.java:519)
          at PluginClassLoader for git//hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:713)
          at PluginClassLoader for git//hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:688)
          at PluginClassLoader for workflow-job//org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:631)
          at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:617)
          at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:664)
          at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:123)
          at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
          at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
          at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
          at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
          at java.base/java.lang.Thread.run(Unknown Source)

       

      Disabling the plugin fixes the instance.

        1. image-2024-08-15-18-28-36-951.png
          image-2024-08-15-18-28-36-951.png
          115 kB

          [JENKINS-73623] Could not initialize class com.hp.octane.integrations.OctaneSDK

          Mark Waite added a comment -

          I believe this will need the fixes that have been requested in JENKINS-72498

          Mark Waite added a comment - I believe this will need the fixes that have been requested in JENKINS-72498

          E added a comment -

          Spoke with ptofan  and he appears to be no longer the maintainer of the plugin. According to the info here https://plugins.jenkins.io/hp-application-automation-tools-plugin/ , the new maintainers are Andrei Bangau and buzas . I se that Laura already has a user here, could someone, please, update the default assignee for the reported bugs to her?

          Thank you!

          E added a comment - Spoke with ptofan   and he appears to be no longer the maintainer of the plugin. According to the info here https://plugins.jenkins.io/hp-application-automation-tools-plugin/ , the new maintainers are Andrei Bangau and buzas . I se that Laura already has a user here, could someone, please, update the default assignee for the reported bugs to her? Thank you!

          Mark Waite added a comment -

          I see that Laura already has a user here, could someone, please, update the default assignee for the reported bugs to her?

          If buzas requests that change, then yes, we can make that change. We generally don't change the default assignee with the new assignee agreeing to accept that assignment.

          Mark Waite added a comment - I see that Laura already has a user here, could someone, please, update the default assignee for the reported bugs to her? If buzas requests that change, then yes, we can make that change. We generally don't change the default assignee with the new assignee agreeing to accept that assignment.

          E added a comment -

          How do we report spam here?

          E added a comment - How do we report spam here?

          Mark Waite added a comment -

          How do we report spam here?

          Thanks for asking. We usually report Jira spam with a ticket to the Jenkins infrastructure help desk The spam comment has been edited and deleted. The edit is necessary in order to not retain the spam comment content in the Jira issue history. The delete removes it from the comments tab.

          Mark Waite added a comment - How do we report spam here? Thanks for asking. We usually report Jira spam with a ticket to the Jenkins infrastructure help desk The spam comment has been edited and deleted. The edit is necessary in order to not retain the spam comment content in the Jira issue history. The delete removes it from the comments tab.

          Laura Buzas added a comment -

          oteb markewaite 

          Since the issue was raised there is another Jenkins plugin release, 24.3, that now supports latest versions of Jenkins: [OpenText Application Automation Tools | Jenkins plugin|https://plugins.jenkins.io/hp-application-automation-tools-plugin/releases/].

          Could you please try it and let me know if the issue is still occurring?

          Laura Buzas added a comment - oteb markewaite   Since the issue was raised there is another Jenkins plugin release, 24.3, that now supports latest versions of Jenkins:  [OpenText Application Automation Tools | Jenkins plugin|https://plugins.jenkins.io/hp-application-automation-tools-plugin/releases/] . Could you please try it and let me know if the issue is still occurring?

          Mark Waite added a comment -

          See my comments in JENKINS-73588

          Mark Waite added a comment - See my comments in JENKINS-73588

          E added a comment -

          Hello buzas . Just tested it on the latest jdk17 version of Jenkins and the error appears to be gone. Thanks a lot!

          E added a comment - Hello buzas . Just tested it on the latest jdk17 version of Jenkins and the error appears to be gone. Thanks a lot!

          E added a comment -

          Issue resolved.

          E added a comment - Issue resolved.

            buzas Laura Buzas
            oteb E
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: