using agent-js-postman in a docker container does not allow launch to end #71
Assignees
Comments
|
Any ideas here guys? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
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:
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!
The text was updated successfully, but these errors were encountered: