Re: Deprecating ruby-runtime

[Owen Mehegan]

gitlab-plugin doesn't depend on it, but gitlab-hook plugin does. It has
been unmaintained for 5 years and functionality is replaced by
gitlab-plugin and gitlab-branch-source.

On Thu, Apr 15, 2021, 12:39 PM Jim Klimov  wrote:

> On April 14, 2021 6:45:30 PM UTC, Oleg Nenashev 
> wrote:
> >I am +1 for depreciation. I would recommend to make an announcement
> >blog
> >about that with e.g. 1-month advance notice, but there is no reason to
> >keep
> >these plugins around. Ruby plugin stack is not maintainable without a
> >full-time contributor, we should pick our battles
> >
> >On Wed, Apr 14, 2021, 20:36 Mark Waite 
> >wrote:
> >
> >>
> >>
> >> On Wed, Apr 14, 2021 at 12:20 PM Daniel Beck  wrote:
> >>
> >>>
> >>> Since the last time we discussed this (and I created the JEP), we
> >added
> >>> deprecation warning support to Jenkins 2.246 and newer, which is
> >basically
> >>> designed for such a case. This makes JEP-7 much cleaner to
> >implement,
> >>> because we now have good ways to inform users about it.
> >>>
> >>> I'd start with a deprecation warning for ruby-runtime and all
> >dependent
> >>> plugins pointing to the JEP or this thread (or, if you want to write
> >it up,
> >>> a blog post), and if folks don't complain offer to take over
> >>> ruby-runtime maintainership in large enough numbers, we can suspend
> >a few
> >>> weeks later, followed by core cleanup. WDYT?
> >>>
> >>>
> >> +1 from me.
> >>
> >>
> >> --
> >> You received this message because you are subscribed to a topic in
> >the
> >> Google Groups "Jenkins Developers" group.
> >> To unsubscribe from this topic, visit
> >>
> >https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> >> To unsubscribe from this group and all its topics, 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/CAO49JtFpo1yfG81wQYMUYp9vq3wFP%2BE40zA5cyAuZLYAQF83JQ%40mail.gmail.com
> >>
> ><
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFpo1yfG81wQYMUYp9vq3wFP%2BE40zA5cyAuZLYAQF83JQ%40mail.gmail.com?utm_medium=email_source=footer
> >
> >> .
> >>
>
> I believe there were plugins depending on it, that got me to have to pick
> java8 explicitly on one system. I think gitlab-plugin might be it.
>
> Jim
>
> --
> Typos courtesy of K-9 Mail on my Android
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> To unsubscribe from this group and all its topics, 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/DCF391B5-3BB1-415C-BD17-10E0D2859FE6%40cos.ru
> .
>

-- 
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/CAHtcACEF8CtS5%2Bmd2WbipJSt0S9EHhp_ZJ96ZQ30KgTqXm4%3DEg%40mail.gmail.com.

Re: Unable to release gitlab-plugin

[Owen Mehegan]

Thanks, you were right on both points! Daniel Beck and I worked on it last
night and finally figured out that my local checkout was borked ages ago. I
fixed that, and then Daniel helped fix the javadoc, and I think that has
sorted it out.

On Wed, Feb 17, 2021, 11:26 PM Jesse Glick  wrote:

> Oh and
>
> > Release preparation already completed. You can now continue with
> release:perform, or start again using the -Dresume=false flag
>
> Start with a clean checkout, or use `git clean -fdx`. (You can also use
> `mvn release:clean`.) maven-release-plugin is a mess; JEP-229 makes it
> unnecessary to go through this.
>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/pCst6cV3PmU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANfRfr16Zv5N5JVrOVapF6%3Dk6Ngta9G79P2bS8YuGdEZ70s7iA%40mail.gmail.com
> 
> .
>

-- 
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/CAHtcACG8ZtZcb88LFSZDodKeZckwL4jfvKaA1aH9G8X%3D08tXUA%40mail.gmail.com.

Re: Proposing Jenkins Docs SIG

[Owen Mehegan]

Hey Mark, I just confirmed that I am able to review, merge, etc. I would be
happy to try and do more of this in the future!

On Mon, May 6, 2019 at 11:58 AM Mark Waite 
wrote:

> That's great, Owen!
>
> Would you be willing to help me test an open question?  I think we need
> more reviewers and more mentors for doc contributions.  As far as I can
> tell, members of the copy-editors team have permission to review pull
> requests to jenkins.io and commit those changes.  I want more people with
> permission to review and merge, but want to be sure that I've understood
> the permissions granted to members of that group.
>
> You're a member of copy-editors.  Can you confirm that you're allowed to
> review jenkins.io pull requests
> , approve them, and merge
> them?
>
> Thanks
>
> On Sun, May 5, 2019 at 7:37 PM Owen B. Mehegan  wrote:
>
>> Hi Mark, I would be happy to get involved with the Docs SIG. 1300 UTC
>> will be too late for me to join the first meeting, but if you want to add
>> me to any email discussions, GitHub groups, etc. please feel free!
>>
>> On Sunday, May 5, 2019 at 5:16:38 AM UTC+10, Mark Waite wrote:
>>>
>>> In keeping with JEP-4
>>> , I'm posting to
>>> the developer mailing list my plan to create and lead the Jenkins Docs
>>> special interest group.
>>>
>>> I'll submit a pull request to jenkins.io with the structure described
>>> in JEP-4 .
>>>
>>> The first Docs special interest group meeting is scheduled for Friday,
>>> May 10, 2019 at 13:00 UTC. Proposed meeting agenda is at
>>> https://docs.google.com/document/d/1uNNo0QJKPHnNp8PGr_jLI8p3K_94ZYD-M0evZOEZ93c/edit#
>>> . We'll be using Zoom for the meeting, URL https://zoom.us/j/557525312
>>> .  We're using Zoom rather than Google Hangouts on Air so that we can test
>>> the Zoom account and so that we participants from China can attend the
>>> meeting.
>>>
>>> Draft mission statement:
>>>
>>> The Docs SIG focuses on improving Jenkins documentation. Improvements
>>> are targeted at both existing and new Jenkins users.  Scope of work
>>> includes reviewing improvement project ideas and working with potentials
>>> mentors and contributors in order to improve Jenkins documentation.
>>>
>>> Thanks,
>>> Mark Waite
>>>
>> --
>> 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/e47eca11-1835-4b17-b5f7-7ca26e039f76%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/5AMXnh3729E/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAO49JtETR2kddgAEwwcGuZ4iUs85pAFTbv8o%2B7K41KRReMq7NA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACGmPsNEWihhVrrJnLeHhrwMez%2BjHbYKAowGKYdVqB7JMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Deprecating ruby-runtime

[Owen Mehegan]

The gitlab-plugin that I maintain is technically a trigger plugin, not an
SCM plugin.

On May 16, 2018 9:31 PM, "Jesse Glick"  wrote:

> On Tue, May 15, 2018 at 7:56 PM, Owen B. Mehegan 
> wrote:
> > It has a single REST endpoint which all GitLab repos can point to.
> > When GitLab POSTs to this, the plugin looks at the GitLab repo in the
> > payload and then triggers all Jenkins jobs which clone that repo.
>
> I thought all SCM plugins had this system? `/git/notifyCommit`,
> `/github-webhook/`, `/mercurial/notifyCommit`,
> `/subversion/:UUID/notifyCommit`, etc.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/Ve0fqAud3Mk/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANfRfr3mE-j0q_WvE1CPb-m%2BUWaS%2Bv3tXBV-
> cGmM2e11Qgj7vQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACE%2BFy%2BZohvzQAniRPay65O6zewbPKQsJLkS5LhYAAj%3DsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Seeking new lead maintainer for the GitLab plugin

[Owen Mehegan]

Thanks! There are lots of open PRs that need review right now. And also a
few issues labeled "bug" which could use investigation. If you'd like to
work on any of those, that would be a great start! It's all in the Github
repo. https://github.com/jenkinsci/gitlab-plugin/

On Oct 21, 2017 9:04 AM, "khalid sookia"  wrote:

> Hello Owen, I would love to help
>
> Le mardi 13 décembre 2016 20:45:00 UTC+1, Owen B. Mehegan a écrit :
>>
>> We are seeking new maintainers for the GitLab plugin! The existing
>> codebase is clean and well-tested thanks to a lot of hard work done by
>> Robin, the former lead maintainer, but he is no longer using GitLab and
>> does not have spare time to keep working on the plugin. We're looking for
>> an active GitLab user and experienced Java programmer to take over. The
>> main work necessary at this point is resolving minor bugs and maintaining
>> support for new versions of GitLab. I've been handling the triage of new
>> issues and improvements to the documentation, but I'm not capable enough
>> (read: at all) with Java to do much with the code. If you're interested,
>> reach out to me here!
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/Fr71Wvo6dns/unsubscribe.
> To unsubscribe from this group and all its topics, 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/78480605-1f1a-435f-9dac-78eb83e58bfa%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFxego5anwNWkvjKAP0XJdrpVJ3BZwQ8w4os5Qt1ecX4g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

[Owen Mehegan]

Having read and edited JEP-1, I am in favor of this idea as presented :)

On Wed, Sep 13, 2017 at 1:34 PM, Keith Zantow  wrote:

> ... random suggestion: "JPI" Jenkins Proposal Initiative/Initiation.
>
> On Wed, Sep 13, 2017 at 4:23 PM, Jesse Glick  wrote:
>
>> On Wed, Sep 13, 2017 at 3:32 PM, R. Tyler Croy 
>> wrote:
>> > I think we should try to reach
>> > consensus on this thread
>>
>> Sounds like a good idea to me! Structure seems pretty clear.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CANfRfr32TJTKwgWmM5oegVZDGCOHnxV-9EoDaO%
>> 2B71jBh6zR5-g%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/CAJTHQaGTECfjPPq_kDt81YEUuWubTmyAqq7b1X%
> 2B4YoGtMrGJDw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFrme5PD-FV8iJ9%2B4yraZtAhuX6iX68%2BtZ9-OYvYbsxfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins build is not running

[Owen Mehegan]

I think this belongs on the jenkinsci-users list. This list is for topics
related to the development of Jenkins and its plugins.

On Aug 23, 2017 1:14 PM, "phanikumar" 
wrote:

> Hello team,
>
> I recently started using Jenkins on kubernetes and configured my kubernetes
> cloud. For testing purpose, I have created a sample Jenkins job and ran the
> build. Now, it is showing (pending—Waiting for next available executor) at
> the build and no node is getting created. I haven't seen any error in
> Jenkins system log as well. Can someone help me how to troubleshoot it.
>
>
>
> --
> View this message in context: http://jenkins-ci.361315.n4.
> nabble.com/Jenkins-build-is-not-running-tp4901501.html
> Sent from the Jenkins dev mailing list archive at Nabble.com.
>
> --
> 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/1503519246069-4901501.post%40n4.nabble.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACG9uLdr%3DNEF3KKzCdMY2e6p5igsdcE0uFVN6_2PTZ6Gmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GitHub and Bitbucket branch source UI refactoring

[Owen Mehegan]

Does this mean we can move forward with working on GitLab branch source
work after these changes are final?

On Fri, Jun 16, 2017 at 11:18 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> Just a quick status update.
>
> In final stages of this work now. Bobby is being a superstar and reviewing
> my 13k LoC change on the Bitbucket branch source - brings lots of feature
> parity with GitHub and adds the configuration ability of the pure Git
> branch source
>
> I am finalising the GitHub Branch Source changes... likely to be another
> big PR
>
> Then there's a 5k LoC change in the Git plugin
>
> Plan is to try and get all merged next week and cut a beta
>
> I'll be looking for people to help test at that stage.
>
> Please respond if you think you can help (lots of bugs fixed as a side
> effect of the refactoring - it makes things more easy to test => I found
> and fixed bugs)
> --
> Sent from my phone
>
> --
> 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/CA%2BnPnMxfYrZphgYDXFD3i%2Bo_
> 7eDn7mn2qVrzJz6wFaoVkNmc%2Bw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACF7FpgZ%3D_i1596JMuWRipfKhxVPNT3n%3D%3DzPt%2BwUOaOb0g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[Owen Mehegan]

Can we have a subgroup for people who always post to the wrong group?
On May 20, 2017 9:25 AM, "Slide"  wrote:

> Groups.io allows subgroups as well. You could have
> plugin-...@jenkins.groups.io, u...@jenkins.groups.io, etc.
>
> On Sat, May 20, 2017, 09:19 Gavin Mogan  wrote:
>
>> One advantage of something like discourse is splitting things up into sub
>> topics
>> * Jenkins Usage
>> * Plugin Development
>> * Jenkins Development
>>
>> Puts everything in one place, but it might get too tempted to split
>> things into tiny tiny groups.
>> I figure it could help with people posting to the wrong mailing lists.
>>
>> Gavin
>>
>> On Monday, May 15, 2017 at 1:47:57 AM UTC-7, Baptiste Mathus wrote:
>>
>>> Well, the main difference for JIRA is that we know where to look at. In
>>> GGroups case, we have nobody/nowhere to shout on ;-)
>>>
>>> 2017-05-15 10:45 GMT+02:00 James Nord :
>>>
>> By that measure we should have moved from JIRA[1] years ago :-)

 So long as I can post from the web using a mobile phone I am fine with
 a replacement.

 [1](it was unavailable at least twice last week)

>>>
 --
 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-de...@googlegroups.com.

>>> To view this discussion on the web visit https://groups.google.com/d/
 msgid/jenkinsci-dev/e5e4cc8d-d03e-4e18-9c88-0062984b937f%
 40googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
>> 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/83f7d872-019d-4e26-9605-ecdddb89345f%
>> 40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CAPiUgVdvXbyzK1V2SiFXM-mYzagf1sZ%
> 2BjSSxixhWLP80yCG3mA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACEaD4WKEh8wcCbuGvRrMRT5j4_36AA7XdqjwrmBn4rWRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[Owen Mehegan]

Moving one group might be wisest.

I won't promise that groups.io will solve all our problems, but my
impression is that it will be easier to get support from them. It appears
that getting support from Google is like shouting into a paper bag.
On May 12, 2017 3:52 PM, "Richard Bywater" <rich...@byh2o.com> wrote:

> Cool - seems reasonable to me then. Would it be best to move one list
> first as a trial or would that be to confusing to people?
>
> Richard
>
> On Sat, 13 May 2017, 10:44 AM Owen Mehegan <omehe...@gmail.com> wrote:
>
>> Yep, like this:
>>
>> ​
>>
>> On Fri, May 12, 2017 at 3:41 PM, Richard Bywater <rich...@byh2o.com>
>> wrote:
>>
>>> Does groups.io support mailing list operation or is it only a web based
>>> service? (My 10 second  scan of the home page on my phone didn't seem to
>>> answer the question :) )
>>>
>>> Richard
>>>
>>> On Sat, 13 May 2017, 10:23 AM Owen Mehegan <omehe...@gmail.com> wrote:
>>>
>>>> I vote for groups.io.
>>>>
>>>> On Fri, May 12, 2017 at 3:17 PM, R. Tyler Croy <ty...@monkeypox.org>
>>>> wrote:
>>>>
>>>>> If you can read this, the Google Group has been reinstated as quietly
>>>>> as it was
>>>>> banned.
>>>>>
>>>>>
>>>>> I think it might be time for us to be moving on :(
>>>>>
>>>>>
>>>>> - R. Tyler Croy
>>>>>
>>>>> --
>>>>>  Code: <https://github.com/rtyler>
>>>>>   Chatter: <https://twitter.com/agentdero>
>>>>>  xmpp: rty...@jabber.org
>>>>>
>>>>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>>>>> --
>>>>>
>>>>> --
>>>>> 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/20170512221709.czb32qypxxjducx7%40blackberry.
>>>>> coupleofllamas.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>>> 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/CAHtcACFevjg6zpZQi4RJsnoBQC2-
>>>> SYXgN0z46_hywr7pDtLEdQ%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACFevjg6zpZQi4RJsnoBQC2-SYXgN0z46_hywr7pDtLEdQ%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
>>> 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/CAMui946ja15DKDeg4kFRyqw7cggPg
>>> oK1WJEFvt-TUEFz3H3x3g%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui946ja15DKDeg4kFRyqw7cggPgoK1WJEFvt-TUEFz3H3x3g%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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/CAHtcACFtFhsxWX54%3D-gpkb9kGcto2oSs9yizrzYh28OYUAx5
>> Og%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACFtFhsxWX54%3D-gpkb9k

Re: So I guess it's time to leave Google Groups

[Owen Mehegan]

Yep, like this:

​

On Fri, May 12, 2017 at 3:41 PM, Richard Bywater <rich...@byh2o.com> wrote:

> Does groups.io support mailing list operation or is it only a web based
> service? (My 10 second  scan of the home page on my phone didn't seem to
> answer the question :) )
>
> Richard
>
> On Sat, 13 May 2017, 10:23 AM Owen Mehegan <omehe...@gmail.com> wrote:
>
>> I vote for groups.io.
>>
>> On Fri, May 12, 2017 at 3:17 PM, R. Tyler Croy <ty...@monkeypox.org>
>> wrote:
>>
>>> If you can read this, the Google Group has been reinstated as quietly as
>>> it was
>>> banned.
>>>
>>>
>>> I think it might be time for us to be moving on :(
>>>
>>>
>>> - R. Tyler Croy
>>>
>>> --
>>>  Code: <https://github.com/rtyler>
>>>   Chatter: <https://twitter.com/agentdero>
>>>  xmpp: rty...@jabber.org
>>>
>>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>>> --
>>>
>>> --
>>> 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/20170512221709.czb32qypxxjducx7%40blackberry.
>>> coupleofllamas.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> 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/CAHtcACFevjg6zpZQi4RJsnoBQC2-
>> SYXgN0z46_hywr7pDtLEdQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHtcACFevjg6zpZQi4RJsnoBQC2-SYXgN0z46_hywr7pDtLEdQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CAMui946ja15DKDeg4kFRyqw7cggPg
> oK1WJEFvt-TUEFz3H3x3g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMui946ja15DKDeg4kFRyqw7cggPgoK1WJEFvt-TUEFz3H3x3g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFtFhsxWX54%3D-gpkb9kGcto2oSs9yizrzYh28OYUAx5Og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: So I guess it's time to leave Google Groups

[Owen Mehegan]

I vote for groups.io.

On Fri, May 12, 2017 at 3:17 PM, R. Tyler Croy  wrote:

> If you can read this, the Google Group has been reinstated as quietly as
> it was
> banned.
>
>
> I think it might be time for us to be moving on :(
>
>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20170512221709.czb32qypxxjducx7%40blackberry.
> coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFevjg6zpZQi4RJsnoBQC2-SYXgN0z46_hywr7pDtLEdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Ambassador Program

[Owen Mehegan]

Sounds good to me :)

On Tue, May 9, 2017 at 4:57 PM, Alyssa Tong  wrote:

> Great question. Submissions can be made via a simple google form. I will
> create this form and include link on the wiki page.
>
> On Tue, May 9, 2017 at 3:55 PM, R. Tyler Croy  wrote:
>
>> (replies inline)
>>
>> On Tue, 09 May 2017, Alyssa Tong wrote:
>>
>> > Hello,
>> >
>> > In the last governance meeting, I proposed Jenkins Ambassador
>> > 
>> program.
>> > There were some questions that came out of that meeting which I hope
>> I've
>> > clarified them via the updated wiki page
>> > . I
>> wanted
>> > to open it up for discussions here and see if there's any
>> > feedback/suggestions for this program.
>> >
>>
>>
>> This looks good to me! What would the nomination process look like? Would
>> that
>> be sending an email somewhere, or what?
>>
>>
>>
>>
>>
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>  xmpp: rty...@jabber.org
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>> --
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/20170509225553.2fnefq4tviafcuxp%
>> 40blackberry.coupleofllamas.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/CAC9wNay27RP3tH%3DZ5g4sLiE%
> 3Dqteg7fbMFyQpdeB6uiWNzn2ZpQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFhFv0pSTwLiaiw4L0ZDYrrQ4Gff9e%3Dw_38ObmVO%2BBGNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Should we only block clear spam, or also irrelevant emails to dev ML? (was: Re: What's Italian for "New-poster moderation for Google Groups has been enabled?")

[Owen Mehegan]

+1
On May 3, 2017 1:54 AM, "Daniel Beck"  wrote:

>
> > On 03.05.2017, at 10:03, Baptiste Mathus  wrote:
> >
> > I would personally prefer the 1) or possibly 1.1) option.
> > 1) is simpler to handle and probably enough provided we update
> https://jenkins.io/mailing-lists/ with a notice like "emails for the
> users ML will be refused"
>
> If this is less effort than explaining it, go for it. The mailing lists
> are clearly documented, and our time is better spent doing things that
> benefit lots of people, than spoon-feeding those incapable of reading
> https://jenkins.io/mailing-lists/
>
> --
> 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/43AFFC70-E216-4E2B-93F0-5850B7DA3081%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACG9y7iqBN7jetWX7_DhwaHsOqLorHh4GFvONR8paBFeoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Regarding the recent waves of mailing list spam

[Owen Mehegan]

Me three. It seems like ideally we would have some folks dedicated who are
in different time zones, and if we each reviewed the moderation queue at
the start of our workday, there would be minimal lag in posting. I'm in PST.

On Mon, Apr 17, 2017 at 10:35 AM, Slide  wrote:

> +1 for me as well. I would definitely be willing to help out.
>
> On Mon, Apr 17, 2017 at 10:26 AM Mark Waite 
> wrote:
>
>> How much time do you think would be required per week for an active
>> moderator, assuming we could enlist 5+ active moderators?
>>
>> I'm interested, so long as active moderation doesn't cost me too much
>> time.
>>
>> Mark Waite
>>
>> On Mon, Apr 17, 2017 at 9:53 AM R. Tyler Croy 
>> wrote:
>>
>>>
>>> As you may have noticed, there has been an uptick in spam getting
>>> through to
>>> the Google Groups run by the Jenkins project. On some lists, these have
>>> resulted in Google flagging the group and bouncing emails from those
>>> groups.
>>>
>>> This was discussed during our last project meeting
>>> (http://meetings.jenkins-ci.org/jenkins-meeting/2017/
>>> jenkins-meeting.2017-04-12-18.00.html),
>>> and as promised I wanted to let everybody know where things stand and
>>> why.
>>>
>>>
>>> If you receive emails as they're posted (non-digest mode) from Google
>>> Groups,
>>> if a spamemr gets through, there's nothing we can do for you. While I
>>> have
>>> added a couple more "Manager" roles to the jenkinsci-users@ list, who
>>> can ban
>>> authors and delete posts, once something is delivered to your inbox,
>>> there's
>>> nothing we can do.
>>>
>>> Some people have suggested first-poster moderation, which is one option,
>>> but
>>> not one I'm personally willing to turn on until more people are active
>>> moderators. Unfortunately I took a weekend off from my morning-routine of
>>> banning spammers two weekends ago, which seems to have led to the recent
>>> surge
>>> and flagging of the group.
>>>
>>>
>>> What we are evaluating between last project meeting and the upcoming one
>>> (April
>>> 26) is whether Google Groups is still a viable option for the Jenkins
>>> project.
>>> A number of other projects have moved to groups.io, which would be a
>>> likely
>>> destination if Google continues to flag our groups.
>>>
>>>
>>>
>>> Consider yourselves updated, feel free to ping me on IRC (rtyler) with
>>> questions.
>>>
>>>
>>> Cheers
>>> - R. Tyler Croy
>>>
>>> --
>>>  Code: 
>>>   Chatter: 
>>>  xmpp: rty...@jabber.org
>>>
>>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>>> --
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-users/20170417155333.h7l2ecplmhbcg2ut%40blackberry.
>>> coupleofllamas.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> 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/CAO49JtGWMW3rhVCV3ZH0%3DQo68pho-G1NvP14poL3A%
>> 3DBdTq40eg%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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/CAPiUgVeGyQmVRqxb%3D3GiAoC9eXi%2BOAnAkP%
> 3DMSoJRHLg8ipOWhw%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACHX%3DZj%2BNAiCu%2B3FVT0_FcrJx-ChVDgAJK7NDpGj9P_6cA%40mail.gmail.com.
For more options, visit 

Re: Seeking new lead maintainer for the GitLab plugin

[Owen Mehegan]

We've had a few volunteers, but more would be welcome! Right now there are
several open PRs which could use a review and +1, and a number of open
issues as well. Some are marked as known bugs or feature requests, which
anyone would be welcome to work on, and a few other unmarked ones need more
investigation. Anything you can do to contribute would be great. Thanks!

On Mon, Mar 27, 2017 at 4:47 PM, Med Arrafi  wrote:

> I would love to help you out! contact me if you're interested
>
> Le mardi 13 décembre 2016 19:45:00 UTC, Owen B. Mehegan a écrit :
>>
>> We are seeking new maintainers for the GitLab plugin! The existing
>> codebase is clean and well-tested thanks to a lot of hard work done by
>> Robin, the former lead maintainer, but he is no longer using GitLab and
>> does not have spare time to keep working on the plugin. We're looking for
>> an active GitLab user and experienced Java programmer to take over. The
>> main work necessary at this point is resolving minor bugs and maintaining
>> support for new versions of GitLab. I've been handling the triage of new
>> issues and improvements to the documentation, but I'm not capable enough
>> (read: at all) with Java to do much with the code. If you're interested,
>> reach out to me here!
>>
> --
> 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/5aec193e-1843-40c6-86d1-70273b99b4af%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACHznDG5GhQ77b_DR%3DKxyn9yr50MRvJ39Nh-M6KqsshaHw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Can a trigger plugin receive events from the /job/JOBNAME endpoint?

[Owen Mehegan]

I'm the caretaker (not quite a maintainer) of the gitlab-plugin. One
user/support headache we frequently have is with people messing up their
config of the GitLab webhook that triggers their jobs. Our plugin requires
GitLab to POST to JENKINS_URL/project/JOBNAME. A lot of people make the
mistake of using JENKINS_URL/job/JOBNAME and get unexpected results,
because although the build triggers the plugin is not invoked and none of
the metadata that GitLab sends is used.

Is it possible for a trigger plugin to hook in at the /job endpoint? I'm
assuming not, because that would tend to confuse the basic "trigger builds
from scripts" functionality. But I thought I would ask anyway, as we could
consider changing this if it were possible.

-- 
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/CAHtcACF1S7VvQVi0q52ktVW8UADPDBurHueu5K_UjtOqDNN-OQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Seeking Advice on Building First CI

[Owen Mehegan]

This list is for discussing the development of Jenkins and its plugins.
Please ask your question on the Users list:
https://groups.google.com/forum/#!forum/jenkinsci-users

On Wed, Feb 8, 2017 at 1:18 PM, Robert Werner 
wrote:

> I'm building a Jenkins based CI for the first time.  Here are the use
> cases I'm considering for it:
>
>1. Ability to run Unit Tests, Integration Tests, & Acceptance Tests in
>Local Dev environment (without Jenkins).
>
>2. Ability to run Unit Tests, Integration Tests, & Acceptance Tests in
>Remote Dev, Staging, & Production environments.
>
>3. When code is reviewed & committed to Master branch then Unit Tests,
>Integration Tests, & Acceptance Tests are run in Remote Dev, Staging, &
>Production environments.
>
>
> #1 is a certainty, essentially a script to rebuild the app and run the
> tests on it.  While this could be done in a few steps in the IDE, I think
> this script would be handy.
>
>
> Where I'm not quite sure about is the workflow that happens next.  My
> first thought is that the developer will commit all of the changes in his
> branch, push these changes to the remote branch, and then issue a pull
> request.  When the code is reviewed, approved, and the branch is merged
> with the Master branch then this will automatically call Jenkins as per #3.
>
>
> But what about #2?  Is it common to give a developer the ability to run
> all of the tests first in these 3 environments (or maybe just Remote Dev?)
> before committing such changes?
>
>
> I would appreciate feedback from all CI experts out there!
>
>
> Robert
>
> --
> 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/de9ff752-ed87-4aaf-a8b7-e007adec54a5%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACG-xEvnDjgvXW25Ty7nzF-aNYu5ES2CG-96w_ubWOWo3g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update Swarm plugins' remoting dependency

[Owen Mehegan]

I would suggest you look at the recent commits and reach out to the person
who did the last release, rather than just posting on this mailing list.
See https://github.com/jenkinsci/swarm-plugin/commits/master

(Perhaps mindjiver should be listed as the maintainer on the wiki page?)

-- 
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/CAHtcACGnc%2BFxGkK7%3DatSv_HdcMRcg26N%2BKgbj0fABHqZsrH_og%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request Gitlab Plugin

[Owen Mehegan]

I will add you as a committer ASAP. Given that we now have a couple of
people jointly maintaining the plugin, I suggest that we limit the use of
direct commits to updating documentation. For code changes, please continue
to use PRs, so we can have some code review. Thanks and welcome aboard!

On Thu, Jan 19, 2017 at 12:26 AM, Abir M  wrote:

> Hi,
> I have been using this plugin quite extensively, especially with the new
> pipeline syntax. Submitted a pull request yesterday to support the new
> syntax #488. There's more to do though and I want to add a few more
> examples to the readme and pipeline based tests. If I can have commit
> access I should have some time in the coming weeks. My Github id
> is colourmeamused, I can sign up for a Jenkins account if needed.
> cheers,
> abir
>
> On Thursday, January 5, 2017 at 9:15:28 AM UTC+11, Owen B. Mehegan wrote:
>>
>> Thanks for your interest! I have given you commit access. Please use it
>> carefully :) Our practice thus far has been to make minor bugfix changes
>> directly to master, but any more significant feature work in branches with
>> a PR for discussion before merging.
>>
>> I have just caught up on a lot of the open issues and PRs, and did a
>> release. If you want to discuss anything with me, the best place would be
>> either via email here or in the #gitlab-plugin channel on Freenode IRC.
>>
>> Welcome aboard!
>>
>> On Wed, Jan 4, 2017 at 2:39 AM, Posa Bogdan  wrote:
>>
>>> Hello,
>>> I want to become a maintainer of GitLab plugin ->
>>> https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin
>>>
>>> GitHub ID: trance1st
>>> Jenkins ID: posabogdan
>>>
>>>
>>> Kind regards,
>>> Bogdan Posa
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/0b106969-8483-4df8-ad61-18bf4b6b2c05%40goo
>>> glegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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/ac96785b-b04b-4860-bae4-bc637946997b%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACEO%3DdG%2BOoE7oSWYxS7PxHg6rHejHJReot_Exx7FG3bBHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bug Triage "Team"

[Owen Mehegan]

This sounds like a solid first pass to me, worth trying out for a month or
so to see how it goes.

I'm also interested in helping, so put me on the list!
On Jan 19, 2017 9:34 AM, "Slide"  wrote:

> There was a discussion in the Governance Meeting yesterday [1] about
> creating a Bug Triage "Team." The goal of this team would be to triage
> issues on [2] to make sure that they are assigned to the correct component,
> assigned to the correct developer and are actually still valid. The reason
> the idea of an official "Team" was put forward would be so that those
> people would have the ok to touch issues across the board. There are some
> people that do this already (Daniel Beck and a few others) who most people
> know, so they have some credibility already, some of the volunteers for
> this may not, so we thought being part of the team would allow users have
> more credibility if they are less well known to the community.
>
> We discussed in the meeting that we should focus on a couple of key areas
>
> 1) issues assigned to the core component with no assignee
> 2) issues assigned to plugins that are part of the "recommended" set of
> plugins for the new install wizard
> 3) issues that are not assigned to anything or anyone in particular
>
> The outcome of a triage on a specific issue would be that the correct
> component(s) and assignee were there. In addition, if possible a test to
> see how reproducible the issue is. If an issue has languished for some time
> and is using very old versions of Jenkins/plugin/etc, we would close the
> issue (it could still be reopened if someone is still seeing the issue).
>
> I'd like to get some feedback on this proposal:
>
> 1) Do we have the correct scope planned out?
> 2) Is more detail needed?
> 3) Anything else you want to ask/propose?
>
> If you want to participate in the team, please let me know and I'll start
> collecting a list of people. Please note, you don't need to be a developer
> to help here, if you can create a Jenkins instance and try and reproduce
> issues, that is great too, or even just getting the component(s) and
> assignees in place would be very helpful.
>
> Thanks,
>
> Alex Earl
>
>
> 1 - http://meetings.jenkins-ci.org/jenkins-meeting/2017/
> jenkins-meeting.2017-01-18-18.01.html
> 2 - https://issues.jenkins-ci.org
>
> --
> 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/CAPiUgVfuKH8SyZdg_MPDi963hLy-
> HAAjfWS8HSYw3zdHLk7FNw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFfDqbu7xPEjVK3wyGEJAut3wwg8c7Mwe8%2Bk85Cwz10Mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request Gitlab Plugin

[Owen Mehegan]

That instance does not build the plugin for release, it just runs the tests
for visibility on Pull Requests.

When releasing, I have always just run that locally, following the
instructions here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org

On Tue, Jan 10, 2017 at 12:57 PM, Posa Bogdan  wrote:

> Hello,
>
> Thanks for accepting me.
> How can I have access to the Jenkins instance which builds the plugin
> https://jenkins.ci.cloudbees.com/job/plugins/job/gitlab-plugin/ ?
>
>
> joi, 5 ianuarie 2017, 00:15:28 UTC+2, Owen B. Mehegan a scris:
>>
>> Thanks for your interest! I have given you commit access. Please use it
>> carefully :) Our practice thus far has been to make minor bugfix changes
>> directly to master, but any more significant feature work in branches with
>> a PR for discussion before merging.
>>
>> I have just caught up on a lot of the open issues and PRs, and did a
>> release. If you want to discuss anything with me, the best place would be
>> either via email here or in the #gitlab-plugin channel on Freenode IRC.
>>
>> Welcome aboard!
>>
>> On Wed, Jan 4, 2017 at 2:39 AM, Posa Bogdan  wrote:
>>
>>> Hello,
>>> I want to become a maintainer of GitLab plugin ->
>>> https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin
>>>
>>> GitHub ID: trance1st
>>> Jenkins ID: posabogdan
>>>
>>>
>>> Kind regards,
>>> Bogdan Posa
>>>
>>> --
>>> 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-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/0b106969-8483-4df8-ad61-18bf4b6b2c05%40goo
>>> glegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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/d05a21b0-bdc5-4223-a2f0-4b28f5375ae2%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACEqLb%2B8GN-niDaSKvxTAARR-EdKLH3Cz0VnL39hG%3Dw5Gg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request Gitlab Plugin

[Owen Mehegan]

Thanks for your interest! I have given you commit access. Please use it
carefully :) Our practice thus far has been to make minor bugfix changes
directly to master, but any more significant feature work in branches with
a PR for discussion before merging.

I have just caught up on a lot of the open issues and PRs, and did a
release. If you want to discuss anything with me, the best place would be
either via email here or in the #gitlab-plugin channel on Freenode IRC.

Welcome aboard!

On Wed, Jan 4, 2017 at 2:39 AM, Posa Bogdan  wrote:

> Hello,
> I want to become a maintainer of GitLab plugin -> https://wiki.jenkins-ci.
> org/display/JENKINS/GitLab+Plugin
>
> GitHub ID: trance1st
> Jenkins ID: posabogdan
>
>
> Kind regards,
> Bogdan Posa
>
> --
> 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/0b106969-8483-4df8-ad61-18bf4b6b2c05%
> 40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFX1eOuVvHBNbemd9Ej4ytWi9ik%3D5SLaGRx-RE83iwd%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should this list be moderated?

[Owen Mehegan]

Oh, I didn't realize that admins could purge messages after they arrive on
the list.

Seems like the general consensus is against more moderation. I'm OK with
that :)

On Wed, Dec 28, 2016 at 10:46 AM, R. Tyler Croy  wrote:

> (replies inline)
>
> On Wed, 28 Dec 2016, Baptiste Mathus wrote:
>
> > I would be +1, because IIRC Google groups allows moderator to validate
> some
> > users forever automatically.
> > So basically, there would be no moderation delay very quickly for the
> vast
> > majority of emails here, and only a slight one for newcomers since I
> expect
> > many of us volunteer to help and hence the new emails would not stay long
> > in the queue.
>
>
> As an existing Moderator for this list, I don't want any more burden plz
> kthx.
>
> Generally speaking, the project needs fewer, not more, manual processes
> right
> now :(
>
>
>
> That said, when I'm not on vacation (which happened recently), I'm
> typically
> purging these stupid job postings every morning when I start my day PST. I
> know
> a few others have access, but they're not as habitual as I am it seems.
>
>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20161228184618.GF9253%40blackberry.coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACFf8VCfAnMgi0MK5Mf9x8zQ1N7FEDSFstJ6Vd6-VdbRug%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Should this list be moderated?

[Owen Mehegan]

It seems like about 1/4 to 1/3 of the new threads on this list are either
spam or topics that belong on the users list instead of here. Is there any
interest in making the list moderated to help improve the signal to noise
ratio? I would be willing to help moderate. I think the only possible
downside is that we do want to direct people to the other list when
appropriate, so a moderator would need to reject their message but tell
them about the other list. But a number of us are doing that all the time
anyway, just as regular replies.

-- 
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/CAHtcACGEbwdzpYyK7J%3Di1ojxTL%3Dca4FBVA6DOfe3DZFi8-bkCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help needed with Workflow support in gitlab-plugin

[Owen Mehegan]

Some comments inline...

On Thu, Nov 12, 2015 at 10:37 AM, Jesse Glick  wrote:

> On Wed, Nov 11, 2015 at 6:22 PM, Owen B. Mehegan 
> wrote:
> > I can't figure out how to access the branch parameters that the
> > plugin is setting. If you look at the 'Using it with a job' section of
> the
> > readme, it has you configure Git to expect variables like
> gitlabSourceBranch
> > and gitlabTargetBranch to be set when a build is triggered by Gitlab.
>
> Two things.
>
> First of all, the code in `onPost` is wrong. See
>
> https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md
>
> for background but basically you need to be using
> `ParameterizedJobMixIn`, which allows `actions` to be passed to any
> build you schedule. There is no need to check for `instanceof
> AbstractProject`.
>

OK, I'll look at refactoring this.

Second, the whole system the plugin is using to specify a branch per
> build can be considered obsolete. Instead, depend on `scm-api`,
> implement `SCMSource`, and use multibranch workflows (or other
> multibranch projects). See `github-branch-source` for an example.
>

I think I get what you're saying: that the plugin should move toward the
multibranch project model, rather than one job which takes a parameter of
branch (and whose current "status" is therefore usually meaningless). I'm
open to that idea but I suspect it will be more work to implement. I'll
consider it part of the roadmap for this plugin.

--
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/CJEbh85zRx8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CANfRfr2y9oMS6T7Maje_VahF7qp5LqoFv0JaTZ7zFYdO-_1hyg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAHtcACGtDiMCHx4mzjRS2Ma9gaw0%3D1WcnScB-a7AJ6ifBkYAxQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Help needed with Workflow support in gitlab-plugin

[Owen Mehegan]

Some comments inline...

On Thu, Nov 12, 2015 at 2:51 AM, Robert Sandell <rsand...@cloudbees.com>
wrote:

> It seems like when the job is not an AbstractProject e.g. a WorkflowJob
> then the job isn't scheduled with parameters
> https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java#L204
>

Aha... would this explain why the plugin also doesn't seem to work with
matrix jobs?


> [1] and [2] are some examples on how to schedule a job with parameters
> where the job implements ParameterizedJobMixIn.ParameterizedJob which any
> job type that takes parameters should implement (FreeStyle, Workflow Maven
> etc)
> There are probably more examples out there.
>
> [1]
> https://github.com/jenkinsci/gerrit-trigger-plugin/blob/master/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/EventListener.java#L231
> [2]
> https://github.com/jenkinsci/dockerhub-notification-plugin/blob/master/src/main/java/org/jenkinsci/plugins/dockerhub/notification/DockerHubWebHook.java#L167
>
> /B
>

Thanks, I might make a pass at solving the immediate problem this way, just
to unblock myself.


>
> On Thu, Nov 12, 2015 at 7:07 AM, Owen Mehegan <omehe...@gmail.com> wrote:
>
>> I tried that, but the values come back null, so I don't think they're
>> getting set as environment variables per se.
>>
>> On Wed, Nov 11, 2015 at 10:04 PM, Mirko Friedenhagen <
>> mfriedenha...@gmail.com> wrote:
>>
>>> Hello Owen,
>>>
>>> as far I know environment variables need to be prefixed with env when
>>> accessing them from Groovy, so maybe it should be
>>> "origin/${env.gitlabSourceBranch}" …?
>>>
>>> Regards
>>> Mirko
>>> --
>>> Sent from my mobile
>>> Am 12.11.2015 00:22 schrieb "Owen B. Mehegan" <o...@nerdnetworks.org>:
>>>
>>>> Earlier this year I bribed an intern and another coworker to implement
>>>> Workflow support in the GitLab plugin (
>>>> https://github.com/jenkinsci/gitlab-plugin for reference). They made
>>>> an initial pass at it, with support from jglick. Now I've realized that the
>>>> support is incomplete. We've since taken over maintainership of the plugin,
>>>> but we're still totally inexperienced with Jenkins plugin code. I have two
>>>> issues that we need help with.
>>>>
>>>> First, I can't figure out how to access the branch parameters that the
>>>> plugin is setting. If you look at the 'Using it with a job' section of the
>>>> readme, it has you configure Git to expect variables like
>>>> gitlabSourceBranch and gitlabTargetBranch to be set when a build is
>>>> triggered by Gitlab. This works fine in freestyle builds. In a Workflow
>>>> build, I used the snippet generator and it gave me this output (corrected
>>>> with double quotes around strings containing variables):
>>>>
>>>> checkout changelog: true, poll: true, scm: [$class: 'GitSCM', branches:
>>>> [[name: "origin/${gitlabSourceBranch}"]],
>>>> doGenerateSubmoduleConfigurations: false, extensions: [[$class:
>>>> 'PreBuildMerge', options: [fastForwardMode: 'FF', mergeRemote: 'origin'
>>>> , mergeTarget: "${gitlabTargetBranch}"]]], submoduleCfg: [],
>>>> userRemoteConfigs: [[name: 'origin', url: 'g...@gitlab.mysite.com:
>>>> test/testrepo.git']]]
>>>>
>>>> But when the job is triggered, those variables are not set - I get a 
>>>> groovy.lang.MissingPropertyException
>>>> for them. I'm pretty sure that the relevant part of the plugin code is
>>>> here:
>>>> https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java#L235
>>>> Beyond that, I'm clueless as to what might need to change.
>>>>
>>>> Second, it seems that if the most recent build of the project failed to
>>>> check out the repo, the plugin fails to trigger any further builds. It logs
>>>> the error, 'Could not find GitSCM for project,' and that's generated here:
>>>> https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/GitLabPushTrigger.java#L802
>>>> I guess this is related to the fact that the plugin ALSO can't trigger a
>>>> brand new job until you run it manually one time. Jesse mentioned that this
>>>> would be a problem - running it causes it to store some gitSCM state which
>>>> the plugin i

Re: Looking for some help with a baffling plugin bug (ansicolor)

[Owen Mehegan]

Turns out this was a failure of the plugin to migrate its global 
configuration after some code was refactored. Open to any guidance about 
best practices for doing that cleanly during an upgrade.

On Monday, October 19, 2015 at 1:59:04 PM UTC-7, Owen Mehegan wrote:
>
> Myself and the maintainers of the jenkins-ansicolor plugin have been 
> struggling with a weird bug. So far I am the only one who can reproduce it, 
> and I can only repro it on my production Jenkins server. A 
> seemingly-identical test server does not exhibit the bug. We seem to have 
> exhausted most of the obvious possible causes. I have isolated the breakage 
> to a specific commit, but that hasn't helped us come up with a fix. I'm 
> hoping that getting some additional experienced eyes on the problem might 
> generate some other suggestions for how we could debug this (I'm also 
> personally limited in that I don't really know Java at all). My comment at 
> https://github.com/dblock/jenkins-ansicolor-plugin/issues/57#issuecomment-148869752
>  
> summarizes the current state of the bug.
>
> Thanks in advance to anyone who takes a look :) 
>

-- 
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/27c20efe-674f-47d3-9096-1fef1a749eff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Looking for some help with a baffling plugin bug (ansicolor)

[Owen Mehegan]

Myself and the maintainers of the jenkins-ansicolor plugin have been 
struggling with a weird bug. So far I am the only one who can reproduce it, 
and I can only repro it on my production Jenkins server. A 
seemingly-identical test server does not exhibit the bug. We seem to have 
exhausted most of the obvious possible causes. I have isolated the breakage 
to a specific commit, but that hasn't helped us come up with a fix. I'm 
hoping that getting some additional experienced eyes on the problem might 
generate some other suggestions for how we could debug this (I'm also 
personally limited in that I don't really know Java at all). My comment at 
https://github.com/dblock/jenkins-ansicolor-plugin/issues/57#issuecomment-148869752
 
summarizes the current state of the bug.

Thanks in advance to anyone who takes a look :) 

-- 
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/a32e4971-0dde-48b3-af24-b48805d1eb5b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins-events] Jenkins @ JavaOne SF ?

[Owen Mehegan]

I'm not planning to go to the conference, but if there is a social thing, I'm 
interested. I might be able to arrange to host at our office in FiDi.

On October 14, 2015 1:38:37 PM PDT, "R. Tyler Croy"  wrote:
>(replies inline)
>
>On Wed, 14 Oct 2015, Alyssa Tong wrote:
>
>> JavaOne SF 2015 is approaching in a few weeks - Oct 25 - 29. We're
>> wondering if there's interest to do something as a community during
>J1 if
>> there's a good # of Jenkins members in town?
>
>
>I don't have a ticket to JavaOne this year (boo) but it is easy enough
>for me
>to get down to the conference.
>
>I think at a minimum meeting up with contributors who are in town for a
>few
>drinks in the afternoon is a must :)
>
>
>
>
>
>- R. Tyler Croy
>
>--
> Code: 
>  Chatter: 
>
>  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
>--
>
>
>
>
>___
>Jenkins-events mailing list
>jenkins-eve...@lists.jenkins-ci.org
>http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/CD5F3B61-C4AB-45B6-B0FE-7114FA10CE34%40nerdnetworks.org.
For more options, visit https://groups.google.com/d/optout.

Re: Request for new Jenkins mark usage

[Owen Mehegan]

I polled a few of my coworkers, and asked them what these three names 
indicate to them:

Jenkins Enterprise by CloudBees
CloudBees Jenkins Enterprise
Jenkins

Everyone agreed that, in that context, it's clear that Jenkins is a 
stand-alone thing, and Jenkins Enterprise by CloudBees is a version of 
Jenkins made by a company/group named CloudBees. But CloudBees Jenkins 
Enterprise left them a little vague on where the heavy lifting was 
happening (my word choice). I also raised the convention of e.g. Red Hat 
Enterprise Linux, and people agreed that that naming makes it clear that 
it's Linux + Red Had secret sauce, rather than Red Hat something or other 
with Linux mixed in. Given that, they would not feel confused by CloudBees 
Enterprise Jenkins. I don't exactly know why this is - just something in 
the brain when you read these things.

This jibes with my instinct as well. It's nothing to do with CloudBees - I 
fully support Kohsuke's point that it's important not to discourage 
commercial involvement with the product. But I think, to put it another 
way, Oracle Enterprise Jenkins sounds better than Oracle Jenkins Enterprise 
(is it Oracle Jenkins, different from regular Jenkins?).

My 2 cents.

On Wednesday, November 5, 2014 10:39:03 AM UTC-8, Kohsuke Kawaguchi wrote:

 Jenkins project necessitates 
 https://wiki.jenkins-ci.org/display/JENKINS/Governance+Document#GovernanceDocument-Trademark
  
 that when a 3rd party uses the name Jenkins it would have to get a 
 blessing from the project meeting.

 In the past, we've established that Jenkins Foo by AcmeCorp is generally 
 an acceptable pattern. CloudBees has gotten several approvals that match 
 this convention, such as Jenkins Enterprise by CloudBees.

 In this post, I'm requesting that we bless AcmeCorp Jenkins Foo as a 
 generally acceptable pattern. And specifically, CloudBees want to get an 
 approval for the following patterns:

- CloudBees Jenkins Enterprise
- CloudBees Jenkins Operations Center
- CloudBees Jenkins Analytics

 With my OSS hat on, I think our guiding principle in the past name usage 
 approval is that the use does not cause confusions among users as to the 
 source of the effort/product. This is the same with other organizations. 
 See what Apache says on this topic 
 http://www.apache.org/foundation/marks/#guidelines. There are a 
 numerous other examples of names that fit this convention in other 
 open-source projects, such as HP Helion OpenStack 
 http://www8.hp.com/us/en/cloud/hphelion-openstack-overview.html, Piston 
 OpenStack http://pistoncloud.com/openstack-cloud-software/, CollabNet 
 Subversion Edge http://www.collab.net/community/subversion, Red Hat 
 Enterprise Linux 
 http://www.redhat.com/en/technologies/linux-platforms/enterprise-linux 
 just to name a few.

 I also think a policy that's not overly restrictive to the participants, 
 even for commercial entities, helps the community grow faster. While 
 commercial interest to an OSS project is always seen bit suspiciously, 
 especially in this project given the past with Oracle, the participation 
 from companies like CloudBees, Praqma, and Red Hat helped in many ways, 
 ranging from putting more developers to event organizations. Linux is a 
 good example of this, which enabled a lot of participations  adoptions. 
 This was always my mental model for Jenkins, and one that fits with the 
 open-ended plugin ecosystem in Jenkins.

 I had some conversation with Andrew and Dean about this topic, and we felt 
 that the next step is to bring this to here for a wider discussion. 

 Dean wanted to make sure (and I hope I'm not putting words in his mouth 
 here) that we aren't bending rules and principles just because it came from 
 CloudBees, as CloudBees is a big player in this community. And I agree --- 
 we should be just as happy to accept Oracle Jenkins Cloud, Microsoft 
 Jenkins Cluster, or whatever, in principle.

 So there it is. Your thoughts and feedbacks appreciated. I'm hoping that 
 we can get this officially approved soon.

 -- 
 Kohsuke Kawaguchi
  

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins JIRA

[Owen Mehegan]

I'll coordinate this with Mark to start with, to avoid spamming the list.
If anyone else is interested, email me! If it sticks, perhaps we can give
it some more official attention/advertisement.

On Fri, Oct 25, 2013 at 4:15 AM, Mark Waite mark.earl.wa...@gmail.comwrote:

 I'm interested in helping with the bug scrub effort.

 Most of my efforts have been focused on testing and bug scrubbing for the
 Git plugin, and I'd prefer to keep my focus there, since I've learned many
 things by focusing my testing and bug verification efforts on that plugin.

 Mark Waite


 On Fri, Oct 25, 2013 at 2:00 AM, Stephen Connolly 
 stephen.alan.conno...@gmail.com wrote:

 Go for it!


 On 25 October 2013 06:33, Owen Mehegan o...@nerdnetworks.org wrote:

 I mentioned this issue to Kohsuke in IRC recently. One of the ways I've
 tried to contribute to Jenkins has been by filing good bugs and following
 up on them. Sometimes it takes some legwork to find the right person to
 assign them to (the JIRA default is not always right), and when I see that
 something has been fixed I close the bug.

 That said, I would be willing to organize a regular volunteer bug scrub
 if anyone else is interested in helping. Perhaps we could coordinate via
 IRC, each grab a bunch of stale open issues, and see if we can get movement
 or closure on them. If this sounds good, get in touch and I'll help get it
 going.

 --
 Twitter: literatesavant
 IRC: autojack
 www.holisticqa.com -- my dev productivity blog

 --
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 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.
 For more options, visit https://groups.google.com/groups/opt_out.


  --
 You received this message because you are subscribed to a topic in the
 Google Groups Jenkins Developers group.
 To unsubscribe from this topic, visit
 https://groups.google.com/d/topic/jenkinsci-dev/B1ONTcvhXBU/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-dev+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Jenkins JIRA

[Owen Mehegan]

I mentioned this issue to Kohsuke in IRC recently. One of the ways I've tried 
to contribute to Jenkins has been by filing good bugs and following up on them. 
Sometimes it takes some legwork to find the right person to assign them to (the 
JIRA default is not always right), and when I see that something has been fixed 
I close the bug.

That said, I would be willing to organize a regular volunteer bug scrub if 
anyone else is interested in helping. Perhaps we could coordinate via IRC, each 
grab a bunch of stale open issues, and see if we can get movement or closure on 
them. If this sounds good, get in touch and I'll help get it going.

--
Twitter: literatesavant
IRC: autojack
www.holisticqa.com -- my dev productivity blog

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.