Re: Plugins using removed Guava APIs

2021-08-10 Thread James Nord 
Thanks Basil,

The operations center ones are released in lock step with a new LTS 
version, so I wouldn't worry too much about regressions there.
We have internal tickets to track all the work (we had previously focused 
on the OSS part as we knew it would take longer due to not being 
maintainers) the internal ones should all be addressed by the time the next 
(not the one in progress) LTS baseline is selected.

Regards

/James

On Sunday, 8 August 2021 at 09:04:20 UTC+1 m...@basilcrow.com wrote:

> Eight CloudBees proprietary plugins appear to require preparation for
> the Guava upgrade, at least in the latest released versions. I have
> included my notes below. It would be helpful if a CloudBees employee
> could prepare these plugins for the Guava upgrade and release new
> versions.
>
> ---
>
> CloudBees RBAC Auto Configurer 1.1.9 uses
> com.google.common.base.CharMatcher#INVISIBLE.
>
> CloudBees Cloud Foundry BOSH CLI 2.2 uses
> com.google.common.base.Objects#toStringHelper.
>
> Elasticsearch Reporter Feeder 2.263.0.1 uses the two-argument
> com.google.common.util.concurrent.Futures#addCallback(ListenableFuture
> future, FutureCallback callback) and the two-argument
> com.google.common.util.concurrent.Futures#transform(ListenableFuture
> input, AsyncFunction function).
>
> Elasticsearch Reporter Reporter 2.263.0.1 uses the two-argument
> com.google.common.util.concurrent.Futures#addCallback(ListenableFuture
> future, FutureCallback callback).
>
> Operations Center Context 2.289.0.6 uses the four-argument
> com.google.common.util.concurrent.TimeLimiter#callWithTimeout(Callable
> callable, long timeoutDuration, TimeUnit timeoutUnit, boolean
> interruptible).
>
> Operations Center Monitoring 2.289.0.3 uses the two-argument
> com.google.common.util.concurrent.Futures#transform(ListenableFuture
> input, AsyncFunction function).
>
> Operations Center Server 2.289.0.7 uses
> com.google.common.util.concurrent.MoreExecutors#sameThreadExecutor.
> You might also want to take a look at its use of
> com.google.common.collect.MapMaker and switch to Caffeine.
>
> Operations Center Single Sign-On 2.289.0.3 uses the four-argument
> com.google.common.util.concurrent.TimeLimiter#callWithTimeout(Callable
> callable, long timeoutDuration, TimeUnit timeoutUnit, boolean
> interruptible).
>

-- 
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/5dcf490b-6035-43e5-a577-cc3e91e285ben%40googlegroups.com.

Re: Choosing Jenkins September LTS release baseline

2021-08-10 Thread Beatriz Munoz 
Morning!

I created https://github.com/jenkinsci/jenkins/pull/5659 
 with the possible candidates 
for tomorrow release candidate LTS. These candidates are:

-  https://issues.jenkins-ci.org/browse/JENKINS-65923  
(https://github.com/jenkinsci/jenkins/pull/5634)
-  https://issues.jenkins.io/browse/JENKINS-66177 
(https://github.com/jenkinsci/jenkins/pull/5628)
-  https://issues.jenkins.io/browse/JENKINS-66094 
(https://github.com/jenkinsci/jenkins/pull/5613)
Thanks!!

> El 3 ago 2021, a las 9:44, Tim Jacomb  escribió:
> 
> Hello
> 
> This is sorted now, thanks for the report Bea
> 
> On Tue, 3 Aug 2021 at 08:21, Beatriz Munoz  > wrote:
> Morning!
> 
> I created https://github.com/bmunozm/jenkins/tree/towards-2.302 
>  but I cannot 
> push it to https://github.com/jenkinsci/jenkins 
> . I need someone with rights that 
> replace https://github.com/jenkinsci/jenkins/tree/stable-2.302 
>  by 
> https://github.com/bmunozm/jenkins/tree/towards-2.302 
>  using the name 
> `stable-2.302` for the branch
> 
> Thank you so much in advance.
> 
>> El 2 ago 2021, a las 12:50, Daniel Beck > > escribió:
>> 
>> 
>> 
>> On Mon, Aug 2, 2021 at 12:35 PM Beatriz Munoz > > wrote:
>> Hi all
>> 
>> Looking into next LTS I released something is really strange in branch 
>> `stable-2.302`. If you compare the branch and the tag `jenkins-2.302` there 
>> are more than 240 files with changes. As the backports are not done yet, I 
>> guess the difference should me minimal.
>> 
>> https://github.com/jenkinsci/jenkins/compare/jenkins-2.302..stable-2.302 
>> 
>> 
>> Looking at https://github.com/jenkinsci/jenkins/commits/stable-2.302 
>>  it seems the 
>> branch is based on a weekly intermediate state around 2.298/2.299 (~June 21) 
>> + some stuff related to PR#5583, rather than 2.302. The branch should be 
>> deleted and recreated. Besides being the wrong baseline, security fixes from 
>> 2.300 would be missing as well.
>> 
>> 
>> -- 
>> 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/CAMo7Pt%2BLx0OREhYS5%2BLB7mueyKRN5MDqiZuHFTBZ5ESd7cMgGQ%40mail.gmail.com
>>  
>> .
> 
> Beatriz Muñoz Manso
> Sr Software 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 jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/5A41AE32-6F20-4C81-A7F1-59AF89548DA6%40cloudbees.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/CAH-3Bid9%3DMKNmpH9yX4qA%3DqxxBYiOJgJy_NDimnwPjUCcD6OuQ%40mail.gmail.com
>  
> .

Beatriz Muñoz Manso
Sr Software 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/17D03184-C4C1-4725-9619-13D295C49ACF%40cloudbees.com.

Re: Stapler IntelliJ Plugin JetBrains Marketplace listing

2021-08-10 Thread Tim Jacomb 
It was already accepted when I logged in, probably done a long time ago

On Tue, 10 Aug 2021 at 02:47, Denys Digtiar  wrote:

> Tim,
> Does it mean that you have accepted the Developer Agreement? Is it OK?
>
> On Tuesday, 3 August 2021 at 06:28:32 UTC+10 timja...@gmail.com wrote:
>
>> Looks like it’s been released now
>>
>> https://plugins.jetbrains.com/plugin/1885-stapler-framework-support/versions
>>
>> On Fri, 30 Jul 2021 at 06:57, Denys Digtiar 
>> wrote:
>>
>>> Thank you Kohsuke! The new release has not completed a JetBrains
>>> approval yet but it is already a part of the Jenkins project on JetBrains
>>> Marketplace.
>>> Now JetBrains requires legal agreement to
>>> https://plugins.jetbrains.com/legal/developer-agreement and
>>> https://plugins.jetbrains.com/legal/approval-guidelines to be able to
>>> manage the plugin.
>>>
>>> On Monday, July 26, 2021 at 6:20:59 PM UTC+10 timja...@gmail.com wrote:
>>>
 cc Kohsuke

 On Fri, 28 May 2021 at 22:37, Oleg Nenashev 
 wrote:

> FTR the plugin was moved to the jenkinsci GitHub organization:
> https://github.com/jenkinsci/idea-stapler-plugin
> Denys will be an admin there once he accepts the invitation to the
> GitHub org
>
> On Monday, May 10, 2021 at 6:33:22 PM UTC+2 Oleg Nenashev wrote:
>
>> FTR I started https://groups.google.com/g/jenkinsci-dev/c/1T3yDHl1nEQ
>> . I have a partially-completed proposal for Stapler in my drafts, so I 
>> went
>> ahead and started the discussion
>>
>> On Monday, May 10, 2021 at 2:16:38 PM UTC+2 Jesse Glick wrote:
>>
>>> On Fri, May 7, 2021 at 7:13 PM Oleg Nenashev 
>>> wrote:
>>>
 should we go ahead and move the repository to the jenkinsci org?

>>>
>>> Fine with me. We should probably move `stapler/stapler` itself
>>> (INFRA-2908); we have already started publishing to the Jenkins 
>>> Artifactory
>>> rather than OSSRH.
>>>
>> --
>
 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/9e8ecbc2-adb2-4a65-bd5d-ee2b53d7b384n%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-de...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/333be135-5f7e-496a-a411-69866b1049d1n%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/75d2210b-65f9-4971-8286-e4e17f3dcc59n%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/CAH-3BifCucfvgjWH-weTiEoW-%3D7M%2BZz1kEJJxEw8Omr5XEuy%3Dw%40mail.gmail.com.