Skip to content
GitLab

Publish to gradle plugin prior to sonatype

Merged Jim Schubert requested to merge evaluate-gradle-publish-order into master

PR checklist

  • Read the contribution guidelines.
  • Ran the shell script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh, ./bin/openapi3/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in .\bin\windows\.
  • Filed the PR against the correct branch: master, 3.4.x, 4.0.x. Default: master.
  • Copied the technical committee to review the pull request if your PR is targeting a particular programming language.

Description of the PR

Publishing to the gradle plugin portal after Sonatype will fail on artifacts unsupported by the portal (asc, sources, etc). This attempts to publish to the portal first, to avoid needing to do a clean/publish after the Sonatype artifacts are published.