-
Notifications
You must be signed in to change notification settings - Fork 286
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
Validate buildpack API version #254
Milestone
Comments
jromero
added a commit
that referenced
this issue
Sep 5, 2019
* Default lifecycle during `create-builder` if no version or URI is specified Resolves #254 Signed-off-by: Javier Romero <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
jromero
added a commit
that referenced
this issue
Sep 6, 2019
* Default lifecycle during `create-builder` if no version or URI is specified Resolves #254 Signed-off-by: Javier Romero <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
jromero
added a commit
that referenced
this issue
Sep 6, 2019
* Default lifecycle during `create-builder` if no version or URI is specified Resolves #254 Signed-off-by: Javier Romero <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
jromero
added a commit
that referenced
this issue
Sep 9, 2019
* Default lifecycle during `create-builder` if no version or URI is specified Resolves #254 Signed-off-by: Javier Romero <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
jromero
added a commit
that referenced
this issue
Sep 9, 2019
* Default lifecycle during `create-builder` if no version or URI is specified Resolves #254 Signed-off-by: Javier Romero <[email protected]> Signed-off-by: Andrew Meyer <[email protected]>
Looks good:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pack create-builder
Buildpack incompatible with lifecycle
Given I have a buildpack.toml for buildpack X with an
api
string field"0.x"
Given A lifecycle with a descriptor file specifying that the lifecycle has Buildpack API other than
0.x
When I run
pack create-builder
while targeting the given lifecycleThen I see an error message:
Buildpack compatible with lifecycle
Given I have a buildpack.toml for buildpack X with an
api
string field"0.x"
When I run
pack create-builder
while targeting lifecycle with a matching Buildpack API versionThen the command completes successfully
pack build
Buildpack incompatible with builder (lifecycle)
Given I have a
buildpack.toml
for buildpack X with anapi
string field"0.x"
Given A builder that specifies a lifecycle with Buildpack API other than
"0.x"
in it's metadataWhen I run
pack build
while targeting the given builderThen I see an error message:
Buildpack compatible with builder (lifecycle)
Given I have a
buildpack.toml
for buildpack X with anapi
string field equal to"0.x"
Given A builder that specifies a lifecycle with Buildpack API
"0.x"
in it's metadataWhen I run
pack build
while targeting the given builderThen the command completes successfully
Missing api metadata
Given a
buildpack.toml
with a missingapi
fieldThen the
api
shall be assumed to be0.1
Given a lifecycle with a missing descriptor file
Then the lifecycles Buildpack API shall be assumed to be
0.1
Given a builder with missing lifecycle api metadata
Then the lifecycles Buildpack API shall be assumed to be
0.1
The text was updated successfully, but these errors were encountered: