mirror of
https://github.com/MonitorControl/MonitorControl.git
synced 2026-05-15 14:15:55 -06:00
[GH-ISSUE #5] CI & Automatic Updates #6
Labels
No labels
Status: Abandoned
arm64
beta
beta
bug
done
duplicate
enhancement
feedback needed from reporter
in progress
invalid
investigating
known Issue
monitor Issue
pull-request
translation
unable to reproduce
unreleased
x86
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/MonitorControl#6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @the0neyouseek on GitHub (Jan 2, 2018).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/5
Originally assigned to: @the0neyouseek, @JoniVR, @waydabber on GitHub.
This issue is to simplify the debug and release process :
@JoniVR commented on GitHub (May 8, 2019):
I think an auto-update feature would be awesome!
I can look into implementing this if you want.
I'd suggest the following things to be in there:
Is there a specific CI service you'd prefer?
I'm personally only experienced with TravisCI but I'm fine with whatever.
@the0neyouseek commented on GitHub (May 8, 2019):
@JoniVR Hi,
I've used CircleCI which works great with macOS/iOS but anything is fine for me (We could also add a bagde to the readme)
For automatic updates I've found this :
@JoniVR commented on GitHub (May 8, 2019):
CircleCI seems to be the more populair choice these days yes. I'm fine with that.
Yup, would be useful.
I wasn't aware of GitHubUpdates before, I've seen Sparkle before. I think Sparkle is generally more used and more supported, however, it looks like GitHubUpdates is a lot easier to implement. So I'm not sure, I found a nice article on using sparkle with github though.
@the0neyouseek commented on GitHub (May 8, 2019):
I also think that Sparkle is the safe bet here as GithubUpdates doesn't seem maintained 👍
@JoniVR commented on GitHub (Apr 2, 2020):
For the CI part, if/when we get to it, Github CI seems to be pretty good now from my experience, maybe that would be a better option now?
@the0neyouseek commented on GitHub (Apr 2, 2020):
💯% agree with that
Le jeu. 2 avr. 2020 à 14:53, Joni Van Roost notifications@github.com a
écrit :
@waydabber commented on GitHub (Sep 29, 2021):
I added sparkle 2 for updates.
@the0neyouseek commented on GitHub (Sep 29, 2021):
@waydabber Did you find a way to auto-generate the AppCast xml file ?
@waydabber commented on GitHub (Sep 29, 2021):
Nope, I just added the app side of the things but did not work on automation at all so there is room for improvement. :)
@waydabber commented on GitHub (Sep 29, 2021):
But as far as I see the appcast xml can easily be edited manually so we could put together a script that automates everything from signing to publishing. But since I could not even apply for an Apple developer membership (somehow my application failed instantly after I enrolled and I should 'contact Apple' but the form offered is broken), I can't even sign or notarize the app so I have hard time trying out the whole process. I hope you or @JoniVR will help. It would be nice if 4.0.0 betas and then stable versions could auto-update (I recommend having a separate beta and stable appcast channel).
@the0neyouseek commented on GitHub (Sep 29, 2021):
@waydabber I was planning on adapting this script I found :
https://github.com/lwouis/alt-tab-macos/blob/master/scripts/update_appcast.sh
For signing @JoniVR could you invite @waydabber and I to your development team in App Store Connect ? This would allow us to sign and notarize the app I think
@waydabber commented on GitHub (Sep 29, 2021):
Nice, a script like that would work nicely with the appcast. It would be really great if there were be a simple scripted process to build and publish the app, both as pre-release and release!
@the0neyouseek commented on GitHub (Sep 29, 2021):
We could use Fastlane for that
@JoniVR commented on GitHub (Sep 29, 2021):
IIRC from my work place, an organisational account requires a D.U.N.S number, which requires a legal entity, not sure though. See:
https://developer.apple.com/programs/enroll/
I'd be happy to help with everything else. I agree Sparkle is pretty important.
@the0neyouseek commented on GitHub (Sep 29, 2021):
@JoniVR Can you not add users to your personal account (if that's what you use to sign) and restrict access using roles ?
@JoniVR commented on GitHub (Sep 29, 2021):
I think I might be able to do it through App Store connect, judging by:
https://help.apple.com/developer-account/#/dev3e8818774
That would require registering the bundle identifier in App Store Connect though. I'll look into it.
@JoniVR commented on GitHub (Sep 29, 2021):
Reopened because I want to keep this visible until we get it all up-and-running if you don't mind.
@JoniVR commented on GitHub (Sep 29, 2021):
Theoretically, We should be able to create a Github workflow that will be triggered when creating a tag, and then make it create a release based on that, updating appcast etc, but that might be quite a lot of work. Good news is that Apple created a better tool for notarising this year, still have to look into that too.
@waydabber commented on GitHub (Sep 29, 2021):
Yes of course, I just bulk closed all with the done tag.
@waydabber commented on GitHub (Sep 30, 2021):
sidenote - here are some ideas and existing solutions to make Sparkle work from GitHub:
https://github.com/sparkle-project/Sparkle/issues/648
@JoniVR commented on GitHub (Sep 30, 2021):
Notes on current sparkle to-do (for tracking purposes, step-by-step):
This is using the
github-pagesbranch, don't remove this branch for now as we'll use it to update theappcast.xmlwithout Pull Requests for releases. ↩︎@stale[bot] commented on GitHub (Oct 26, 2022):
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require attention? This issue may be closed if no further activity occurs. Thank you for your contributions.