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

build schema registry signed assemblies #1000

Merged
merged 7 commits into from
Aug 20, 2019
Merged

build schema registry signed assemblies #1000

merged 7 commits into from
Aug 20, 2019

Conversation

mhowlett
Copy link
Contributor

@mhowlett mhowlett commented Jul 1, 2019

initial PR to test CI build of signed schema registry related assemblies. not yet for review

appveyor.yml Outdated
@@ -11,24 +11,28 @@ environment:

build_script:
- cmd: SET STRONG_NAME_OPTIONS=/p:SignAssembly=true;AssemblyOriginatorKeyFile=Confluent.Kafka.snk;PackageId=Confluent.Kafka.StrongName;Title=Confluent.Kafka.StrongName;AssemblyName=Confluent.Kafka.StrongName;BaseOutputPath=bin-sn\
- cmd: SET STRONG_NAME_OPTIONS_SR=/p:SignAssembly=true;AssemblyOriginatorKeyFile=Confluent.SchemaRegistry.snk;PackageId=Confluent.SchemaRegistry.StrongName;Title=Confluent.SchemaRegistry.StrongName;AssemblyName=Confluent.SchemaRegistry.StrongName;BaseOutputPath=bin-sn\
Copy link
Contributor

Choose a reason for hiding this comment

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

what's with the trailing backslash?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i don't know, it's probably not necessary, this is just copying from the Confluent.Kafka case which works.

not for review. there's a lot more to be done here. this is for testing only.

@mhowlett
Copy link
Contributor Author

following the advice here: https://www.pedrolamas.com/2018/09/11/start-strong-naming-your-assemblies/ , this PR introduces signing on all assemblies distributed via nuget - Confluent.Kafka, Confluent.SchemaRegistry and Confluent.SchemaRegistry.Serdes, and no longer builds Confluent.Kafka.StrongName (which is now irrelevant).

additionally, the associated unit test assemblies are signed since this acts as a test that all dependencies (including the above) are signed.

@mhowlett
Copy link
Contributor Author

note also: confluentinc/avro#16 (comment)

this pr resolves: #973 - @longbaochenlong @zhoubo56 , feel free to confirm.

@mhowlett
Copy link
Contributor Author

and @edenhill - ready for your OK.

@mhowlett mhowlett changed the base branch from 1.1.x to 1.2.x August 20, 2019 20:27
Copy link
Contributor

@edenhill edenhill left a comment

Choose a reason for hiding this comment

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

LGTM, but some batch file inconsistencies

appveyor.yml Outdated
- cmd: IF "%APPVEYOR_REPO_TAG%" == "true" (dotnet pack src/Confluent.SchemaRegistry.Serdes/Confluent.SchemaRegistry.Serdes.csproj -c %CONFIGURATION%)
- cmd: IF NOT "%APPVEYOR_REPO_TAG%" == "true" (dotnet pack src/Confluent.SchemaRegistry.Serdes/Confluent.SchemaRegistry.Serdes.csproj -c %CONFIGURATION% --version-suffix ci-%APPVEYOR_BUILD_NUMBER%)

- cmd: IF "%APPVEYOR_REPO_TAG%" == "true" dotnet pack src/Confluent.SchemaRegistry.Serdes/Confluent.SchemaRegistry.Serdes.csproj -c %CONFIGURATION%
Copy link
Contributor

Choose a reason for hiding this comment

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

Inconsistency: the IF statements above have () around the dotnet command

@mhowlett mhowlett merged commit 14e0d0e into confluentinc:1.2.x Aug 20, 2019
@mhowlett
Copy link
Contributor Author

@longbaochenlong @zhoubo56 - the 1.2.0-RC1 packages are now on nuget and should all now be strong named. feel free to test this and confirm here. thanks!

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