Skip to content
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

[pdqtest-2.0] - tweak PDK integration to avoid churn #50

Closed
GeoffWilliams opened this issue Sep 19, 2018 · 1 comment
Closed

[pdqtest-2.0] - tweak PDK integration to avoid churn #50

GeoffWilliams opened this issue Sep 19, 2018 · 1 comment

Comments

@GeoffWilliams
Copy link
Member

From slack chat on puppet #testing:

create Gemfile.project and then in Makefile and make.ps1 copy it over to Gemfile.local. When these scripts run, die with an error if Gemfile.local already exists with different content otherwise proceed to bundle exec.... To get the initial set of files, do pdk new module --skip-interview in a tempdir and copy the files I want during pdqtest init. pdqtest init will also drop a .sync.yml to prevent pdk update clobbering integrations in .travis.yml and bitbucket-pipelines.yml ... get vanilla PDK files when you do pdk new module and your not wanting to use PDQTest.

Also if the Gemfile already exits on a project created with PDK, just leave it alone and never touch it

GeoffWilliams added a commit that referenced this issue Sep 19, 2018
Rewrite PDK integration to address #50 and update docs
@GeoffWilliams
Copy link
Member Author

fixed in 1.9.9beta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant