You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the browserstack local connection process doesnt been killed properly after the bamboo job is done / finish executing some test against the browserstack. As attached image, the process seem like been added each time the bamboo job been triggered and leave the old one. This will cost the process redundant even thought it was idle.
Browerstack plugin version : 1.0.4
Bamboo version : 6.5
The text was updated successfully, but these errors were encountered:
There is two separate issue in here and #8 where that ticket is mainly for only specific bamboo job should start/trigger the Browserstack Local plugin and not all available Bamboo job.
I noticed that the browserstack local connection process doesnt been killed properly after the bamboo job is done / finish executing some test against the browserstack. As attached image, the process seem like been added each time the bamboo job been triggered and leave the old one. This will cost the process redundant even thought it was idle.
Browerstack plugin version : 1.0.4
Bamboo version : 6.5
The text was updated successfully, but these errors were encountered: