-
Notifications
You must be signed in to change notification settings - Fork 289
Added repositories for deb/rpm packages on buildkite #780
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
Conversation
Looks like a working solution for #298 |
BTW I couldn't find a workflow run for this in your fork. Can you do a quick release test there? |
It... disappeared somehow? Anyway look at new release: https://github.com/stone-w4tch3r/sourcegit-fork/actions/runs/12139933496 |
Note that actual push failed because I already changed repository/organization names in an action. But previous packages were pushed successfully |
I see, but action is not failed because error is ignored. Would you add |
Looks good |
Hi everyone, the new CI workflow |
I've pushed these packages manually, and modify the @@ -24,8 +24,9 @@ jobs:
uses: ./.github/workflows/package.yml
with:
version: ${{ needs.version.outputs.version }}
publish-packages:
+ needs: [package, version]
name: Publish Packages
uses: ./.github/workflows/publish-packages.yml
secrets:
BUILDKITE_TOKEN: ${{ secrets.BUILDKITE_TOKEN }} Is it right? |
Yep. Checked, without this line publish fails. You need to return it back to release.yml |
the original PR missed this line. I've added it to |
I can't find repos on buildkite. What links to use? Checked |
rpm package via buildkite works as expected |
Added appimagehub into readme #798 |
In issue #298 we discussed distributing rpm/deb packages via dedicated repositories.
Initial idea was to use packagecloud, but since it is now not accessible for new users, buildkite was used as a replacement. Actually, it was quite hard to handle all it's bugs, but now it works!
You can try test packages here: rpm and deb.
To make it all work, you need: