-
Notifications
You must be signed in to change notification settings - Fork 10
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
[BUG] absolute paths stored as artifact annotation create unexpected pulling behavior #10
Labels
bug
Something isn't working
Comments
afflom
added a commit
to afflom/client
that referenced
this issue
May 25, 2022
jpower432
added a commit
to jpower432/client
that referenced
this issue
May 25, 2022
Since the build path is in a disposable directory, it cannot be included in the "title" annotation on the artifacts. To fix this, relative paths within the workspace are passed to the oras client and the directory is changed before processing. Closes ortelius#10 Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
jpower432
added a commit
to jpower432/client
that referenced
this issue
May 26, 2022
Since the build path is in a disposable directory, it cannot be included in the "title" annotation on the artifacts. To fix this, relative paths within the workspace are passed to the oras client and the directory is changed before processing. Closes ortelius#10 Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
jpower432
added a commit
to jpower432/client
that referenced
this issue
Jun 1, 2022
Since the build path is in a disposable directory, it cannot be included in the "title" annotation on the artifacts. To fix this, relative paths within the workspace are passed to the oras client and the directory is changed before processing. Closes ortelius#10 Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
jpower432
added a commit
to jpower432/client
that referenced
this issue
Jun 21, 2022
Since the build path is in a disposable directory, it cannot be included in the "title" annotation on the artifacts. To fix this, relative paths within the workspace are passed to the oras client and the directory is changed before processing. Closes ortelius#10 Signed-off-by: Jennifer Power <barnabei.jennifer@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When using
oras
CLI to retrieve an artifact published by the client, all files are written to the absolute path where they were original published from.What behavior was expected?
The artifacts to be copied to the current directory (or directory specified) when copying.
The text was updated successfully, but these errors were encountered: