INFRA-741 fixed. But I agree that it is better to not assign them. Also our community CI should evolve soon with our recent partnership with Azure : https://jenkins.io/blog/2016/05/18/announcing-azure-partnership/
On Thu, Aug 4, 2016 at 9:15 AM, Craig Rodrigues <rodr...@freebsd.org> wrote: > I'm OK with Cloudbees using a template to lock things down for > jenkins.io.cloudbees.com. > > One thing I would suggest is that in JIRA, if someone files an issue at > https://issues.jenkins-ci.org > in Project *Infrastructure*, Component: *ci*, instead of auto-assigning > the issue to one > person (rtyler), it goes to a team of people who can maintain this. > > For example, I filed https://issues.jenkins-ci.org/browse/INFRA-741 in > June, and that got punted to Andrew Bayer. > Andrew is super-busy doing dev work on Jenkins, so I'm glad he has helped > in the past, but I don't > think this kind of stuff should get assigned to him, because his > considerable brainpower is better spent > on other activities, IMHO. > > Regarding Travis, it is an excellent service, and I use it heavily for > some other projects I am involved in. > I have also used Appveyor and Codecov.io, and they are also excellent > services. > > Travis and Appveyor are slightly competing with Jenkins, so I think it is > understandable for Cloudbees to want to > favor Jenkins for doing CI rather than using third party products and > services. It doesn't look good, otherwise. > > However, the Jenkins project and Cloudbees should see what can be done to > improve the level of support, > and also the feature set of jenkins.io.cloudbees.com, so that users do > not even have to consider using Travis > for Jenkins plugins. > > On a side note, I hope that the Plumber plugin work that Andrew has been > working on goes farther along. > Andrew gave me a demo of a YAML based configuration of a pipeline > workflow. I was impressed. This is very close > to the YAML configurations that Travis and Appveyor offer. > > -- > Craig > > > On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi <k...@kohsuke.org> wrote: > >> >> Like I said in my previous email, it's just that in >> jenkins.io.cloudbees.com we choose to use a template to lock things down. >> >> -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVeNHKKoRT-9Mv%3DJY41D%2BNWa%3DEogXQiS7n358C1fNNN%3DXg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- ----- Arnaud Héritier http://aheritier.net Mail/GTalk: aheritier AT gmail DOT com Twitter/Skype : aheritier -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-9vBC6y28pZODjgDLcQWW_tD7pQmfTqp%3Dd7h8pYZ5keLw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
