D-Net
/
openaire-graph-docs
6
1
Fork 5
Code Issues 5 Pull Requests 2 Packages Projects Releases 47 Wiki Activity

Release information #26

Merged
schatz merged 1 commits from release_properties into main 2022-12-13 12:56:56 +01:00
Conversation 2 Commits 1 Files Changed 1 +8
claudio.atzori commented 2022-12-06 15:49:54 +01:00
Owner
Copy Link

This PR adds a file release.properties that declares information related with the project release project.

The idea behind it is to have this information used by an automated script run by the CI that will automatically make the declared release version available in https://code-repo.d4science.org/D-Net/openaire-graph-docs/releases

This PR adds a file `release.properties` that declares information related with the project release project. The idea behind it is to have this information used by an automated script run by the CI that will automatically make the declared release version available in https://code-repo.d4science.org/D-Net/openaire-graph-docs/releases
claudio.atzori self-assigned this 2022-12-06 15:49:54 +01:00
sandro.labruzzo was assigned by claudio.atzori 2022-12-06 15:49:54 +01:00
schatz was assigned by claudio.atzori 2022-12-06 15:49:54 +01:00
claudio.atzori added 1 commit 2022-12-06 15:49:54 +01:00
schatz commented 2022-12-06 17:54:20 +01:00
Member
Copy Link

So, we have to manually update this file so that the automated script get the required information for the upcoming release ?

So, we have to manually update this file so that the automated script get the required information for the upcoming release ?
claudio.atzori commented 2022-12-13 11:58:17 +01:00
Author
Owner
Copy Link

So, we have to manually update this file so that the automated script get the required information for the upcoming release ?

Exactly. At the moment I don't see another way for managing the version increments in a more aumated way. These properties should be then used, along with others defined in the jenkins pipeline, by this script that will create the git tag, the release, and attatch the build package as an asset of the release.

> So, we have to manually update this file so that the automated script get the required information for the upcoming release ? Exactly. At the moment I don't see another way for managing the version increments in a more aumated way. These properties should be then used, along with others defined in the jenkins pipeline, by [this script](https://code-repo.d4science.org/D-Net/Gitea-auto-release) that will create the git tag, the release, and attatch the build package as an asset of the release.
schatz merged commit 24af35739e into main 2022-12-13 12:56:56 +01:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
schatz
sandro.labruzzo
claudio.atzori
2 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/openaire-graph-docs#26
No description provided.
Delete Branch "release_properties"

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?