Use CI to build and publish release #35

Closed
opened 8 months ago by 6543 · 12 comments
6543 commented 8 months ago
Collaborator
There is no content yet.

@6543 do you know if there is a way to make a release (via gitea api) an actual release and not a draft?

I am not there yet, but i am close:

https://codeberg.org/vanous/Gadgetbridge/src/branch/test-release/.woodpecker.yml

https://codeberg.org/vanous/Gadgetbridge/src/branch/test-release/test.sh

https://codeberg.org/vanous/Gadgetbridge/releases/tag/nightly

What i will probably do is to do a cron job on another remote server and push changes from "upstream" to my "origin" and generate nightly builds from that, delete old asset or complete release and add a new one...

cheers!
P.

@6543 do you know if there is a way to make a release (via gitea api) an actual release and not a draft? I am not there yet, but i am close: https://codeberg.org/vanous/Gadgetbridge/src/branch/test-release/.woodpecker.yml https://codeberg.org/vanous/Gadgetbridge/src/branch/test-release/test.sh https://codeberg.org/vanous/Gadgetbridge/releases/tag/nightly What i will probably do is to do a cron job on another remote server and push changes from "upstream" to my "origin" and generate nightly builds from that, delete old asset or complete release and add a new one... cheers! P.

To add to this: not sure why, but now it works. I reference HEAD, this is perhaps required.

Also, other finds:

https://tulpa.dev/cadey/gitea-release this is did not try.

http://plugins.drone.io/drone-plugins/drone-gitea-release/ this i tried and it requires a tag to be created to work, so i thought i cannot use it, but in reality i am also creating a tag... so maybe this is not a bad solution, not sure yet.

My plan is to actually always remove the previous nightly release/tag and publish a new one, which i find preferable and the release auto-expire doesn't yet work in gitea.

To add to this: not sure why, but now it works. I reference HEAD, this is perhaps required. Also, other finds: https://tulpa.dev/cadey/gitea-release this is did not try. http://plugins.drone.io/drone-plugins/drone-gitea-release/ this i tried and it requires a tag to be created to work, so i thought i cannot use it, but in reality i am also creating a tag... so maybe this is not a bad solution, not sure yet. My plan is to actually always remove the previous nightly release/tag and publish a new one, which i find preferable and the release auto-expire doesn't yet work in gitea.
OK, i have it running, will see if this is viable. https://codeberg.org/vanous/Gadgetbridge/commit/ff4db4e36 https://codeberg.org/vanous/Gadgetbridge/releases
momar added the
documentation
label 8 months ago

Does anyone know what is the length limit of body in the https://codeberg.org/api/swagger#/repository/repoCreateRelease ? It seems like some 500 characters. Then it fails.

Does anyone know what is the length limit of `body` in the https://codeberg.org/api/swagger#/repository/repoCreateRelease ? It seems like some 500 characters. Then it fails.
Poster
Collaborator

hmm it is limited by db backend constrains i would say

hmm it is limited by db backend constrains i would say

@6543

hmm it is limited by db backend constrains i would say

When I edited the release via web, it saved much longer text... I searched the source just very quickly and didn't see any reason for that. I will look again later.

@6543 >hmm it is limited by db backend constrains i would say When I edited the release via web, it saved much longer text... I searched the source just very quickly and didn't see any reason for that. I will look again later.
Collaborator

Can you please check if the web backend actually has a different limit? We did some changes to our database schemas recently to use the new upstream defaults (which weren't changed during migration). Maybe it's actually less now ...

Can you please check if the web backend actually has a different limit? We did some changes to our database schemas recently to use the new upstream defaults (which weren't changed during migration). Maybe it's actually less now ...

@fnetX

Can you please check if the web backend actually has a different limit? We did some changes to our database schemas recently to use the new upstream defaults (which weren't changed during migration). Maybe it's actually less now ...

Via the web I can add a lot more text, I have not bumped into a limit (yet). I just retried.
https://codeberg.org/vanous/Gadgetbridge/releases

Be aware that this release should be deleted and new one created @ 23:55 , so that long text will likely be gone.

@fnetX >Can you please check if the web backend actually has a different limit? We did some changes to our database schemas recently to use the new upstream defaults (which weren't changed during migration). Maybe it's actually less now ... Via the web I can add a lot more text, I have not bumped into a limit (yet). I just retried. https://codeberg.org/vanous/Gadgetbridge/releases Be aware that this release should be deleted and new one created @ 23:55 , so that long text will likely be gone.

FWIW I decided to give it another shot and it now works and git log doesn't need to be trimmed.

FWIW I decided to give it another shot and it [now works](https://codeberg.org/vanous/Gadgetbridge/releases) and git log doesn't need to be trimmed.
Collaborator

Out of curiosity: why is this in the pages repo? Shouldn't this go to the CI feedback repo? Or am I stupid right now? 🙈

Out of curiosity: why is this in the pages repo? Shouldn't this go to the CI feedback repo? Or am I stupid right now? 🙈

@momar

Out of curiosity: why is this in the pages repo? Shouldn't this go to the CI feedback repo? Or am I stupid right now? 🙈

Yes, hard to say ☺️. At least it is somewhere. Feel free to move it.

@momar >Out of curiosity: why is this in the pages repo? Shouldn't this go to the CI feedback repo? Or am I stupid right now? 🙈 Yes, hard to say ☺️. At least it is somewhere. Feel free to move it.
Collaborator

Seems like Codeberg-CI/feedback#3 is the place to go there, I'll close this for now & create another one for CI build for pages. 🙃

Seems like https://codeberg.org/Codeberg-CI/feedback/issues/3 is the place to go there, I'll close this for now & create another one for CI build for pages. 🙃
momar closed this issue 7 months ago
momar added
​i̶n̶v̶a̶l̶i̶d̶
and removed
documentation
labels 7 months ago
momar locked as Resolved and limited conversation to collaborators 7 months ago
Sign in to join this conversation.
Loading…
There is no content yet.