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

Update travis-ci config #2

Merged
merged 4 commits into from
Jul 13, 2014
Merged

Conversation

aotd1
Copy link

@aotd1 aotd1 commented Jul 9, 2014

Added php 5.6 and hhvm builds,
Code coverage report (you can see sample here),
Automatic code style check with php_codesniffer - just run ./runTests.sh

@aotd1
Copy link
Author

aotd1 commented Jul 9, 2014

Oh, after run ./runTests.sh you can see coverage report in .reports/index.html =)

@zzantares
Copy link
Owner

Isn't scrutinizer-ci a paid service? how will this work if I'm not going to pay for this service?, I guess works ok in your fork since is linked with your github account, but in my side, if I merge your commits, that will not work in my repo, isn't it?

@aotd1
Copy link
Author

aotd1 commented Jul 9, 2014

It's free for Open-Source Repositories.
If you link your github repo it start working for you as static analysis tool. It subscribes on repository commits. Scrutinizer Code Quality

For code coverage report you need to edit build config https://scrutinizer-ci.com/g/ZzAntares/ProxmoxVE/settings/build-config

imports:
    - php
tools:
    external_code_coverage: true

Travis generate coverage report and send it to scrutinizer-ci =) Code Coverage

@zzantares
Copy link
Owner

Thanks Alexey, can't review this until today.

zzantares added a commit that referenced this pull request Jul 13, 2014
Update travis-ci config adding scrutinizer-ci
@zzantares zzantares merged commit 3dd398b into zzantares:master Jul 13, 2014
@mm580486 mm580486 mentioned this pull request Nov 20, 2020
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

Successfully merging this pull request may close these issues.

2 participants