[Jenkins-infra] How to enable Travis CI for jenkins plugin repo
aheritier at gmail.com
Mon Sep 5 16:41:48 UTC 2016
it can be discussed on the infra list infra at lists.jenkins-ci.org and if
everyone is agree it could be changed.
I agree that I don't really see the interest of using default assignees in
Jira (I always found this counter productive)
On Mon, Sep 5, 2016 at 6:35 PM, Craig Rodrigues <rodrigc at freebsd.org> wrote:
> Thanks for fixing this. How can I put a proposal to the Jenkins admins
> that if a ticket is filed with Project* Infrastructure*, Component *CI*
> it gets assigned to a group of people, and not a single person?
> I'm not able to attend the weekly Jenkins governance meetings.
> Due to the popularity of Jenkins and the high volume of e-mails,
> the Jenkins mailing lists are increasingly becoming hard to follow
> and unusable for tracking the status of requests.
> On Thu, Aug 4, 2016 at 12:40 AM, Arnaud Héritier <aheritier at gmail.com>
>> 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 <rodrigc at freebsd.org>
>>> I'm OK with Cloudbees using a template to lock things down for
>>> One thing I would suggest is that in JIRA, if someone files an issue at
>>> 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
>>> 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.
>>> On Wed, Jul 20, 2016 at 4:14 PM, Kohsuke Kawaguchi <kk at kohsuke.org>
>>>> 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
>>> 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+unsubscribe at googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> For more options, visit https://groups.google.com/d/optout.
>> Arnaud Héritier
>> 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+unsubscribe at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> For more options, visit https://groups.google.com/d/optout.
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jenkins-infra