Repository navigation
Skip upstream analysis and extra artifacts in Lyo acceptance builds - #42
Merged
Merged
Conversation
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.
The manual acceptance workflow only needs upstream Lyo artifacts to verify this archive server. Its upstream install now disables the SpotBugs, Spotless, and Enforcer profiles and skips source JAR attachment and CycloneDX SBOM generation, in addition to the existing test and Javadoc skips.
The directory helper remains active because it supplies Lyo build paths. The archive project's own
verifystep is unchanged.Validation: actionlint, zizmor, and
git diff --checkpassed. A local effective-POM check confirmed that no SpotBugs, Spotless, or Enforcer goals are bound with these profiles disabled; a non-recursive Lyo parent package smoke check passed and reported skipped Javadocs and CycloneDX output. The full upstream reactor build was not run.The Dash snapshot repository release policy is fixed upstream in eclipse-lyo/lyo#1072 rather than overridden by downstream CI settings. The warning fix applies to acceptance builds once that change is merged into the selected Lyo branch.