-
Notifications
You must be signed in to change notification settings - Fork 103
[ci] separate build and testing jobs #1005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Verification agent
🧩 Analysis chain
Verify that the build step produces the installer at
_out/assets
.This upload step assumes
make build
outputs_out/assets/cozystack-installer.yaml
. Please confirm the root Makefile’s build target writes the artifact there, otherwise the upload will fail.🏁 Script executed:
Length of output: 162
I want to confirm this command is indeed part of the
build
target in the root Makefile. Let’s grab a few lines of context around it:🏁 Script executed:
Length of output: 269
Let’s confirm that the
build
target depends on themanifests
step (which generates the installer):🏁 Script executed:
Length of output: 324
Ensure the installer is generated before uploading
The
build
target in the root Makefile (line 10) only depends onbuild-deps
and builds container images; it never invokes themanifests
rule that renders_out/assets/cozystack-installer.yaml
(defined on line 41). As written, the upload step will fail because the installer file isn’t produced.Please address this by either:
manifests
as a prerequisite of thebuild
target (e.g.build: build-deps manifests
), ormake manifests
(ormake -C packages/core/installer/ assets
) step in your GitHub workflow before the upload.🤖 Prompt for AI Agents