-
Notifications
You must be signed in to change notification settings - Fork 52
Release Automation Jenkins pipelines issues. #62
Comments
This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya |
@swatiseagate Can you please update fixes details here. |
@shailesh-vaidya Addressed above issues in release automation job :
|
Old : http://cortx-storage.colo.seagate.com/releases/eos/Cortx-1.0.0-34-rc13/
|
|
This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya |
@swatiseagate Can you please confirm if this issue is resolved. |
This issue is resolved now. @shailesh-vaidya |
We should below issues in Release Automation Job pipeline
If release_note_url is not provided as input then email notification should not contain Release_Note: details . Currently it adds row like
Release_Note: | EOS Build Release Notes Cortx-1.0.0-230
Build location should be tagged build location and not actual location. Currently it shows
Build_location: | http://cortx-storage.colo.seagate.com/releases/eos/github/Cortx-v1.0.0_Beta/rhel-7.7.1908/Cortx-1.0.0-230/prod/
RELEASE is getting added multiple times in RELEASE.INFO file
e.g Refer http://cortx-storage.colo.seagate.com/releases/eos/github/Cortx-v1.0.0_Beta/rhel-7.7.1908/Cortx-1.0.0-230/prod/RELEASE.INFO
RELEASE: "Cortx-1.0.0-35-rc14"
RELEASE: Cortx-1.0.0-100-rc13
Metadata rpm is generated but not added in Release Build.
Refer - http://eos-jenkins.mero.colo.seagate.com/job/Release_Engineering/job/Release-automation/68/console . From console
logs Beta-230-1.x86_64.rpm is generated however it is not added into http://cortx-storage.colo.seagate.com/releases/eos/github/Cortx-v1.0.0_Beta/rhel-7.7.1908/Cortx-1.0.0-230/prod/
The text was updated successfully, but these errors were encountered: