How to restrict no of builder

[selva vignesh]

Hi Team,
I have written plugin that actually make a apicall to my internal product. 
Where I have to restrict number builder not being added more than 10.
Is this possible? if so, please let me know. It would be great, having 
sample code snippet.
Thanks in advance.

-- 
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/95a267da-b7b4-45b4-9953-129330797a96%40googlegroups.com.

Re: Adoption of FSTrigger plugin

[tiberius soanea]

Hi Tony,

Thanks for the quick response.
For fixing the issue i just updated the pom with the latest versions for 
the dependecies and added a dependency to the matrix project. I made no 
changes to the code.
Is this something you are already planning to do soon or should i submit a 
PR?

Best regards,
Tiberius

miercuri, 27 noiembrie 2019, 17:11:04 UTC+1, Tony Noble a scris:
>
> Hi Tiberius,
>
> I'm the maintainer of the FSTrigger plugin - apologies for the wiki page 
> not being up to date, I've recently taken all the xtrigger-related plugins 
> on and am still in the process of rationalising / updating.
>
> If there's a issue/fix with the plugin, please feel free to submit a PR 
> for the git project and I'll take a look and sort a release.
>
> Regards,
>
> Tony
>
> On Wed, Nov 27, 2019 at 4:05 PM tiberius soanea  > wrote:
>
>> Hello,
>>
>> I am working with Thales on Jenkins and its plugins.
>> I fixed a ticket regarding FSTrigger plugin that doesn't work correctly 
>> with Jenkins since the 2.107.2 version so i would like to adopt the plugin 
>> to be able to provide the updated version.
>>
>> Link to plugin: https://plugins.jenkins.io/fstrigger
>> GitHub username: TiberiusSoanea
>> Jenkins infrastructure account id: TiberiusSoanea
>>
>> Thank you,
>> Tiberius Soanea
>>
>> -- 
>> 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/eed5e799-3f44-4360-82f1-287fd275f034%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/9e28c423-c47f-47f4-95f8-15a9be02d358%40googlegroups.com.

Update on Blue Ocean Status from CloudBees

[Jeremy Hartley]

There has been some confusion for a while about the status of Blue Ocean. 
As the product manager for Jenkins at CloudBees I would like to provide an 
update on CloudBees point of view with regards to the status of Blue Ocean.


CloudBees Point of View

Jenkins is not going anywhere and it needs a modern, up-to-date, UX for the 
next ten years of the projects’ life. CloudBees is investing in 
transformatively improving the Jenkins UI/UX. We have started a project to 
revamp the Jenkins User Experience and launched a new User Experience 
Special Interest Group (SIG) to involve the open source community in this 
process. 

CloudBees does not believe that Blue Ocean is the most appropriate vehicle 
with which to make these changes. As such, we will focus on alternative 
approaches and we will not be working on any major new functionality within 
Blue Ocean.

As we implement improvements to the Jenkins UI and UX, the Blue Ocean 
pipeline experience will remain relevant to users for quite some time. The 
work on the new UX will be prioritised and due to the relative modernity of 
the Blue Ocean pipeline UX, it is not a candidate to be replaced early on 
in the process. During this time we will selectively address significant 
security issues and functional defects.

As a part of the Jenkins OSS project, we encourage community contributions 
that resolve functional issues and add small enhancements to Blue Ocean. We 
intend to merge worthy community PRs and release these at a regular 
cadence. 


Any questions are of course welcome


Thanks 


Jeremy Hartley

-- 
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/3647f3af-bb06-42c9-95f2-65fce2db3d1e%40googlegroups.com.

Re: ANN: Proposal for a new User Experience SIG

[Jeremy Hartley]

Everybody is welcome to join. I will announce the next meeting date 
tomorrow and be distributing the minutes and the video recording. We are 
planning to use the Jenkins User Experience mailing list as the main place 
to talk about this: https://groups.google.com/forum/#!forum/jenkinsci-ux 

On Tuesday, November 26, 2019 at 7:11:32 PM UTC+1, Amit Dar wrote:
>
> Hi,
>
> I'd like to join the user experience group of jenkins. 
>
> Thanks. 
>
> On Tue, Nov 26, 2019, 14:20 Baptiste Mathus > 
> wrote:
>
>> Hi folks,
>>
>> So as a reminder, the first "User eXperience Special Interest Group" (aka 
>> UX SIG) meeting is planned at 16:00 UTC+1 today.
>>
>> Note: if you cannot attend, but would like to be involved, that is 
>> possible and more than welcome. If so, please just mention this (in private 
>> to me if preferred for now), and we'll make sure to include you in next 
>> steps.
>>
>> Thanks!
>>
>> Le mar. 19 nov. 2019 à 19:40, Parker Ennis > > a écrit :
>>
>>> FWIW, definitely a +1 from me.
>>>
>>> Best,
>>>
>>> On Mon, Nov 18, 2019 at 6:29 AM Jeremy Hartley >> > wrote:
>>>
 In keeping with JEP-4 
 , I'm posting to 
 the developer mailing list my plan to create and lead the Jenkins User 
 Experience  special interest group.

 I'll submit a pull request to jenkins.io with the structure described 
 in JEP-4 .

 The first UX special interest group meeting is scheduled for Tuesday, 
 November 26th, 2019 at 16:00 UTC. The proposed meeting agenda is at 
 
 https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit?usp=sharing
  
 . We'll be using Zoom to host the meetings and record them 
 https://cloudbees.zoom.us/j/621503564. The videos will be published to 
 YouTube.

 *Draft mission statement*:

 The User Experience SIG focuses on improving Jenkins user interface and 
 user experience. The SIG will seek feedback from the community on the 
 current UI and UX and new designs proposed by SIG members and others and 
 will discuss alternatives, identify compromises, and test implementations 
 to improve the Jenkins UI / UX.

 Thanks,

 Jeremy Hartley

 -- 
 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/74080e7c-3665-4464-8e5d-580d82aaab41%40googlegroups.com
  
 
 .

>>>
>>>
>>> -- 
>>>
>>> *Parker Ennis*
>>>
>>> *Product Marketing Manager*
>>>
>>> [image: CloudBees-Logo.png]
>>>
>>>
>>> M: (803) 386-7562
>>> E: ren...@cloudbees.com 
>>> Skype: parker.cb
>>> Twitter: @Parker_CB 
>>>
>>>
>>> -- 
>>> 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/CAJ2%2BM_AjZnFed6r8QL8UMBbZZFKT7aMPRDjQH%3DOTqZF0bJUY9g%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 jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5HKP%2BWdidEH%3De%3DfNgEndGKGHLuuorbBQs10NoEnLC2Fg%40mail.gmail.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2288ddad-bf8c-4cfa-927e-e5487b8fd479%40googlegroups.com.

Re: Adoption of FSTrigger plugin

[Tony Noble]

Hi Tiberius,

I'm the maintainer of the FSTrigger plugin - apologies for the wiki page
not being up to date, I've recently taken all the xtrigger-related plugins
on and am still in the process of rationalising / updating.

If there's a issue/fix with the plugin, please feel free to submit a PR for
the git project and I'll take a look and sort a release.

Regards,

Tony

On Wed, Nov 27, 2019 at 4:05 PM tiberius soanea 
wrote:

> Hello,
>
> I am working with Thales on Jenkins and its plugins.
> I fixed a ticket regarding FSTrigger plugin that doesn't work correctly
> with Jenkins since the 2.107.2 version so i would like to adopt the plugin
> to be able to provide the updated version.
>
> Link to plugin: https://plugins.jenkins.io/fstrigger
> GitHub username: TiberiusSoanea
> Jenkins infrastructure account id: TiberiusSoanea
>
> Thank you,
> Tiberius Soanea
>
> --
> 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/eed5e799-3f44-4360-82f1-287fd275f034%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/CAEWqh9GM-%2BP08StaEheDgQauKFdYbmpgY_eSBsJ5Md02%3DOcBLg%40mail.gmail.com.

Adoption of FSTrigger plugin

[tiberius soanea]

Hello,

I am working with Thales on Jenkins and its plugins.
I fixed a ticket regarding FSTrigger plugin that doesn't work correctly 
with Jenkins since the 2.107.2 version so i would like to adopt the plugin 
to be able to provide the updated version.

Link to plugin: https://plugins.jenkins.io/fstrigger
GitHub username: TiberiusSoanea
Jenkins infrastructure account id: TiberiusSoanea

Thank you,
Tiberius Soanea

-- 
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/eed5e799-3f44-4360-82f1-287fd275f034%40googlegroups.com.

Do not use the new plugin-pom with the BOM profile.

[James Nord]

Hi all,

There are issues using the jenkins-bom for dependency versioning in the 
plugin pom.

Whilst it works for a single plugin, any plugins that are deployed using 
this also force any plugins that depend on them to enable the profile (as 
it can not be enabled per module).  likewise the other way around is 
probably very similar.

Adding dependecnyManagement based on a profile was probably not a great 
idea in hindsight :-(

Whilst I do not thing the change should be reverted, I don;t think people 
should use it unless they think very carefully.

possible solutions are 
1) flatten the pom
2) split the parent into bom/no bom

I'm busy with a release cycle right now, but plan to try again later this 
week.

/James

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0598e832-e486-4058-8138-51bf08739afd%40googlegroups.com.

Re: Possible LTS regression in commons-compress

[James Nord]

I have tracked the cause of the issue to an optimisation we had for the old 
Hudson code to not flush all the time to prevent lots of small chunks being 
flushed (as the old implementation flushed for each block (512 bytes)) 

If I disable that then the code works with 1.15 and above.  I have not 
looked into the code to see if commons compress also has issues with 
flushing, but I doubt any other plugins will be doing any similar 
optimisation.

/James




On Wednesday, November 27, 2019 at 8:23:47 AM UTC, Baptiste Mathus wrote:
>
> Sounds to me we should git bisect commons-compress between 1.14 and 1.15 
> usage, to nail and possibly confirm Björn's hypothesis?
>
> On Wed, Nov 27, 2019 at 8:36 AM 'Björn Pedersen' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote:
>
>> Hi,
>>
>> I have 2 changes that seem candiates:
>> 1) 1.15 enforces blocklen=512 which is different from the old default and 
>> raises an error if anything else is specified
>>  (
>> https://commons.apache.org/proper/commons-compress/javadocs/api-1.19/index.html
>> )
>> 2) 1.16 renamed the preserveAbsolutePath to TarArchiveEntry 
>> 
>> (String 
>> 
>>  name, 
>> boolean preserveAbsolutePath)
>> (less likely that is the cause).
>>
>> Björn
>>
>> Am Mittwoch, 27. November 2019 01:03:40 UTC+1 schrieb James Nord:
>>>
>>> Hi all,
>>>
>>> just a quick note, I *think *I have discovered a regression in 2.204 
>>> upcoming LTS due to commons-compress library bump.
>>>
>>> One of our plugins was using TarInputStream 
>>> for
>>>  
>>> 2.190 but this is now restricted.
>>> so without bumping core we moved the code over to use the 
>>> commons-compress version (and all is happy).
>>>
>>> However when bumping the Jenkins version to 2.204 which picks up the 
>>> newer compress we have lots of unit test failures due to what seems like 
>>> (at very first glance as I just narrowed it down and its late!) empty tar 
>>> files (when they should not be empty)
>>>
>>> as a (quick and dirty) test I made the commons-compress version 
>>> configurable and it does seem like this is the issue
>>>
>>> mvn test -Dtest=TheTest -Djenkins.version=2.204 -DcompressVersion=1.19 
>>> -Denforcer.skip *fails*
>>> mvn test -Dtest=TheTest -Djenkins.version=2.204 -DcompressVersion=1.10 
>>> -Denforcer.skip passes
>>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.10 
>>> -Denforcer.skip passes
>>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.19 
>>> -Denforcer.skip 
>>> *fails*
>>> doing some more bisection
>>>
>>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.15 
>>> -Denforcer.skip 
>>> *fails*mvn test -Dtest=TheTest -Djenkins.version=2.190.3 
>>> -DcompressVersion=1.13 -Denforcer.skip passes
>>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.14 
>>> -Denforcer.skip passes
>>>
>>>
>>> I don't yet know what is causing this (but it does appear to be 
>>> something in commons-compress 1.15 and I will investigate that.  (
>>> changelog 
>>> 
>>> )
>>>
>>> But this seems very scary to me (and I am surprised there has not been 
>>> some reports in the weeklies of archives etc not working correctly).  Also 
>>> very weired as 1.15 has been released for a good amount of time.
>>>
>>> Will continue the investigation tomorrow but if this rings a bell with 
>>> anyone in any reported Jiras it would be good to correlate.
>>>
>>> /James
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkin...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/8b3e8989-4f34-4b1d-a285-036837dc6bd1%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/6259ccf6-f5de-469e-a7db-18ff7dd52651%40googlegroups.com.

have trouble resetting password on https://accounts.jenkins.io/passwordReset

[Ted Xiao]

I tried to reset my password for user fengxx (used on 
https://issues.jenkins-ci.org/), but no email received. I double checked 
spam folder but no luck.
there is no support contact info on 
https://accounts.jenkins.io/passwordReset, any Jenkins infra ops team 
member can help?

-- 
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/90d934a3-8bf2-4669-b0a8-4a900f82fd15%40googlegroups.com.

Re: Possible LTS regression in commons-compress

[Baptiste Mathus]

Sounds to me we should git bisect commons-compress between 1.14 and 1.15
usage, to nail and possibly confirm Björn's hypothesis?

On Wed, Nov 27, 2019 at 8:36 AM 'Björn Pedersen' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi,
>
> I have 2 changes that seem candiates:
> 1) 1.15 enforces blocklen=512 which is different from the old default and
> raises an error if anything else is specified
>  (
> https://commons.apache.org/proper/commons-compress/javadocs/api-1.19/index.html
> )
> 2) 1.16 renamed the preserveAbsolutePath to TarArchiveEntry
> 
> (String
> 
>  name,
> boolean preserveAbsolutePath)
> (less likely that is the cause).
>
> Björn
>
> Am Mittwoch, 27. November 2019 01:03:40 UTC+1 schrieb James Nord:
>>
>> Hi all,
>>
>> just a quick note, I *think *I have discovered a regression in 2.204
>> upcoming LTS due to commons-compress library bump.
>>
>> One of our plugins was using TarInputStream
>> for
>> 2.190 but this is now restricted.
>> so without bumping core we moved the code over to use the
>> commons-compress version (and all is happy).
>>
>> However when bumping the Jenkins version to 2.204 which picks up the
>> newer compress we have lots of unit test failures due to what seems like
>> (at very first glance as I just narrowed it down and its late!) empty tar
>> files (when they should not be empty)
>>
>> as a (quick and dirty) test I made the commons-compress version
>> configurable and it does seem like this is the issue
>>
>> mvn test -Dtest=TheTest -Djenkins.version=2.204 -DcompressVersion=1.19
>> -Denforcer.skip *fails*
>> mvn test -Dtest=TheTest -Djenkins.version=2.204 -DcompressVersion=1.10
>> -Denforcer.skip passes
>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.10
>> -Denforcer.skip passes
>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.19
>> -Denforcer.skip
>> *fails*
>> doing some more bisection
>>
>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.15
>> -Denforcer.skip
>> *fails*mvn test -Dtest=TheTest -Djenkins.version=2.190.3
>> -DcompressVersion=1.13 -Denforcer.skip passes
>> mvn test -Dtest=TheTest -Djenkins.version=2.190.3 -DcompressVersion=1.14
>> -Denforcer.skip passes
>>
>>
>> I don't yet know what is causing this (but it does appear to be something
>> in commons-compress 1.15 and I will investigate that.  (changelog
>> 
>> )
>>
>> But this seems very scary to me (and I am surprised there has not been
>> some reports in the weeklies of archives etc not working correctly).  Also
>> very weired as 1.15 has been released for a good amount of time.
>>
>> Will continue the investigation tomorrow but if this rings a bell with
>> anyone in any reported Jiras it would be good to correlate.
>>
>> /James
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/8b3e8989-4f34-4b1d-a285-036837dc6bd1%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/CAPyTVp0pRuigKbyCNqW%3DJPdSTE7zdxMLEMHpPdpe9t2L3Z8k_w%40mail.gmail.com.