Description of problem: 1. We have had complaints from developers that 'retest this please' doesn't trigger a regression run job at centos CI. 2. There's no way to verify the last failure is against which retest trigger. 3. Also the logs archive isn't exposed in the job which makes developer's life difficult to debug CI failures. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
1. Short answer is it does. We need to update the admin list with the current active developers. Please provide an update on this ticket. 2. Does that matter? It will always be against the latest commit on the pull request. There's nothing I can do about this. This is how Github behaves. 3. Uh, that's the job of the glusterd job to do. You're welcome to look at examples that we've done for glusto and others and create a similar artifact on Jenkins.
atinmu madhu-1 vpandey-RH rishubhjain kshlm harigowtham aravindavk rafikc30 The above is a good list to start with. Regarding 3, Kaushal - can you please help as I believe this is a massive gap.
The list is now updated. Closing this bug as there are no infra actions remaining.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days