[JIRA] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file

2016-05-31 Thread mpen...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mpendas resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Thank you for the response. I was expecting the plugin to look for the result file in the workspace directory of the job, not the build directory. I was assuming the same behavior as the junit plugin. I see now that this plugin uses the results of the junit plugin not that actual junit file produced by a given test framework.  
I think if you were a bit more explicit about that in the help available in the jenkins job configuration, it would avoid this question in the future. 
Again thanks for the help and for writing the plugin! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-35106 
 
 
 
  HP ALM plugin fails to find junit results file  
 
 
 
 
 
 
 
 
 

Change By:
 
 mpendas 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 

[JIRA] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file

2016-05-26 Thread mpen...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mpendas updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35106 
 
 
 
  HP ALM plugin fails to find junit results file  
 
 
 
 
 
 
 
 
 

Change By:
 
 mpendas 
 
 
 
 
 
 
 
 
 
 I am only trying to upload test results to ALM. This is running on RedHat Linux. No HP  LAM  ALM  software is installed on the jenkins machine.The Junit plugin finds the results file the HP ALM plugin does not find the file:Recording test resultsBuild step 'Publish JUnit test result report' changed build result to UNSTABLEINFO: 'Upload test result to ALM' Post Build Step is being invoked.INFO: No Test Report found.INFO: 'Upload test result to ALM' Completed.Finished: UNSTABLEThe file path for both plugins is: **/fit_tests/ApiResults.xml 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [hp-application-automation-tools-plugin] (JENKINS-35106) HP ALM plugin fails to find junit results file

2016-05-24 Thread mpen...@java.net (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 mpendas created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-35106 
 
 
 
  HP ALM plugin fails to find junit results file  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ofir Shaked 
 
 
 

Components:
 

 hp-application-automation-tools-plugin 
 
 
 

Created:
 

 2016/May/24 7:52 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.642  HP Application Automation Tools plugin ver. 4.01  java version "1.7.0_71"  OpenJDK Runtime Environment (rhel-2.5.3.1.el6-x86_64 u71-b14)  OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)  Red Hat Enterprise Linux Server release 6.6 (Santiago)  
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 mpendas 
 
 
 
 
 
 
 
 
 
 
I am only trying to upload test results to ALM. This is running on RedHat Linux. No HP LAM software is installed on the jenkins machine. 
The Junit plugin finds the results file the HP ALM plugin does not find the file: 
Recording test results Build step 'Publish JUnit test result report' changed build result to UNSTABLE INFO: 'Upload test result to ALM' Post Build Step is being invoked. INFO: No Test Report found. INFO: 'Upload test result to ALM' Completed. Finished: UNSTABLE 
The file path for both plugins is: **/fit_tests/ApiResults.xml 
 
 
 
 
 

[JIRA] (JENKINS-14826) Have the Build User Vars plugin expose the build user's email address

2012-08-16 Thread mpen...@java.net (JIRA)














































mpendas
 created  JENKINS-14826


Have the Build User Vars plugin expose the build users email address















Issue Type:


Improvement



Assignee:


Unassigned


Components:


plugin



Created:


16/Aug/12 2:11 PM



Description:


It would be useful for the Build User Vars plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin) to also expose the build users email address from the jenkins DB.




Project:


Jenkins



Labels:


plugin
user
envinronment-variables




Priority:


Minor



Reporter:


mpendas

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14770) expose the jenkins login id as an environment variable

2012-08-13 Thread mpen...@java.net (JIRA)














































mpendas
 commented on  JENKINS-14770


expose the jenkins login id as an environment variable















Yes, it does. Thank you.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14770) expose the jenkins login id as an environment variable

2012-08-10 Thread mpen...@java.net (JIRA)














































mpendas
 created  JENKINS-14770


expose the jenkins login id as an environment variable















Issue Type:


Improvement



Assignee:


Gregory Boissinot



Components:


envinject



Created:


10/Aug/12 8:08 PM



Description:


I would be very useful to have the jenkins login id exposed as an environment variable to shells executed as a build step. Basically added to this set:

The following variables are available to shell scripts

BUILD_NUMBER
The current build number, such as "153"
BUILD_ID
The current build id, such as "2005-08-22_23-59-59" (-MM-DD_hh-mm-ss)
JOB_NAME
Name of the project of this build, such as "foo" or "foo/bar"
BUILD_TAG
String of "jenkins-${JOB_NAME}-${BUILD_NUMBER}". Convenient to put into a resource file, a jar file, etc for easier identification.
EXECUTOR_NUMBER
The unique number that identifies the current executor (among executors of the same machine) that's carrying out this build. This is the number you see in the "build executor status", except that the number starts from 0, not 1.
NODE_NAME
Name of the slave if the build is on a slave, or "master" if run on master
NODE_LABELS
Whitespace-separated list of labels that the node is assigned.
WORKSPACE
The absolute path of the directory assigned to the build as a workspace.
JENKINS_HOME
The absolute path of the directory assigned on the master node for Jenkins to store data.
JENKINS_URL
Full URL of Jenkins, like http://server:port/jenkins/
BUILD_URL
Full URL of this build, like http://server:port/jenkins/job/foo/15/
JOB_URL
Full URL of this job, like http://server:port/jenkins/job/foo/




Project:


Jenkins



Labels:


build
user




Priority:


Minor



Reporter:


mpendas

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira