-
Notifications
You must be signed in to change notification settings - Fork 293
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix create-builder with multiple buildpacks of same id #459
Conversation
- Remove comptability layer (except for lifecycle symlink) - Remove comptability metadata from builder creation - Introduce COMPILE_PACK_WITH_VERSION env variable for running acceptance tests - Add pack_previous_fixtures_overrides directory to enable overriding fixtures used for previous pack versions Signed-off-by: Andrew Meyer <ameyer@pivotal.io> Signed-off-by: Natalie Arellano <narellano@pivotal.io>
44eedd5
to
cb76022
Compare
acceptance/acceptance_test.go
Outdated
defer os.RemoveAll(tmpPreviousPackFixturesPath) | ||
|
||
h.RecursiveCopy(t, previousPackFixturesPath, tmpPreviousPackFixturesPath) | ||
h.RecursiveCopy(t, filepath.Join("testdata", "pack_previous_fixtures_overrides"), tmpPreviousPackFixturesPath) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I understand why this is needed. Maybe it's worth creating a README.md
in that directory that entails exactly why you would put stuff in that directory.
Also, would it not suffer from the same problems we originally had with "pack_previous" in which you had to update the repo after a release because "current" was (de)moted to "previous"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would vote on punting on the docs so we can get this out. Thoughts @jromero?
It won't suffer from the same problems if it just has the version-related files like it has now. But true, it could suffer in general. Hopefully these are the only type of files we'd need. We'll keep an eye on this.
- Remove compat unit tests that are no longer needed - Only add the compat layer path to the layers for an image if the compat.tar exists - `make acceptance` should only require previous pack fixtures to be a valid directory if the env variable is set Signed-off-by: Natalie Arellano <narellano@pivotal.io> Signed-off-by: Andrew Meyer <ameyer@pivotal.io>
- Place lifecycle symlink in lifecycle layer since it is all that is left of the compat logic Signed-off-by: Andrew Meyer <ameyer@pivotal.io>
Resolves #430
for previous pack versions
Signed-off-by: Natalie Arellano narellano@pivotal.io
Signed-off-by: Andrew Meyer ameyer@pivotal.io