Selfhosted

54838 readers

346 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Workflow artifacts from forgejo runner not accessible from other workflows (feddit.uk)

submitted 1 day ago by Await8987@feddit.uk to c/selfhosted@lemmy.world

3 comments fedilink hide all child comments

Hi all, I have recently started using Forgejo runners and it's a great tool. I have run into this surprising limitation with accessing artifacts and I wonder if I am just doing something totally wrong?

If I use the artifacts within the same workflow file as per the tests: e2e test then this works as you would expect. But if you have two separate workflow files, so example one with a build step, and one with a deploy step. then the deploy step has no way to access the artifacts?

I also found an open issue which indicates that the github implementation for accessing the artifacts using a token is not currently possible either.

I am surprised I have not seen more people talking about this, so I wonder if I am just doing something really obviously wrong! The fundamental part is that I am using uses: to specify the first stage from the other workflow file.

Where am I going wrong?

jobs:
  build:
    runs-on: docker
    uses: ./.forgejo/workflows/build.yml

  deploy:
    needs: build

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world 1 points 1 day ago (2 children)

How's everything else getting to your storage from your main container? They don't share.

[–] Await8987@feddit.uk 2 points 1 day ago

@just_another_person@lemmy.world sorry to answer your actual question: Using https://data.forgejo.org/forgejo/upload-artifact@v4 and https://data.forgejo.org/forgejo/download-artifact@v4

[–] Await8987@feddit.uk 1 points 1 day ago

@just_another_person@lemmy.world The runner picks up the task and when they are in the same workflow file the tasks are executed on the same run_id (as far as I understand) which means when using download artifacts code: https://code.forgejo.org/forgejo/download-artifact/src/tag/v4/ the request for artifacts works correctly as the request has the right ID. But sadly when they are separate tasks it requests the wrong ID (as I understand) and the section in the readme about downloading from other workflow runs is incorrect as its just mirrored from github, and the run_id and token field is not implemented which is discussed in this ticket. But I am shocked that everyone is not running into this? Still think im being dumb...