Skip to content

Evaluating https issues in CircleCI (on top of CiscoM31-maven-https#5034

Merged
jimschubert merged 5 commits intomasterfrom
CiscoM31-maven-https
Jan 18, 2020
Merged

Evaluating https issues in CircleCI (on top of CiscoM31-maven-https#5034
jimschubert merged 5 commits intomasterfrom
CiscoM31-maven-https

Conversation

@jimschubert
Copy link
Member

@jimschubert jimschubert commented Jan 18, 2020

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project before.
  • Run the shell script(s) under ./bin/ (or Windows batch scripts under.\bin\windows) to update Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit, and these must match the expectations made by your contribution. You only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the code or mustache templates for a language ({LANG}) (e.g. php, ruby, python, etc).
  • File the PR against the correct branch: master, 4.3.x, 5.0.x. Default: master.
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

@jimschubert
Copy link
Member Author

@sebastien-rosset circleci looks good now. Thanks for working to get that fixed!

jimschubert added a commit that referenced this pull request Jan 19, 2020
* master:
  Evaluating https issues in CircleCI (on top of CiscoM31-maven-h… (#5034)
jimschubert added a commit to jimschubert/openapi-generator that referenced this pull request Jan 19, 2020
This continues on work in OpenAPITools#5033 and OpenAPITools#5034 which convert all http usage
to https to unblock CircleCI builds.

In OpenAPITools#5034, mavenCentral() DSL was updated to explicitly target the https
maven repo because Gradle didn't force TLS 1.2 until v4.8.1 and many of
our examples use earlier versions of Gradle.  The Kotlin meta generator
was missed because it is a .kts build file rather than build.gradle, and
the mustache filename doesn't have kts in it; the file was updated as if
it was build.gradle (groovy syntax).
jimschubert added a commit that referenced this pull request Jan 19, 2020
This continues on work in #5033 and #5034 which convert all http usage
to https to unblock CircleCI builds.

In #5034, mavenCentral() DSL was updated to explicitly target the https
maven repo because Gradle didn't force TLS 1.2 until v4.8.1 and many of
our examples use earlier versions of Gradle.  The Kotlin meta generator
was missed because it is a .kts build file rather than build.gradle, and
the mustache filename doesn't have kts in it; the file was updated as if
it was build.gradle (groovy syntax).
@wing328 wing328 added this to the 4.2.3 milestone Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants