[JIRA] (JENKINS-62200) MF Application Automation Tools plugin: violation of RFC7230

2020-05-11 Thread 'li....@hpe.com (JIRA)' via Jenkins Issues
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-62200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MF Application Automation Tools plugin: violation of RFC7230   
 

  
 
 
 
 

 
 This is not something we could fix at the plugin side. The header is in the response of ALM.  Should rise an ticket to ALM.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206132.1588843012000.24579.1589186160165%40Atlassian.JIRA.


[JIRA] (JENKINS-62200) MF Application Automation Tools plugin: violation of RFC7230

2020-05-11 Thread 'li....@hpe.com (JIRA)' via Jenkins Issues
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-62200  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MF Application Automation Tools plugin: violation of RFC7230   
 

  
 
 
 
 

 
 This is not something we could fix at the plugin side. The header is in the response of ALM.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206132.1588843012000.24577.1589185620174%40Atlassian.JIRA.


[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55

2019-12-30 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55   
 

  
 
 
 
 

 
 The plugin supports both authenticate with and without apikey. And this didn't change for several releases. So please provide me the console output may be it is because of something else.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203596.1576509162000.1132.1577758140130%40Atlassian.JIRA.


[JIRA] (JENKINS-60505) Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55

2019-12-30 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60505  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Microfocus Application Automation Tools Ver:6.0 not supporting ALM 12.55   
 

  
 
 
 
 

 
 Could you provide me the console output of the failed job?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203596.1576509162000.1130.1577757480503%40Atlassian.JIRA.


[JIRA] (JENKINS-60395) ALM jenkins plugin: ALM results upload issue

2019-12-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60395  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ALM jenkins plugin: ALM results upload issue   
 

  
 
 
 
 

 
 Could you please send me the console output of the 1st and 2nd job by email?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203449.1575673998000.4797.1576030440192%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-20 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi Sergio Cuenca, I got your point. But I think you're a little milk the bull. How about a better solution? You know, there're two jobs in the plugin called 'Execute functional tests from ALM'  and 'Execute tests using ALM Lab Management' either of them can execute ALM test. You can configure them in your Jenkins build and ALM will execute the tests and got the result. So simple, this is how other customers use this plugin to do automation and this is why no other customer has such requirement like yours. If you're insist to have such feature in the plugin, I can do it. But as it is over-specific, it may take time to make a new job to do this. Because your request is actually not upload external test result. It's actually upload the result back to test which already exist in ALM. They're a little different and we couldn't change the function of the current job. But even if we achieve this, the whole thing sounds like going around in circle, doesn't it? It's not elegant. The plugin already provided a better way to automation. So could you please think about my suggestion?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.4819.1574319300170%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-20 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi Sergio Cuenca, Usually user creates test cases in ALM 'Test Plan' module to execute ALM tests such as 'VAPI', 'MANUAL', 'BUSINESS PROCESS' etc. These are ALM tests not external test. What we upload to ALM server through Jenkins plugin are external tests such like Junit, Nunit etc. For these kinds of tests, we don't create test plan before upload. They're created during upload. Besides, what test type do you chose when you create the test case? There's no 'EXTERNAL-TEST' option. This type is assigned to test case during upload too.   Do you mean you're automating some of the tests that used to be executed manually in ALM? Which are actually ALM tests?    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.4771.1574304900234%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi [~scuenca],I understand. You want that the plugin would not create new tests if there are already tests with the same name. Just new runs would be created. Am I correct?Then, what about the test sets? Are there test sets already exists? Besides, what if other customer still want new testsets and tests being uploaded to the specified folder even there’re same name in other folders?In many years after Jenkins plugin being published, it's the first time we got such request. Please understand we have to consider most common usage.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.4151.1574234880450%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi [~scuenca],I understand. You want  that  the plugin  would  not  to  create new tests if there are already tests with the same name. Just new runs  would  be created. Am I correct?Then, what about the test sets? Are there test sets already exists?Besides, what if other customer still want new testsets and tests being uploaded to the specified folder even there’re same name in other folders?In many years after Jenkins plugin being published, it's the first time we got such request. Please understand we have to consider most common usage.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.4153.1574234880490%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to inform test version executed   
 

  
 
 
 
 

 
 Hi [~scuenca],A normal test instance doesn't have  “ Test Version Number” , “Test Version Date”, “Test Version Time” .  Is it an  Are they  user defined  field  fields ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.4116.1574232960954%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi Sergio Cuenca, I understand. You want that the plugin would not create new tests if there are already tests with the same name. Just new runs would be created. Am I correct? Then, what about the test sets? Are there test sets already exists?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.4113.1574232900185%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to inform test version executed   
 

  
 
 
 
 

 
 Hi Sergio Cuenca, A normal test instance doesn't have  “Version Number”. Is it an user defined field?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.4105.1574216280206%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to inform test version executed   
 

  
 
 
 
 

 
  Hi [~scuenca],There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run?Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong. Or the test version just indicates the version of Junit? BR,Roy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3071.1574150520295%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to inform test version executed   
 

  
 
 
 
 

 
  Hi [~scuenca],There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run?Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong.   Or the test version just indicates the version of Junit? BR,Roy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3069.1574150460133%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60174  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to inform test version executed   
 

  
 
 
 
 

 
  Hi Sergio Cuenca, There's no test version concept in ALM. As the test result will be parsed to ALM test set, test and run. What would you like the test version belong to? I mean should it be a field of ALM test set or ALM test or ALM run? Per my understanding, different versions for Junit test may be different tests for ALM test. Correct me if I'm wrong.   BR, Roy  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.3056.1574146200151%40Atlassian.JIRA.


[JIRA] (JENKINS-60174) To be able to inform test version executed

2019-11-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Roy Lu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60174  
 
 
  To be able to inform test version executed   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Maria Narcisa Galan Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203134.1573743302000.2999.1574129400374%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Roy Lu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60175  
 
 
  To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Maria Narcisa Galan Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2996.1574129400321%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi [~scuenca],1. Are you saying the tests were uploaded to Root/Automated tests/ and either to Root/Automated/Module 1, Root/Automated/Module 2, Root/Automated/Module 3?2.  As I remember  Currently  only one path you can define in Jenkins plugin. For example here's Root/Automated tests/.  IF  If  you want to define multiple patchs,  while  which  folder would you like the different tests being uploaded to?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2993.1574129340215%40Atlassian.JIRA.


[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder

2019-11-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-60175  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: To be able to define test cases in hierarchy folder   
 

  
 
 
 
 

 
 Hi Sergio Cuenca, 1. Are you saying the tests were uploaded to Root/Automated tests/ and either to Root/Automated/Module 1, Root/Automated/Module 2, Root/Automated/Module 3? 2. As I remember only one path you can define in Jenkins plugin. For example here's Root/Automated tests/. IF you want to define multiple patchs, while folder would you like the different tests being uploaded to?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203135.1573743439000.2990.1574129281199%40Atlassian.JIRA.


[JIRA] (JENKINS-59512) I am getting Connection timed out while testing HP ALM connection throu Jenkins

2019-09-25 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-59512  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: I am getting Connection timed out while testing HP ALM connection throu Jenkins   
 

  
 
 
 
 

 
 Hi Which build step were you using?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202135.1569336332000.5670.1569462660230%40Atlassian.JIRA.


[JIRA] (JENKINS-58565) Jenkins build not grabbing hptoolslauncher

2019-09-11 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Anda Sorina Laakso  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58565  
 
 
  Jenkins build not grabbing hptoolslauncher   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Roy Lu Anda Sorina Laakso  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200715.1563505716000.1141.1568189040254%40Atlassian.JIRA.


[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly

2019-09-11 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58134  
 
 
  Some of the testcase status can't be parsed correctly   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200179.1561100594000.1138.1568188981233%40Atlassian.JIRA.


[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing

2019-08-28 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Daniel Gront  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59090  
 
 
  Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Roy Lu Daniel Gront  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2442.1567046160258%40Atlassian.JIRA.


[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing

2019-08-28 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Roy Lu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59090  
 
 
  Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Maria Narcisa Galan Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2439.1567046100157%40Atlassian.JIRA.


[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing

2019-08-28 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Maria Narcisa Galan  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59090  
 
 
  Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Roy Lu Maria Narcisa Galan  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2436.1567046040365%40Atlassian.JIRA.


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

2019-07-02 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 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  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.345.1562121000174%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-27 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 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.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.10418.1561626780364%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-26 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Were you using a multibranch pipeline job?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.9141.1561538880461%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 Could you please provide the console output of this job?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7749.1561428720192%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7075.1561365000818%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 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?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7055.1561363200129%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly

2019-06-23 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-58134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Some of the testcase status can't be parsed correctly   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/hpe-application-automation-tools-plugin/pull/241  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200179.1561100594000.7012.1561359420041%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


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

2019-06-23 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  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?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.7011.1561359360122%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly

2019-06-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-58134  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200179.1561100594000.5078.1561101120081%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly

2019-06-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58134  
 
 
  Some of the testcase status can't be parsed correctly   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 

  
 
 
 
 

 
 "PASSED" can't be uploaded to ALM. Only "Passed" can be recognized.  The logic of parsing should be improved.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200179.1561100594000.5072.1561100700168%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly

2019-06-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58134  
 
 
  Some of the testcase status can't be parsed correctly   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-06-21 07:03  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
  "PASSED" can't be uploaded to ALM. Only "Passed" can be recognized.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

   

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

2019-06-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55276  
 
 
  HP ALM Plugin - when job is branched only branch appear in HP ALM   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196363.154529647.2137.1560842280295%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

2019-06-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 Hi Daniel Gront, Yes this is a issue of a build step belongs to our plugin. We may need Bogdan's help on this.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.2131.1560842100380%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56748) Execution Report not triggered

2019-05-27 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-56748  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Execution Report not triggered   
 

  
 
 
 
 

 
 Hi Daniel Gront, This need to be assigned to Bogdan's team. It look like a similar requirement they've dealt with before.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198389.1553529416000.13037.1559011980137%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-56262) Upload external test result has issue with ALM15p3 with client type restriction on

2019-02-26 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56262  
 
 
  Upload external test result has issue with ALM15p3 with client type restriction on   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM

2019-02-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-55276  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

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

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-56262) Upload external test result has issue with ALM15p3 with client type restriction on

2019-02-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56262  
 
 
  Upload external test result has issue with ALM15p3 with client type restriction on   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-02-25 05:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env

2019-01-30 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-55718  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55718  
 
 
  Support ALM15SSO/Make sure the login process could work in some problematic ALM env   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env

2019-01-23 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-55718  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55718  
 
 
  Support ALM15SSO/Make sure the login process could work in some problematic ALM env   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env

2019-01-22 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-55718  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env

2019-01-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55718  
 
 
  Support ALM15SSO/Make sure the login process could work in some problematic ALM env   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Gront  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-01-22 05:26  
 
 
Priority: 
  Trivial  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 Authentication process enhancement. First we're going to support ALM15SSO. Second, some customer's ALM env always got wrong authentication point. We gonna make sure the Jenkins won't be blocked by this ALM issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env

2019-01-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Roy Lu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55718  
 
 
  Support ALM15SSO/Make sure the login process could work in some problematic ALM env   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Daniel Gront Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM

2019-01-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  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?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55250) Upload external test result failed when using API key to login ALM14

2018-12-23 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-55250  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in future release.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55250  
 
 
  Upload external test result failed when using API key to login ALM14   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55250) Upload external test result failed when using API key to login ALM14

2018-12-19 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-55250  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55250  
 
 
  Upload external test result failed when using API key to login ALM14   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55250) Upload external test result failed when using API key to login ALM14

2018-12-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-55250  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302

2018-12-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing it for no response for a long time.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53985  
 
 
  Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-55250) Upload external test result failed when using API key to login ALM14

2018-12-18 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55250  
 
 
  Upload external test result failed when using API key to login ALM14   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-12-19 02:15  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-11-07 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-53491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53491  
 
 
  Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-11-07 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-53491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53491  
 
 
  Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-48192) HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2

2018-11-07 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm closing it for no response.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48192  
 
 
  HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Reopened Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)

2018-11-07 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm closing it for no response for a long time.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53088  
 
 
  Node Xml  is not valid to updateAlmEntity Rest Service. (Testset)
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302

2018-11-07 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53985  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302   
 

  
 
 
 
 

 
 Hi Oliver Schuhmacher, Is there any proxy been set in your browser? If yes, set the proxy in Jenkins proxy. If no, we may need a session to look into it. But in my experience, all the 302 issues I've met are because of proxy.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-10-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
 Ready for test.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302

2018-10-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53985  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302   
 

  
 
 
 
 

 
 Hi Oliver Schuhmacher, In 5.5 it should be using Jenkins proxy configuration. What's the version are you using?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-10-24 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-53491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53491  
 
 
  Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53088  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Node Xml  is not valid to updateAlmEntity Rest Service. (Testset)
 

  
 
 
 
 

 
 Hi Jesús Benavente, What build step are you using? Upload test result? Can you provide the console output of the build?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53088  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Node Xml  is not valid to updateAlmEntity Rest Service. (Testset)
 

  
 
 
 
 

 
 Hi Daniel Gront, I don't know why the PR was mentioned in the first comment. Seems this case is talking about a different thing.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-53491  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-52812) Support NUnit V3 Report in Jenkins Plug-in

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Done  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52812  
 
 
  Support NUnit V3 Report in Jenkins Plug-in   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-51239) Send client type in Jenkins Plugin to support API Key in ALM1260

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated  JENKINS-51239  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51239  
 
 
  Send client type in Jenkins Plugin to support API Key in ALM1260   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-48192) HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-48192  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2   
 

  
 
 
 
 

 
 Have you filled the 'client type' field?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-48192) HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-48192  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HP ALM SaaS 12.50 -"Cannot append QCSession cookies" error for Execute HP tests using HP ALM Lab Management" Build Step with HPE plugin version 5.2   
 

  
 
 
 
 

 
 Hi @emmanuel souris  Have you filled the 'client type' field?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302

2018-10-17 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53985  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302   
 

  
 
 
 
 

 
 It mainly because of proxy. Can you visit ALM from the machine where you build the jenkins job?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53088  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Node Xml  is not valid to updateAlmEntity Rest Service. (Testset)
 

  
 
 
 
 

 
 Hi Jesús Benavente, Is the  some new format that we don't support now? What's the format?   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-50059) Unable to upload test results to ALM. Failed login to ALM Server.Exception: com.hpe.application.automation.tools.common.SSEException: java.net.ConnectException: Connection timed

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50059  
 
 
  Unable to upload test results to ALM. Failed login to ALM Server.Exception: com.hpe.application.automation.tools.common.SSEException: java.net.ConnectException: Connection timed out: connect   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Reopened Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-52753) Uploads archived junit results from Jenkinsfile

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52753  
 
 
  Uploads archived junit results from Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-52753) Uploads archived junit results from Jenkinsfile

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-52753  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uploads archived junit results from Jenkinsfile   
 

  
 
 
 
 

 
 I created same ticket to track it https://issues.jenkins-ci.org/browse/JENKINS-53491 So close this one. I'll implement this in the new ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu edited a comment on  JENKINS-53116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)   
 

  
 
 
 
 

 
 I created same ticket to track it https://issues.jenkins-ci.org/browse/JENKINS-53491So close this one. I'll implement this in the new ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53116  
 
 
  Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)

2018-09-12 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)   
 

  
 
 
 
 

 
 I created same ticket to track it https://issues.jenkins-ci.org/browse/JENKINS-53491 So close this one.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)

2018-09-11 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53116  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)   
 

  
 
 
 
 

 
 Hi,  Jesús Benavente The PR is not created well. It has more than 700+ files change. Would you please create a correct PR to jenkinsci:latest? Thanks.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53271) Pipeline step of SSE and upload and SSE AUT missing client type

2018-09-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53271  
 
 
  Pipeline step of SSE and upload and SSE AUT missing client type   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53153) REST request failure during test execution if the server is ALM 12.60 p1

2018-09-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53153  
 
 
  REST request failure during test execution if the server is ALM 12.60 p1   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53154) Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type

2018-09-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53154  
 
 
  Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-09-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53491  
 
 
  Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-09-10 08:32  
 
 
Labels: 
 jenkins hp-application-automation-tools pipeline plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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, s

[JIRA] (JENKINS-53491) Support Pipeline of "Upload test result to ALM"

2018-09-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53491  
 
 
  Support Pipeline of "Upload test result to ALM"   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Labels: 
 hp-application-automation-tools jenkins pipeline plugin ALM  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-50059) Unable to upload test results to ALM. Failed login to ALM Server.Exception: com.hpe.application.automation.tools.common.SSEException: java.net.ConnectException: Connection timed

2018-09-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-50059  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to upload test results to ALM. Failed login to ALM Server.Exception: com.hpe.application.automation.tools.common.SSEException: java.net.ConnectException: Connection timed out: connect   
 

  
 
 
 
 

 
 Hi anu nagan, The latest release support it now. Please configure proxy infor in Jenkins proxy settings.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53154) Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type

2018-09-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-53154  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53153) REST request failure during test execution if the server is ALM 12.60 p1

2018-09-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-53153  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53271) Pipeline step of SSE and upload and SSE AUT missing client type

2018-09-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-53271  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-52753) Uploads archived junit results from Jenkinsfile

2018-09-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-52753  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Uploads archived junit results from Jenkinsfile   
 

  
 
 
 
 

 
 I don't understand. What you're asking is uploading Junit result which is already supported in "Upload test result to ALM".   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
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] (JENKINS-53271) Pipeline step of SSE and upload and SSE AUT missing client type

2018-08-28 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53271  
 
 
  Pipeline step of SSE and upload and SSE AUT missing client type   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-08-28 07:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 Pipeline step "Execute tests using ALM Lab Management and Publish tests result" and  "Execute AUT Environment preparation using Micro Focus ALM Lab Management" missing client type. They're rarely used.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This mess

[JIRA] (JENKINS-53154) Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type

2018-08-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53154  
 
 
  Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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] (JENKINS-53154) Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type

2018-08-21 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53154  
 
 
  Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-08-21 08:13  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 Leave client type field empty can not pass authentication of ALM1260 which doesn't need client type.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
  

[JIRA] (JENKINS-53153) REST request failure during test execution if the server is ALM 12.60 p1

2018-08-20 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-53153  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: REST request failure during test execution if the server is ALM 12.60 p1   
 

  
 
 
 
 

 
 Add xml header for ALM 1260 p1. Get request may fail on 1260 p1 without xml header. SQL query generation may fail.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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] (JENKINS-53153) REST request failure during test execution if the server is ALM 12.60 p1

2018-08-20 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53153  
 
 
  REST request failure during test execution if the server is ALM 12.60 p1   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-08-21 06:09  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)  
 

  
 

   





-- 
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] (JENKINS-51239) Send client type in Jenkins Plugin to support API Key in ALM1260

2018-05-10 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51239  
 
 
  Send client type in Jenkins Plugin to support API Key in ALM1260   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Roy Lu  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2018-05-10 07:42  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Roy Lu  
 

  
 
 
 
 

 
 Send client type when invoking ALM API so that it can be bypass the restriction of access after turning on API Key restriction. The correct process is as follows: 1. customer admin add a client type into extended white list in ALM. 2. customer admin tells the users the client type name. 3. users set the client type when executes ALM Jenkins Plug-in.   Example source code to set client type: ALM Productized REST scenario: • /api/authentication/sign-in: Add Header: Key Value ALM-CLIENT-TYPE %CLIENT_TYPE_NAME% ALM Technical Preview scenario • /qcbin/rest/site-session: Add the following XML node to the posted data:  … · …   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

 

[JIRA] (JENKINS-50111) HP ALM Plugin - allow adding a custom result file in the External Test Type

2018-05-09 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu started work on  JENKINS-50111  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-46843) Run Cleanup Test Case if Test is Failed

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Evan Chen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46843  
 
 
  Run Cleanup Test Case if Test is Failed   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 xiwen zhao Evan Chen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Evan Chen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21986  
 
 
  RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Ofir Shaked Evan Chen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Evan Chen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21987  
 
 
  RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Bogdan Girman Evan Chen  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-21986) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Ofir Shaked  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21986  
 
 
  RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Setting Test Execution Duration   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Roy Lu Ofir Shaked  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-21987) RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu assigned an issue to Bogdan Girman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-21987  
 
 
  RunTestSet Function Within AlmTestSetsRunner.cs Incorrectly Using Timeout Parameter   
 

  
 
 
 
 

 
Change By: 
 Roy Lu  
 
 
Assignee: 
 Roy Lu Bogdan Girman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-22435) Unable to connect to ALM QC 11.5. Jenkins throws error saying "server is not available"

2018-05-03 Thread li....@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Roy Lu commented on  JENKINS-22435  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect to ALM QC 11.5. Jenkins throws error saying "server is not available"   
 

  
 
 
 
 

 
 I'll close it if no problem.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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.


  1   2   >