Conversation
…ra workflow Packaging landed in flagos-ai#12 but nothing publishes the built deb/rpm; this adds the same thin caller libtriton_jit uses. The shared workflow guards pre-release tags, waits for build-deb/build-rpm of the tagged commit, and fails if no package could be uploaded.
Contributor
Author
|
2.2 pairing: #62 cherry-picks this onto Both are open on purpose, per the release process (fix on the default branch, then cherry-pick to the release branch). With 2.2 close, #62 is the time-sensitive one — this PR carries the change forward for the line after 2.2 and does not block the release. |
Contributor
Author
|
Closing: packages are now built and published centrally from flagos-ai/build-infra, so this repository no longer needs its own publishing step. Thanks for the reviews. |
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.
Why
build-deb.yml/build-rpm.yml(#12) produce packages on everyv*tag, but nothing publishes them:v0.2.0built green on 06-24 and the artifacts expired after 7 days. FlagOS Nexus currently holds no FlagSparse package.What
Adds
.github/workflows/upload-nexus.yml, a thin caller of the sharedflagos-ai/build-infra/.github/workflows/upload-nexus.yml— identical to the one libtriton_jit already uses. The shared workflow:rc/a/b/dev) onpush, always publishes onworkflow_dispatchbuild-deb.yml(required) andbuild-rpm.yml(optional) of the same commit, downloads their artifactsflagos-apt-hosted, rpm →flagos-yum-hostedusing the org-levelNEXUS_TOKENNo change to the build workflows. After merge, the existing
v0.2.0can be published with a manual dispatch (rebuild + upload) without re-tagging.Part of FEP-0019 Wave 1 (flagos-ai/community#59).