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

HP ALM Plugin - when job is branched only branch appear in HP ALM

      when running "uploadResultToALM" in branched pipeline JOB_NAME is
      JOB_NAME=JOB_NAME/BRANCH
       

      HP ALM will present field "Jenkins Job Name" with only the branch name without the actual job name

          [JENKINS-55276] HP ALM Plugin - when job is branched only branch appear in HP ALM

          Noam Angel added a comment -

          i dont set JOB_NAME at all. for ex JOB_NAME="deploy_overcloud/master" what I will get in HP ALM is only "master"

          im using multibranch pipeline

          Noam Angel added a comment - i dont set JOB_NAME at all. for ex JOB_NAME="deploy_overcloud/master" what I will get in HP ALM is only "master" im using multibranch pipeline

          Roy Lu added a comment -

          Well. Do you mean you use the string "deploy_overcloud/master" as the job name but only get "master" in ALM?

          Roy Lu added a comment - Well. Do you mean you use the string "deploy_overcloud/master" as the job name but only get "master" in ALM?

          Noam Angel added a comment - - edited

          if you use the multibranch pipeline job type,  any job the you will create  will have a JOB_NAME combined from JOB_NAME and BRANCH, its set by the JOB itself not by me or by code in pipeline. somewhere in the way to uploadResultToALM -> HP ALM it gets trimmed. so yes i only get "master" which is not helpful

           

          Noam Angel added a comment - - edited if you use the multibranch pipeline job type,  any job the you will create  will have a JOB_NAME combined from JOB_NAME and BRANCH, its set by the JOB itself not by me or by code in pipeline. somewhere in the way to uploadResultToALM -> HP ALM it gets trimmed. so yes i only get "master" which is not helpful  

          Roy Lu added a comment -

          Could you please provide the console output of this job?

          Roy Lu added a comment - Could you please provide the console output of this job?

          Noam Angel added a comment -

           

           here is the console output 

          http://paste.openstack.org/show/753336/

           

          Noam Angel added a comment -    here is the console output  http://paste.openstack.org/show/753336/  

          Roy Lu added a comment -

          Were you using a multibranch pipeline job?

          Roy Lu added a comment - Were you using a multibranch pipeline job?

          Noam Angel added a comment -

          yes

          Noam Angel added a comment - yes

          Roy Lu added a comment -

          Well. It seems the multibranch pipeline job would make the job path one level more. 

          Usually it should be like:

          /var/lib/jenkins/jobs/featureset022/builds/14/junitResult.xml

          But your case is:

          /var/lib/jenkins/jobs/featureset022/branches/osp14/builds/14/junitResult.xml

          Build got it's parent's name as job name. But it got actually branch name in your case. I'm trying to find how to get actually name in a build.

          Roy Lu added a comment - Well. It seems the multibranch pipeline job would make the job path one level more.  Usually it should be like: /var/lib/jenkins/jobs/featureset022/builds/14/junitResult.xml But your case is: /var/lib/jenkins/jobs/featureset022/branches/osp14/builds/14/junitResult.xml Build got it's parent's name as job name. But it got actually branch name in your case. I'm trying to find how to get actually name in a build.

          Roy Lu added a comment - Looks like it's a common issue. https://issues.jenkins-ci.org/browse/JENKINS-44278 https://stackoverflow.com/questions/43639031/how-to-get-the-displayname-of-a-jenkins-multibranch-pipeline-job

          Rollin added a comment -

          It's not an issue of the plugin. It will or already be fixed in Jenkins.

          Rollin added a comment - It's not an issue of the plugin. It will or already be fixed in Jenkins.

            roy_lu Roy Lu
            noama Noam Angel
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: