-
Notifications
You must be signed in to change notification settings - Fork 0
As a pack CLI user, I must select a builder with: pack set-default-builder #36
Comments
To solution a tad, I think one way we could address this is to leave the initial default builder |
TODO: add more detail for each image (e.g., bionic vs. cflinuxfs3, buildpacks included), also recommend |
* pack build will provide suggestions if no default builder is set [buildpacks/roadmap#36] Signed-off-by: Danny Joyce <djoyce@pivotal.io> Signed-off-by: Emily Casey <ecasey@pivotal.io>
This feature is essentially done in master of pack. However, I temporarily commented out the actual references to the suggested builders b/c neither currently work with master of pack We should probably hold on acceptance until the builders work... |
Per speaking with @djoyahoy, holding off testing this until the CF/heroku suggestions are truly randomized. |
After discussion with @sclevine @nebhale @jkutner @hone It seems that we would like to take "Samples Builders", section out of the suggestions. This raises an interesting question... our acceptance tests run against the samples builder, once the samples builder is no longer a default or even a suggested builder this doesn't seem as appropriate any more. What should we do instead? Is testing against a builder created with |
* actually print suggested builders (builders are not guaranteed to work until pack beta release) [buildpacks/roadmap#36] Signed-off-by: Emily Casey <ecasey@pivotal.io>
* adds additional suggested builders * adds description of suggested builders * provide user with tip to try inspect-builder command [buildpacks/roadmap#36] Signed-off-by: Emily Casey <ecasey@pivotal.io>
@ekcasey @ameyer-pivotal @djoyahoy Any pointers for how to mimic this scenario on my machine? |
@mgibson1121 you can delete the |
This passes acceptance |
Acceptance Criteria
When I install the
pack
CLI on a workstation that has not had v0.1.0 installed at any pointAnd
pack set-default-builder
has not been run with pack v0.1.0And I run
pack build
orpack run
Then I see:
Notes:
The text was updated successfully, but these errors were encountered: