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
bundle install surprisingly resolves dependencies for all gems in a Gemfile,
even gems in excluded groups. As a result, the "release prep" workflow failed
trying to resolve gems that are only needed when running task acceptance tests.
In Gemfile:
bolt was resolved to 4.0.0, which depends on
orchestrator_client was resolved to 0.7.2, which depends on
faraday was resolved to 1.9.0, which depends on
faraday-patron was resolved to 2.0.2, which depends on
patron
There are multiple dependency chains causing this:
bolt (5.0.1) → r10k (>= 3.10, < 5)
r10k (3.16.2) → puppet_forge (>= 2.3.0, < 4.0.0)
puppet_forge (3.2.0) → faraday (~> 1.3)
Also
beaker-abs (1.1.0) → vmfloaty (>= 1.0, < 2)
vmfloaty (1.8.1) → faraday (~> 1.5, >= 1.5.1)
This commit moves the beaker related gems to task_spec/Gemfile, similar to what
is done for acceptance/Gemfile.
It sets Gemfile to be unmanaged so we don't regress on 7246266 the next
time we `pdk update`
It updates the task_acceptance_tests GH workflow to run `bundle install` in
the `task_spec` directory.
One important change is you no longer need to set GEM_BOLT as an environment
variable **before** running "bundle install".
0 commit comments