Update TeamCity CI to use IntelliJ 2019.3
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
The problem that blocks updating our inspections pipeline from IntelliJ 2017.2.4 (https://youtrack.jetbrains.com/issue/IDEA-215273) is marked as solved in IntelliJ 2019.3. IntelliJ 2019.3 is expected to be released in late 2019. Eventually, this version should become available in [TeamCity configuration](https://teamcity.jetbrains.com/admin/editRunType.html?id=buildType:OpenSourceProjects_Druid_Inspections&runnerId=RUNNER_1393&cameFromUrl=%2Fadmin%2FeditBuildRunners.html%3Fid%3DbuildType%253AOpenSourceProjects_Druid_Inspections%26init%3D1&cameFromTitle=) (if you a Druid committer but cannot open this page, please [acquire administrator rights](https://github.com/apache/incubator-druid/blob/master/dev/teamcity.md#becoming-a-project-administrator)):
Contributor guide
Research direction
Start by reading dev/teamcity.md, then inspect the linked TeamCity configuration for the Druid inspections build. Confirm the IntelliJ version currently used and update the configuration to IntelliJ 2019.3 once it is available; done means the inspections pipeline uses the requested version.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100