Release Automation Jenkins pipelines issues. about cortx-re HOT 8 CLOSED

This issue is resolved now. @shailesh-vaidya

from cortx-re.

This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya

from cortx-re.

@swatiseagate Can you please update fixes details here.

from cortx-re.

@shailesh-vaidya Addressed above issues in release automation job :

• Now release note option will be visible only if input parameter is provided in jenkins job then only it will be in email notification

• Build location is updated
  e.g. - http://cortx-storage.colo.seagate.com/releases/eos/Cortx-1.0.0-34-rc13/

• RELEASE was getting added multiple times in RELEASE.INFO file but added logic to handle that like below:
  grep -q "RELEASE" $Release_dir/$Tag_name/RELEASE.INFO||sed -i '/BUILD/a RELEASE: '"$Tag_name"'' $Release_dir/$Tag_name/RELEASE.INFO

• Generated metadata RPM is now available at build location.

from cortx-re.

@swatiseagate

1. Use cortx instead of eos in the url

Old : http://cortx-storage.colo.seagate.com/releases/eos/Cortx-1.0.0-34-rc13/
New : http://cortx-storage.colo.seagate.com/releases/eos/Cortx-1.0.0-34-rc13/

2. Please add shailesh, priyank and me also in the email list

from cortx-re.

@shailesh-vaidya

1. Changed Build location url to use "cortx" instead of "eos"
2. Added Shailesh, Priyank and Gowthaman in email list.

from cortx-re.

This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya

from cortx-re.

@swatiseagate Can you please confirm if this issue is resolved.

from cortx-re.