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

Can't upload binaries compiled in previous jobs, as cloning step fails due to directory not being empty #55

Open
ConorHartin opened this issue Aug 2, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@ConorHartin
Copy link

ConorHartin commented Aug 2, 2024

Orb version:

circleci/[email protected]

What happened:

I am running pyinstaller in both windows & linux executors, and persisting the namespace containing the output of those jobs so it will be available in the github-cli orb so I can upload those files specifically. If I attach that namespace to the upload job, then it never gets to the upload command because the clone command fails due to the "." directory not being empty. If I run pre-steps commands to create a tmp folder and cd into that, it just gets ignored and the orb's clone command (which I don't actually need to run, as I already cloned the repo in question in order to run pyinstaller on it to generate the files I actually want to upload) runs from the default directory. There doesn't seem to be a way to set the working_directory of an orb job as far as I can tell. It's possible this is not a limitation of the orb and I'm just not configuring it correctly, but I currently don't see a way to configure it to do that.
I also tried running the release job, but that always times out on CircleCI, appearing to hang indefinitely.

Expected behavior:

To be able to upload files created outside the githhub-cli orb.

Additional Information:

@ConorHartin ConorHartin added the bug Something isn't working label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant