Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

github actions to release fail #5

Closed
jurgenvinju opened this issue Nov 12, 2021 · 10 comments
Closed

github actions to release fail #5

jurgenvinju opened this issue Nov 12, 2021 · 10 comments
Assignees

Comments

@jurgenvinju
Copy link
Member

https://github.com/usethesource/typepal/runs/4189164598?check_suite_focus=true

I'm at a loss here. What is going on? This is the same action we use for other projects.

Run softprops/action-gh-release@v1
  with:
    draft: true
    files: /**/*
    token: ***
  env:
    MAVEN_OPTS: -Xmx4G -Dhttps.protocols=TLSv1.2 -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=WARN -Dorg.slf4j.simpleLogger.showDateTime=true -Djava.awt.headless=true
    JAVA_HOME_11.0.13_x64: /opt/hostedtoolcache/jdk/11.0.13/x64
    JAVA_HOME: /opt/hostedtoolcache/jdk/11.0.13/x64
    JAVA_HOME_11_0_13_X64: /opt/hostedtoolcache/jdk/11.0.13/x64
    GITHUB_TOKEN: ***
Error: EACCES: permission denied, scandir '/boot/efi'
@DavyLandman
Copy link
Member

Something funky is happening here. I'll does this only happen for his repo? The other ones are fine right?

@jurgenvinju
Copy link
Member Author

jurgenvinju commented Nov 13, 2021 via email

@DavyLandman
Copy link
Member

you could try switching the machine to a different version of ubuntu? else I'll give some debugging a try tomorrow.

@jurgenvinju
Copy link
Member Author

jurgenvinju commented Nov 15, 2021 via email

@jurgenvinju
Copy link
Member Author

going down to ubuntu 18 LTS (from 20) did not have any effect.

@DavyLandman
Copy link
Member

ok. I'll take this one tomorrow.

@jurgenvinju
Copy link
Member Author

jurgenvinju commented Nov 15, 2021 via email

@jurgenvinju
Copy link
Member Author

Finally I see what is going wrong:

`files: /**/*`

This means that a variable is resolving to the empty string, namely:

steps.build-artifact.outputs.artifact-root-dir

So that seems to be the problem. The search pattern then starts to browse the entire file system including directories that it does not have access too. Hence the error message.

@jurgenvinju
Copy link
Member Author

that's because it depends on the previous step that was commented out. build-artifact is the id of that previous action step.

@DavyLandman
Copy link
Member

DavyLandman commented Nov 15, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants