Avoid Duplicate harness_ruby_agent Gem Addition in Parallel Test Steps
next fiscal quarter
B
Burgundy Antelope
In the current implementation, when running parallel Test steps with TI enabled, the harness_ruby_agent gem is added to the Gemfile multiple times. This occurs because the Gemfile is shared across parallel steps, and each step adds the gem individually.
To address this, we propose an enhancement to check the Gemfile for an existing harness_ruby_agent gem declaration before adding it. This will prevent duplicate entries and ensure the gem is only added if it's not already present.
This enhancement will improve the handling of Gemfiles when running parallel Test steps in TI.
Log In
N
Nofar Bluestein
next fiscal quarter
B
Burgundy Antelope
As reported earlier in https://support.harness.io/hc/en-us/requests/70303?page=1 so I'm copying the comments from there.
At the moment it just causes bundler warnings because the added gem declarations match. It's unknown if this will cause bundler to fail in the future, so it's best to heed the warnings and fix the issue while you're aware of it.
So, for now it doesn't break things, and only makes debugging pipeline failures more difficult because of the extra warnings.
N
Nofar Bluestein
pending feedback
N
Nofar Bluestein
Thank you for your valuable feedback.
To better assess the priority of this request, could you please clarify if you’ve noticed any functional or performance impact on Test Intelligence (TI) when the harness_ruby_agent gem is added multiple times to the Gemfile in parallel Test steps?