My original idea is that provides an alternative choice instead of replacing it. So, in my opinion, we can enable the GitHub actions if it's not harmful.
On Wed, Oct 9, 2019 at 6:06 AM Joseph P <[email protected]> wrote: > Here is one PR for feedback: > https://github.com/jenkins-infra/pipeline-library/pull/117/files > > Been waiting an hour for deploy stage to get green build on GitHub. > > So ci.jenkins.io is blocking 😠> I have considered removing the Jenkinsfile on some repos and just use > GitHub or Travis and forget incremental exist😰 > > On Monday, October 7, 2019 at 5:29:00 PM UTC+2, Olblak wrote: >> >> So right now Olbak the ACI agents are failing creating large queue. >> >> ci.jenkins.io must be stable if you want us to continue using it. >> >> >> What I tried to say in my previous answer was, if the issue is >> ci.jenkins.io then first let try to fix it. >> And if there is a another use case then let's discuss it. >> Regarding ci.j.io I'll probably start a document to collect feedback in >> the coming days >> >> --- >> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D >> --- >> >> >> >> >> On Fri, Oct 4, 2019, at 9:07 PM, Victor Martinez wrote: >> >> I do understand the value for using other CI/CD systems. My only concerns >> are when there are different GitHub checks and some of them are green and >> some others are red. That particular lack of reliability might imply more >> steps to troubleshoot to debug logs in different systems. I like the idea >> of dog-fooding even though when it does imply suffering some issues that >> other CI/CD systems might not have. >> >> As a consequence of decoupling this from the ci.jenkins.io then it could >> be more difficult to solve those issues in the ci.jenkins.io. That's >> something quite valuable no just for us as users but also for other users >> of the Jenkins project. >> >> I'd be happy to discuss this in another thread, if it has not been >> discussed recently, provide more feedback and gather other's point of view. >> >> Cheers >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/097e8aff-f133-4bd8-8ca3-2af74488d047%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/097e8aff-f133-4bd8-8ca3-2af74488d047%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/3c289e1b-0919-4eb5-8f83-f0bb0ac580a5%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/3c289e1b-0919-4eb5-8f83-f0bb0ac580a5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Zhao Xiaojie (Rick) Blog: https://github.com/LinuxSuRen Twitter: https://twitter.com/suren69811254 -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEBbiJaHY9Fe%2BBQ44ho7Hhetu4w7zykQ9mo--amu94wJw%40mail.gmail.com.
