Re: File Leak Detector

[Manuel Ramón León Jiménez]

+1

On Tue, Mar 1, 2022 at 12:28 PM Oleg Nenashev 
wrote:

> +1
>
>
> On Tuesday, March 1, 2022 at 8:36:47 AM UTC+1 timja...@gmail.com wrote:
>
>> +1
>>
>> On Tue, 1 Mar 2022 at 01:26, Mark Waite  wrote:
>>
>>>
>>>
>>> On Monday, February 28, 2022 at 6:13:52 PM UTC-7 Basil Crow wrote:
>>>
 kohsuke/file-leak-detector has not seen commits since 2018. There are
 a number of open PRs that need to be processed and released, including
 important PRs to add Java 11 support (see JENKINS-52308).

 We recently moved mock-javamail from Kohsuke's GitHub organization to
 the Jenkins GitHub organization. In the process, I also modernized the
 library and transferred release permissions to the core team.

 I would like to propose we do the same for kohsuke/file-leak-detector.
 I am willing to do the modernization work, just as I did for
 mock-javamail.

 Please let me know what you think. If there is consensus in favor of
 this plan, I will open a GitHub issue and ping Kohsuke.
>>>
>>>
>>> +1 from me.
>>>
>>> --
>>> 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/72ca6c90-018e-414c-9f3e-c84eddbdd466n%40googlegroups.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/2bc3ddce-97bc-4e56-a958-575530dba938n%40googlegroups.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/CADN1OJ0%3DLJoTn77mtHk%2BbwP-EySNkZM3rpv6h7b2uNzdwshnog%40mail.gmail.com.

Re: Jenkins acceptance tests are passing!

[Manuel Ramón León Jiménez]



OMG, I thought I won't live to see them ✅

Congratulation!!!

On Thu, Oct 28, 2021 at 5:48 PM Tim Jacomb  wrote:

> To quote Ulli:
> "This is the first time (since inception) that the ATH test suite is .
> Wow, we need to celebrate  
>
>
> https://github.com/jenkinsci/acceptance-test-harness/pull/706#issuecomment-953960043
>
> Hopefully we can keep them that way or at least failures should be more
> easy to motivate people to fix.
>
> There's been red blindness forever here.
>
> Anyway
> Thanks all who have contributed to fixing here
>
> Tim
>
> --
> 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/CAH-3Bic3PyVe7dykW9gWhzsBLiZdm0fPLPC%2BvZpz9auWOqqRmQ%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/CADN1OJ3Qr_OcQsToedfZhk3LZWXyiCGNHHyweATiLCZ-X-vLHA%40mail.gmail.com.

Re: Plugin end-of-life (EOL) policy

[Manuel Ramón León Jiménez]

I'm in for this proposal. We need a way to clean up the ecosystem to be
able to progress easily without investing too much on things that are not
used.

We can discuss and polish the details, but the aim remains the same.

Thank you Oleg for triggering the discussion.

On Tue, May 4, 2021 at 7:08 PM Oleg Nenashev  wrote:

> I tentatively put the topic to the tomorrow's governance meeting agenda:
> https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.1gtco63t6ztr
> We will discuss it if there are the stakeholders from this thread and
> enough time left.
>
>
>
> On Monday, May 3, 2021 at 3:25:32 PM UTC+2 Jesse Glick wrote:
>
>> On Mon, May 3, 2021 at 3:46 AM Daniel Beck  wrote:
>>
>>> Something more extensible, with version ranges like we do for security
>>> warnings could help here:
>>> "This plugin is likely to break the UI once you update Jenkins to
>>> 2.277.x" and "no fix is available" or "update to version X or newer".
>>>
>>
>> FYI https://issues.jenkins.io/browse/JENKINS-49651
>>
> --
> 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/9c82d2f8-4f8a-4cf2-b1a1-ea8247c8e530n%40googlegroups.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/CADN1OJ31%3D_fRNMSxSktSBr%3DzmfYEW6QgSbk63L0MQUmvORbNTw%40mail.gmail.com.

Re: [Heads-up] Removing commons-digester from Jenkins Core (and the link with our plugins EOL policy discussion :-))

[Manuel Ramón León Jiménez]

I'm against a JEP for Digester removal. It doesn't need it IMO. I'm in for
anything to avoid us dealing with the same problems in the future. We need
to modernize Jenkins in many aspects and those old / unmaintained plugins
are an obstacle and a waste of effort. Something like put for adoption
every plugin without a release for a year or use another label and state
clearly that the effort from the community won't take into account the
plugins with this label. Or something like that.

Basically what Oleg wrote on the email *Plugin end-of-life (EOL) policy.*

Thanks!

On Wed, May 5, 2021 at 4:58 AM Oleg Nenashev  wrote:

> What about a quick JEP? We are working on removing obstacles in the
> process, an a test for the new process would be great
>
> On Wed, May 5, 2021, 01:16 Basil Crow  wrote:
>
>> On Tue, May 4, 2021 at 2:02 PM Baptiste Mathus  wrote:
>> > So the big question is: what do we do?
>> >
>> > I personally think we should NOT make these PRs land if no maintainer
>> steps up.
>> > In other words, once we merge and release the Core PR, these plugins
>> will likely just fail loading on newer Jenkins releases.
>>
>> I concur with Baptiste. For plugins that have not seen any activity,
>> yet alone a release, in more than five years (and on which no other
>> plugins depend), I do not believe the benefit to be gained is worth
>> the cost.
>>
>> --
>> 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/m2fEX5ALvbg/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/CAFwNDjp9q5sdO%2BuYUH2voGYqufHs%2BE3gULdvdnwCHwgWGByLEg%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/CAPfivLDz5m2Z8W441jCPQAxsj%3DvfG2uK5TdRJZpLXSH8uanKfA%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/CADN1OJ1%3DpCdSQrQiqM%2BxVgOczh0n9MoyiV3HcPGQkc3r%3D0k8gg%40mail.gmail.com.

Re: Welcome Ewelina Wilkosz - new Jenkins Governance Board Member

[Manuel Ramón León Jiménez]

Congrats Ewelina!

On Mon, Mar 15, 2021 at 12:56 PM Oleg Nenashev 
wrote:

> Dear all,
>
> We are happy to announce that we have finished the interim board member
> selection procedure. The Mar 10 Governance meeting has confirmed Ewelina
> Wilkosz as a new Jenkins Governance Board member who will replace Marky
> Jackson in this role. The term will last until the Jenkins elections in
> late 2022. Ewelina's statement from the 2020 elections is available here
> 
> .
>
> About Ewelina : *Jenkins
> Contributor since 2017, when she got involved in Jenkins Configuration as
> Code Plugin development. Voted Most Valuable Contributor in 2018. **She
> has 14 years of experience in IT, working as a CI/CD consultant since the
> beginning of 2017. In that role she’s trying to solve* *numerous issues
> Jenkins users are facing daily - as developers, administrators, maintainers*
> *.*
>
> Welcome aboard Ewelina!
>
> Best regards,
> Oleg Nenashev
>
> --
> 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/CAPfivLC3jALq-E%3DC%3Dt_in_H2_C%3DoaHUdqMo8PLYNOEMFf8Fhqg%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/CADN1OJ1rL_k9zHV0TGWA4ENeLYEo3NAQu39fPiOc03b%3DsD_rUg%40mail.gmail.com.

Re: Releasing tables-to-divs regression fixes for 2.277.1

[Manuel Ramón León Jiménez]

+1

On Wed, Mar 10, 2021 at 1:11 AM Mark Waite 
wrote:

> +1 from me also for releases of plugins that are up for adoption.
>
> On Tue, Mar 9, 2021 at 5:07 PM Oleg Nenashev 
> wrote:
>
>> Thanks all! I will start releasing up-for-adoption plugins tomorrow
>>
>> On Tuesday, March 9, 2021 at 9:08:00 PM UTC+1 timja...@gmail.com wrote:
>>
>>> > Approve releasing up-for-adoption plugins without taking ownership.
>>>
>>> +1
>>>
>>> On Tue, 9 Mar 2021 at 19:14, 'Gavin Mogan' via Jenkins Developers <
>>> jenkin...@googlegroups.com> wrote:
>>>
 if you do released un-maintained plugin, can you make sure the release
 notes clearly indicate that its a non maintainer release, lots of people
 use last release to see how maintained a plugin in, resetting that value
 when there will be no followup will be frustrating.

 On Tue, Mar 9, 2021 at 10:43 AM Jesse Glick 
 wrote:

> On Tue, Mar 9, 2021 at 10:04 AM Oleg Nenashev 
> wrote:
>
>>
>>- Approve releasing up-for-adoption plugins without taking
>>ownership.
>>
>> +1
>
> --
> 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/CANfRfr0%2B0zDWS5MsAsJAV3pw_FGQrkhpfcf2NuU06E-LWAD6CA%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-de...@googlegroups.com.

>>> To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuussuaRkhY0ABSX%3DHFRbiuN5Kw4rOeFdgWxc6zjS%3DdCHQ%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/2d2d80a7-578d-45bf-9565-23ebbcd1b0c2n%40googlegroups.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/CAO49JtGo%3DipEDU63oRxvybejLSCMMQMXOVhxbksx0DDAEEpWjw%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/CADN1OJ17aNuB59wh6cG8jhTMU0DmpNaTk1uoYhPnGaANuesVdg%40mail.gmail.com.

Adopt msbuild

[Manuel Ramón León Jiménez]

Hi

I have a PR to fix some PCT failures pending to merge in *msbuild* plugin.
The plugin is under adoption and I want to take over it. At least to
improve its health. In addition, Baptiste Mathus also filed a PR to test
the plugin against Java11.  If possible, I would like to add as maintainers
my whole team, as we work together and it may ease the maintenance. We are:


   - mramonleon
   - batmat
   - rsandell
   - alecharp
   - bitwiseman
   - carroll
   - olamy

Thanks!

-- 
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/CAHHyvkN_Nn256knh47uWPB1vdP3srDeHLtPrsdtMZmZN_3xDtw%40mail.gmail.com.

Re: Core Baseline Java8 -> Java11?

[Manuel Ramón León Jiménez]

I love getting rid of old frameworks / libraries / ... to take advantage of
all new stuff provides, but it's painful for users to migrate. The Java JDK
is like changing your foundations and with all those new pain-potential
changes we've made, I agree with Daniel, it's better to go little by little.

On Fri, Dec 4, 2020 at 11:06 AM Daniel Beck  wrote:

>
>
> > On 4. Dec 2020, at 09:43, Ullrich Hafner 
> wrote:
> >
> > Ok, I understand that. I wasn’t aware that so may people are still using
> Java 8.
>
> Jenkins stats (scroll down for recent months):
>
> https://stats.jenkins.io/plugin-installation-trend/jvms.json
>
> Obviously, Jenkins influences the stats here with what's on Docker images
> etc.; but still. Assuming the stats are correct, that's a tiny percentage
> of users on JDK 11, and IMO not enough to be confident about raising the
> requirement without potentially causing issues for a lot of users.
>
> I suggest we get through tables-to-divs, X-Stream, and Acegi changes first
> and look at this again perhaps mid 2021.
>
> --
> 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/B0F7B51D-897F-41B4-B29D-23F01C3C5BEC%40beckweb.net
> .
>

-- 
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/CADN1OJ3-RONd4v1xXbjCkbr91jWOfbLOxOkkXzMQrM7yrZQFnQ%40mail.gmail.com.

Re: ANN: Jenkins 2020 Elections - Results

[Manuel Ramón León Jiménez]

Congratulations!!!

On Thu, Dec 3, 2020 at 11:52 PM Oleg Nenashev 
wrote:

> Dear all,
>
> We have finished the 2020 elections. On behalf of the Jenkins community
> and the elections committee, we congratulate all newly elected board
> members and officers! These roles are an essential part of Jenkins'
> community governance and well-being, and we are excited to see contributors
> taking these roles.
>
> We would like to thank all candidates who participated this year. We had 9
> governance board and 3 release officer candidates: Andrey Falko, Baptiste
> Mathius, Ewelina Wilkosz, Frederic Gurr, Gavin Mogan, Justin Harringa, Mark
> Waite, Marky Jackson, Steven Terrana, Victor Martinez, and Zhao Xiaojie
> (Rick). Regardless of the results, all of them are awesome community
> leaders who actively participate in the Jenkins project and represent its
> users. Their contributions are instrumental to the project’s success, and
> we highly appreciate them. Thank you!
>
> Election results, effective on Dec 03:
>
>-
>
>Gavin Mogan  and Marky Jackson
> will join Kohsuke Kawaguchi, 
> Ullrich
>Hafner and Oleg Nenashev on the Jenkins Governance Board
>
>-
>
>Tim Jacomb  will become the new Release
>Officer 
>-
>
>Marky Jackson  will become the
>new Events Officer 
>(uncontested)
>-
>
>Olivier Vernin  will continue in the role
>of Infrastructure Officer
> for another
>term (uncontested)
>-
>
>Daniel Beck  will continue in the role
>of Security Officer 
>for another term (uncontested)
>-
>
>Mark Waite  will continue in the role
>of Documentation Officer
> for another
>term (uncontested)
>
>
> We also thank Alex Earl, Alyssa Tong, R. Tyler Croy and Oliver Gondža who
> are stepping down from their roles this year. All of them have been
> long-time Jenkins community leaders, and we are looking forward to keeping
> working with them.
>
> Raw election results can be found here: Governance Board elections
> , 
> Release
> Officer Elections
> .
> If you are interested to learn more, please stay tuned for the announcement
> blogpost which should land soon (pull request
> ). There is also a
> retrospective document available here
> ,
> any feedback and suggestions will be appreciated!
>
>
>
> Best regards,
>
> Jenkins 2020 Elections Committee
>
> --
> 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/CAPfivLCpDDv57%3DmUvT-CnfZK2a%3DseJAHV9a_FLf%2BmJxWZoq%3D2w%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/CADN1OJ2RM2vr3zuErjy18ae6yBkn8DAvyqsGNne%2BOkiMB6mjBw%40mail.gmail.com.

Re: Limited time to maintain my plugins

[Manuel Ramón León Jiménez]

Hi Andrew.

It's great to have more people willing to help on this plugin.

Regarding the PR, I suggest you tackle Daniel's concerns. At first glance
it seems to be superseding the credentials functionality some way. It has
two risks:
1. Maybe we're trying to solve a problem using an approach that requires
extensive changes, but it could be resolved looking from a different angle,
using already existing features.
2. We may introduce security risks derived from the credential management,
something very battle tested on the credentials implementation.

I've not reviewed this PR thoroughly though. My recommendation is to tackle
Daniel Beck's concern to be sure we don't regret in the future.

Thank you for your work on this, best regards.


On Wed, Dec 2, 2020 at 8:39 PM Andrew Grimberg <
agrimb...@linuxfoundation.org> wrote:

> Greetings folks,
>
> Dominik, sorry to see you don't have the time anymore. That being said,
> I would like to step up for maintainer rights on the Config File
> Provider listed below:
>
> Config File Provider https://plugins.jenkins.io/config-file-provider/
> maintained at: https://github.com/jenkinsci/config-file-provider-plugin
>
> In particular I'm trying to get the following PR out the door:
>
> https://github.com/jenkinsci/config-file-provider-plugin/pull/90
>
> Also, I've looked at the rest of the current PRs and issues and believe
> that I can work through the list (hopefully!)
>
> My GitHub ID is 'tykeal' which is also my Jenkins infra id
>
> -Andy-
>
> On 11/26/20 11:14 PM, Dominik Bartholdi wrote:
> > Hi all,
> >
> > After many years as an active maintainer of several plugins (some of
> > which go back to the time when we still talked about the H-word),
> > i have to be honest to the community (and myself!): I just can’t spend
> > as much time to maintain the plugins as required and as I would love to…
> > Therefore I have to step back as the main contributor for the following
> > plugins and mark them as open for adoption:
> >
> > Config File Provider https://plugins.jenkins.io/config-file-provider/
> > 
> > Conditional BuildStep https://plugins.jenkins.io/conditional-buildstep/
> > 
> > Scriptlerhttps://plugins.jenkins.io/scriptler/
> > 
> > Managed Scriptshttps://plugins.jenkins.io/managed-scripts/
> > 
> > Security Realm by custom script https://plugins.jenkins.io/script-realm/
> > 
> > Node and Label parameterhttps://plugins.jenkins.io/nodelabelparameter/
> > 
> > Run Condition https://plugins.jenkins.io/run-condition/
> > 
> >
> > There are a couple of other plugins I also created, but these already
> > have new contributors and therefore should be OK as they are.
> > If you do use one of these, please consider adopting it.
> >
> > This is actually quite a hard decision for me and took longer then it
> > should have. I really loved the time in this community, I made some
> > great friends and
> > I often think back about the times we had at FOSDEM, JW and the
> > CodeHouse in SF.
> >
> > I will still be around, read the ML and might provide fixes if I
> > can (after all I’m still using Jenkins myself and I need to keep it
> > alive :)) - but I think this is fairer to the whole community…
> >
> > Many thanks!
> >
> > /Domi (imod)
> >
> > --
> > 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/CF749317-030F-4874-83BF-90C94A746269%40fortysix.ch
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CF749317-030F-4874-83BF-90C94A746269%40fortysix.ch?utm_medium=email_source=footer
> >.
>
> --
> Andrew J Grimberg
> Manager Release Engineering
> The Linux Foundation
>
> --
> 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/1880e4cf-4fac-45c6-bf2a-3005d44631e6%40linuxfoundation.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 

Re: msbuild and windows-slaves plugins for adoption?

[Manuel Ramón León Jiménez]

Thanks Oleg for the information.


On Wed, Nov 18, 2020 at 5:01 PM Oleg Nenashev 
wrote:

> Hello Ramon,
>
> https://github.com/jenkinsci/windows-slaves-plugin has been marked for
> adoption about 1 month ago.
> Before that I have tried reaching out multiple parties who might be
> interested, no response though.
>
> Regarding the MSBuild plugin, it is definitely inactive. Currently only
> maintainers can put the plugins for adoption, we do not have a process for
> forcing this state on abandoned plugins. There is JEP-11
>  from
> Craig Rodriguez which allows doing that, but this JEP is also inactive.
>
> BR, Oleg
>
>
>
>
> On Wednesday, November 18, 2020 at 4:34:42 PM UTC+1
> manuel.ramon...@gmail.com wrote:
>
>> Hi all. I've filed these PRs at *msbuild-plugin* and
>> *windows-slaves-plugin* more than a month ago. They are to *enable
>> dependabot*. I've not received any feedback from the maintainers (but
>> Oleg, he's not able to maintain it though).
>>
>>- https://github.com/jenkinsci/msbuild-plugin/pull/40
>>- https://github.com/jenkinsci/windows-slaves-plugin/pull/31
>>
>> I'm wondering if we may *mark them for adoption*.
>>
>> What do you think?
>>
>> Thank you.
>>
> --
> 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/8c71e4bb-5913-417c-b244-a84116f1843fn%40googlegroups.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/CADN1OJ3PMBJEgJJZmius73ekKd%2BJk2LHJrEcHKeEYOPQbvJFwg%40mail.gmail.com.

msbuild and windows-slaves plugins for adoption?

[Manuel Ramón León Jiménez]

Hi all. I've filed these PRs at *msbuild-plugin* and *windows-slaves-plugin*
more than a month ago. They are to *enable dependabot*. I've not received
any feedback from the maintainers (but Oleg, he's not able to maintain it
though).

   - https://github.com/jenkinsci/msbuild-plugin/pull/40
   - https://github.com/jenkinsci/windows-slaves-plugin/pull/31

I'm wondering if we may *mark them for adoption*.

What do you think?

Thank you.

-- 
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/CAHHyvkOnK4NMZwq6C8bLCjS_wV6RmLvo5VGPT7UhvsjaxWbgTw%40mail.gmail.com.

Dependabot on Graddle plugin

[Manuel Ramón León Jiménez]

Hi Stefan, would you be able to take a look at this PR:
https://github.com/jenkinsci/gradle-plugin/pull/101

It will enable dependabot on the repo to automatically file a PR with
dependency updates, improving the maintainability of the plugin letting it
be up to date.

Thank you!

-- 
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/CAHHyvkMqdjUstM_7bqBV5-BQ9-dZ4VmHRw8bJMXRm4b6irVwgg%40mail.gmail.com.

Re: Ask for security contact without maintainers approval

[Manuel Ramón León Jiménez]

Already merged!

Thank you all.

On Wed, Nov 18, 2020 at 12:44 PM Baptiste Mathus  wrote:

> Adding Stefan in the thread, using the email I could find from the commits
> on the gradle plugin.
>
> @Stefan:
>
>- Do you still consider yourself a maintainer of the Jenkins Gradle
>plugin?
>- If so, can you review and approve
>https://github.com/jenkins-infra/repository-permissions-updater/pull/1708
>if fine?
>
> Thanks!
>
>
> Le mer. 18 nov. 2020 à 12:34, Manuel Ramón León Jiménez <
> manuel.ramon.leon.jime...@gmail.com> a écrit :
>
>> Hello.
>>
>> We, the *Foundation Security members* have filed several PRs to help on
>> addressing security vulnerabilities on several plugins. You can find them
>> with this filter:
>>
>> https://github.com/jenkins-infra/repository-permissions-updater/search?q=foundation_security_members_q=foundation_security_members
>>
>> We still have pending this one:
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/1708
>> The current maintainers didn't answer so far.
>>
>> Do you agree to move forward and add us as security contact? We can help
>> in addressing security issues. We cannot commit to becoming maintainers
>> though.
>>
>> Specially to Security members: Daniel Beck and others.
>>
>> Thank you.
>>
>> --
>> 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/CAHHyvkN1TKwY-GQVZkO9RJ%2BKboN1jXiWoK69zs78B%2Bra%2ByWwXw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHHyvkN1TKwY-GQVZkO9RJ%2BKboN1jXiWoK69zs78B%2Bra%2ByWwXw%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5w6CEBKQD1RNeqoPx23hYSMnHGrXGaia4xrmX3St%2BOVQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5w6CEBKQD1RNeqoPx23hYSMnHGrXGaia4xrmX3St%2BOVQ%40mail.gmail.com?utm_medium=email_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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAHHyvkPUcMabGYR6E380%3Dh5f-8Y_mA478tmufDPiggJvMvR_%2BA%40mail.gmail.com.

Ask for security contact without maintainers approval

[Manuel Ramón León Jiménez]

Hello.

We, the *Foundation Security members* have filed several PRs to help on
addressing security vulnerabilities on several plugins. You can find them
with this filter:
https://github.com/jenkins-infra/repository-permissions-updater/search?q=foundation_security_members_q=foundation_security_members

We still have pending this one:
https://github.com/jenkins-infra/repository-permissions-updater/pull/1708
The current maintainers didn't answer so far.

Do you agree to move forward and add us as security contact? We can help in
addressing security issues. We cannot commit to becoming maintainers though.

Specially to Security members: Daniel Beck and others.

Thank you.

-- 
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/CAHHyvkN1TKwY-GQVZkO9RJ%2BKboN1jXiWoK69zs78B%2Bra%2ByWwXw%40mail.gmail.com.

Re: ATH

[Manuel Ramón León Jiménez]

+1 same here

On Thu, Oct 29, 2020 at 5:09 PM globero  wrote:

> +1 same here
>
> On Thu, Oct 29, 2020 at 4:52 PM Mark Waite 
> wrote:
>
>> +1 from me (though I'm not an ATH maintainer, just an ATH execution
>> observer). Thanks for your efforts on the acceptance test harness.
>>
>> On Thu, Oct 29, 2020 at 6:43 AM jn...@cloudbees.com 
>> wrote:
>>
>>> Hi all,
>>>
>>> I would like to co-maintain the ATH.  I've been trying to reduce it's
>>> flakyness over time and its smooth running is fundamental to my day job.
>>>
>>> I already have access on the GH repo - so this is a request for release
>>> permissions.
>>>
>>> https://github.com/jenkins-infra/repository-permissions-updater/pull/1736
>>>
>>> Regards
>>>
>>> /James
>>>
>>> --
>>> 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/ae81309d-67c2-41e6-8aa3-e8a2cf1fc253n%40googlegroups.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/CAO49JtEiqugLUnJtxbN11Qg5Eck%3DWuh_cH_%3DWz_TKhDw33AzWA%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/CADN1OJ1NjQ_iOOhawgNargGNPey-XPBgjQCSdBZ2mdK8-s0nfg%40mail.gmail.com.

Re: Request to adopt a plugin

[Manuel Ramón León Jiménez]

Hi

Glad to see you're both willing to help on that. We cannot say the plugin
is abandoned, recently Francisco Robles Martín
 joined us and Raihaan Shouhell
 is doing a pretty good job.

I've removed the adopt-this-plugin topic from the repo to avoid further
confusions. Sorry for the misunderstanding.

It would be great to have you both aboard, we would like you to contribute
with some PRs first to become a maintainer to have enough confidence you
understand pretty well the plugin and each merge implications.

If you like challenges I urge you to rethink the UI, the configuration page
right now is very hard to use effectively and it would help enormously to
any Jenkins administrator trying to use the plugin. Looking into it is a
good way to take deep knowledge about how it works.

Thank you for your interest, looking forward to seeing your first Pull
Request.

Best regards.


On Fri, Oct 2, 2020 at 3:41 PM Oleg Nenashev  wrote:

> Hi all,
>
> There might be some confusion. According to the commit history, the plugin
> is actively maintained now:
> https://github.com/jenkinsci/ec2-plugin/commits/master . Last substantial
> merge was 2 weeks ago . Ramon Leon has took ownership 5 months ago
> according to
> https://github.com/jenkins-infra/repository-permissions-updater/pull/1533
> , and then another maintainer joined on Aug 25:
> https://groups.google.com/g/jenkinsci-dev/c/alJpUbtKYh0/m/4QpxyYHoBQAJ
>
> I suspect that the maintainers just forgot to remove the adopt-this-plugin
> GitHub topic. Before we proceed with ownership transfer, I think we need
> explicit confrmation from Ramon Leon and Martin Frobles.
>
> Best regards,
> Oleg
>
> On Friday, October 2, 2020 at 12:04:04 AM UTC+2 himansh...@gmail.com
> wrote:
>
>> Thank you Mark.
>>
>> No we have not submitted any pull requests yet. Surely we can start with
>> them.
>>
>> Thanks again. Looking forward to contribute to the Jenkins community.
>>
>> Regards,
>> Himanshu
>>
>> On Thursday, October 1, 2020 at 12:21:25 PM UTC-7 Mark Waite wrote:
>>
>>> Thanks to you and Deepika for your willingness to help.  That's great!
>>>
>>> We usually prefer that those adopting a plugin have submitted pull
>>> requests to the plugin prior to adopting it.  Have you previously submitted
>>> pull requests to the plugin?  If not, would you be willing to start with
>>> pull requests?
>>>
>>> To others, I've worked with Himanshu and Deepika on Jenkins training.
>>> I'm +1 to allow them to adopt the plugin but would love to have support
>>> from others that are willing to assist them while they work on the plugin.
>>>
>>> On Thu, Oct 1, 2020 at 1:17 PM Himanshu Gautam 
>>> wrote:
>>>
 Hello,

 We recognize the value provided by the Amazon EC2 plugin. Since it is
 up for adoption, We love to help maintain it.

 Here is the link to the plugin: https://plugins.jenkins.io/ec2/

 Our GitHub usernames:
 https://github.com/hgautam
 https://github.com/dhgautam

 Our Jenkins infrastructure IDs:
 hgautam
 dgautam


 Regards,
 Himanshu Gautam and Deepika Gautam

 --
 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/ef3e27a7-7153-40c5-aec6-fc95373c7175n%40googlegroups.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/dc03b3e5-bc5d-4592-9765-024daeda9d3cn%40googlegroups.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/CADN1OJ3ixTsXGSwxY5XbN_iFb0xOnWMXmw3TnuhpemTn%3DQrYjQ%40mail.gmail.com.

Re: ci.jenkins.io - maintainers can now re-run build via checks

[Manuel Ramón León Jiménez]

Great, thank you for the heads up.

On Tue, Sep 8, 2020 at 9:55 AM Arnaud Héritier  wrote:

> Awesome 
>
> On Tue, Sep 8, 2020 at 9:53 AM Tim Jacomb  wrote:
>
>> Hi all
>>
>> Just an update to let you know that you can now re-run failed builds via
>> GitHub checks on ci.jenkins.io.
>> (Only maintainers, i.e. write access can do this, authors need to push a
>> code change or close / reopen)
>>
>> This is made possible with the GitHub checks plugin
>> , by Kezhi as part of GSoC.
>>
>> See Kezhi's blog post for more details:
>> https://www.jenkins.io/blog/2020/08/31/github-checks-api-plugin-coding-phase-3/
>>
>>
>> Thanks
>> Tim
>>
>> --
>> 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/CAH-3BicXBAQKwaZJSMwkhAdhi_XeBfH%2BkwwsvkHWaYc2_OzvVQ%40mail.gmail.com
>> 
>> .
>>
>
>
> --
> Arnaud Héritier
> 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-_32-XbVtwrnEEdMZ%2B6eEd4ju14dUueMUk5nOjUc6DLJw%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/CADN1OJ1P%3DsBCqE%2BYZNJbcEYNhnEwixK%3DasuN17A0T%3D6PXB86WA%40mail.gmail.com.

Re: Instability on ci.jenkins.io Ubuntu EC2 agents

[Manuel Ramón León Jiménez]

Hi Chris, we've recently released a security fix for EC2 plugin. It implies 
reading the AWS EC2 console to get the ssh key used in the instance to 
communicate securely. The existing instances are configured with accept-new 
strategy, which guarantee they're going to be working even though the 
server key is not trusted. But the first time the Jenkins master connects 
to the ec2 instance, it now waits until the instance console is ready with 
the key printed. If the template was configured with a timeout it may 
expires because this operation could take several minutes. By default this 
timeout is empty, so there shouldn't be any problem, although you may see 
more time in provisioning the instances for the first time. All the 
information is here: https://github.com/jenkinsci/ec2-plugin/#security You 
can move to the *off* strategy to work as before, but it's insecure 
allowing a MitM attack.

Another issue is when you configure to connect to your ec2 instances with 
the ssh client, instead of the pure java client and the ssh command 
installed is pretty old. This command doesn't support the option -o 
StrictHostKeyChecking= and the connection doesn't take place.

Let me know whether this explanation fits to the case.

Thank you.

On Thursday, May 7, 2020 at 8:40:00 PM UTC+2, Mark Waite wrote:
>
>
>
> On Thu, May 7, 2020 at 12:18 PM Chris Kilding  > wrote:
>
>> Hi Mark,
>>
>> Thanks, that explains it. Off-hand thought - can AWS PrivateLink - or the 
>> Azure equivalent - do anything to improve connection reliability in our 
>> multi cloud setup? (I know these services are more intended for on prem to 
>> cloud links, but maybe it can help here.)
>>
>>
> I'm hesitant to speculate on solutions until we better understand the 
> problem.  I run 11 agents on AWS spot instances that are connected to a 
> master at my house.  There are times when those 11 AWS computers are also 
> connected to a Jenkins master on a different computer.  I've run that 
> configuration for a year or more and have not had more than 3 or 4 
> connectivity issues.
>
> I am reasonably confident that the network between the AWS data center and 
> the Azure data center is no worse than the network between the master 
> inside my house and the 11 spot instances running on AWS.  However, that's 
> just speculation on my part.
>  
>
>> In the meantime my workaround is to push trivial commits when I need it 
>> to try again. That suffices during PR development, but I can’t do that in 
>> master for the fun of it.
>>
>> Chris
>>
>> On Thu, 7 May 2020, at 4:12 PM, Mark Waite wrote:
>>
>>
>>
>> On Thu, May 7, 2020 at 8:27 AM Chris Kilding > > wrote:
>>
>> Hi,
>>
>> I'm seeing a range of instability on the Ubuntu EC2 build agents on 
>> ci.jenkins.io over the past week, including tests randomly taking 
>> forever and timing out, and instances randomly being terminated mid-build.
>>
>>
>> Yes, plenty of ideas, but no solutions yet.  Sorry for the unreliability 
>> of those build agents.
>>
>> We were hosting all our build agents in Azure when Microsoft was 
>> sponsoring the Jenkins project infrastructure.  That sponsorship expired 
>> late in 2019 so that the Jenkins project was paying the full price of its 
>> infrastructure hosted on Azure.
>>
>> AWS became a sponsor in early 2020.  In order to immediately reduce 
>> costs, we've added AWS EC2 agents using the EC2 plugin.  The Jenkins master 
>> and the Jenkins containerized agents ("ACI") continue to run on Azure for 
>> now, while the Ubuntu agents are now provisioned by the EC2 plugin.
>>
>> Unfortunately, the agents provisioned by the EC2 plugin randomly lose 
>> their connection to the Jenkins master on Azure.  That loss of connection 
>> disrupts the job that is running on the agent and causes the types of 
>> annoying behaviors that you have seen.
>>
>> We're currently putting first focus on completing the core release 
>> automation project so that we can deliver Jenkins weekly, LTS, and security 
>> releases without requiring Kohsuke perform the release.  Jenkins weekly 
>> releases 2.232, 2.233, and 2.234 were delivered from core release 
>> automation without requiring Kohsuke take any action.  We're working on the 
>> automation for long term support releases and for security releases.
>>
>> Intense focus on the EC2 agent connection failures will have to wait 
>> until we either have more people to assist with infrastructure or we have 
>> completed the core release automation project.  Those who would like to 
>> assist with Jenkins infrastructure are welcome to join the weekly 
>> infrastructure meetings and to chat on the IRC channel #jenkins-infra. 
>>
>> Thanks,
>> Mark Waite
>>
>>  
>>
>> This didn't used to happen previously when I think the builds were 
>> running in Azure.
>>
>> Any ideas?
>>
>> Chris
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving 

Warn or avoid overriding CLI methods

[Manuel Ramón León Jiménez]

Hello everyone.

I've been working on an issue recently. While trying to call the
*disable-job* CLI method, we receive:

*ERROR: object is not an instance of declaring class*

The root cause is because a plugin has overridden the method:
https://github.com/jenkinsci/multi-branch-project-plugin/blob/master/src/main/java/com/github/mjdetullio/jenkins/plugins/multibranch/TemplateDrivenMultiBranchProject.java#L480

So now, if you try to disable a Freestyle job, it fails because it's
expecting a *TemplateDrivenMultiBranchProject* one.

I open this to have feedback about what is best to do here:

   - Avoid overriding CLI methods
   - Warn about that fact on Jenkins console
   - Warn about that fact on Jenkins CLI commands list page
   - Warn about that fact on the CLI command output directly (may break
   some automations)
   - Others


I filed a ticket, not sure what works better:
https://issues.jenkins-ci.org/browse/JENKINS-61893

Thank you, best regards.

-- 
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/CAHHyvkOhbYpGUNmY-SB8eVT7oyUOQKS5yRPPJa5t2JzrFF4ztA%40mail.gmail.com.

Re: [GSOC 2020 PROJECT IDEA] Jenkins distribution customize service

[Manuel Ramón León Jiménez]

Hi.

I've been working on some ideas pretty similar to all you are suggesting
here. The ultimate goal is, sort of:
* Allow to have a Jenkins ready with all stuff in a single click or
command. Or compared to IKEA: avoid having to mount the IKEA furniture
manually because unlike IKEA, we have dozens of *Shrönghon screw* (aka
plugins) and people usually don't know what to use to get their furniture
mounted :-)
* Allow people to share "their Jenkins", meaning Jenkins version +
plugins + sample-running jobs + configurations (but credentials) to allow
community to reuse them. Some projects have contributed to allow that
without too much effort, like JCasC, custom-war-packager, ...
* Allow people to kind of vote for packages to be able to find out the most
mature or relevant among all existing.
* Have a centralized and easy to maintain repository of such "Jenkins
configurations". It could be as easy as a GH repo with a certain template
(readme + configuration file + assets), although some features like voting
may be missed.

Beyond the specific proposal I made I find there are a lot of people
thinking on the same problem and slightly different solutions. So it would
be great to align efforts on the same direction to extract the most from us
to achieve something deliverable in a short time.

Not sure under what umbrella we could do that, GSoC, JEP, ... though.

Best regards.

On Mon, Feb 24, 2020 at 11:55 PM Chris Kilding <
chris+jenk...@chriskilding.com> wrote:

> Jesse - cheers for pointing out the previous AWS packaging attempt, I will
> take a look.
>
> Re version pinning, if this can’t be done in the POM, are there any
> Jenkins tools which can do this, apart from the cloudbees assured update
> feed? (I’m thinking of how we could support users on Jenkins community
> edition.)
>
> Re what gets included - we could insist that any plugins included in a
> cloud vendor metapackage meet certain criteria, so that they can play
> together better:
> - They must be able to no-op if the user doesn’t need them (ie their
> default is to quietly sit on the Jenkins server and not do anything, until
> the user configures them).
> - They must all use the same cloud provider SDK artifact (probably the
> Jenkins re-packaged HPI version of the SDK).
> - If appropriate, they must all take their baseline configuration from the
> same cloud provider ‘global config’ plugin.
>
> Re pre-defined packages - I would certainly like to see the cloud vendors
> get more involved with supporting their respective Jenkins plugins.
>
> Chris
>
> --
> 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/623C5041-5D06-47C9-BD2F-CA7336B7BC53%40chriskilding.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/CAHHyvkM2xJjf90UsYyeeQJGxjH%2Buc59XoJRFXchf%3DLHs-h5Rng%40mail.gmail.com.

Re: Proposal: Expanding the Jenkins Core maintainers team

[Manuel Ramón León Jiménez]

It would be an honor.

On Tuesday, January 21, 2020 at 1:01:58 PM UTC+1, Oleg Nenashev wrote:
>
> Dear all,
>
> *TL;DR*: I propose to expand the Jenkins Core maintainers team by 
> inviting the most active code reviewers to the team. 
>
> As you probably know, Jenkins core maintainers capacity has been a 
> long-standing issue which was impacting the velocity of the Jenkins core 
> and, in some case, leading to regressions due to missed issues during 
> reviews. In September 2019 we created a new Core Pull Request Reviewers 
> team 
> 
>  in 
> order to onboard more reviewers and provide a clear path to join the 
> Jenkins Core team (aka "Jenkins core maintainers"). Currently the 
> reviewers team 
>  
> includes 10 members including me and Mark Waite. Mark was added to the 
> Jenkins Core team in November 2019 as per this discussion 
> 
> .
>
> The "onboard more reviewers " part was a huge success IMHO. We largely 
> increased number of reviews in the Jenkins core. Below you can find some 
> stats and I extracted from DevStats . 
> Please take them with a grain of salt, because there are some artifacts I 
> see in other repositories:
>
>- Last quarter we got to almost *700 *reviews. Before the change we 
>had *400 *reviews in the previous quarter. (query 
>
> ).
>  
>Quarters are counted till Dec 31, 2019.
>- During the last quarter the newcomer reviewers team members did more 
>than *150 *reviews (query 
>
> ).
>  
>This number is lower than the one above, but apparently it  ignores 
>re-reviews
>- We went from *2.5* to *4* reviews on average in pull requests. 
>Number of incoming pull requests was quite stable over past quarters (
>query 
>
> ).
>  
>Note that the review numbers IIUC includes re-reviews. Before introducing 
>the team we used to merge a lot of PRs with just one review, but it does 
>not happen anymore
>- Time to engagement slightly improved, but no drastic improvements 
>there (query 
>
> 
>)
>
> IMHO it is time to proceed with the second part, "provide a clear path to 
> join the Jenkins Core team". Based on the data, I suggest we expand the 
> core team by inviting the most active code reviewers to it. Effectively it 
> means granting merge permissions. I suggest the following:
>
>- 5 most active reviewers are invited to join the Jenkins Core 
>maintainers  team: Raihaan 
>Shouhell , Matt Sicker 
>, Tim Jacomb , Ramon 
>Leon , Evaristo Gutiérrez 
>  
>- All maintainers will need to sign individual CLA 
>    (and company CLA if 
>   needed) before getting permissions
>   - The team provides access to 32 repositories: Jenkins modules, 
>   libraries and core developer tools like Parent POMs. I will probably 
> clean 
>   it up a bit
>- We ensure that there is a knowledge transfer process established to 
>help new maintainers
>   - We start doing regular office hours with Q and joint PR 
>   grooming/review sessions, e.g. every 2 weeks. I am ready to run such 
>   sessions
>   - Maintainer guidelines and best practices are documented in the 
>   Jenkins core repo. We will gradually create this documentation together 
>   during KT sessions  
>   - TBD - we create a new public chat for core maintainers so that 
>   conversations can happen outside highly populated #jenkins and 
>   jeninsci/jenkins channels in IRC and Gitter. Maybe YAGNI?
>- We encourage more contributors to join the reviewers team. Having 
>more contributors is always great!
>
> What do you think?
>
> Best regards,
> Oleg Nenashev
>
> Reviews by Core PR reviewers team in this quarter (Oleg and Mark are 
> excluded):
> [image: image.png]
>
> Jenkins Core code reviews by quarter:
> [image: image.png]
>
> Jenkins core pull request by quarter:
> [image: image.png]
>
>

-- 
You received this message 

Re: debugger doesnot stop at breakpoints while debugging Jenkins core in Intellij

[Manuel Ramón León Jiménez]

Could you change the address to 5000 and remote debugging on this port?


On Tue, Sep 3, 2019 at 8:25 PM varun vikas  wrote:

> Hi,
>
> I am trying to remote debug Jenkins core code.
> I run command java
> -jar -agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=8000
> jenkins.war
> jenkins started successfully on port 8000.
>
> Now I do remote debugging and set some breakpoints , but debugger is not
> stopping at breakpoints.
> I am not able to find out , what may be the issue.
>
> I have set breakpoints
> in jenkins\core\src\main\java\hudson\WebAppMain.java file.
>
> Thanks,
> Varun
>
> --
> 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/a3065164-03d4-4c29-8426-70325dc824f3%40googlegroups.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/CADN1OJ0y071ceTvpvuwZaOeyZ80QhrHAEigry609Q0G%3DHUDh%2Bg%40mail.gmail.com.

Re: The future of LTS certification

[Manuel Ramón León Jiménez]

Hello Martin.

I don't have clear enough what this implies, but count on me if you need.

Best regards.

On Fri, Jan 4, 2019 at 1:30 PM martinda  wrote:

> Hello Manuel,
>
> On Thursday, January 3, 2019 at 4:49:12 AM UTC-5, Manuel Ramón León
> Jiménez wrote:
>>
>> Hello and happy new year.
>>
>> Splitting the ATH tests is very interesting from my PoV. It will let
>> plugin developers be more conscious of its existence and perhaps, it could
>> help to have a more well maintained and useful set of tests.
>>
>>>
>>>
>  Would you be interested mentoring the ATH improvements proposal
> <https://docs.google.com/document/d/1M15rktOEOIPlDrlS13f42bSJLbI0P47hplBIAL_FX_g/edit>?
> We need at least one more mentor on that proposal.
>
> Martin
>
> --
> 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/df71c90a-ee16-4f2c-a22f-9290f6c6e443%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/df71c90a-ee16-4f2c-a22f-9290f6c6e443%40googlegroups.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/CAHHyvkObrAA0Xy6igs7LvLyis3ZZk6SxRFGWB6gFQEORPp6K6Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: The future of LTS certification

[Manuel Ramón León Jiménez]

Hello and happy new year.

Splitting the ATH tests is very interesting from my PoV. It will let plugin
developers be more conscious of its existence and perhaps, it could help to
have a more well maintained and useful set of tests.

Best regards.

On Thu, Jan 3, 2019 at 10:17 AM Oleg Nenashev 
wrote:

> Thanks for the interest Sahil!
>
> My advice would be to stick to Docker for now, unless you see special
> benefits of K8s and other systems.
> We do not have a ready-to-fly Kubernetes setup inside the Jenkins
> infrastructure, and it's also quite complicated to do local development
> with it.
>
> I would like to start contributing to the project from now as it is nearly
>> impossible to complete the whole project in GSoC timeline.
>>
>
> Yes, likely. Note that we do not expect a GSoC student to complete the
> entire project of such scale. In your proposal you can focus on a
> particular area only so that you are not overcommitted.
>
> Best regards,
> Oleg
>
> On Wednesday, January 2, 2019 at 6:11:08 PM UTC+1, Sahil Khan wrote:
>>
>> Hello,
>> Last year in 2018 I applied for the similar GSoC Project for Improvement
>> of ATH.Here is the link to my GSoC Proposal of 2018.
>> 
>> I would like to start contributing to the project from now as it is
>> nearly impossible to complete the whole project in GSoC timeline.
>> I would like to get some suggestons on like how to start the project and
>> if going for container technology then which one would be the best.
>>
> --
> 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/43fd6d65-fa15-457a-ba0a-78d15e0f3f49%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/CAHHyvkOiD%2BXdwiDngZX1%3DVM2uZv_%2BgTVnG6bCtoP4KnDAoTewA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Be able to merge on core

[Manuel Ramón León Jiménez]

Hello guys, happy new year.

I'm working at CloudBees on the open source size and due to the limited 
bandwith from Oleg and to gain more velocity in some developments, 
specially on *java11*, I believe it could be interesting that you allow me 
to have write permission on Jenkins core and jenkins infra github repos to 
be able to merge some PRs. 

If it helps: 

I've being contributing with some PRs already merged to the core as well as 
reviewed some other ones:

   - PRs merged into core:
   - https://github.com/jenkinsci/jenkins/pull/3816
  - https://github.com/jenkinsci/jenkins/pull/3769
  - https://github.com/jenkinsci/jenkins/pull/3768
  - https://github.com/jenkinsci/jenkins/pull/3718
  - https://github.com/jenkinsci/jenkins/pull/3695
  - https://github.com/jenkinsci/jenkins/pull/3648
   - PRs reviewed in core:
   - https://github.com/jenkinsci/jenkins/pull/3786
  - https://github.com/jenkinsci/jenkins/pull/3795
  - https://github.com/jenkinsci/jenkins/pull/3797
  - https://github.com/jenkinsci/jenkins/pull/3807
  - https://github.com/jenkinsci/jenkins/pull/3804
  - https://github.com/jenkinsci/jenkins/pull/3815
  - https://github.com/jenkinsci/jenkins/pull/3818
  
  
I'm also a maintainer of two plugins (
plugin-apache-httpcomponents-client-4-api 

 
and plugin-jdk-tool 

).

My user id in all systems (github, jenkins jira, ...) is: *mramonleon*

Thank you, kind regards.

-- 
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/7fedc96c-5b22-4234-a2b5-b7afd5dc688a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.