search

mcdcorp / opentest

Open source test automation tool for web applications, mobile apps and APIs
https://getopentest.org
MIT License
447 stars 107 forks source link

Actor self termination after session is completed #521

Closed TripleG closed 2 years ago

TripleG commented 2 years ago

Hi,

Scenario:

I want to have a Jenkins nodes under a label - let's say windows-chrome. Under this label I want to group all nodes which will execute tests on Windows Chrome. This allows us to have easy scalability by just adding new nodes under the same label. The problem is that when I tell Jenkins to run a test template on windows-chrome label, it will select any of the free nodes. On the selected node an actor process will be started. But I don't want the actor process to remain running after the test execution is done. I cannot kill the actor reliably, because I don't know on which exact node it was started(any from the group can be selected).

What do you think of adding a configuration option in actor.yaml that will allow the actor process to self terminate after session is completed, i.e it can be used only once to run a session?

If we have such option, we'll not have to worry to cleanup the actor processes explicitly.

TripleG commented 2 years ago

@adrianth , do you have any thoughts on that?

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.