CI: Prepare artefacts for sdg linux rpi repo (To be reviewed after release)#3341
Draft
liviutomoiaga wants to merge 2 commits into
Draft
CI: Prepare artefacts for sdg linux rpi repo (To be reviewed after release)#3341liviutomoiaga wants to merge 2 commits into
liviutomoiaga wants to merge 2 commits into
Conversation
liviutomoiaga
force-pushed
the
staging/setup-deploy-rpi-binaries-on-top-level-flow
branch
2 times, most recently
from
ba02dc3 to
789cc80
Compare
gastmaier
reviewed
May 26, 2026
| # Condition: Fork PRs blocked (no secrets access). Push scope handled by workflow trigger. | ||
| deploy_rpi_artifacts: | ||
| needs: [assert_build] | ||
| if: github.repository_owner == 'analogdevicesinc' |
Collaborator
There was a problem hiding this comment.
Suggested change
| if: github.repository_owner == 'analogdevicesinc' | |
| if: ${{ github.event.pull_request.head.repo.full_name == github.repository || github.event_name == 'push' }} |
The current format tries to upload for pull requests from forks, too.
For forks prs, github.repository_owner is still analogdevicesinc
|| github.event_name == 'push' is safe because github.repository_owner == 'analogdevicesinc' is already gated on previous runs (the ci/cd never runs for push on forks (waste of resources), only intentional prs).
so, effectively, the rule is
(github.repository_owner == 'analogdevicesinc' && github.event_name == 'push') ||
(github.event.pull_request.head.repo.full_name == github.repository && github.event_name == 'pull_request')
the should match what you need:
under analogdevicesinc, run on push and pull request, only if the origin owner is analogdevicesinc too
gastmaier
reviewed
May 26, 2026
| adi_bcm*_defconfig-* | ||
| dtb-* | ||
|
|
||
| # Condition: Fork PRs blocked (no secrets access). Push scope handled by workflow trigger. |
Collaborator
There was a problem hiding this comment.
Comment not necessary necessary
liviutomoiaga
force-pushed
the
staging/setup-deploy-rpi-binaries-on-top-level-flow
branch
from
789cc80 to
b19f40b
Compare
liviutomoiaga
commented
May 26, 2026
| - rpi-6.6.y | ||
| - rpi-6.12.y | ||
| - staging/rpi/* | ||
| - rpi/release/* |
Collaborator
Author
There was a problem hiding this comment.
@gastmaier - should I update top-level.yml with conditional push trigger on staging/rpi/* or rpi/release/* ?
liviutomoiaga
force-pushed
the
staging/setup-deploy-rpi-binaries-on-top-level-flow
branch
from
b19f40b to
b453999
Compare
gastmaier
approved these changes
May 27, 2026
Collaborator
gastmaier
left a comment
gastmaier
left a comment
There was a problem hiding this comment.
Thanks! I reduced the contents write permission to read
Use deploy-kuiper-artifacts.yml shared action to deploy to sdg-linux cloudsmith (S3). Reduce contents write permission to read. Signed-off-by: Liviu Tomoiaga <Liviu.Tomoiaga@analog.com>
gastmaier
force-pushed
the
staging/setup-deploy-rpi-binaries-on-top-level-flow
branch
from
6db22bc to
6d552fe
Compare
Reduce the trigger events only for rpi/release/* push or pull-request. Remove Upload to Cloudsmith step since it will be done on top-level.yml. Signed-off-by: Liviu Tomoiaga <Liviu.Tomoiaga@analog.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
2 participants
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.
Consolidate the separate Kuiper and RPI artifact deployment workflows into a single unified workflow, reducing duplication and simplifying maintenance. This implementation should replace azure-pipelines-rpi.yml from main branch.
PR Description
necessary to understand them. List any dependencies required for this change.
any space), or simply check them after publishing the PR.
description and try to push all related PRs simultaneously.
PR Type
PR Checklist