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

23 views
Skip to first unread message

noamangel@gmail.com (JIRA)

unread,
Dec 20, 2018, 4:02:02 AM12/20/18
to jenkinsc...@googlegroups.com
Noam Angel created an issue
 
Jenkins / Bug JENKINS-55276
HP ALM Plugin - when job is branched only branch appear in HP ALM
Issue Type: Bug Bug
Assignee: Daniel Gront
Components: hp-application-automation-tools-plugin
Created: 2018-12-20 09:01
Priority: Minor Minor
Reporter: Noam Angel

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

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

daniel.gront@microfocus.com (JIRA)

unread,
Dec 20, 2018, 4:32:03 AM12/20/18
to jenkinsc...@googlegroups.com

daniel.gront@microfocus.com (JIRA)

unread,
Dec 20, 2018, 4:33:02 AM12/20/18
to jenkinsc...@googlegroups.com

li.lu2@hpe.com (JIRA)

unread,
Jan 22, 2019, 12:19:02 AM1/22/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276
 
Re: HP ALM Plugin - when job is branched only branch appear in HP ALM

Can you show me how you configure the uploadResultToALM pipeline job?

noamangel@gmail.com (JIRA)

unread,
Jan 22, 2019, 4:23:02 AM1/22/19
to jenkinsc...@googlegroups.com

uploadResultToALM(almDomain: 'SDN',
almProject: 'alm_project_testing',
almServerName: 'alm-server',
almTestFolder: 'tempest
',
almTestSetFolder: env.BRANCH_NAME + '
' + (env.JOB_NAME - env.BRANCH_NAME - '/'),
almTimeout: '',
clientType: '',
credentialsId: 'e28dfgdg1fb-fb6d-4e48-a480-4532gfdh',
jenkinsServerUrl: JENKINS_URL,
testingFramework: 'JUnit',
testingResultFile: '**/junitResult.xml',
testingTool: 'tempest')

li.lu2@hpe.com (JIRA)

unread,
Feb 25, 2019, 12:57:02 AM2/25/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

Job name is uploaded to a field called 'jenkins-job-name'.

li.lu2@hpe.com (JIRA)

unread,
Jun 18, 2019, 3:18:01 AM6/18/19
to jenkinsc...@googlegroups.com
Roy Lu closed an issue as Not A Defect
 
Change By: Roy Lu
Status: Open Closed
Resolution: Not A Defect

noamangel@gmail.com (JIRA)

unread,
Jun 18, 2019, 4:38:02 AM6/18/19
to jenkinsc...@googlegroups.com
Noam Angel reopened an issue
 

please see full picture (scroll to right side), my branch is osp13 

 

the issue is that JOB_NAME=JOB_NAME/BRANCH we get only the branch name in ALM without the actual job

Change By: Noam Angel
Resolution: Not A Defect
Status: Closed Reopened

li.lu2@hpe.com (JIRA)

unread,
Jun 24, 2019, 2:56:02 AM6/24/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276
 
Re: HP ALM Plugin - when job is branched only branch appear in HP ALM

Hi Noam,

In the plugin, job name is fixed as the job's name. Can't be customized to other value. We set the job's name to the 'jenkins-job-name' field. So the value updated to this field is actually a fixed value.
You said 'JOB_NAME=JOB_NAME/BRANCH'. Do you mean you changed job name during the pipeline script building?

noamangel@gmail.com (JIRA)

unread,
Jun 24, 2019, 3:05:03 AM6/24/19
to jenkinsc...@googlegroups.com

in jenkins pipeline using a branched pipeline the name the value of JOB_NAME is equal "JOB_NAME/BRANCH_NAME" by default 

i did not set it during pipeline run, I just mention it because i validated during the run the this is the actual value.

the issue the 'jenkins-job-name' get trimmed JOB_NAME equal to only the BRANCH_NAME

li.lu2@hpe.com (JIRA)

unread,
Jun 24, 2019, 4:00:02 AM6/24/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

Hi Noam Angel,

As I tested, no matter you're using a pipeline job or a freestyle job, the 'jenkins-job-name' always takes job's name as the value. Unless you customized the name somehow in your pipeline script.
There's no problem during the result uploading. As long as you set the job name as you wish, plugin will upload it. So, please check the script you set the job name. 

Or could you please attach the whole script. 

BTW, is your job name dynamic?

noamangel@gmail.com (JIRA)

unread,
Jun 24, 2019, 4:07:01 AM6/24/19
to jenkinsc...@googlegroups.com

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

li.lu2@hpe.com (JIRA)

unread,
Jun 24, 2019, 4:30:03 AM6/24/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

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

noamangel@gmail.com (JIRA)

unread,
Jun 24, 2019, 4:34:03 AM6/24/19
to jenkinsc...@googlegroups.com

if you use the multibranch pipeline job type  and job the will run 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

 

noamangel@gmail.com (JIRA)

unread,
Jun 24, 2019, 4:35:03 AM6/24/19
to jenkinsc...@googlegroups.com
Noam Angel edited a comment on Bug JENKINS-55276
if you use the multibranch pipeline job type ,   and any job the you will run 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

 

li.lu2@hpe.com (JIRA)

unread,
Jun 24, 2019, 10:12:02 PM6/24/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

Could you please provide the console output of this job?

noamangel@gmail.com (JIRA)

unread,
Jun 25, 2019, 2:11:02 AM6/25/19
to jenkinsc...@googlegroups.com

li.lu2@hpe.com (JIRA)

unread,
Jun 26, 2019, 4:48:03 AM6/26/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

Were you using a multibranch pipeline job?

noamangel@gmail.com (JIRA)

unread,
Jun 26, 2019, 5:07:02 AM6/26/19
to jenkinsc...@googlegroups.com

li.lu2@hpe.com (JIRA)

unread,
Jun 27, 2019, 5:13:04 AM6/27/19
to jenkinsc...@googlegroups.com
Roy Lu commented on Bug JENKINS-55276

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.

li.lu2@hpe.com (JIRA)

unread,
Jul 2, 2019, 10:30:02 PM7/2/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages