Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

using agent-js-postman in a docker container does not allow launch to end #71

Open
Christopher-Kane opened this issue Nov 16, 2021 · 1 comment
Assignees

Comments

@Christopher-Kane
Copy link

Hey everyone!

I appreciate whoever is taking a look at this bug issue within github. I will try to describe the issue as best I can.

I managed to get agent-js-postman to work locally as expected in a local windows jenkins instance where it finishes with

Finish launch cq3o6sokw12fq70
Success finish launch cq3o6sokw12fq70

This is exactly what I want to see and the launch appears as expected within report portal.

After I saw it was working as I wanted to locally without Docker, I decided to build a docker image with agent-js-postman since that is currently how all if not most of our automation is executed today. Once I built the image and got it working, I ran the exact same automation that I did locally but from within docker and a non-local jenkins instance.

Instead of eventually seeing a "finish launch" and "success finish launch", the last lines in the console output in jenkins are:

Finish test item 40599u1kw2eb6sz
Success finish item 40599u1kw2eb6t0
Success finish item 40599u1kw2eb6sw
Success finish item 40599u1kw2eb6sr
Success finish item 40599u1kw2eb6st
Success finish item 40599u1kw2eb6su
Success finish item 40599u1kw2eb6sy
Success finish item 40599u1kw2eb6sv
Success finish item 40599u1kw2eb6sz
Success finish item 40599u1kw2eb6ss
Success finish item 40599u1kw2eb6sx

Which you can see does not include the "finish launch" or "success finish launch" which seems to be what report portal is looking for to determine when a launch is finished. Additionally, pressing force finish from the UI is not a workaround as it appears the job finishes before the automation itself is actually complete, which means I end up missing a decent amount of tests that I would need to include if I were reporting on these results.

Are there any suggestions or things that I could try to have both my local instance of jenkins without docker and the non-local jenkins instance with Docker finish with the exact same results?

Please let me know what information I can provide to help with this issue. Thanks so much!

@Christopher-Kane
Copy link
Author

Any ideas here guys?

@AmsterGet AmsterGet self-assigned this Nov 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants