D-Net
/
Gitea-auto-release
6
0
Fork 1
Code Issues Pull Requests 1 Packages Projects Releases Wiki Activity

Absolute paths in the zip file #1

New Issue
Closed
opened 2022-12-19 12:15:15 +01:00 by claudio.atzori · 5 comments
claudio.atzori commented 2022-12-19 12:15:15 +01:00
Owner
Copy Link

@schatz reported that the zip file created using a this script contains absolute paths that, when run in the context of the jenkins pipeline, will be relative to the jenkins worker filesystem.
It would be more convenient to create the zip file using relaive paths instead.

What do you think?

@schatz reported that the zip file created using a this script contains absolute paths that, when run in the context of the jenkins pipeline, will be relative to the jenkins worker filesystem. It would be more convenient to create the zip file using relaive paths instead. What do you think?
sandro.labruzzo was assigned by claudio.atzori 2022-12-19 12:15:15 +01:00
sandro.labruzzo commented 2022-12-19 12:29:00 +01:00
Owner
Copy Link

we can pass the build path as external args for the script so you che use ${pwd}

we can pass the build path as external args for the script so you che use ${pwd}
schatz commented 2022-12-19 12:35:33 +01:00
Member
Copy Link

Basically, the problem is that when creating the release from Jenkins, the resulted release.tar.gz contains all folder/subfolder names till the build/ directory.
Check the attached image.
Probably, it would more convenient to include only the contents of the build/ directory.

Basically, the problem is that when creating the release from Jenkins, the resulted `release.tar.gz` contains all folder/subfolder names till the `build/` directory. Check the attached image. Probably, it would more convenient to include only the contents of the `build/` directory.
Capture.PNG
2.8 KiB
Capture.PNG
michal.politowski commented 2023-01-12 16:24:12 +01:00
Member
Copy Link

I would consider this a blocker. The release packages for the documentation should definitely not depend on the build location - the paths inside should be relative to the build directory as Serafeim says.

This should be a simple change to the way tar is used in the script if I'm not mistaken.

I would consider this a blocker. The release packages for the documentation should definitely not depend on the build location - the paths inside should be relative to the `build` directory as Serafeim says. This should be a simple change to the way `tar` is used in the script if I'm not mistaken.
michal.politowski commented 2023-01-18 10:16:09 +01:00
Member
Copy Link

@schatz could you test making a new release using this fixed version of the script?

@schatz could you test making a new release using this fixed version of the script?
schatz commented 2023-01-18 13:59:41 +01:00
Member
Copy Link

Yes, this is a new release: https://code-repo.d4science.org/schatz/openaire-graph-docs/releases/tag/1.2
This seems to be resolved now, thanks!

Yes, this is a new release: https://code-repo.d4science.org/schatz/openaire-graph-docs/releases/tag/1.2 This seems to be resolved now, thanks!
Sign in to join this conversation.
master
Branches Tags
Clear current reference
master
simplify_repo_name
Clear current reference
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
sandro.labruzzo
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: D-Net/Gitea-auto-release#1
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?