Skip to content

chore: license checking in posttest #2785

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

Closed
wants to merge 1 commit into from
Closed

Conversation

jinwoo
Copy link

@jinwoo jinwoo commented Jan 8, 2018

This can't be checked in until a license issue with
@google-cloud/common-grpc is fixed. It has a transitive dependency,
jsonify, which has "Public Domain" as its license. But Public Domain
is not a valid license for Google's open source projects.

Also the 'log-driver' package is whitelisted.

Additonal minor changes:

  • add the version field: this is a required field
  • fix the private field: this is a boolean field. "true" --> true.
  • package-lock.json is committed.

This can't be checked in until a license issue with
`@google-cloud/common-grpc` is fixed. It has a transitive dependency,
`jsonify`, which has "Public Domain" as its license. But Public Domain
is not a valid license for Google's open source projects.

Also the 'log-driver' package is whitelisted.

Additonal minor changes:
- add the `version` field: this is a required field
- fix the `private` field: this is a boolean field. "true" --> true.
- package-lock.json is committed.
@jinwoo jinwoo requested a review from lukesneeringer as a code owner January 8, 2018 19:11
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jan 8, 2018
@jinwoo
Copy link
Author

jinwoo commented Jan 8, 2018

The license checking fails due to jsonify. The issue is tracked by #2786.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 56a656e on jinwoo:jsgl into 0afd915 on GoogleCloudPlatform:master.

@jinwoo
Copy link
Author

jinwoo commented Jan 8, 2018

Huh? All CI tests passed, which is unexpected. They should've failed in the posttest phase.

Looking at the test setup, it looks like none of the tests are actually run. Test scripts just run lint and the build script. Is this intended?

@jinwoo
Copy link
Author

jinwoo commented Jan 8, 2018

@stephenplusplus Can you check the CI setup? None of the tests seem to run on CI.

@stephenplusplus
Copy link
Contributor

Hey @jinwoo, we just branched common-grpc out into its own repo: https://github.com/googleapis/nodejs-common-grpc. Can you add the license checking changes there? I'm not sure what the fate of this repo will be, but that was the last bit of code we had here.

@stephenplusplus stephenplusplus removed the cla: yes This human has signed the Contributor License Agreement. label Jan 9, 2018
@jinwoo
Copy link
Author

jinwoo commented Jan 9, 2018

Got it. Branching out common-grpc seems like the way to go. Thanks.

@jinwoo jinwoo deleted the jsgl branch January 9, 2018 17:54
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.

4 participants