Repository navigation
Add instruction for building the plugin for different environments - #69
Merged
Merged
Conversation
Also correct the required Java version and the distribution path in CONTRIBUTING.md.
Add a warning about overlapping builds and the way to build in a separate worktree, use the real error messages in troubleshooting, and state the expected disk use and build time.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
documentation/BuildingPlugin.md, which covers how to build one or all environments (252–263), the build options, checking and installing a build, and common failures.CONTRIBUTING.md: the required Java version is 21, not 17, and the zip is written tointellij-plugin/build/distributions, notbuild/distributions. It now links to the new doc.Documentation only: no code or build changes.
Verification
Run on this branch in a worktree that no other build was using:
buildPluginpasses for252,253,261,262and263. In each zip, the version and build range inplugin.xmlmatch its environment.buildPlugin -PbaseIDE=clionon261, run straight after263, also produces correct metadata.verifyPluginon261reports the plugin as compatible.environmentNamefails with the message the doc quotes.helpinstead ofbuildPlugin), and an unquoted-PpluginVersion=2026.22.1does split at the dot.Not run: the
run*tasks, installing a zip in an IDE, andbaseIDE=pycharmorbaseIDE=rider.An earlier test run in a checkout shared with other builds produced a zip named for 2026.1 that contained the
plugin.xmlof 2026.3. It didn't reproduce in isolation, so the doc now warns against overlapping builds.CI
"Check the plugin for 262" passes. "Check the plugin for 261" failed with "The self-hosted runner lost communication with the server", the problem addressed by #67, which isn't on
mainyet. This PR changes only documentation.For reviewers
publish.yamlbuilds and publishes only252,253and261, so CI doesn't publish262or263. The doc describes this as it stands today. I can't tell whether it's intentional, so it may need its own change.