Re: kerberos-sso plugin lookign for a new maintianer.

[ogondza]

Dependabot's PRs are something to take a look at. It is a good way to 
become intimate with Jenkins plugin build process and dependency resolution 
struggles: https://github.com/jenkinsci/kerberos-sso-plugin/pulls

I also went through the open JIRAs and closed the outdated items. These 
seem reasonable simple:

- https://issues.jenkins.io/browse/JENKINS-39051
- https://issues.jenkins.io/browse/JENKINS-39052
- https://issues.jenkins.io/browse/JENKINS-38782

On Thursday, November 2, 2023 at 5:19:57 PM UTC+1 tiwarij...@gmail.com 
wrote:

> Hi Oliver,
>
> Thank you for inviting me. I have accepted the invitation.
>
> I went through the issues list on JIRA. It is divided into bugs and 
> improvements. I noticed a few issues are dated back to 2016 and 2017. 
>
> Could you suggest some beginner-friendly issues to start with?
>
> Thanks & Regards,
> Jagruti
>
> On Thu, Nov 2, 2023 at 5:31 PM ogondza  wrote:
>
>> Thanks, Jagruti Tiwari!
>>
>> I have sent you and invitation to maintain the GH repo. Follow up with 
>> filing a PR to get the release permissions, and tag me for approval: 
>> https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#plugins-marked-for-adoption
>>
>> Thanks!
>>
>> On Monday, October 30, 2023 at 5:13:08 PM UTC+1 tiwarij...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> I want to take up the task of maintaing this plugin.
>>>
>>> Am familiar with Kerberos and Jenkins. This means I have to read the 
>>> documentation at every step. 
>>>  
>>> I understand Kerberos' and Jenkins' purpose and functioning. 
>>>
>>> I would like to learn the ropes of a Jenkins plugin maintainer and 
>>> maintain many more plugins in the future.
>>>
>>> Thanks,
>>> Jagruti Tiwari 
>>>
>>> On Mon, 30 Oct, 2023, 4:50 pm ogondza,  wrote:
>>>
>>>> Hello,
>>>>
>>>> As the only active maintainer of the plugin for past several years, I 
>>>> will no longer maintain it going forward. (No time, the org migrated to 
>>>> SAML).
>>>>
>>>> If you are interested to carry the torch long term, please let me know. 
>>>> Otherwise, I will flag the plugin officially up for an adoption.
>>>>
>>>> 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-de...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/3903a58f-ba74-4e92-a4ea-cea608e3d79cn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/3903a58f-ba74-4e92-a4ea-cea608e3d79cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/1ebaaae6-abca-4280-ae52-9106444ba7ecn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/1ebaaae6-abca-4280-ae52-9106444ba7ecn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7072c2ad-33af-4d69-89b6-0f66a22c8439n%40googlegroups.com.

Re: kerberos-sso plugin lookign for a new maintianer.

[ogondza]

Thanks, Jagruti Tiwari!

I have sent you and invitation to maintain the GH repo. Follow up with 
filing a PR to get the release permissions, and tag me for 
approval: 
https://www.jenkins.io/doc/developer/plugin-governance/adopt-a-plugin/#plugins-marked-for-adoption

Thanks!

On Monday, October 30, 2023 at 5:13:08 PM UTC+1 tiwarij...@gmail.com wrote:

> Hi,
>
> I want to take up the task of maintaing this plugin.
>
> Am familiar with Kerberos and Jenkins. This means I have to read the 
> documentation at every step. 
>  
> I understand Kerberos' and Jenkins' purpose and functioning. 
>
> I would like to learn the ropes of a Jenkins plugin maintainer and 
> maintain many more plugins in the future.
>
> Thanks,
> Jagruti Tiwari 
>
> On Mon, 30 Oct, 2023, 4:50 pm ogondza,  wrote:
>
>> Hello,
>>
>> As the only active maintainer of the plugin for past several years, I 
>> will no longer maintain it going forward. (No time, the org migrated to 
>> SAML).
>>
>> If you are interested to carry the torch long term, please let me know. 
>> Otherwise, I will flag the plugin officially up for an adoption.
>>
>> 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-de...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/3903a58f-ba74-4e92-a4ea-cea608e3d79cn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/3903a58f-ba74-4e92-a4ea-cea608e3d79cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1ebaaae6-abca-4280-ae52-9106444ba7ecn%40googlegroups.com.

Re: kerberos-sso plugin lookign for a new maintianer.

[ogondza]

The repo: https://github.com/jenkinsci/kerberos-sso-plugin

On Monday, October 30, 2023 at 12:19:58 PM UTC+1 ogondza wrote:

> Hello,
>
> As the only active maintainer of the plugin for past several years, I will 
> no longer maintain it going forward. (No time, the org migrated to SAML).
>
> If you are interested to carry the torch long term, please let me know. 
> Otherwise, I will flag the plugin officially up for an adoption.
>
> 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/eac88b11-e5db-467b-861a-529cee6eac01n%40googlegroups.com.

kerberos-sso plugin lookign for a new maintianer.

[ogondza]

Hello,

As the only active maintainer of the plugin for past several years, I will 
no longer maintain it going forward. (No time, the org migrated to SAML).

If you are interested to carry the torch long term, please let me know. 
Otherwise, I will flag the plugin officially up for an adoption.

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/3903a58f-ba74-4e92-a4ea-cea608e3d79cn%40googlegroups.com.

Re: Releasing JCasC support for ghprb-plugin

[ogondza]

I understand it feels strange, though it is the second best thing we can do 
in case we lack a maintainer.
On Wednesday, January 6, 2021 at 5:53:37 PM UTC+1 msi...@cloudbees.com 
wrote:

> I'd prefer if this plugin has an actual maintainer. Otherwise, this
> also seems like false advertising that the plugin is still supported
> by anyone.
>
> On Wed, Jan 6, 2021 at 10:45 AM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> >
> > If you do a release and there are new bugs are you going to handle them?
> >
> > Without a maintainer it seems like deploying to prod and not monitoring 
> afterwards.
> >
> > Gavin
> >
> > On Wed., Jan. 6, 2021, 6:03 a.m. Marky Jackson,  
> wrote:
> >>
> >> Same, no objections
> >>
> >> On Jan 6, 2021, at 6:01 AM, Mark Waite  wrote:
> >>
> >> 
> >> No objections from me.
> >>
> >> On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža  wrote:
> >>>
> >>> Hey, there is a long anticipated feature merged in in the plugin[1][2],
> >>> but no maintainer appears to be active to cut a release.
> >>>
> >>> Are there any objections if I step in a do the release?
> >>>
> >>> [1] https://github.com/jenkinsci/ghprb-plugin/pull/731
> >>> [2] https://issues.jenkins-ci.org/browse/JENKINS-55793
> >>> --
> >>> oliver
> >>>
> >>> --
> >>> 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/f3e65b25-477d-a780-ceae-eb8dec945f40%40gmail.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/CAO49JtETdyEZtHzG2%2BLGBHyBmKHZPTjLQffozt16GWYb%3DP_htg%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/CE90DAE5-AF7D-452E-BAAB-6DD82A6B0B5A%40gmail.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_Dut0W%3DJyR48uxTvPpUgZg2vS1nRsAtHREKW%2BGsbjfXRX%3Dw%40mail.gmail.com
> .
>
>
>
> -- 
> Matt Sicker
> Senior Software Engineer, CloudBees
>

-- 
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/8c9149bf-b71b-4184-a280-2280ad1eeb66n%40googlegroups.com.

Re: Data binding: Bind repeatable list of textboxes into List

[ogondza]

Thanks for confirmation, folks. The issue have pointed me to using textarea 
to represent the list of strings making my life a whole lot simpler!
On Wednesday, January 6, 2021 at 7:57:36 PM UTC+1 Jesse Glick wrote:

> Note that `CustomDescribableModel` was intended to help with this sort of 
> case (`String` → `List` and vice-versa) but AFAIK is not yet 
> honored by `configuration-as-code`, which does not use `structs` APIs for 
> its introspection.
>

-- 
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/6416a171-393b-4d5d-ba41-09eed1602ff2n%40googlegroups.com.

Re: LTS baseline selection for the successor of 2.235

[ogondza]

Avoiding 2.250 so it is not confused with 2.150 is an interesting 
suggestion, though it does not outweigh stability so 2.249 is preferable 
over 2.251.

I do not think backporting the only fix from 2.250 to 2.249 is going to 
confuse anyone: users need to track *when* the fix was introduced in weekly 
and LTS separately and I doubt they care much *how* specifically it have 
happened.

*So, I am declaring 2.249 a winner.*

As always, thanks a lot for all the inputs! Even when your suggestions was 
not followed, please keep them coming to ensure the hight quality of the 
results produced.

Thanks!
--
oliver

-- 
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/00077a7b-71fb-495c-b9ae-4928b1c66aaco%40googlegroups.com.

Re: Backporting for LTS 2.222.1 started

[ogondza]

I agree that this one is quite nasty. Let's keep an eye on that and see if 
it can be fixed in .1.

--
oliver

-- 
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/161d5d28-5536-47e4-ad84-3d6821d07a49%40googlegroups.com.

Re: Jenkins 2.204.3 LTS RC testing started

[ogondza]

Mark, how does the second RC perform in your testing?

--
oliver

-- 
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/e8b6a596-3ce3-41f0-9ab7-fcc125526d9c%40googlegroups.com.

Re: Jenkins 2.204.3 LTS RC testing started

[ogondza]

Mark, thanks for reporting this. I have published an RC respin[1] with Java 
8, until we identify the reason why is this causing problems.

Please make sure the ongoing testing is done with 
ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69 (sha256). 
Thanks!

[1] http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war

--
oliver

-- 
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/005cb301-b149-44b4-bf3a-25dbd5ca35dd%40googlegroups.com.

Re: Jenkins 2.204.1 LTS RC testing started

[ogondza]

Thank you guys very much for keeping the quality bar high! As Baptiste 
said, better to be alarmed for without defect.

My internal testing have not revered anything. The 2.204.1 can be released 
today.

--
oliver

-- 
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/7366e9f6-9759-465b-9b81-4da9cea0ee7a%40googlegroups.com.

Re: Backporting for LTS 2.204.1 started

[ogondza]

Thanks Baptiste. But as you said, this will be postponed to .2.

On Tuesday, December 3, 2019 at 3:36:09 PM UTC+1, Baptiste Mathus wrote:
>
> Just as heads-up, also because I am not fully sure of the usual 
> practice/process: but I think this is worth mentioning: 
> https://issues.jenkins-ci.org/browse/JENKINS-57304 fix was just merged, 
> hence should land in next weekly next Monday or so.
>
> If possible to consider, I think this could be a good candidate maybe. The 
> fix is a one-liner. 
>
> I would fully understand we'll wait for .2 for this one to receive more 
> weekly testing to be eligible for an LTS backport. 
> I just thought I'd mention it given it will not show up in the filter 
> before next week when it's finally marked as Resolved and released.
>
> Cheers
>
> Le lun. 25 nov. 2019 à 22:27, Oleg Nenashev  > a écrit :
>
>> I went through 2.205 and 2.206 changes and marked JIRA issues which may 
>> deserve backporting.
>>
>> Best regards,
>> Oleg
>>
>>
>> On Friday, November 22, 2019 at 9:18:16 AM UTC+1, ogondza wrote:
>>>
>>> Backporting has started and the RC is scheduled for 2019-12-04. 
>>>
>>> Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 
>>> Fixed: 
>>> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-fixed 
>>> Rejected: 
>>> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-rejected 
>>> -- 
>>> oliver 
>>>
>> -- 
>> 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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/a6a15fb4-defb-4475-a045-ecaa69de8270%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/a6a15fb4-defb-4475-a045-ecaa69de8270%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f59e383f-9d2f-4d78-ad3a-3c24f3b113cf%40googlegroups.com.

Re: Next LTS baseline selection

[ogondza]

I like that idea, Jesse. Can we agree on picking 2.204 with JENKINS-58993 
patched to only fail when assertions are on?

--
oliver

-- 
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/95885a12-770a-41cb-ae4a-9279fe904e73%40googlegroups.com.

Re: Next LTS line selection open. Due 2019-08-27

[ogondza]

See the previous message: 
https://groups.google.com/d/msg/jenkinsci-dev/FM8_kG1kdw8/sIOvRmEeBQAJ

-- 
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/a4ec1e7d-1264-48fb-b504-eafe0ebc1627%40googlegroups.com.

Re: Jenkins 2.176.3 LTS RC testing started

[ogondza]

I have published new RC with the late backport in. Available via 
http://mirrors.jenkins-ci.org/war-stable-rc/2.176.3/jenkins.war 


--
oliver

-- 
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/9aca46e2-36ec-4634-82e0-be03fe06d2c7%40googlegroups.com.

Re: 2.176.1 LTS RC regression found (Was: Jenkins 2.176.1 LTS RC testing started)

[ogondza]

Alright, I have filed https://github.com/jenkinsci/jenkins/pull/4047 to 
revert remoting on master. Once reviewed, I will backport that revert to 
LTS as well. Thanks!

On Tuesday, May 28, 2019 at 5:13:02 PM UTC+2, Oleg Nenashev wrote:
>
> Remoting version downgrade is reasonable IMO.
>
>
> On Tue, May 28, 2019, 17:07 Antonio Muñiz  > wrote:
>
>> Reverting the remoting upgrade is ok for me too. 
>> Then we can work on a fix for JENKINS-57713 
>>  - IMO the "no 
>> retry" logic should be enabled by a parameter instead of being the default, 
>> so cloud implementations not wanting this can disable it.
>>
>> On Tue, 28 May 2019 at 16:15, Oliver Gondža > > wrote:
>>
>>> That is spot-on Antonio. I can imagine it will break any plugin using 
>>> JNLP launcher where the VM can happen to be ready sooner than the 
>>> computer is created.
>>>
>>> For me, reverting https://github.com/jenkinsci/jenkins/pull/4005 is 
>>> preferable over changing the baseline this late in the cycle.
>>>
>>> Do you guys intent to revert it in weekly, provide a fix or do something 
>>> else? I am asking so we can coordinate actions...
>>>
>>> On 28/05/2019 14.44, Antonio Muñiz wrote:
>>> > JENKINS-57713  - 
>>> > This is breaking a proprietary cloud implementation. It's a regression 
>>> > for us.
>>> > 
>>> > On Thu, 23 May 2019 at 16:16, Oliver Gondža >>  
>>> > > wrote:
>>> > 
>>> > Hello everyone,
>>> > 
>>> > Latest LTS RC was made public and it is ready to be tested. Final
>>> > release is scheduled for 2019-06-05.
>>> > 
>>> > 
>>> > Postponed:
>>> >  JENKINS-57528   CriticalJenkins 
>>> 2.178
>>> >  Jenkins in Docker does not install detached 
>>> plugins
>>> > when there is no
>>> > UC data
>>> > https://issues.jenkins-ci.org/browse/JENKINS-57528
>>> > 
>>> >  JENKINS-25369   Minor   Jenkins 
>>> 2.178
>>> >  DNS multicast error messages
>>> > https://issues.jenkins-ci.org/browse/JENKINS-25369
>>> > 
>>> >  JENKINS-57477   CriticalJenkins 
>>> 2.178
>>> >  Cancelling a job results in "sendctrlc.x64...exe"
>>> > stops working
>>> > https://issues.jenkins-ci.org/browse/JENKINS-57477
>>> > 
>>> > Fixed:
>>> >  JENKINS-57412   Major   Jenkins 
>>> 2.177
>>> >  Incorrect deletion for setup wizard of Chinese
>>> > localization files on
>>> > Jenkins LTS 2.176
>>> > https://issues.jenkins-ci.org/browse/JENKINS-57412
>>> > 
>>> >  JENKINS-57111   Major   Jenkins 
>>> 2.177
>>> >  Base class setChannel does not handle exceptions
>>> > from onOnline call
>>> > https://issues.jenkins-ci.org/browse/JENKINS-57111
>>> > 
>>> > 
>>> > Please, report your findings in this thread.
>>> > 
>>> > Download bits from
>>> > http://mirrors.jenkins-ci.org/war-stable-rc/2.176.1/jenkins.war
>>> > 
>>> > Thanks!
>>> > -- 
>>> > oliver
>>> > 
>>> > -- 
>>> > 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 jenkin...@googlegroups.com 
>>> > >> >.
>>> > To view this discussion on the web visit
>>> > 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/02142c5b-b89e-fbed-5243-a16b7b956c8c%40gmail.com
>>> .
>>> > For more options, visit https://groups.google.com/d/optout.
>>> > 
>>> > 
>>> > 
>>> > -- 
>>> > Antonio Muñiz
>>> > Human, Engineer
>>> > CloudBees, Inc.
>>> > 
>>> > -- 
>>> > 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 jenkin...@googlegroups.com  
>>> > .
>>> > To view this discussion on the web visit 
>>> > 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRNyGPHV7Q%2B2z22T%2BD5QM6P3HXgowYW6NnS1rScB5SFUQ%40mail.gmail.com
>>>  
>>> > <
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRNyGPHV7Q%2B2z22T%2BD5QM6P3HXgowYW6NnS1rScB5SFUQ%40mail.gmail.com?utm_medium=email&utm_source=footer
>>> >.
>>> > For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>> -- 
>>> oliver
>>>
>>> -- 
>>> 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 jenkin...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.c

Re: Jenkins extended choice parameter plugin: do you have write permission?

[ogondza]

This is the second public call for maintainer's attention with no reply. I 
have flagged the plugin up-for-an-adoption.

Vimil, feel free to correct once you are back, but for now, we have to 
presume this is abandoned.

Thanks
--
oliver

-- 
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/d640ccd6-77ef-42d3-942c-7821cdce90ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: The future of LTS certification

[ogondza]

There is a striving discussion in the docs. One thing I failed to realize 
we need soon enough is the list of "Recognized use-cases" of ATH (drafted 
in the doc) I would like to get feedback on from as many people as I can.

Another hot topic is how do deal with tests failing because of a defect in 
a component during the time it is being fixed. On one hand people do not 
want to be annoyed by known red tests but on the other we need ATH to be 
able to point out that defect to people interested in using the defective 
component.

Do not hesitate to join us!

Thanks!
--
oliver

-- 
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/f838b165-c4d7-44b8-a03c-413c56d1b3de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: The future of LTS certification

[ogondza]

Thank you everyone for the feedback. We have put together an initial draft 
of what will become new process of ATH maintenance. I intend to 
collectively craft the final shape of the document in a couple of coming 
weeks and then make it official by adding it as a github repo contribution 
guidelines.

There are several long term goals we kept in mind:
- Tolerable running time over breadth of the suite.
- Reliable build status over keeping every test ever written.

Please, take a time to digest that and let us know what you think. Every 
question, suggestion or correction is welcome.

https://docs.google.com/document/d/1k9sDlssxs0URZOjbF3jmBhTf-LoA7JQKj5TLIONmuVA/edit#
Thanks
--
oliver

-- 
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/01b4d7fe-cd91-4561-9706-b04b27e15781%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.150 started

[ogondza]

Backporting is over. We have one candidate postponed for .2:

Postponed:
JENKINS-48775CriticalTue, 20 Nov 2018 14:53:06 +
Proxy authentication error 407 even if 'check proxy' works
https://issues.jenkins-ci.org/browse/JENKINS-48775
Fixed:
JENKINS-54551BlockerFri, 9 Nov 2018 09:16:13 +
Revert JENKINS-53462 if necessary
https://issues.jenkins-ci.org/browse/JENKINS-54551
JENKINS-54310MinorWed, 7 Nov 2018 08:30:12 +
java.io.IOException: Stream is closed when the CLI has not read 
entirely the input
https://issues.jenkins-ci.org/browse/JENKINS-54310
JENKINS-49196MinorThu, 8 Nov 2018 12:06:57 +
java.io.IOException: Premature EOF when shutdown CLI command is used
https://issues.jenkins-ci.org/browse/JENKINS-49196
JENKINS-38719MinorWed, 14 Nov 2018 19:09:55 +
ConsoleAnnotatorFactory serves stale JavaScript and CSS when a 
plugin is upgraded/downgraded
https://issues.jenkins-ci.org/browse/JENKINS-38719

--
oliver

-- 
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/822d2cb6-59c0-4789-81ad-188b948b7373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.138.1 started

[ogondza]

Please note the backporting window will effectively close on Friday 
2018-08-24, in UTC morning hours. That is when the RC will be published and 
testing period will start. I apology for such a late notice. Note that 
there are no candidates nominated until now so there should be no impact on 
the actual LTS.

--
oliver

-- 
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/45ab5b33-89e0-4e2e-a812-7f21878725be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.121.1 started

[ogondza]

The backporting window is closing this Wednesday. There ware no candidates 
nominated (likely due to recent baseline choice) BUT there is the 
outstanding problem of JENKINS-51253[0].

There does not seem to be a consensus on whether/how to fix it[1] so I am 
wondering which version of remoting we prefer to use for 2.121 LTS. I lean 
towards using pre-JENKINS-45287[2] remoting - before the regression was 
introduced. But there are alternatives of shipping current master or 
expediting the fix.

Thoughts?

[0] https://issues.jenkins-ci.org/browse/JENKINS-51253
[1] https://github.com/jenkinsci/packaging/pull/107
[2] https://issues.jenkins-ci.org/browse/JENKINS-45287

-- 
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/6ba611bf-61ca-4f37-b346-06b5322daa3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to be made a maintainer of audit-trail-plugin

[ogondza]

My apology for the delay. I do not object if someone takes over the 
maintenance of this unmaintained plugin. Thanks!

--
oliver

-- 
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/1a1a743a-438f-49f6-ad1f-67b86990d4d0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Speeding up the ATH

[ogondza]

Hey,

Here is my draft for the smoke tests 
https://github.com/jenkinsci/acceptance-test-harness/pull/365
and documentation of the test acceptance / removal: 
https://github.com/jenkinsci/acceptance-test-harness/pull/364

Please, comment there for tuning. Note things can be further refined after 
merged...

--
oliver

-- 
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/a3755ed7-a648-4f3f-a175-a8930d70c33e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.73.1 LTS RC testing started

[ogondza]

Agreed on the meeting the release will be cut with the regression compared 
to 2.60 line (with remoting 3.10) and Jenkins docker container will be 
updated not to be impacted. The proper fix will target 2.73.2.

--
oliver

-- 
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/a078b162-f745-408e-bd07-a245b959aba5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.73.1 LTS RC testing started

[ogondza]

I have reverted remoting back to version 3.10 and pushed another RC asking 
Mark to retest.

Relevant issue https://issues.jenkins-ci.org/browse/JENKINS-46754

--
oliver

-- 
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/191467ae-0ddb-4cec-a047-f3e824da4db0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.73.1 started

[ogondza]

Given my traveling next week and a set of nontrivial candidates, I am 
postponing RC to Monday after scheduled date 2017-09-04.

-- 
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/ec628d09-5e69-4b51-a9b8-08560089d952%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.60.1 started

[ogondza]

Backporting is ready and RC will be pushed tomorrow morning UTC time.

$ lts-candidate-stats 2.60.1
Rejected:
JENKINS-40693MinorFri, 26 May 2017 08:06:29 +
badMessage: 400 Bad Host header for HttpChannelOverHttp
https://issues.jenkins-ci.org/browse/JENKINS-40693
Fixed:
JENKINS-44120MajorFri, 19 May 2017 23:10:39 +
Git checkout hangs after update on 2.59
https://issues.jenkins-ci.org/browse/JENKINS-44120

Note the hiccups ATH was experiencing on master and now on stable branch 
too are gone. (I have reconfigured both builds to use JDK 8 a while ago but 
version 7 was hardcoded in the build script for some reason which is 
something I have not noticed. ATH was broken in a way Jenkins log was not 
preserved so it was not easy to find out without fixing the bug first.)

-- 
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/9ce1f3ef-8275-4528-a557-cc5ec2ab51fa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.46.3 LTS RC testing started

[ogondza]

ATH has captured a regression[1] in .3 I am investigating right now. 
Compared to .2 it seems to pick workflow-job 2.12 (instead of 2.11) that 
fails to load as it requires Jenkins 2.60+.

[1] 
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/1492/testReport/core/InstallWizardTest/wizardInstallSugestedTest/
[2]
```
INFO: Attempting to dynamic load 
/home/ogondza/code/jenkins/acceptance-test-harness/jhrevert/plugins/workflow-job.jpi
May 24, 2017 2:29:43 PM hudson.model.UpdateCenter$DownloadJob run
SEVERE: Failed to install Pipeline: Job
java.io.IOException: Failed to dynamically deploy this plugin
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1899)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1656)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: Failed to install workflow-job plugin
at hudson.PluginManager.dynamicLoad(PluginManager.java:875)
at hudson.PluginManager.dynamicLoad(PluginManager.java:814)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1895)
... 5 more
Caused by: java.io.IOException: Pipeline: Job v2.12 failed to load.
 - You must update Jenkins from v2.46.3-SNAPSHOT (private-05/24/2017 12:25 
GMT-ogondza) to v2.60 or later to run this plugin.
at 
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:621)
at hudson.PluginManager.dynamicLoad(PluginManager.java:865)
... 7 more
```

-- 
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/c5d37991-c634-4435-8d94-8b07a149d67b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline DSL objects - class-loaders and compilation

[ogondza]

Thanks for commenting on the PR. Am I right to assume that there is no 
practical advantage to distribute the objects that are returned into 
pipeline as runtime-compiled groovy, much less loading it through pipeline 
provided classloader? Returning POJOs of compiled classes is the way to 
go...

Thanks.
--
oliver

-- 
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/8c20df3b-f8af-494d-9bf8-0198a3387da0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.46.2 LTS RC testing started

[ogondza]

The tests looks good and noone reported any problems as well. This will be 
released on Wednesday unless something urgent pops up.

--
oliver

-- 
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/68f77f19-4c4c-49f9-99e5-bf2e8958a71e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Time for Jenkins to require Java 8 to run

[ogondza]

I am undecided on the subject. There clearly always are reasons to use 
newer/better version but is JDK 7 support really blocking us somewhere? 
Bugs we cannot fix / need to awkwardly compensate, features we can not 
deliver on Java 7?

I felt much stronger against dropping Java 6 as we identified several 
architecture/OS combinations with no Java 7+ vendor making the platforms 
(RHEL4, itanium architecture, Solaris 9 (IIRC)) not usable as Jenkins 
nodes. (Yes, you can run agent on older Java version but it causes subtle 
problems.) However, oracle does not seem to drop any of the platforms (at 
least those we care for) between 7 and 8.

What we can do right now, to make this a bit less troublesome to users and 
easier to digest for community, is creating a general time plan for 
dropping support of JDKs (or other things) we would follow in specific 
cases. Something like:

- Month 0: Announce the intention publicly, with this plan attached.
- Month 3: Drop support for Jenkins weekly. Declare what LTS will be the 
last one to support the think we are dropping. Since we gave people time to 
get prepared, we do not have to try hard to prolong the support in LTS 
branch. IOW, I see no reason to do whole new LTS line after the support was 
dropped for weeklies.
- Month 3-5: LTS.1 with support dropped is released.
- Month 12?: In case of Java, encourage the use from plugins / use it as 
default. Extending the support in plugins allow people to consume plugin 
updates/fixes after upstream has dropped support without upgrading Java. 
This is especially subtle as IIRC plugin manager offers plugin updates 
(perhaps even core ones) that require newer Java version than the one 
installed on master, and there is no guarantee plugin that needs Java 8 
require core with same requirement.

--
oliver

-- 
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/503afa20-4e4d-4aad-91d4-e28439cf269c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PR Builder not setup for foreman-node-sharing plugin

[ogondza]

Thanks guys, it works now.

--
oliver

-- 
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/2b32b5d5-a7a5-4426-beee-425d4d3a49e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: PR Builder not setup for foreman-node-sharing plugin

[ogondza]

Hmm, There is no job for that plugin at all. When I tried to create it from 
maven template I got "ERROR: script not yet approved for use". Is this not 
something that should be done by IRC bot when plugin is forked?

--
oliver

-- 
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/e5cc1319-7f63-4e47-b768-527252e57032%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker workflow runs with user not fully configured

[ogondza]

https://issues.jenkins-ci.org/browse/JENKINS-38438

--
oliver

-- 
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/abe61d3d-b9e6-4995-9c39-027b0a251f84%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [SPAM Low] [Proposal] - Release Jenkins 2.7.4 on this week

[ogondza]

The test results[1] looks good. I am pushing the RC at the moment for 
manual retesting. Once confirmed, I am ok to get that released.

FYI, I suggest[2] to have an explicit link type for issue that introduced 
another one. So hopefully, such situation will be lot less likely to 
reoccur.

[1] 
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable-2.7/1/
[2] https://issues.jenkins-ci.org/browse/INFRA-915

--
oliver

-- 
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/2cef2e9a-2620-4254-8418-ddcb8ab6a86b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.7.3 LTS RC testing started

[ogondza]

I have respun the RC with 
https://github.com/jenkinsci/jenkins/commit/27d8f06f1baabb320cc86527250bed5a7dacf85e
 
reported by Oleg.

Please make sure you are using build "rc-08/24/2016 06:31" for further 
testing.

Thanks 
-- 
oliver 

-- 
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/bfd4d942-b930-4bc9-a9dc-0e7deb89c314%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Automate recommended plugin unittest run against latest Jenkins core

[ogondza]

Right, not the best wording. What I had in mind is: "It is something we 
would like to have confirmed before declaring the release is good to go".

Unfortunately, many maintainers do not put that much effort into making 
sure their plugins work with latests cores, myself including.

--
oliver

-- 
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/f373a327-d354-4446-87d8-25eb2472d733%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 2.7.1 has started

[ogondza]

I consider backporting to be close. All was backported except for 
JENKINS-35641 and JENKINS-34923 where I would like it to have some extra 
soaking time. Note that I will not be able to attend the Governance meeting 
(travelling) so I will proceed with the rc at the closest time I am 
available unless I hear some objection, either here or in meeting logs, or 
the ATH will fail seriously.

--
oliver

-- 
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/4f621098-ed39-462d-a245-52f882650d89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 2.7.1 has started

[ogondza]

stephenconnolly on JENKINS-35402: [~olivergondza] I really would like this in 
the 2.7.1 LTS

 

-- 
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/4b27217d-6487-4091-b46b-d869f4326d69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins cloud health reporting

[ogondza]

An example of how integration with provisioning plugins will look like: 
https://github.com/jenkinsci/openstack-cloud-plugin/pull/71

--
oliver

-- 
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/90ccf518-1a14-4f2d-b53b-f84b31ae074e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.651.2 has started

[ogondza]

I have backported remoting 2.57 to fix JENKINS-28289, JENKINS-33999 and 
JENKINS-32980. In case it incorporates another problems I have miss, let me 
now here or on the meeting.

--
oliver

-- 
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/651e8e25-2698-4763-84ae-ba23cf3c3e4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins cloud health reporting

[ogondza]

Finally, there is something to show:

-- 
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/e1330f77-e43e-447e-8952-d508748f1254%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.651.2 has started

[ogondza]

I have backported the nobrainers but the remoting related stuff deserves 
another look tomorow.

--
oliver

-- 
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/21a8a656-9ae8-4519-bd57-5e8dcf54b625%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.651.2 has started

[ogondza]

Consider https://github.com/jenkinsci/jenkins/pull/2283 once merged.

--
oliver

-- 
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/968be354-0b27-4b9d-974d-41e771b029e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for 1.651.2 has started

[ogondza]

Hi, 

Backporting for next LTS release is on. The RC will be published 
2016-04-27. 

Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 

 
Fixed: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.651.2-fixed 
-- 
oliver 

-- 
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/9f632903-254a-4837-847d-a59aab817b31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.651.1 has started

[ogondza]

As agreed on meeting, I reverted JENKINS-28289 and JENKINS-26580 as they 
caused regression (JENKINS-33886). The tests runs fine. Oliver, please 
publish the RC.

-- 
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/9c958fc5-f851-453a-bd7d-7ea02b523088%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins cloud health reporting

[ogondza]

Thanks, I have started to work on this and expect to have something to show 
latter this week.

It seems to be possible to do a lot in cloud agnostic way (count 
provisioning attempts, report failures with exceptions, timings, etc.). 
Though, more interesting things will require plugins to integrate 
explicitly (separating provisioning attempts by template, record listener 
log, etc.).

https://github.com/jenkinsci/cloud-stats-plugin

-- 
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/4f7b160b-fa4f-4838-a681-42df8079f37d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] Openstack plugin 2.0 Beta is out

[ogondza]

Version 2.0 is out[1], it should be available in update centers shortly.

[1] 
http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/openstack-cloud/2.0/
--
oliver

-- 
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/3c864382-08e5-41ee-890b-a48ba86a71d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: LTS status

[ogondza]

I went through my regular routine and all looks good. Nobody else reported 
anything so I guess that is a green light for you.

--
oliver

-- 
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/de223882-d6d6-410e-9b0c-be9379021747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 initial setup plugin selection

[ogondza]

How about some criteria for testing? Requiring X% for code coverage is 
clearly wrong. But how about the plugin needs to have _some_ tests? What I 
believe we should do is having a CI that verifies the plugin selection 
against the core version. Not sure we should use ATH or 
plugin-compat-tester or both.

--
oliver

-- 
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/07f5637d-bd73-4a03-96ba-c9baa790ff6c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.642.1 LTS RC testing started

[ogondza]

As agreed post meeting, this is good to be released. Kohsuke, could you?

--
oliver

-- 
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/1026bbdf-3d9a-404a-a8eb-3d1776915241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.636.1 has started

[ogondza]

The backporting is over. On the last meeting we agreed[1] to use more 
recent and more stable LTS baseline: 1.642. Kohsuke, we are ready for the 
RC.

[1] 
http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-01-06-19.01.html

--
oliver

-- 
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/318027aa-c382-4bad-b542-43af09709716%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Changing the upcoming LTS baseline?

[ogondza]

I have prepared stable branch for both 1.636 and 1.642[1]. Running ATH 
agains both:

https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable/549/
https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness-stable-1.642/1/

[1] https://github.com/olivergondza/jenkins/commits/stable-1.642 (yes, only 
one commit to backport if we pick such a new baseline)

--
oliver

-- 
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/2c69af60-b575-4f4d-9810-fca0d452210f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Script Security plugin dry-run for pre-approval?

[ogondza]

I would welcome if there ware multiple strategies aside of Whitelist-ing. I 
have got several plugins to update, but as those started to use 
script-security, I have to check it is not going to break anything first. 
What would help me (and Andrew) in this case is something akin permissive 
selinux mode - do not interrupt any operation for now, but report what the 
problems are. Once all are ironed out, I will switch to enforcing mode 
again. I promise.

--
oliver

-- 
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/40cf1c62-981f-4499-be88-8464f1c7e0c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.625.3 LTS RC testing started

[ogondza]

We are ready for the release.

-- 
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/45223cc8-38ec-4440-a56b-2bc2d5013511%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.625.3 has started

[ogondza]

Backported JENKINS-31649. Thanks Jesse.

-- 
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/322e0560-ec6e-4b27-9b47-4f8fd26a0891%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.625.3 has started

[ogondza]

As Daniel said, none of the issues was released in any weekly. I agree 
JENKINS-31649 is of low risk so I am opened to backport it. Although, the 
priority is only major, not many votes, not clear who is affected, no 
unittests.

I do not consider JENKINS-31718 to be a serious candidate for .3 as will 
likely not make it to the core when LTS is released, not even talking about 
any soakng...

--
oliver

-- 
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/f493f38a-73d5-4ab7-afec-adfb063e82cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 1.625.2 status

[ogondza]

It is, I have just updated the testing thread.

--
oliver

-- 
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/52090dd3-b036-4b68-a754-95e1f211726b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.625.2 LTS RC testing started

[ogondza]

Testing is done, we are ready for the release.

--
oliver

-- 
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/2f75cc50-8b07-4c60-9c7c-a1b2d9d29277%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for a plugin

[ogondza]

Great, forked as https://github.com/jenkinsci/openshift-pipeline-plugin. 
Welcome aboard!

--
oliver

-- 
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/62fa420d-1372-467e-a427-bea1c497c1b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request hosting for a plugin

[ogondza]

Hi,

I would like to recommend changing the maven GID:UID and the java packages 
so it will be not conflict with other artifacts or other Jenkins plugins 
(the is not the only one openshift plugin for Jenkins). 
com.openshift.jenkins:openshift-builder/com.openshift.jenkins.plugins.builder?

Perhaps management/tasks/steps would sound better to you than builder.

None of that is a reason not to fork you plugin, though.

-- 
oliver

-- 
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/d6c25e39-4de4-4cea-9553-07d5d0791be0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.0 proposal

[ogondza]

I see several problems with this BC breaking approach:

- Countless instances will have to use both the DB and the FS as backend 
simultaneously for some time. If this will span several upgrades, 
downgrades will be a pain for the whole time.
- There are plugins that depend on files heavily. (Copy artifact plugin was 
not fixed to use ArtifactManager since 1.532 (and as it depends on 
attributes that are not provided by the abstraction it is a bit tricky)).

My rough estimate is this would require fixing tens of percents of all 
plugins.

Note that I am not suggesting to use the as the persistence API for next 10 
years but as a way to ensure all plugins will be DB compatible without 
rework.

-- 
oliver

-- 
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/26501e09-ecca-469a-8038-c0cacf4737d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.625.1 has started

[ogondza]

Is this tracked somewhere? How will this be addressed on master branch?

--
oliver

-- 
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/393aab17-4d61-4ff5-8ab5-55e8701cf9a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Guidance on how far SECURITY fixes should go

[ogondza]

On Tuesday, September 15, 2015 at 2:04:54 PM UTC+2, Stephen Connolly wrote:
>
>
> The security fixes are typically prepared in advance for this reason 
> and pushed to every branch at the same time to minimize exposure. If 
> we do not do the concurrent releases then LTS becomes vulnerable. 


I understand that, though it is enough we dictate LTS users when to update 
(even if there is no other way, they are hardly happy about that). If those 
users can not rely there will be no breaking changes (even within one LTS 
line) it will hurt stability (because of the breakage we may caused) and 
security (as admins can postpone the upgrade because of the potential of 
breakage) IMO.

What is the other side of the coin here? The fixes will be smaller and 
simpler for sure if we are allowed not to preserve BC in 100% of cases. 
Anything else?

--
oliver

-- 
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/a2b2e18e-41d2-4c29-a1ce-03392a5b8509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Protecting githib master branches against force-push

[ogondza]

My idea was preventing incidents like [1] to happen.

I do not see a problem with force-pushing to feature branches (provided 
noone based ones work on that), not to mention we do not encourage people 
to create feature branches in core repo.

[1] 
http://jenkins-ci.org/content/summary-report-git-repository-disruption-incident-nov-10th

--
oliver

-- 
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/818ef4a1-8ced-4681-abeb-1468a550b2e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: 1.609.3 RC posted

[ogondza]

It does not seems to be published. [1] gives 404 and [2] serves 1.609.1-rc 
(not even 1.609.2-rc).

[1] http://mirrors.jenkins-ci.org/war-stable-rc/1.609.3/jenkins.war
[2] http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war

--
oliver

-- 
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/baed07fe-1a7d-4394-b30c-d40b222b737c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.609.3 has started

[ogondza]

Right, The backporting is finished.

--
oliver

-- 
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/391be06f-f1af-40dd-8b0b-2cf411efa7d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Approval for XebiaLabs patron message

[ogondza]

+1

--
oliver

-- 
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/9d97df82-97d6-40a7-9e9e-e4e057a1c502%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.609.2 has started

[ogondza]

I have backported the rest: JENKINS-28690, JENKINS-28840, JENKINS-27289, 
JENKINS-14899 and JENKINS-28926.

--
oliver

-- 
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/616f9b23-6424-4313-89ce-3dbba869c8c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way to hide default actions?

[ogondza]

I am not familiar with the plugin implementation enough, though I see no 
reason why such behaviour should not be in core as well. Anyway, having 2 
plugins that does to same with slightly different defaults sounds odd to me.

How about adding an option to the existing plugin that would register 
servlet filter to replace core's own `build` action by plugin's 
implementation?

--
oliver

-- 
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/4ddd18e4-da78-4856-b1f2-afa7bd665cf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is there a way to hide default actions?

[ogondza]

There already is a plugin that injects parameters via URL already[1]. In 
that particular case it is the _plugin's_ URL that was hidden as it was 
causing confusion to users and was accessed by pre-generated URLs most of 
the time.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Build+With+Parameters+Plugin

--
oliver

-- 
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/da306393-1def-4246-b346-19b3c069f48f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.609.2 has started

[ogondza]

On Tuesday, June 16, 2015 at 10:14:21 PM UTC+2, Jesse Glick wrote:
>
> The important part of the JENKINS-27289 was released over a month ago. 
>

Right: https://github.com/jenkinsci/jenkins/compare/8e19340...905930f

--
oliver

-- 
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/8c41bd5d-826e-4979-91ad-3791d3d8c061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.609.2 has started

[ogondza]

On Tuesday, June 16, 2015 at 9:10:37 PM UTC+2, Daniel Beck wrote:
>
> Could you add the end of backporting to your announcements in the future? 
> It would be helpful to know when they're shorter than the usual two weeks. 
> I proposed the qualifying half of JENKINS-27289 on the 10th, less than 48 
> hours after you announced backporting. 
>

I admit, following the cycles is not easy when me and Kohsuke often do not 
announce/release with strict 2 week cadence. Though, I as understand the 
model delayed release or announcement does not affects the schedule. 
Meaning, even if release is not cut exactly on Wednesday (or the 
backporting is not announced right after the release) the backporting is on 
anyway and the period will not be extended (unless we agree otherwise on 
the meeting).

All that said, I will try to get the write access to the calendar so we can 
track this in an easier to follow way.

--
oliver

-- 
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/32bd4376-5a9a-47a2-bf6c-383260e73861%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.609.2 has started

[ogondza]

Both backported.

--
oliver

-- 
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/b9f546dc-39a3-4d1c-b91b-2d541614f94a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [UX] Jenkins controls compaction proposal

[ogondza]

I am quite surprised how many people is dissatisfied with the sidepanel in 
current form. However, shell we ever do something about sidepanel, we will 
have to deal with it gracefully as plugins can contribute sidepanel tasks 
in several ways. Representing controls in an uniform way would be helpful 
actually (or at least something we will have to do anyway).

This PR comment might be 
related: https://github.com/jenkinsci/jenkins/pull/1703#issuecomment-103482968

--
oliver

-- 
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/74354f56-cdab-4873-87d3-2319d9886235%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: What will the next LTS be (was Re: Next LTS is 1.596)

[ogondza]

See:
#topic LTS.next planning
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-01-22-19.01.log.html

I identified these 2:

- Announced weekly release might prove itself to be of low quality
19:33:28  It feels like beefing up the QA effort into the main 
line release is the pre-requisite for us to be able to mechanically pick 
the LTS base version
- Low quality work can get into those releases because of the pressure it 
poses on contributors/commiters
19:34:05  I am afraid that knowing what will be the next lts 
before it is released can motivate people push changes to those releases in 
a hurry degrading their quality

But as you said, we can hold dangerous changes until the LTS.next is 
released. Perhaps this will allow us to merge more PRs we are not so sure 
about right after the crucial release to give it extra long time until 
picked up by the following LTS.next.

-- 
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/676a55b7-b94b-4987-b435-5ac6b39fb8f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.596.2 RC Testing started

[ogondza]

The RC testing is over, we are ready for the release.

--
oliver

-- 
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/0b13827e-b8f6-41a6-82f5-a2320b8e8ae7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.596.2 started

[ogondza]

Backporting is complete, we are ready for RC.

--
oliver

-- 
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/04e50d8b-1462-4f58-a0a2-061b4ef09a6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.596.1 RC Testing started

[ogondza]

Testing period is over, we are ready for the release.

--
oliver

-- 
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/b31eee62-f3b9-4655-a72b-a9a5b21e2c32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.596.1 started

[ogondza]

Backporting is over, we are ready for the RC.

--
oliver

-- 
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/deaad1de-c192-4a65-b8f6-a79a5568548e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Test Failure: "UpdateCenterTest.data:47->doData:73 » CertificateExpired NotAfter: Tue Jan 27"

[ogondza]

https://issues.jenkins-ci.org/browse/INFRA-219

--
oliver

-- 
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/63c2ab58-47f4-4212-83fe-558036dbf08a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Hot to set a particular buildwrapper using java/Groovy

[ogondza]

Call add() to buildWrappersList. See: 
https://github.com/jenkinsci/build-timeout-plugin/blob/master/src/test/java/hudson/plugins/build_timeout/BuildTimeoutWrapperIntegrationTest.java#L47

--
oliver

-- 
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/cfdeca01-0e39-4734-95c3-d99ad091d069%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ATH execution for 580.2

[ogondza]

I have merged and pushed jenkins-1.580.2 to stable-1.580. The pipeline 
should be back again.

--
oliver

-- 
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/55bd2a2b-510f-49ae-80d3-43b9d21ef8b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 1.580.2 RC Testing

[ogondza]

On Thursday, December 4, 2014 3:08:39 PM UTC+1, Mark Waite wrote:
>
> Is there a way to make that available as a docker image so that my startup 
> and recovery time from experimenting with the RC would be reduced?  Maybe 
> it is already available and I don't know where to look?
>

No, as far as I know. Though, we would like to hear how people (would like 
to) do the LTS RC testing. So we can make that easier and hopefully attract 
more testers.

--
oliver

-- 
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/d5c202c1-81f2-432f-8791-06e17c31f340%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for 1.580.1 started

[ogondza]

That would be great, Jesse, thanks! I will let you know as soon as 
backports are ready.

--
oliver

-- 
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: 1.565.3 LTS RC testing started

[ogondza]

Manual testing is over. Thank you guys for your help!

--
oliver 

-- 
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: 1.565.2 LTS RC testing started

[ogondza]

RC testing is over. No new regressions introduced. 


--

oliver 

-- 
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: 1.565.1 LTS RC testing started

[ogondza]

RC testing is over. No new regressions was discovered.

Thank you guys for testing it!

--

oliver 

-- 
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: Backporting for 1.565.1 has started

[ogondza]

Backporting is over with 25 fixes in 1.565.1. RC should be published later 
today.


Single candidate was rejected:: 
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+%221.565.1-rejected%22

--

oliver 

-- 
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: automatic workspace cleanup

[ogondza]

On Saturday, July 5, 2014 8:05:00 AM UTC+2, Shirhen Ince wrote:
>
> I want it to be automatic not that every user will need to chose to do 
> so... this plugin does not do it.
>

This is valid feature request for WS Cleanup plugin.

--
oliver 

-- 
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: Backporting for 1.554.3 started

[ogondza]

Backporting is over. We are ready for RC.


--

oliver

-- 
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: People using the LDAP plugin to connect to Active Directory

[ogondza]

Let's agree to disagree.

I'll note one more scenario used by several people: running ATH against old 
Jenkins versions. It used to work with 1.480 and a bunch of outdated 
plugins until very recently with minimal maintenance costs.


I am keen to see your scalability framework made public.

--

oliver

-- 
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: People using the LDAP plugin to connect to Active Directory

[ogondza]

I agree with Ulli here. Upgrade tests is something that would be great to 
have but turning ATH to what you describe does not make sense.

1) We _do_ want to know that version under test work on its own and not 
only if you upgrade your config from some earlier version.

2) If we start using config xml to configure/verify we are introducing 
another interface that can and will change. As we have to keep all our page 
objects there will be more breakage due to changes in SUT than before 
(changes in persistence does not affect ATH now).

3) What you suggest allows test creator to create test fixture using _some_ 
core/plugin version. Whole test suite will then inconsistently test if 
upgrade works from different version for every test. I expect more serious 
approach from upgrade tests.* Not to mention that such tests will be close 
to useless a year from now as it will be performing upgrades most users 
already performed.

4) Having one test failure for one change seem nice in theory but after a 
year and half of fixing selenium tests to reflect UI changes I am not 
really motivated to work against that goal.

* What I would like to make sure is users can upgrade from LTS to LTS-rc 
and from master to master-rc preserving the same functionality. We should 
use existing POs to setup fixture, then upgrade Jenkins/plugins and execute 
WHEN and THEN using newer version. This comes for free as we are 
maintaining page objects already, no one need to update XML fixtures 
regularly to cover upgrade most people will undergo soon and adding new use 
case like upgrading to last LTS release line from the previous one is just 
a matter of test parameterization.

-- 
oliver

-- 
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: RC testing for 1.554.2 started

[ogondza]

Rc testing period is over. No regressions was discovered.

We had a lot of people contributing to manual testing in this cycle. Thank 
all of you.

--

oliver

-- 
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: How the get the user that does the build?

[ogondza]

Hi,

See `Run.getCauses()`. You can extract user identity from 
UserCause|UserIdCause.

--

oliver

-- 
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: Backporting for 1.554.2 started

[ogondza]

On Wednesday, May 14, 2014 11:20:27 AM UTC+2, Stephen Connolly wrote:
>
>
>
> https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7
>
> But I also understand if this is too late in the day and we need to wait 
> for 1.554.3...
>

Yes, we will. Note the issue is not resolved.

-- 
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: Solidifying acceptance-test-harness API

[ogondza]

On Tuesday, May 13, 2014 12:49:54 PM UTC+2, Robert Sandell wrote:
>
> As long as the version number reflects API compatibility I don't see any 
> problems with not staying backwards compatible and no direct need for a 
> "stable" version.
>

This is a good compromise.

-- 
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: Backporting for 1.554.1 started

[ogondza]

See backported fixes: 
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+10172+AND+labels+%3D+%221.554.1-fixed%22

Tests are passing[1], acceptance test are in a good shape[2].

Thanks marco-miller for testing and backporting 
https://issues.jenkins-ci.org/browse/JENKINS-21579.

[1] https://jenkins.ci.cloudbees.com/job/core/job/jenkins_lts_branch/

[2] https://jenkins.ci.cloudbees.com/job/core/job/acceptance-test-harness/

-- 
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: much belated 1.532.3 RC posted

[ogondza]

All selenium tests that does not pass, are replaced with passing acceptance 
tests. Manual testing is also done. Thank you Mark. For me this release is 
good to go.

https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.532.x+RC+Testing

--

oliver

-- 
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.