-
Notifications
You must be signed in to change notification settings - Fork 52
Fail Component Job if Release job failed #64
Comments
This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya |
@gowthamchinna Is this fixed now? |
@shailesh-vaidya This is not yet fixed need discussion before implementing this. Mostly Release job fail because of RE issues need to decide whether we need to notify component team for this |
This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya |
@gowthamchinna Lets discuss this in next scrum. |
This issue/pull request has been automatically marked as stale because it has not had recent activity. Tagging @shailesh-vaidya |
This issue/pull request has been marked as |
@swatiseagate Could you please take a look into this. |
This issue/pull request has been marked as |
@swatiseagate Could you please update on this. |
This issue/pull request has been marked as |
@swatiseagate - Could you please update on this. If this is done and verified by @gowthamchinna Please add details and close. |
Changes are done in jenkins jobs for all branches to fail the component job if the downstream release job fails. Reviewed from @gowthamchinna. |
Due to Github intermittent failure, Release Job failed but component job passed with bad rpm url. this causes
Ref : http://eos-jenkins.mero.colo.seagate.com/job/Release_Engineering/job/github-work/job/GitHub%20Release/2773/
Bad Build (No GPG key) : http://cortx-storage.colo.seagate.com/releases/eos/github/release/rhel-7.7.1908/2773/dev/
The text was updated successfully, but these errors were encountered: