Conversation
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
|
Ignore the PackIt failures, this can't even run on Linux... |
|
The PackIt failures are because we need to bump deps on the Fedora side as well whenever they're updated in |
|
This lgtm. Please also add something to the README to document how the new release pipeline works for future reference. |
|
Line-wrapped readme so that it's editable by a human in a text editor and added a couple of sentences about where the latest installer will come from when/if this is merged |
jannau
left a comment
jannau
left a comment
There was a problem hiding this comment.
ok with me. I left a few comments to simplify the CI workflows
Signed-off-by: James Calligeros <[email protected]>
This reusable workflow builds the installer then uploads the artefact to the correct endpoint. It is designed to be wrapped and called by workflows with the correct triggers and endpoint specified as an input. Signed-off-by: James Calligeros <[email protected]>
This workflow runs on every tagged release and uploads the build to the CDN as the latest production version Signed-off-by: James Calligeros <[email protected]>
Builds on every push to main and uploads the artefact to the CDN for use as the latest dev installer Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
Signed-off-by: James Calligeros <[email protected]>
jannau
left a comment
jannau
left a comment
There was a problem hiding this comment.
thanks, looks good.
do we want to drop the packit integration?
| run: | | ||
| sudo apt-get update | ||
| sudo apt-get install --no-install-recommends -y gcc-aarch64-linux-gnu | ||
| sudo apt-get install --no-install-recommends -y 7zip jq |
There was a problem hiding this comment.
nit: could be a single apt-get install ...
|
I'd rather not, but instead we should fix it so the Packit runs work again (which will probably happen once we update the spec in Fedora for a new release). |
|
merging this. If we have additional installer changes it's useful not to wait for them to test the CI in meaningful way shortly after it is merged |
4 participants
Been a while since we updated the deps, and while doing so noticed that the release procedure is basically that one Honda Odyssey ad.
Bump the runtime dependencies and tethered m1n1 version, and add some CI pipelines so that manual handling for releases is reduced. If we decide to go down this path, we should then move the bootstrap scripts into the installer data repo so that they can be updated without manual branch handling.