Hello Dorin,

I had been typing name of Domain and Project, which I select when I login to ALM, so these are without any whitespace.

Hello kovacsa,

What MicroFocus plugin version and what ALM server version are you using?

Dorin.

Hello kovacsa,

1. If possible, please provide here a short video recording of the steps you are using, for both scenarios:
   • from Jenkins side (Job config page and Console output results)
   • from ALM side (just Authenticate and Login actions from Internet Explorer)
2. For best support please open a ticket at:
   https://www.microfocus.com/en-us/support/login or
   https://support.microfocus.com/contact/swgrp.html
   Or, propose a date/time when you are available online so we can schedule a support session with you. 

Thank you,
Dorin.

Hello,

versions: Jenkins 2.318, ALM 12.55, Micro Focus Application Automation Tools 7.0.

Sorry, but I can't share video.

Hello kovacsa,

How do you like to proceed further?

Would you open a ticket online or prefer to schedule a support session?

Hello Akos,

On what Node do you build your Jenkins Job? Are you using the master or are you using a Node connected to your Jenkins server?

You can parametrize jobs, at the configuration, to chose where to build your Jenkins job. (see attachments)

"Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building on master in workspace .... "

Hello hildaboth,

I use built-in node, which is Windows Server 2012 R2 (amd64). There is UFT and also Jenkins installed on this node.

dorin7bogdan : How could I check ALM logs, to see where is connectivity problem.

Hello kovacsa,

Since the ALM team is more able to provide help about ALM, please open a ticket at:
https://www.microfocus.com/en-us/support/login or
https://support.microfocus.com/contact/swgrp.html

Thank you for understanding.

Hello kovacsa,

From ALM team I got the following information: 

The problem might be the user is not belonged to the project.
The Login passed, that means username and password are good.
But the Connect to project failed.
There are 2 possible causes:
  1. domain/project names are not right
  2. the login user does not belong to the project.

If you are sure both 1 and 2 are valid, then:

  1. Enable Webgate logs on the Jenkins node: 

• The Webgate log tool is from <server url>/qcbin/Apps/

• Create the folder C:\WebGateLogs and apply these changes:
  

  2. In ALM site administrator,  set ALM Server / qc log and sa log both to "DEBUG" level:

The location of the ALM server logs can be found in the ALM site administrator UI when you enable them.

  3. reproduce the issue once and collect the webgate log on the Jenkins node machine and the ALM server qc/sa logs on the ALM server machine.