Skip to content

Conversation

@liviutomoiaga
Copy link

Ensures artifact availability during the transition period.

PR Description

This PR adds Cloudsmith artifact publishing capability to the Azure CI pipeline, ensuring artifact availability during the transition period from Artifactory to Cloudsmith.

  • Add new Publish_to_Cloudsmith job to Azure pipeline for uploading build artifacts to Cloudsmith
  • Add prepare_artifacts_for_cloudsmith.sh script to organize and upload kernel images and DTBs
  • Include wiki-scripts repository as a pipeline resource for the Cloudsmith upload utility

PR Type

  • Bug fix (a change that fixes an issue)
  • New feature (a change that adds new functionality)
  • Breaking change (a change that affects other repos or cause CIs to fail)

PR Checklist

  • I have conducted a self-review of my own code changes
  • I have compiled my changes, including the documentation
  • I have tested the changes on the relevant hardware
  • I have updated the documentation outside this repo accordingly
  • I have provided links for the relevant upstream lore

@AAndrisa
Copy link
Contributor

Please separate this changes in 2 different commits, on for the script, and one for the azure pipeline integration.
Check the linux repository commit structure, path:to:file: description

Copy link

@vasbimpikasadi vasbimpikasadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few comments merely on minor readability/maintainability improvements.

@liviutomoiaga
Copy link
Author

Please separate this changes in 2 different commits, on for the script, and one for the azure pipeline integration. Check the linux repository commit structure, path:to:file: description

Thanks for the heads-up. I’ve split the original commit into two representative commits.

@cseci
Copy link
Collaborator

cseci commented Dec 15, 2025

Linux Test Harness results now available here.

@liviutomoiaga liviutomoiaga force-pushed the staging/add-cloudsmith-upload-step branch from 97abe1a to 8911836 Compare December 17, 2025 06:01
  Publish_to_Cloudsmith jobs run on:
  - PRs (non-fork) targeting main, next_stable, or 202* branches
  - Direct pushes to main, next_stable, or 202* branches

Signed-off-by: Liviu Tomoiaga <[email protected]>
@liviutomoiaga liviutomoiaga force-pushed the staging/add-cloudsmith-upload-step branch from 8911836 to 6319bb5 Compare December 17, 2025 06:10
@cseci
Copy link
Collaborator

cseci commented Dec 17, 2025

Linux Test Harness results now available here.

@liviutomoiaga
Copy link
Author

Hi @vasileiosbi @artursartamonovsadi @AAndrisa - I’ve applied your suggestions. Let me know if there’s anything else to adjust; otherwise, we can mark this PR 🟢 and merge it into main

  Add prepare_artifacts_for_cloudsmith.sh which:
  - Organizes kernel images and DTBs by architecture/platform
  - Generates git properties file with branch and commit info
  - Uploads artifacts to Cloudsmith using wiki-scripts utility
  - Sets Azure pipeline variables for downstream stages

  Called from azure-pipelines.yml in the Publish_to_Cloudsmith job.

Signed-off-by: Liviu Tomoiaga <[email protected]>
@liviutomoiaga liviutomoiaga force-pushed the staging/add-cloudsmith-upload-step branch from 6319bb5 to b0b0630 Compare December 19, 2025 11:23
Comment on lines +33 to +34
CLOUDSMITH_REPO="linux"
SERVER_PATH="${CLOUDSMITH_REPO}/"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the CLOUDSMITH_REPO variable should still point to "sdg-linux", because that's the repo's name in cloudsmith. My previous comment was referring to the version of the packages, which should be linux/... (i.e. L34 should be SERVER_PATH="linux/" and remove the extra "/" on L134)

@cseci
Copy link
Collaborator

cseci commented Dec 19, 2025

Linux Test Harness results now available here.

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.

7 participants