-
Notifications
You must be signed in to change notification settings - Fork 102
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
Zuul gating #78
Comments
@mnaser you’re referencing a PR and issue that i’ve created and i’m not sure what you mean when referencing these. Can you ellaborate a bit more what you want to do? I do understand what you want to do with Zuul although this project uses Circle CI already, but i guess there could be more than one build system involved. |
@mikejoh that was my bad. I meant number 2 (add the jobs to the Zuul repo) and not number 1 (adding a GitHub application) in the context of my sentence :) |
Oh, right, makes sense! :) |
@mnaser any chances to work on this? If not, are you okay with flagging this for 1.2.0? |
Hi Jorge:
I don't think I have time to work on this right now, there's a few things I
need to focus on getting done
I'll try to get to it when I can.
Thanks
Moahmmed
…On Thu, Jul 2, 2020 at 11:57 AM Jorge Niedbalski ***@***.***> wrote:
@mnaser <https://github.com/mnaser> any chances to work on this? If not,
are you okay with flagging this for 1.2.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#78 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADKMZ7DHUORTSB6OMWXP33RZSVAJANCNFSM4KFSYJYA>
.
--
Mohammed Naser
VEXXHOST, Inc.
|
No work has been done or is planned to be done on this topic. |
We currently have a Zuul for open source projects that we run/maintain and I'd like to ask if it's possible to add this project to it.
It would allow us to do speculative testing and gating if we want to at some point too. It would just involve adding a GitHub application and adding the Zuul jobs in-repo (which I can do #2 but not #1)
The text was updated successfully, but these errors were encountered: