• Type: Bug
• Resolution: Not A Defect
• Priority: Blocker
• Component/s: core
• Labels:

  • automation
  • configuration
  • jenkins
  • results
  • testing
• Environment:

  Hide

  jenkins 2.89.4
  Windows Server 2012 R2 Standart - X64 (.net 3.5)
  Java 1.8.0_161
  Chrome 63.0.3239.132 - 64 bits
  
  Plugins:
  bouncycastle API Plugin2.16.2
  Command Agent Launcher Plugin 1.2
  jQuery plugin 1.12.4-0
  Node and Label parameter plugin 1.7.2
  Pipeline: API 2.25
  Pipeline: Job 2.17
  Pipeline: Step API 2.14
  Pipeline: Supporting APIs 2.18
  SCM API Plugin 2.2.6
  Script Security Plugin 1.41
  Structs Plugin 1.14
  Token Macro Plugin 2.3

  Show

  jenkins 2.89.4 Windows Server 2012 R2 Standart - X64 (.net 3.5) Java 1.8.0_161 Chrome 63.0.3239.132 - 64 bits Plugins: bouncycastle API Plugin2.16.2 Command Agent Launcher Plugin 1.2 jQuery plugin 1.12.4-0 Node and Label parameter plugin 1.7.2 Pipeline: API 2.25 Pipeline: Job 2.17 Pipeline: Step API 2.14 Pipeline: Supporting APIs 2.18 SCM API Plugin 2.2.6 Script Security Plugin 1.41 Structs Plugin 1.14 Token Macro Plugin 2.3

[JENKINS-49575] Tests run in background when installing as a service - Windows Server 2012

Collapse comment: Oleg Nenashev added a comment - 2018-02-23 17:17

Oleg Nenashev added a comment - 2018-02-23 17:17

Not a defect, this is a default behavior.
You can setup the interactive mode in jenkins.xml: https://github.com/kohsuke/winsw/blob/master/doc/xmlConfigFile.md#interactive

Expand comment: Oleg Nenashev added a comment - 2018-02-23 17:17

Oleg Nenashev added a comment - 2018-02-23 17:17 Not a defect, this is a default behavior. You can setup the interactive mode in jenkins.xml: https://github.com/kohsuke/winsw/blob/master/doc/xmlConfigFile.md#interactive