Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fully automate release process #38

Closed
FWDekker opened this issue Feb 26, 2023 · 2 comments
Closed

fully automate release process #38

FWDekker opened this issue Feb 26, 2023 · 2 comments
Assignees
@FWDekker
Labels
enhancement Improvement of existing feature packaging Packaging and distribution of the software release Adjustment to existing or future releases

Comments

@FWDekker
Copy link
Owner

a few things that are currently semi-automated but should be fully automated:

  • release is first set to draft, and then manually released. but that is working fine now, i don't need to verify everything manually anymore, just release it right away
  • for https://github.com/FWDekker/homebrew-mommy i have to manually trigger the Update workflow. make it so that this is done automatically. best idea: commit and push to homebrew-mommy from inside this repo. now i only need to figure out where to do the installation verification for homebrew then...
  • for aur, i should locally check out the aur repo containing the pkgbuild, update the necessary info, and then push back~ here i need to put the ssh key for uploading somewhere, and also see if i can use my pgp key somewhere, and preferably also check the sha256 sum!
@FWDekker FWDekker added enhancement Improvement of existing feature release Adjustment to existing or future releases packaging Packaging and distribution of the software labels Feb 27, 2023
@FWDekker FWDekker self-assigned this Feb 27, 2023
@FWDekker
Copy link
Owner Author

FWDekker commented Mar 1, 2023

for homebrew-mommy i have changed the code so that the update first creates a PR which is then checked with ci and should only be merged if it succeeds. i should do something similar for the aur package (create a aur-mommy repo which (manually) mirrors with the real aur repo?) which (after forcefully syncing with the aur server, since force-pushing is not allowed) creates a pr with updates, which, once approved, deploys by pushing to the aur remote?

either way, what remains is for me to decide on how to test this. i want to run tests in the homebrew-mommy and aur-mommy repos because then I can verify that the build script works before pushing the update. but what if the ./build.sh has changed, and then I fix that in the homebrew-mommy repo, and then I find out that the ./build.sh contains a bug?

i should keep the tests in the *-mommy repos, definitely. what's left is to find a way in which i can test a dev version of mommy against a dev version of *-mommy. i guess i could just leave that alone for now, keep that part semi-automated, since it still requires some manual checking?

FWDekker added a commit that referenced this issue Mar 2, 2023
@FWDekker
mommy automatically updates homebrew now~ 🚅
5b115ee 
partially fixes #38~
@FWDekker
Copy link
Owner Author

FWDekker commented Mar 3, 2023

the aur part is fixed in 6d9dadc. i hope. it's not actually tested yet 💀

@FWDekker FWDekker closed this as completed Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FWDekker FWDekker

Labels
enhancement Improvement of existing feature packaging Packaging and distribution of the software release Adjustment to existing or future releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@FWDekker