Regarding jenkins job setup for screenster tests

[Gagana B]

Hi,

I wanted to set up a jenkins job to run screenster test everyday and check the run report can you please help me with the steps to integrate and set up screenster tests on jenkins.

the help doc https://screenster.io/documentation/screenster-ci-client/ was not so usefull for me

thanks in advance


Gagana

[Yevhen Badorov]

Hi Gagana,

The documentation that you mentioned contains all the necessary information for integrating Screenster with CI systems. Some additional info on what exactly doesn't work for you may help us figure out what goes wrong.

You can also check out Screenster support plans at https://screenster.io/support/

Best regards,

Screenster team

[Gagana B]

what does CIFolderPath mean here "-jar <screensterCIFolderPath>/screenster-ci.jar " ?

[Yevhen Badorov]

Gagana,

You can find this info at the top of the documentation page. It says:

where:

• screensterCIFolderPath – path to the folder with the unzipped Screenster CI client.

Best regards,

Screenster team

[Gagana B]

I am trying to run this command on a ubuntu machine and getting below exception. can you help here

Exception in thread "main" io.screenster.ciclient.common.ApiException: HTTP  403: null

[Yevhen Badorov]

Gagana,

Screenster CI client has never been tested in a Linux environment. But it should work thought.

The HTTP response code means that you don't have access to the server. Please check your credentials passed to the CI client.

Best regards,

Screenster team

[Gagana B]

There is no issue with credentials the auth was successful; since its 403 with null; looks like an unhandled exception.

please get it tested once from your technical team and let me know if any more info is needed

[Yevhen Badorov]

Gagana,

How do you know that the auth was successful? The HTTP 403 indicates that you don't have access to the server. It's not an unhandled exception.

By the way, could you please post here the full command you're using without the username and password?

Best regards,

Screenster team

[Gagana B]

The authorization was successful when I ran the command. below is the response I got in cmd

[main] DEBUG io.screenster.ciclient.CiManager:32 - Authorize on Screenster...
 [main] DEBUG io.screenster.ciclient.CiManager:36 - Authorized.


The cmd I ran is mentioned below. let me know if I am missing anything here

java -Duser=<<username>> -Dpassword=<<password>> -Dhost=https://cloud01.screenster.io/ -jar screenster-ci.jar rJZc56ma,MAeHKW4i

[Yevhen Badorov]

Gagana,

Are you using the same email that you're using on this forum instead of  -Duser=<<username>>   ?

Best regards,

Screenster team

[Gagana B]

I am using the email which was used to login to screenster [[prashantks@<<domian>>.com]]

[Yevhen Badorov]

Gagana,

According to our logs, the login attempt was rejected because of the wrong credentials.

Please check your login/password

Best regards,

Screenster team

[Gagana B]

Hi ,
Can we pls get on a quick call to bridge the understanding gap here.
I'm getting authorized when i ran the command

[main] DEBUG io.screenster.ciclient.CiManager:32 - Authorize on Screenster...
 [main] DEBUG io.screenster.ciclient.CiManager:36 - Authorized.

and I'm using the right credentials so can we quickly sync up on what is wrong here and help us in getting this issue resolved.

[Yevhen Badorov]

Hi Gagana,

The reason you're getting the error because you're either providing wrong credentials or you don't have access to the listed projects (or at least to one of them).

Please check the credentials and project hashes.

Best regards,

Screenster team

[Gagana B]

I re-verified the project access and credentials used and the project and suite hashes everything looks fine to me.
What else needs to be checked from my side?
It would be better if we can connect on call and quickly check and t unblock us from this issue.

let me pls know the suitable time for a call

[Yevhen Badorov]

Gagana,

A project with the hash "MAeHKW4i" that you specified doesn't exist on the server. Are you sure the hash is correct?

Best regards,

Screenster team

[Gagana B]

That is the hash code of the suite, I deleted that suite yesterday evening around 6pm IST and  created new suite and using this hash now <<DaKVzxHt>> for suite and this is the project hash <<rJZc56ma>>
so cmd I'm using is 

java -Duser=<<UN>> -Dpassword=<<PW>> -Dhost=https://cloud01.screenster.io/ -jar screenster-ci.jar rJZc56ma,DaKVzxHt

and still facing the same error

Exception in thread "main" io.screenster.ciclient.common.ApiException: HTTP  403: null

[Yevhen Badorov]

Gagana,

You're mixing projects and suites.

Please read the documentation carefully.

java -Duser=<userEmail> -Dpassword=<userPassword> -jar <screensterCIFolderPath>/screenster-ci.jar <projectList> 

where

projectList – the list of project hash codes (you can find them in project settings) separated with commas. Example:
48DaCx01,D3qQ4H75

Also the optional parameters can be passed:

-Dtype=<project>

where

project – by default you are executing selected Screenster projects with your CI jobs but if you set this parameter to suite, you’ll be able to execute selected suites instead.

You can find all these info above in the documentation https://screenster.io/documentation/screenster-ci-client/

Best regards,

Screenster team

[Gagana B]

Got your point,

Find the image of the project hash here  https://prnt.sc/ufiba5 

This is the command used

Gaganas-MacBook-Air:~ gaganab$ java -Duser=<<UN>> -Dpassword=<<PW>> -Dhost=https://cloud01.screenster.io/ -jar screenster-ci.jar rJZc56ma

16:52:22.618 [main] DEBUG io.screenster.ciclient.CiManager:32 - Authorize on Screenster...

16:52:24.787 [main] DEBUG io.screenster.ciclient.CiManager:36 - Authorized.

16:52:24.792 [main] DEBUG io.screenster.ciclient.execution.ExecutionStrategy:49 - Launch 'rJZc56ma' with verification type _default in 'Firefox'...

Exception in thread "main" io.screenster.ciclient.common.ApiException: HTTP  403: null

Still the same exception 

[Gagana B]

Hi good morning,

any updates on this.

awaiting your response

[Yevhen Badorov]

Hi Gagana,

Using Screenster API (directly or via Screenster CI client) is not allowed on the Screenster cloud.

The API is available for local Screenster. You can find more here https://screenster.io/documentation/local-installation/

Best regards,

Screenster team

[Gagana B]

Hi Badorov,

Good morning.

Thanks for the reply. But how do I set up a Jenkins job for the screenster test suite https://screenster.io/documentation/screenster-ci-client/ this doc was not helpful in that case? can you help me with Jenkins setup up please

[Yevhen Badorov]

Hi Gagana,

As I said before, using Screenster API (directly or via Screenster CI client) is not allowed on the Screenster cloud.

The API is available for local Screenster. You can find more on installing Screenster locally here https://screenster.io/documentation/local-installation/

Best regards,

Screenster team