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

Jenkins PIpeline script ALM configuration failing

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I am using the below pipeline script to connect to ALM and run the test

      runFromAlmBuilder almApiKey: '', almClientID: '', almDomain: 'XXXX', almPassword: 'XXXX', almProject: 'ARDWEB_PRD', almRunHost: '', almRunMode: 'RUN_LOCAL', almServerName: 'ALM', almTestSets: '''Root
      test1
      prx''', almTimeout: '7200', almUserName: 'SSSS', filterTestsModel: [blockedCheckbox: false, failedCheckbox: false, noRunCheckbox: false, notCompletedCheckbox: false, passedCheckbox: false, testName: ''], isSSOEnabled: false

       

      After build I am getting the below error

      WorkflowScript: 9: Missing required parameter: "almRunResultsMode" @ line 9, column 13.
                     runFromAlmBuilder almApiKey: '', almClientID: '', almDomain: 'XXXX', almPassword: 'XXXX', almProject: 'XXXXX', almRunHost: '', almRunMode: 'RUN_LOCAL', almServerName: 'ALM', almTestSets: '''Root
      test1
      prx''', almTimeout: '7200', almUserName: 'SSSS', filterTestsModel: [blockedCheckbox: false, failedCheckbox: false, noRunCheckbox: false, notCompletedCheckbox: false, passedCheckbox: false, testName: 'SanityTobeDeletedForTest'] ,isSSOEnabled: false
                     ^

      1 error

       at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
       at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
       at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
       at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
       at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
       at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
       at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
       at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
       at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
       at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
       at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
       at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561)
       at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522)
       at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:327)
       at hudson.model.ResourceController.execute(ResourceController.java:97)
       at hudson.model.Executor.run(Executor.java:427)
      Finished: FAILURE

       

      Please note on a free style job when we use the same plug in its working all fine. Please help I can totally stuck here

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          Refer to the Pipeline Syntax generator on http://your-jenkins-server/pipeline-syntax for a guided assistant that will help you provide correct and required parameters to the pipeline step.

          Show
          markewaite Mark Waite added a comment - Refer to the Pipeline Syntax generator on http://your-jenkins-server/pipeline-syntax for a guided assistant that will help you provide correct and required parameters to the pipeline step.
          Hide
          divvya Divya Rajan added a comment -

          Hi Mark,

           

          I got that working on Windows machine. Now trying to configure the same on a slave which is in linux. Master have the plug in installed while triggering i am getting permission denied error. As its a Linux container how do we run the HpToolsLauncher.exe. Will the same plug in works for Linux too please let me know.

           
          11:35:52 Executing shell script inside container [user] 11:35:52 Executing command: "/home/jenkins/workspace/QA/downstreamQA/HpToolsLauncher.exe" "-paramfile" "props18022020060552418.txt" 11:35:52 exit*11:35:52* /bin/sh: line 36: /home/jenkins/workspace/QA/downstreamQA/HpToolsLauncher.exe: Permission denied
           

          Regards,
          Divya

          Show
          divvya Divya Rajan added a comment - Hi Mark,   I got that working on Windows machine. Now trying to configure the same on a slave which is in linux. Master have the plug in installed while triggering i am getting permission denied error. As its a Linux container how do we run the HpToolsLauncher.exe. Will the same plug in works for Linux too please let me know.   11:35:52 Executing shell script inside container [user] 11:35:52 Executing command: "/home/jenkins/workspace/QA/downstreamQA/HpToolsLauncher.exe" "-paramfile" "props18022020060552418.txt" 11:35:52 exit*11:35:52* /bin/sh: line 36: /home/jenkins/workspace/QA/downstreamQA/HpToolsLauncher.exe: Permission denied   Regards, Divya
          Hide
          markewaite Mark Waite added a comment -

          Please don't use Jenkins issue reports as a question and answer site. The mailing lists and chat systems are much better suited to questions. I am not a user of MicroFocus Performance Center. I don't know how to make it work in your environment or any other environment. Since it is a purchased product, you should contact the seller for assistance.

          Show
          markewaite Mark Waite added a comment - Please don't use Jenkins issue reports as a question and answer site. The mailing lists and chat systems are much better suited to questions. I am not a user of MicroFocus Performance Center. I don't know how to make it work in your environment or any other environment. Since it is a purchased product, you should contact the seller for assistance.
          Hide
          danieldananm Daniel Danan added a comment -

          I am releasing version 1.1.4.

          Hopefully this one contains the fix for this issue.

          If possible, generate your pipepline script from Pipeline syntax once again before running it. 

           

          Show
          danieldananm Daniel Danan added a comment - I am releasing version 1.1.4. Hopefully this one contains the fix for this issue. If possible, generate your pipepline script from Pipeline syntax once again before running it.   

            People

            Assignee:
            danieldananm Daniel Danan
            Reporter:
            divvya Divya Rajan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: