-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request to join the build group #1303
Comments
+1! |
Excellent -- welcome @danbev! Are there any platforms that you are very familiar with? (At some point we want to make a list of who knows which platforms very well) Also, just so we know, are you looking to help out with the Ansible/automation side at all, or just helping with different flaky tests/failures? Both are very very useful |
@danbev I forget, do you work on/with OpenShift? |
I mostly interested in being able to attempt to fix CI failures when for my pull requests instead of just reporting them as not related and moving on. |
Yep, our main deployment environment is OpenShift. |
@danbev Our next build WG meeting is scheduled for 4pm EST / 8pm UTC on June 12 -- if you're not fully onboarded by then, please feel free to join anyways. Once this gets a few more +1s, then we can begin that process! |
Hello @danbev and welcome. |
@refack Thanks! 😄 |
I believe @danbev is unavailable for most or all of July but hopefully we can pick this up again at the end of July or beginning of August. |
@danbev Still interested? Is there anything we can do on the Build WG side to increase your interest? |
@Trott Sorry, I did not realise this was still open. I don't have time at the moment I'm afraid. |
I'd like to join the build working group so that I can troubleshoot failure on CI servers.
Thanks
/Dan
The text was updated successfully, but these errors were encountered: