Skip to content

app.json "test" script for Heroku CI #406

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

Merged
merged 1 commit into from
Mar 24, 2017

Conversation

dzuelke
Copy link
Contributor

@dzuelke dzuelke commented Nov 28, 2016

This allows tests to automatically run in the (currently in beta) Heroku CI service.

@dzuelke
Copy link
Contributor Author

dzuelke commented Nov 29, 2016

poke :)

@dzuelke
Copy link
Contributor Author

dzuelke commented Nov 30, 2016

Any chance to get this merged before SymfonyCon begins @javiereguiluz? :)

@javiereguiluz
Copy link
Member

I know nothing about Heroku ... so I cannot review or test this myself. I was waiting to receive any approval/reject comment from anyone.

Luckily you are trustworthy, so I guess I'll have to merge this blindly.

"postdeploy": "php bin/console doctrine:schema:create && php bin/console doctrine:fixtures:load -n"
"postdeploy": "php bin/console doctrine:schema:create && php bin/console doctrine:fixtures:load -n",
"test-setup": "php bin/console doctrine:schema:create && php bin/console doctrine:fixtures:load -n",
"test": "phpunit"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any chance to use ./vendor/bin/phpunit here since we lock PHPUnit's version in the dev dependencies?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

$(composer config bin-dir) is on $PATH on Heroku, so it uses the right one. I can change it though.

This actually begs the related question if it might be a good best practice for this project to, in composer.json, have a test entry in scripts that says phpunit? Then people can run composer test, similar to how they'd do with NPM ;)

@bocharsky-bw
Copy link
Contributor

Has CI already worked on Heroku for users? I triggered an error in unit tests here, but Heroku still successfully build the app without any errors.

Should we wait until this feature will be stable and available for all Heroku users? I see you mentioned it's currently in beta.

@stof
Copy link
Member

stof commented Nov 30, 2016

@dzuelke is there any doc about Heroku CI anywhere ? I haven't found any

@dzuelke
Copy link
Contributor Author

dzuelke commented Nov 30, 2016

It's in private beta, @bocharsky-bw and @stof. I'm also happy to wait with this PR until it's GA, @javiereguiluz :)

@dzuelke
Copy link
Contributor Author

dzuelke commented Mar 23, 2017

This is now in public beta, so merge away, @stof or @bocharsky-bw :)

@javiereguiluz
Copy link
Member

Thank you @dzuelke.

@javiereguiluz javiereguiluz merged commit 1e46fd1 into symfony:master Mar 24, 2017
javiereguiluz added a commit that referenced this pull request Mar 24, 2017
This PR was merged into the master branch.

Discussion
----------

app.json "test" script for Heroku CI

This allows tests to automatically run in the (currently in beta) Heroku CI service.

Commits
-------

1e46fd1 app.json "test" script for Heroku CI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants