Skip to content

Comments

Add CI workflow to publish a continuous release#380

Merged
Sapd merged 2 commits intoSapd:masterfrom
nicola02nb:master
Dec 6, 2024
Merged

Add CI workflow to publish a continuous release#380
Sapd merged 2 commits intoSapd:masterfrom
nicola02nb:master

Conversation

@nicola02nb
Copy link
Contributor

@nicola02nb nicola02nb commented Nov 25, 2024 •
edited
Loading

Changes made

Created a CI workflow files that compiles and publish a "Continuos build" on every push to master branch.

This gives users a way to get the latest features without building the project on their own

You can check the result on my fork

Checklist

  • I adjusted the README (if needed)
  • For new features in HeadsetControl: I discussed it beforehand in Issues or Discussions and adhered to the wiki

@nicola02nb nicola02nb changed the title Add CI workflows publish a continuous release Add CI workflow to publish a continuous release Nov 29, 2024
@Sapd
Copy link
Owner

Sapd commented Dec 4, 2024

Thank you! Great contribution.

I thought also of doing something like this. Currently Windows Builds are in fact pushed but hidden inside the artifcats window.

Just two points:

  • Would it make sense to include it already in the existing flows? I myself guess not bc. this one is just excluded on push. Just something to think about
  • Does the Release automatically replace other releases named "continous"?

Also there could be a question about signing releases (as there was before from AUR contributors), but I am not sure how it would work in a flow as that. Currently the normal releases are manually signed by myself.

@nicola02nb
Copy link
Contributor Author

nicola02nb commented Dec 4, 2024 •
edited
Loading

  • Does the Release automatically replace other releases named "continous"?

It shouldn't replace latest release, it just creates a new pre-release, tagged as continuous

Let me check

EDIT:

Removes latest continuosus tagged release

@nicola02nb
Copy link
Contributor Author

nicola02nb commented Dec 4, 2024

  • Would it make sense to include it already in the existing flows? I myself guess not bc. this one is just excluded on push. Just something to think about

In my opinion makes sense so users have an easier way to access to latest features before release wihout needing to search through CI arctifacts...

@nicola02nb
Copy link
Contributor Author

nicola02nb commented Dec 4, 2024

Also there could be a question about signing releases (as there was before from AUR contributors), but I am not sure how it would work in a flow as that. Currently the normal releases are manually signed by myself.

I dont know much about signing releases... I can only say that my idea was ment only for pre-release which should not need signing? I guess you can do it when you create the official release?

@Sapd Sapd merged commit 689c1fc into Sapd:master Dec 6, 2024
@Sapd
Copy link
Owner

Sapd commented Dec 6, 2024

In my opinion makes sense so users have an easier way to access to latest features before release wihout needing to search through CI arctifacts...

I agree

I dont know much about signing releases... I can only say that my idea was ment only for pre-release which should not need signing? I guess you can do it when you create the official release?

I think that is fine, it could be added afterwards when its requested and really needed

Infactionfreddy pushed a commit to Infactionfreddy/HeadsetControl that referenced this pull request Dec 8, 2025
@nicola02nb
Add CI workflow to publish a continuous release (Sapd#380)
26fc02a 
* Add continuous CI build workflow for multi-platform support
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@nicola02nb @Sapd