Await8987

joined 2 years ago
[–] Await8987@feddit.uk 1 points 11 hours 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...

 

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
[–] Await8987@feddit.uk 1 points 1 week ago (1 children)

Any company funded by venture capital is coming for your money eventually, whatever they say in the short term.

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

Disagree this is bad news, stable is more important tbh

[–] Await8987@feddit.uk 3 points 2 weeks ago (1 children)

OP I'm fairly certain your issue is with your music file metadata rather than the software. I suspect if you clean it with musicbrainz picard or open it with a tag editor you will find its using slightly different characters in different metadata fields. You can test this by loading up one of the offending files, clearing all of its metadata and see if that looks better!