mirror of
https://github.com/cbeuw/Cloak.git
synced 2026-04-26 21:15:55 +03:00
[GH-ISSUE #130] Azure Pipelines Continuous Build #110
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Cloak#110
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 @notsure2 on GitHub (Sep 12, 2020).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/130
Hello
@cbeuw How about setting up free Azure Pipelines Pipeline to build and push git releases from every commit ? this way you don't have to build it by hand and it doesn't remain out of date for long time until you manually release.
They give 1800 build minutes free which is enough I think for Cloak and its rate of commits.
@cbeuw commented on GitHub (Sep 12, 2020):
Good shout. I didn't actually know about this. I'll set it up if it appears suitable
@notsure2 commented on GitHub (Sep 12, 2020):
I noticed you added the pipeline file then removed it. Not suitable ? @cbeuw
@cbeuw commented on GitHub (Sep 12, 2020):
I just need to figure out how to write the yaml file properly. Currently it's complaining that it can't find GOROOT, and I don't quite know where to put the built binaries. I'll make a new branch to test the yaml so it doesn't bloat up master. I'll probably do these tomorrow because it's quite late now
@notsure2 commented on GitHub (Sep 12, 2020):
i think you can add a "step" that saves them in azure build artifacts. they store up to 2 GB for free. Then when you reach the limit you can delete old ones automatically I guess. Maybe there's a setting there for that. Alternatively maybe there's a step to communicate to github to publish a release. I only used the building part and use ssh to deploy for my stuff.
@cbeuw commented on GitHub (Sep 12, 2020):
Ideally I want it to release to github automatically, as uploading the build artifacts manually is basically what I'm doing right now. I had a look and there is a task that lets you do that, so it's definitely achievable
@cbeuw commented on GitHub (Sep 13, 2020):
It appears to be working now. Thanks again for the heads-up. I'll try to set it up for Cloak-android as well which could save a lot of work, but it's going to be more complicated I assume