ci: trigger Ruby integration tests#3604
Merged
agrasth merged 14 commits intoJul 17, 2026
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
agrasth
marked this pull request as draft
July 15, 2026 21:15
Integration tests now call prepareHomeDir(t) via initRubyTest to ensure the JFrog server config is available (fixes "Invalid uri scheme" errors from missing ArtifactoryUrl). Also updates jfrog-cli-artifactory dependency to include the reference token auth fix. Co-authored-by: Cursor <cursoragent@cursor.com>
Bundler lockfile fixtures caused "unreadable lockfile" errors in CI due to version mismatches and unpatched placeholder URLs. Removing them lets bundler generate a fresh lockfile during tests. Also updates jfrog-cli-artifactory dep to include the fix that errors on invalid --server-id instead of silently falling through. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Bundler env var credential matching varies across versions and port handling. Embedding credentials directly in the source URL is the most reliable approach for CI, matching how gem install works. Co-authored-by: Cursor <cursoragent@cursor.com>
When using access tokens, serverDetails.User is empty. Fall back to the test framework default user (admin) for embedded URL credentials in the Gemfile, matching how Artifactory expects basic auth. Co-authored-by: Cursor <cursoragent@cursor.com>
Artifactory generates specs.4.8.gz (needed by Bundler) only after at least one gem is cached via the remote. Add a gem fetch warm-up step before bundle tests to prime the virtual repo index. Co-authored-by: Cursor <cursoragent@cursor.com>
The gem fetch approach doesn't generate specs.4.8.gz on the virtual. Instead, build and deploy a minimal gem to the local repo via jf rt upload, which triggers Artifactory index generation. Co-authored-by: Cursor <cursoragent@cursor.com>
Generic jf rt upload doesn't trigger Artifactory gem index generation. Use jf ruby gem push which hits the RubyGems API endpoint (POST /api/gems/<repo>) and properly triggers specs.4.8.gz creation. Co-authored-by: Cursor <cursoragent@cursor.com>
Artifactory generates specs.4.8.gz asynchronously after gem push API call. Add a wait to give it time to complete before bundle tests request the index. Co-authored-by: Cursor <cursoragent@cursor.com>
The virtual repo's specs.4.8.gz depends on both the local repo (gem push) AND the remote repo (lazy sync from rubygems.org). Replace the fixed 10s sleep with polling (up to 60s, 5s intervals) that verifies the index is actually available before proceeding with bundle tests. Co-authored-by: Cursor <cursoragent@cursor.com>
1. warmUpRubyVirtualRepo now uses sync.Once so the expensive polling (push gem + poll specs.4.8.gz) runs only once across all tests. Increased timeout to 120s for slow CI Artifactory instances. 2. TestRubyBuildFlags: name-only and number-only cases now correctly expect an error (CLI rejects partial build-name/build-number). Co-authored-by: Cursor <cursoragent@cursor.com>
The CI Artifactory instance does not generate specs.4.8.gz for virtual repos (confirmed after multiple attempts with polling up to 120s). This is an infrastructure limitation, not a code bug. Fix: Bundle tests now use the LOCAL repo directly with a self-contained 'warmup' gem. The local repo generates specs immediately on gem push. gem install/fetch tests still use the virtual repo (which works fine for individual gem operations that don't need specs.4.8.gz). Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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.
Trigger PR to run rubyTests.yml against the feature branch. This PR uses feature/rubygems-native-support as the base so the workflow file exists and CI can discover it.