Modifying engine cart CI build parameterization #4256
Merged
+2
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At present, EngineCart's parsing of
.engine_cart.yml
will overwritethe
ENGINE_CART_RAILS_OPTIONS
set in CircleCI (seecbeer/engine_cart/102 for some details). The present overwrite
behavior is reasonable. As the removed
.engine_cart.yml
targetedpre-Rails 5 behavior, I opted to remove it.
In doing so, this would now "activate" the
.circleci/config.yml
declaration of
ENGINE_CART_RAILS_OPTIONS
. As we have coffee script inHyrax (for better or worse) and we have ActionCable usage, I needed to
revisit the now activated parameters.
Note: This is in preparation for allowing PostgreSQL as the database
for CircleCI.
As this impacts the
.internal_test_app
generation, I also needed tobump the Regen number.
TL;DR: A 4 year old file that we no longer need is silently trampling
on a CI variable. That CI variable has likely not been used. It now will
be used, but needed modifications to reflect that usage.
I hope this works, as iterating on the CI process is always time
consuming as it requires coordination of remote resources.
@samvera/hyrax-code-reviewers