Skip to content

fix: correct ec2-install.sh help text, typos, and license handling#29

Merged
pio-kol merged 10 commits into
mainfrom
pkolacz/ec2-install-fixes
Jun 24, 2026
Merged

fix: correct ec2-install.sh help text, typos, and license handling#29
pio-kol merged 10 commits into
mainfrom
pkolacz/ec2-install-fixes

Conversation

@pio-kol

@pio-kol pio-kol commented Jun 23, 2026

Copy link
Copy Markdown
Member

Fixes to the EC2 quickstart install script, found while testing the AWS EC2 quickstart end to end (Develocity 2026.2).

  • Help example filename. The -h example referenced ./install.sh; the script is ec2-install.sh.
  • Tested-OS note. "tested with Ubuntu 24.04" → "26.04", matching the quickstart guide (which selects Ubuntu 26.04).
  • Post-install typo. "pre-configured setting.gradle.kts" → "settings.gradle.kts".
  • -v / --version printed nothing. It referenced $Script_Version, but the variable is $SCRIPT_VERSION (also clears the shellcheck SC2034/SC2154 warnings).
  • License path. Dropped the hard-coded ./ prefix in the Helm --set-file argument so an absolute --license path works; the documented relative path still resolves.

The ec2-install.sh.sha256 checksum is regenerated automatically by the "Generate SHA256 Checksum" workflow on this PR.

Related docs fix: gradle/dv-docs#2036 — findings: gradle/dv-docs#2037

pio-kol added 4 commits June 23, 2026 12:12
Found while testing the AWS EC2 quickstart end to end.

- Help example referenced ./install.sh; the script is ec2-install.sh.
- "tested with Ubuntu 24.04" -> 26.04, matching the quickstart guide.
- Post-install message typo: setting.gradle.kts -> settings.gradle.kts.
- -v/--version printed nothing: it referenced $Script_Version instead of the
  defined $SCRIPT_VERSION.
- License path: drop the hard-coded ./ prefix so an absolute --license path
  also works (previously only a relative path resolved correctly).
The Generate SHA256 Checksum workflow did not run on the PR, so update the
checksum manually to keep it in sync with the script.
The Generate SHA256 Checksum workflow was not updating the checksum on PRs.
Fix it so it regenerates and commits ec2-install.sh.sha256 onto the PR branch
whenever the script changes:

- Add `permissions: contents: write` so the workflow can push.
- Check out the PR head branch (`ref: github.head_ref`) instead of the
  detached merge ref, so the commit can be pushed back to the PR.
- Generate the checksum from inside AWS/EC2 so the file records the bare
  `ec2-install.sh` name (the guide runs `sha256sum -c` from the working dir;
  a path-qualified entry would fail validation).
- Only commit when the checksum actually changed, to avoid failing on a no-op.
Validated end to end: get-helm-4 installs Helm 4.2.2 and the Develocity
standalone chart deploys cleanly (10/10 pods ready, /ping UP). Helm 4 is within
Develocity's supported range. Regenerate the checksum to match the new script.
@pio-kol

pio-kol commented Jun 23, 2026

Copy link
Copy Markdown
Member Author

@copilot resolve the merge conflicts in this pull request

Copilot AI commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

@copilot resolve the merge conflicts in this pull request

Merge conflicts resolved in e3c925a. The only conflict was in ec2-install.sh.sha256ec2-install.sh auto-merged cleanly (our fixes + the v4.4.3 DEVELOCITY_PLUGIN_VERSION bump from main). The checksum was regenerated for the merged script.

@pio-kol pio-kol closed this Jun 23, 2026
@pio-kol pio-kol reopened this Jun 23, 2026
Comment thread AWS/EC2/ec2-install.sh.sha256
Comment thread .github/workflows/generate-ec2-quickstart-sha256-checksum.yml Outdated
Comment thread AWS/EC2/ec2-install.sh.sha256
@pio-kol pio-kol closed this Jun 23, 2026
@pio-kol pio-kol reopened this Jun 23, 2026
@pio-kol pio-kol requested a review from svx June 24, 2026 07:54
@pio-kol pio-kol merged commit 433025b into main Jun 24, 2026
2 checks passed
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.

3 participants