{"id":62,"date":"2025-01-21T07:14:41","date_gmt":"2025-01-21T06:14:41","guid":{"rendered":"https:\/\/chosesoft.eu\/?p=62"},"modified":"2025-01-21T07:15:27","modified_gmt":"2025-01-21T06:15:27","slug":"gitea-runners","status":"publish","type":"post","link":"https:\/\/chosesoft.eu\/index.php\/2025\/01\/21\/gitea-runners\/","title":{"rendered":"Gitea Runners"},"content":{"rendered":"\n

If you use gitea as GIT repo you are able to start using a atomation as well as Act Runners<\/a>.<\/p>\n\n\n\n

First at your gitea server create new action runner.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n<\/figure>\n\n\n\n

And now you should run gitea Act runners. (you can do it in Linux host (virtual or physical) or docker). I have example to run directly at synology as docker project.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n\n\n\n

Both Gieta and Gitea Action runners run at synoogy HW. <\/p>\n\n\n\n

You can see avail. runners in gitea now. <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

So create yaml with pipeline in .gitea<\/a>\/workflows folder. And you can run your pipeline like:<\/p>\n\n\n\n

<\/circle><\/circle><\/circle><\/g><\/svg><\/span><\/path><\/path><\/svg><\/span>
name<\/span>:<\/span> <\/span>Gitea<\/span> <\/span>Actions<\/span> <\/span>Demo<\/span><\/span>\nrun<\/span>-<\/span>name<\/span>:<\/span> <\/span>$<\/span>{{<\/span> <\/span>gitea<\/span>.<\/span>actor<\/span> <\/span>}}<\/span> <\/span>is<\/span> <\/span>testing<\/span> <\/span>out<\/span> <\/span>Gitea<\/span> <\/span>Actions<\/span> \ud83d\ude80<\/span><\/span>\non<\/span>:<\/span> [<\/span>push<\/span>]<\/span><\/span>\n<\/span>\njobs<\/span>:<\/span><\/span>\n  <\/span>Explore<\/span>-<\/span>Gitea<\/span>-<\/span>Actions<\/span>:<\/span><\/span>\n    <\/span>runs<\/span>-<\/span>on<\/span>:<\/span> <\/span>ubuntu<\/span>-<\/span>latest<\/span><\/span>\n    steps<\/span>:<\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83c\udf89 The job was automatically triggered by a ${{ gitea.event_name }} event.<\/span>"<\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83d\udc27 This job is now running on a ${{ runner.os }} server hosted by Gitea!<\/span>"<\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83d\udd0e The name of your branch is ${{ gitea.ref }} and your repository is ${{ gitea.repository }}.<\/span>"<\/span><\/span>\n      <\/span>-<\/span> name<\/span>:<\/span> <\/span>Check<\/span> <\/span>out<\/span> <\/span>repository<\/span> <\/span>code<\/span><\/span>\n        uses<\/span>:<\/span> <\/span>actions<\/span>\/<\/span>checkout<\/span>@<\/span>v4<\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83d\udca1 The ${{ gitea.repository }} repository has been cloned to the runner.<\/span>"<\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83d\udda5\ufe0f The workflow is now ready to test your code on the runner.<\/span>"<\/span><\/span>\n      <\/span>-<\/span> name<\/span>:<\/span> <\/span>List<\/span> <\/span>files<\/span> <\/span>in<\/span> <\/span>the<\/span> <\/span>repository<\/span><\/span>\n        run<\/span>:<\/span> <\/span>|<\/span><\/span>\n          <\/span>ls<\/span> <\/span>$<\/span>{{<\/span> <\/span>gitea<\/span>.<\/span>workspace<\/span> <\/span>}}<\/span>          <\/span><\/span>\n      <\/span>-<\/span> run<\/span>:<\/span> <\/span>echo<\/span> <\/span>"<\/span>\ud83c\udf4f This job's status is ${{ job.status }}.<\/span>"<\/span><\/span><\/code><\/pre><\/div>\n\n\n\n
\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n<\/figure>\n","protected":false},"excerpt":{"rendered":"
If you use gitea as GIT repo you are able to start using a atomation as well as Act Runners. First at your gitea server create new action runner. And now you should run gitea Act runners. (you can do it in Linux host (virtual or physical) or docker). I have example to run directly […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-62","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/posts\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/comments?post=62"}],"version-history":[{"count":2,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/posts\/62\/revisions"}],"predecessor-version":[{"id":79,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/posts\/62\/revisions\/79"}],"wp:attachment":[{"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/media?parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/categories?post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/chosesoft.eu\/index.php\/wp-json\/wp\/v2\/tags?post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}