• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: hp-application-automation-tools-plugin
• Labels:

  • Octane
• Environment:

  Hide

  Jenkins version: 2.190.1 LTS (Windows Installer).
  Java version: JDK 1.8.0_181
  Jenkins host: WS2012 R2 Standard No service pack.
  Plugin: Micro Focus Application Automation Tools’ plugin version 5.9.
  ALM Octane version: 12.60 (CP10).
  ALM Octane O/S: Windows 2016
  ALM Octane setup: Clustered environment.
  ALM Octane: Using TLS 1.2 (Port 8443).
  Octane API: API Access is successfully generated.
  
  

  Show

  Jenkins version: 2.190.1 LTS (Windows Installer). Java version: JDK 1.8.0_181 Jenkins host: WS2012 R2 Standard No service pack. Plugin: Micro Focus Application Automation Tools’ plugin version 5.9. ALM Octane version: 12.60 (CP10). ALM Octane O/S: Windows 2016 ALM Octane setup: Clustered environment. ALM Octane: Using TLS 1.2 (Port 8443). Octane API: API Access is successfully generated.

1. 

   Post_build_Actions.png

   17 kB

   2019-10-21 11:58

2. 

   Octane_Job_Status.png

   5 kB

   2019-10-21 11:56

3. 

   Jenkins_Console_Output.png

   37 kB

   2019-10-21 11:56

4. 

   Before_Jenkins_Restart.png

   65 kB

   2019-10-21 11:56

5. 

   After_Jenkins_Restart.png

   56 kB

   2019-10-21 19:08

[JENKINS-59866] Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts

Minh Tran created issue - 2019-10-21 12:05

Minh Tran made changes - 2019-10-21 12:08

Environment

Original: Jenkins version: 2.190.1 LTS. Java version: JDK 1.8.0_181 Jenkins host: WS2012 R2 Standard No service pack. Plugin: Micro Focus Application Automation Tools’ plugin version 5.9. ALM Octane version: 12.60 (CP10). ALM Octane O/S: Windows 2016 ALM Octane setup: Clustered environment. ALM Octane: Using TLS 1.2 (Port 8443). Octane API: API Access is successfully generated.

New: Jenkins version: 2.190.1 LTS (Windows Installer). Java version: JDK 1.8.0_181 Jenkins host: WS2012 R2 Standard No service pack. Plugin: Micro Focus Application Automation Tools’ plugin version 5.9. ALM Octane version: 12.60 (CP10). ALM Octane O/S: Windows 2016 ALM Octane setup: Clustered environment. ALM Octane: Using TLS 1.2 (Port 8443). Octane API: API Access is successfully generated.

Minh Tran made changes - 2019-10-21 19:08

Attachment

Original: After_Jenkins_Restart.png [ 49218 ]

Minh Tran made changes - 2019-10-21 19:08

Attachment

New: After_Jenkins_Restart.png [ 49223 ]

Minh Tran made changes - 2019-10-21 21:10

Description

Original: Hi, I am currently having issue with "Octane Cucumber test reporter" plugin which could be reproduced as below steps: Steps:  # Create a Maven project using cucumber framework and "com.hpe.alm.octane.OctaneGherkinFormatter:target\\gherkin-results\\ManualRunnerTest_OctaneGherkinResults.xml" plugin.  # Create a freestyle Jenkins job for above maven project and add the "Octane Cucumber test reporter" and "Publish Thucydides Test Reports" to Post-build Actions.  # Create an Octane pipeline job that links to Jenkins job above.  # Build the job and ensure the result is passed.  # Validate the HTML report is published in Jenkins and ManualRunnerTest_OctaneGherkinResults.xml is generated in Jenkins workspace\target\gherkin-results.  # Restart Jenkins Expected:  * Job status is still passed.  * HTML Report is still accessible. Actual:  * Job status is turned to failed.  * HTML Report is inaccessible. Please see attached the screenshots of the job status before and after Jenkins restart, console output log, and octane pipeline status.

New: Hi, I am currently having issue with "Octane Cucumber test reporter" plugin which could be reproduced as below steps: Steps:  # Create a Maven project using cucumber framework and "com.hpe.alm.octane.OctaneGherkinFormatter:target\\gherkin-results ManualRunnerTest_OctaneGherkinResults.xml" plugin.  # Create a freestyle Jenkins job for above maven project and add the "Octane Cucumber test reporter" and "Publish Thucydides Test Reports" to Post-build Actions.  # Create an Octane pipeline job that links to Jenkins job above.  # Build the job and ensure the result is passed.  # Validate the HTML report is published in Jenkins and ManualRunnerTest_OctaneGherkinResults.xml is generated in Jenkins workspace\target\gherkin-results.  # Restart Jenkins Expected:  * Job status is still passed.  * HTML Report is still accessible. Actual:  * Job status is turned to failed.  * HTML Report is removed. Please see attached the screenshots of the job status before and after Jenkins restart, console output log, and octane pipeline status.

Maria Narcisa Galan made changes - 2019-10-22 08:06

Assignee

Original: Maria Narcisa Galan [ narcisamgalan ]

New: Radi Berkovich [ radislavb ]

Maria Narcisa Galan made changes - 2019-10-23 08:24

Labels

Original: hp-application-automation-tools

New: Octane

Minh Tran made changes - 2019-10-23 22:48

Resolution		New: Fixed [ 1 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]