Skip to content

build: bump up Gradle to v6#1061

Merged
KengoTODA merged 26 commits into
masterfrom
gradle-6
Jan 16, 2020
Merged

build: bump up Gradle to v6#1061
KengoTODA merged 26 commits into
masterfrom
gradle-6

Conversation

@KengoTODA

@KengoTODA KengoTODA commented Jan 16, 2020

Copy link
Copy Markdown
Member
  • configure Gradle wrapper to use Gradle v6.1
  • follow the official guideline to migrate from v5 to v6
    • Replace java plugin with java-library that provides suggested api and implementation
    • replace compile and testCompile configuration with api, implementation and testImplementation
    • update configuration related to jacoco
  • upgrade spotless to support the latest Gradle

@KengoTODA KengoTODA self-assigned this Jan 16, 2020
@KengoTODA KengoTODA marked this pull request as ready for review January 16, 2020 10:39
@KengoTODA KengoTODA changed the title build: bump up Gradle to v6 WIP: build: bump up Gradle to v6 Jan 16, 2020
@KengoTODA

Copy link
Copy Markdown
Member Author

This change affects the <scope> of dependencies: jaxen and Saxon becomes runtime package.
I think it is OK because usage of them isn't exposed on any SpotBugs API.

  <dependency>
    <groupId>jaxen</groupId>
    <artifactId>jaxen</artifactId>
    <version>1.1.6</version>
    <scope>runtime</scope>
  </dependency>
  <dependency>
    <groupId>net.sf.saxon</groupId>
    <artifactId>Saxon-HE</artifactId>
    <version>9.9.1-2</version>
    <scope>runtime</scope>
  </dependency>

@KengoTODA KengoTODA changed the title WIP: build: bump up Gradle to v6 build: bump up Gradle to v6 Jan 16, 2020
@KengoTODA

Copy link
Copy Markdown
Member Author

the coverage info is not generated as expected, I will try to fix it.

@KengoTODA KengoTODA changed the title build: bump up Gradle to v6 WIP: build: bump up Gradle to v6 Jan 16, 2020
@sonarqubecloud

Copy link
Copy Markdown

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@KengoTODA KengoTODA changed the title WIP: build: bump up Gradle to v6 build: bump up Gradle to v6 Jan 16, 2020
@KengoTODA

Copy link
Copy Markdown
Member Author

Confirmed that jacocoRootReport works as expected in this build:

https://travis-ci.org/spotbugs/spotbugs/jobs/637976286?utm_medium=notification&utm_source=github_status

@spotbugs/everyone this PR is ready to review, please check.
The commit history is not beautiful, better to squash-and-merge. ;)

@KengoTODA KengoTODA merged commit f716edc into master Jan 16, 2020
@KengoTODA KengoTODA deleted the gradle-6 branch January 16, 2020 23:58
KengoTODA added a commit that referenced this pull request Jun 7, 2020
this feature was disabled by #1061 unexpectedly
KengoTODA added a commit that referenced this pull request Jun 8, 2020
* ci: build SpotBugs with Eclipse in PR

* ci: run SonarQube analysis on the GitHub Actions

* ci: ensure sonarqube task runs after jacocoRootReport task

* ci: fetch all histories in the target branch

to avoid the following error from :sonarqube task

> Could not find ref: master in refs/heads, refs/remotes/upstream or refs/remotes/origin

* ci: upgrade scanner-api to fix connection leak bug

SonarSource/sonar-scanner-java-library@c0c757f

* ci: add GITHUB_TOKEN to build, to use GitHub Checks in PR

* ci: fix checkout config

* ci: omit verbose log of wget to make the build log enough small

* ci: upgrade scanner-api to fix connection leak bug

* ci: enable build scan to confirm that the updated sonar-scanner-api is used

https://guides.gradle.org/creating-build-scans/

* ci: try to bump up sonar-scanner-engine to the latest ver.

* ci: try to git-fetch to avoid SQ error

https://community.sonarsource.com/t/error-warn-could-not-find-ref-develop-in-refs-heads-or-refs-remotes-origin-after-updating-to-7-6/6420/3\?u\=kengotoda

* build: add com.gradle.enterprise plugin to stabilize builds on Travis

* ci: simplify SQ related build script

* ci: remove build-scan related config to stabilize build on Travis CI

* Revert "ci: remove build-scan related config to stabilize build on Travis CI"

This reverts commit f7a55ec.

* ci: fetch all histories in the target branch

to avoid the following error from :sonarqube task

> Could not find ref: master in refs/heads, refs/remotes/upstream or refs/remotes/origin

* ci: use token to pass Git auth

https://github.blog/2012-09-21-easier-builds-and-deployments-using-git-over-https-and-oauth/\#using-oauth-with-git

* ci: sign Eclipse plugin

* ci: migrate pages deployment to Actions

* ci: simplify the sign procedure on the master branch

refs spotbugs/spotbugs-gradle-plugin@ef626ad

* ci: stop using Travis CI for better performance

* ci: disable needless build scan

* build: introduce Gradle Build Cache

this feature was disabled by #1061 unexpectedly

* ci: enable buildscan temporally

* ci: run CI build in parallel

* build: bump up Gradle to 6.5

* ci: disable build cache and build scan

to enable build cache, we need to keep the server running,
with enough RAM. but it is too expencive to keep, and its effect
is not so big.

* docs: replace the build badge in README.md
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