How does a stapler work with select tag

[Nikhil Bhoski]

i have below entry in config.jelly for BuildWrapper class 

  

  

  ${installation.name} 
   
   
  

 



I am trying to validate the dropdown using doCehck method in the same 
descriptor with below signature

public FormValidation doCheckMRoot(@QueryParameter final String mRoot) {
if(mRoot==null) {
return FormValidation.error("No Root selected");
}else {
return FormValidation.warning("root is set");
}
}


doCheck method does not get executed is there a different way that 
validation for  tag works ? 


-- 
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/13f8f0a5-85e2-475c-a053-75b739ae4ea7%40googlegroups.com.

Re: Finding relevant jelly for branch-api

[Raihaan Shouhell]

Oh i was thinking because ViewImpl in branch-api calls getItems in 
getDisplayName since view has to call get items it can just check the size 
from there eliminating the need to call getItems twice or three times. 
Only problem is that view has to be reworked to incorporate this. Might not 
be worth the trouble.

On Wednesday, 22 January 2020 23:29:45 UTC+8, Jesse Glick wrote:
>
> On Wed, Jan 22, 2020 at 9:48 AM Raihaan Shouhell 
> > wrote: 
> > when core calls getItems() in jelly 
> >  you can get the size and therefore skip the need for permissions checks 
>
> `getItems` would still need to run permission checks, regardless of 
> where it is implemented. 
>

-- 
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/a69a2a45-8e98-43e7-b82f-ae12a9c5cb97%40googlegroups.com.

Re: Jenkins comic project: Call for brainstorming volunteers

[Alyssa Tong]

+advocacy and outreach sig.

Just a reminder that we will be meeting tomorrow via the Advocacy and
Outreach Sig channel to brainstorm the voice and personality for the butler
in the Jenkins comic.

DATE: Thursday, 23 January 2020

TIME: 5pm CET | 8am PT | 11am ET
Call in: Join Zoom Meeting https://zoom.us/j/324404020

https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit?usp=sharing

Thank you,
alyssa




On Thu, Jan 16, 2020 at 3:34 PM Alyssa Tong  wrote:

> Thanks Arnaud for sharing ..too funny. I love the idea of members as
> "proud to be a butler"
>
> On Tue, Jan 14, 2020 at 10:50 PM Arnaud Héritier 
> wrote:
>
>> Hi
>>
>>   I won’t be able to attend but related to this topic I wanted to share
>> this experiment done by Oleg with my head already Created by commit strip:
>>
>> https://twitter.com/oleg_nenashev/status/1214694618811514881?s=21
>>
>>   Couldn’t we take the opportunity to have something similar for visible
>> members of the community and create a communication around “proud to be
>> butler” or something like this ?
>>
>> Cheers
>>
>> Le mer. 15 janv. 2020 à 02:23, Alyssa Tong  a
>> écrit :
>>
>>> Hello,
>>>
>>> We are looking to do a fun project with Jenkins.  We are looking to do
>>> Jenkins comic with the help and talent of CommitStrip. Thank you to
>>> CloudBees for sponsoring this project. On Thursday, 23 Jan we will be
>>> holding a brainstorming session with CommitStrip to discuss the tone of
>>> voice for the butler, and what ever else CommitStrip may need to give life
>>> to the butler.  If you'd like to be involved in this process, pls add your
>>> name and email address to this gdoc
>>> 
>>> so I may send you call-in info once we are close to 23 Jan.
>>>
>>> thank you,
>>> alyssa
>>>
>>> --
>>> 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/CAC9wNaybYttkcTYo%2BjWhi-4cUpjnCEgXWU4cW6ZvnWjW3A-%2B1w%40mail.gmail.com
>>> 
>>> .
>>>
>> --
>> -
>> Arnaud Héritier
>> http://aheritier.net
>> Mail/GTalk: aheritier AT gmail DOT com
>> Twitter/Skype : aheritier
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8mrkQBNkcwvLBbG8pvM%2BHkGxccjL-5Hg%3DUiEo1r6ghaA%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/CAC9wNayPQmW64kH0EO-jGNjWTHgR4p6eXabTpK7tbDbYBDBaWw%40mail.gmail.com.

Re: Support List on jenkins.io?

[Marky Jackson]

I like the idea of waiting for the advocacy meeting but that doesn’t mean we 
can’t get started on a WIP pr 

> On Jan 22, 2020, at 9:21 PM, 'Gavin Mogan' via Jenkins Developers 
>  wrote:
> 

-- 
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/109FCAAB-2CF4-4225-B89F-0E3BEEC87B03%40gmail.com.

Re: Support List on jenkins.io?

['Gavin Mogan' via Jenkins Developers]

> I like the idea of pr’s. Are you also saying that the list is available
for any company to pr?

Yep, Literally "community managed list of commercial support", just like
the wiki

> I would be good with a list where every company can pr but how does a
company fleet validated. I see room for companies or supposed companies to
abuse the process and ultimately the project.

as someone (i think mark) has been saying on gitter. We have a super open
trust model. I really like that. if it does get abused, its worth
re-visiting, but for now I think its worth doing

But it can absolutely wait for the advocacy meeting

On Wed, Jan 22, 2020 at 9:18 PM Marky Jackson 
wrote:

> I like the idea of pr’s. Are you also saying that the list is available
> for any company to pr?
> I also think with the move to the CDF it will operate much like the CNCF
> and have certified service providers.
> I would be good with a list where every company can pr but how does a
> company fleet validated. I see room for companies or supposed companies to
> abuse the process and ultimately the project.
>
> On Jan 22, 2020, at 9:06 PM, Richard Bywater  wrote:
>
> 
> This seems to be along the lines of what Oleg raised mid-last year (
> https://groups.google.com/d/msg/jenkinsci-dev/-1cDktjaI6A/FRT21zTqDQAJ ).
>
> I think that there does need to be a very clear steer that the project
> itself runs on a voluntary basis and perhaps have a list of
> commercial support available but I think rather than having the list as
> curated as such it should be done in a way that commercial companies can
> list their details (and, as I said in the previous email, make sure that
> its clearly said that the Jenkins project doesn't endorse any of them).
>
> I'm guessing it should be fairly simple to create a page on jenkins.io
> and have companies provide PRs to have their company included (and, at that
> point, whomever approves the PR needs a bit of guidance about what
> information should/shouldn't be allowed to be provided by the company).
>
> Richard.
>
> On Thu, 23 Jan 2020 at 17:32, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Hey Everyone,
>>
>> As one of the few that regularly hang out in the users channels (#jenkins
>> on irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt
>> about a central location where we can point users to for commercial support.
>>
>> There's definitely some users who come in, ask straight forward
>> questions, and usually pretty easy to fix ("check what version of java",
>> "your using the wrong type of pipeline, see examples", etc) but sometimes
>> there's definitely issues that last weeks, and its fundamental
>> understanding of what needs to be done ("How do I CI?", "Whats wrong with
>> this >
>> So how does everyone feel of a page on jenkins.io where we can go:
>> "Looking for more support than the volunteers can offer? Looking to share
>> sensitive info? Need help in a short amount of time? Feel free to contact
>> any of these professional services"
>>
>> I'm certainly conflicted at maintaining the curated list, or playing
>> favoritism at all, but its also frustrating when after a while of bad
>> communication you want to walk away, but they ping you, or pm you asking
>> for more help.
>>
>> Gavin
>>
>> --
>> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%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/CAAy0hwcPo7jFUO3OzL3MOo0hxBemACb9SVgR45BhJwQ0GFnLSQ%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/5DEDA5FA-715F-4BFE-9D1B-2CCB9CE6925F%40gmail.com
> 
> .
>

-- 
You received this 

Re: Support List on jenkins.io?

[Marky Jackson]

I like the idea of pr’s. Are you also saying that the list is available for any 
company to pr? 
I also think with the move to the CDF it will operate much like the CNCF and 
have certified service providers.
I would be good with a list where every company can pr but how does a company 
fleet validated. I see room for companies or supposed companies to abuse the 
process and ultimately the project.

> On Jan 22, 2020, at 9:06 PM, Richard Bywater  wrote:
> 
> 
> This seems to be along the lines of what Oleg raised mid-last year ( 
> https://groups.google.com/d/msg/jenkinsci-dev/-1cDktjaI6A/FRT21zTqDQAJ ). 
> 
> I think that there does need to be a very clear steer that the project itself 
> runs on a voluntary basis and perhaps have a list of commercial support 
> available but I think rather than having the list as curated as such it 
> should be done in a way that commercial companies can list their details 
> (and, as I said in the previous email, make sure that its clearly said that 
> the Jenkins project doesn't endorse any of them).
> 
> I'm guessing it should be fairly simple to create a page on jenkins.io and 
> have companies provide PRs to have their company included (and, at that 
> point, whomever approves the PR needs a bit of guidance about what 
> information should/shouldn't be allowed to be provided by the company).
> 
> Richard.
> 
>> On Thu, 23 Jan 2020 at 17:32, 'Gavin Mogan' via Jenkins Developers 
>>  wrote:
>> Hey Everyone,
>> 
>> As one of the few that regularly hang out in the users channels (#jenkins on 
>> irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt 
>> about a central location where we can point users to for commercial support.
>> 
>> There's definitely some users who come in, ask straight forward questions, 
>> and usually pretty easy to fix ("check what version of java", "your using 
>> the wrong type of pipeline, see examples", etc) but sometimes there's 
>> definitely issues that last weeks, and its fundamental understanding of what 
>> needs to be done ("How do I CI?", "Whats wrong with this > stacktrace and no pipeline", etc)
>> 
>> So how does everyone feel of a page on jenkins.io where we can go:
>> "Looking for more support than the volunteers can offer? Looking to share 
>> sensitive info? Need help in a short amount of time? Feel free to contact 
>> any of these professional services"
>> 
>> I'm certainly conflicted at maintaining the curated list, or playing 
>> favoritism at all, but its also frustrating when after a while of bad 
>> communication you want to walk away, but they ping you, or pm you asking for 
>> more help.
>> 
>> Gavin
>> 
>> -- 
>> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%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/CAAy0hwcPo7jFUO3OzL3MOo0hxBemACb9SVgR45BhJwQ0GFnLSQ%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/5DEDA5FA-715F-4BFE-9D1B-2CCB9CE6925F%40gmail.com.

Re: Support List on jenkins.io?

['Gavin Mogan' via Jenkins Developers]

Yea I don't think we'd want to curate it, but allow it to be PRs to manage.
Like the awesome lists.

> The wiki has https://wiki.jenkins.io/display/JENKINS/Commercial+Support .
Wiki is read only now, so we need a place on jenkins.io for that type of
information.

Yea that would be what I was thinking. Just a list, no promises.

I really love the powerdns model though its a little extreme

> Users of PowerDNS open-source software can ask questions on our public
mailing lists, where operators must supply full details of their problem,
including actual IP addresses and real domain names that are relevant to
the problem
.


We've had a number of people post pipelines with missing brackets, or
different variable names. We point out that the problem is there, they
mention its a snippet. So error message line numbers don't line up, etc.

But yea, +1 for the discussion, I just want to highlight it as an issue.


On Wed, Jan 22, 2020 at 9:06 PM Richard Bywater  wrote:

> This seems to be along the lines of what Oleg raised mid-last year (
> https://groups.google.com/d/msg/jenkinsci-dev/-1cDktjaI6A/FRT21zTqDQAJ ).
>
> I think that there does need to be a very clear steer that the project
> itself runs on a voluntary basis and perhaps have a list of
> commercial support available but I think rather than having the list as
> curated as such it should be done in a way that commercial companies can
> list their details (and, as I said in the previous email, make sure that
> its clearly said that the Jenkins project doesn't endorse any of them).
>
> I'm guessing it should be fairly simple to create a page on jenkins.io
> and have companies provide PRs to have their company included (and, at that
> point, whomever approves the PR needs a bit of guidance about what
> information should/shouldn't be allowed to be provided by the company).
>
> Richard.
>
> On Thu, 23 Jan 2020 at 17:32, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Hey Everyone,
>>
>> As one of the few that regularly hang out in the users channels (#jenkins
>> on irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt
>> about a central location where we can point users to for commercial support.
>>
>> There's definitely some users who come in, ask straight forward
>> questions, and usually pretty easy to fix ("check what version of java",
>> "your using the wrong type of pipeline, see examples", etc) but sometimes
>> there's definitely issues that last weeks, and its fundamental
>> understanding of what needs to be done ("How do I CI?", "Whats wrong with
>> this >
>> So how does everyone feel of a page on jenkins.io where we can go:
>> "Looking for more support than the volunteers can offer? Looking to share
>> sensitive info? Need help in a short amount of time? Feel free to contact
>> any of these professional services"
>>
>> I'm certainly conflicted at maintaining the curated list, or playing
>> favoritism at all, but its also frustrating when after a while of bad
>> communication you want to walk away, but they ping you, or pm you asking
>> for more help.
>>
>> Gavin
>>
>> --
>> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%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/CAAy0hwcPo7jFUO3OzL3MOo0hxBemACb9SVgR45BhJwQ0GFnLSQ%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/CAG%3D_Dusn3mDUFv19ny0HPHN3Z%2BO%2BfZXYA3Ut6WNdnJjEDmWt4Q%40mail.gmail.com.

Re: Support List on jenkins.io?

[Richard Bywater]

This seems to be along the lines of what Oleg raised mid-last year (
https://groups.google.com/d/msg/jenkinsci-dev/-1cDktjaI6A/FRT21zTqDQAJ ).

I think that there does need to be a very clear steer that the project
itself runs on a voluntary basis and perhaps have a list of
commercial support available but I think rather than having the list as
curated as such it should be done in a way that commercial companies can
list their details (and, as I said in the previous email, make sure that
its clearly said that the Jenkins project doesn't endorse any of them).

I'm guessing it should be fairly simple to create a page on jenkins.io and
have companies provide PRs to have their company included (and, at that
point, whomever approves the PR needs a bit of guidance about what
information should/shouldn't be allowed to be provided by the company).

Richard.

On Thu, 23 Jan 2020 at 17:32, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hey Everyone,
>
> As one of the few that regularly hang out in the users channels (#jenkins
> on irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt
> about a central location where we can point users to for commercial support.
>
> There's definitely some users who come in, ask straight forward questions,
> and usually pretty easy to fix ("check what version of java", "your using
> the wrong type of pipeline, see examples", etc) but sometimes there's
> definitely issues that last weeks, and its fundamental understanding of
> what needs to be done ("How do I CI?", "Whats wrong with this  pages of stacktrace and no pipeline", etc)
>
> So how does everyone feel of a page on jenkins.io where we can go:
> "Looking for more support than the volunteers can offer? Looking to share
> sensitive info? Need help in a short amount of time? Feel free to contact
> any of these professional services"
>
> I'm certainly conflicted at maintaining the curated list, or playing
> favoritism at all, but its also frustrating when after a while of bad
> communication you want to walk away, but they ping you, or pm you asking
> for more help.
>
> Gavin
>
> --
> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%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/CAAy0hwcPo7jFUO3OzL3MOo0hxBemACb9SVgR45BhJwQ0GFnLSQ%40mail.gmail.com.

Re: Support List on jenkins.io?

[Marky Jackson]

Gavin, 
I certainly empathize with what you are saying about that and agree on a need 
for a better way to help.
I am not sure a good option is available. 
Adding support like reference runs the risk of a conflict with how that list is 
curated, as you mentioned. It also semi takes the open-source ethos away, in my 
opinion. That still does not mean we are a help desk. 
I also think we need a code of conduct that lays out some cadence on what 
gitter is and is not.
I think this is a good topic for the advocacy meeting taking place on February 
13th, and I will add it to the agenda.
In the meantime, I would like you to know how much I appreciate you and the 
other volunteers who provide help day in and day out.

> On Jan 22, 2020, at 8:32 PM, 'Gavin Mogan' via Jenkins Developers 
>  wrote:
> 
> 
> Hey Everyone,
> 
> As one of the few that regularly hang out in the users channels (#jenkins on 
> irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt about 
> a central location where we can point users to for commercial support.
> 
> There's definitely some users who come in, ask straight forward questions, 
> and usually pretty easy to fix ("check what version of java", "your using the 
> wrong type of pipeline, see examples", etc) but sometimes there's definitely 
> issues that last weeks, and its fundamental understanding of what needs to be 
> done ("How do I CI?", "Whats wrong with this  no pipeline", etc)
> 
> So how does everyone feel of a page on jenkins.io where we can go:
> "Looking for more support than the volunteers can offer? Looking to share 
> sensitive info? Need help in a short amount of time? Feel free to contact any 
> of these professional services"
> 
> I'm certainly conflicted at maintaining the curated list, or playing 
> favoritism at all, but its also frustrating when after a while of bad 
> communication you want to walk away, but they ping you, or pm you asking for 
> more help.
> 
> Gavin
> 
> -- 
> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%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/AA48B65B-5ADC-4009-8A81-40E06695A714%40gmail.com.

Re: Support List on jenkins.io?

[Mark Waite]

I like the idea very much.

We could create a page and allow changes to the page through pull
requests.  If an organization wants to note that it provides commercial
support for Jenkins, they do it by pull request.

I don't think we should put too much overhead on organizations that want to
add themselves to the page (or collection of pages).  As an example, I
could imagine a DevOps consultancy submitting a pull request with their
contact information.  Possibly, a page template with a catalog page that
lists all the pages using that template.  When an organization wants to
state their willingness to provide commercial support, they add a page that
describes the service they offer.

The wiki has https://wiki.jenkins.io/display/JENKINS/Commercial+Support .
Wiki is read only now, so we need a place on jenkins.io for that type of
information.

On Wed, Jan 22, 2020 at 9:32 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hey Everyone,
>
> As one of the few that regularly hang out in the users channels (#jenkins
> on irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt
> about a central location where we can point users to for commercial support.
>
> There's definitely some users who come in, ask straight forward questions,
> and usually pretty easy to fix ("check what version of java", "your using
> the wrong type of pipeline, see examples", etc) but sometimes there's
> definitely issues that last weeks, and its fundamental understanding of
> what needs to be done ("How do I CI?", "Whats wrong with this  pages of stacktrace and no pipeline", etc)
>
> So how does everyone feel of a page on jenkins.io where we can go:
> "Looking for more support than the volunteers can offer? Looking to share
> sensitive info? Need help in a short amount of time? Feel free to contact
> any of these professional services"
>
> I'm certainly conflicted at maintaining the curated list, or playing
> favoritism at all, but its also frustrating when after a while of bad
> communication you want to walk away, but they ping you, or pm you asking
> for more help.
>
> Gavin
>
> --
> 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/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%40mail.gmail.com
> 
> .
>


-- 
Thanks!
Mark Waite

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

Support List on jenkins.io?

['Gavin Mogan' via Jenkins Developers]

Hey Everyone,

As one of the few that regularly hang out in the users channels (#jenkins
on irc, or #jenkinsci/jenkins on gitter) I was wondering how everyone felt
about a central location where we can point users to for commercial support.

There's definitely some users who come in, ask straight forward questions,
and usually pretty easy to fix ("check what version of java", "your using
the wrong type of pipeline, see examples", etc) but sometimes there's
definitely issues that last weeks, and its fundamental understanding of
what needs to be done ("How do I CI?", "Whats wrong with this https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuskDeuV3oKOANSiKH9uB%3DyZgZyZeqxUELZ2ru-%2BbD2VYg%40mail.gmail.com.

Re: Dash / DevDocs docset for Jenkins

[Jesse Glick]

On Wed, Jan 22, 2020 at 10:43 AM Chris Kilding
 wrote:
> Jenkins admins in my company utilise the Pipeline DSL reference and the 
> JobDSL reference quite heavily - these are the things we’d most like to have 
> in an offline docset.

Not sure offhand about `job-dsl`, but the Pipeline DSL is better
referenced within the product itself, e.g.

https://ci.jenkins.io/pipeline-syntax/

which takes into account the precise versions of installed plugins,
and gives much more information than the static HTML could.

-- 
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/CANfRfr3aK%2BPPwadfPpDKHHyFLY_F5gqKM%3DiBus9VKyH2U5n3HQ%40mail.gmail.com.

Re: Dash / DevDocs docset for Jenkins

['Nik Reiman' via Jenkins Developers]

Yes! Big +1 to that idea. I've been wanting to have a docset for the pipeline 
DSL for awhile now, but I never got around to hacking something together. Such 
a resource would be much appreciated.


From: jenkinsci-dev@googlegroups.com  on behalf 
of Chris Kilding 
Sent: Wednesday, January 22, 2020 16:42
To: jenkinsci-dev@googlegroups.com
Subject: Dash / DevDocs docset for Jenkins

Hello,

Would the community be interested in having a Dash/DevDocs docset for Jenkins? 
I’d be willing to do the packaging work for this if there is sufficient 
interest.

For our part, Jenkins admins in my company utilise the Pipeline DSL reference 
and the JobDSL reference quite heavily - these are the things we’d most like to 
have in an offline docset.

Chris

PS If you don’t know what Dash or DevDocs are, see https://kapeli.com/dash and 
https://devdocs.io

--
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/120f232d-8cdf-4b52-acc3-4f48bdc172f3%40www.fastmail.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/AM0PR10MB3521985005997083E75F1B25940C0%40AM0PR10MB3521.EURPRD10.PROD.OUTLOOK.COM.

Re: JIRA Sign Up Issues

[Olblak]

Hi David,

Thanks for reporting this, It seems the problem is not gone.
I give it another look


---
gpg --keyserver keys.gnupg.net --recv-key 52210D3D
---


On Wed, Jan 22, 2020, at 3:53 PM, Marky Jackson wrote:
> Currently there is an issues being worked on with LDAP
> 
>> On Jan 22, 2020, at 1:33 AM, David Hodgkinson  
>> wrote:
>> 
>> Hi there,
>> 
>> When attempting to sign up for an account here: 
>> https://accounts.jenkins.io/signup in order to open a bug report with a 
>> plugin I get the following error:
>> 
>> HTTP ERROR 500

>> Problem accessing /doSignup. Reason:

>> Server Error
>> 
>> Caused by:

>> javax.servlet.ServletException: javax.servlet.ServletException: 
>> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access 
>> to parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:503)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
at 
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.servlet.ServletException: javax.naming.NoPermissionException: 
[LDAP: error code 50 - no write access to parent]; remaining name 
'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
... 15 more
Caused by: javax.naming.NoPermissionException: [LDAP: error code 50 - no write 
access to parent]; remaining name 
'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3162)
at 

Dash / DevDocs docset for Jenkins

[Chris Kilding]

Hello,

Would the community be interested in having a Dash/DevDocs docset for Jenkins? 
I’d be willing to do the packaging work for this if there is sufficient 
interest.

For our part, Jenkins admins in my company utilise the Pipeline DSL reference 
and the JobDSL reference quite heavily - these are the things we’d most like to 
have in an offline docset. 

Chris

PS If you don’t know what Dash or DevDocs are, see https://kapeli.com/dash and 
https://devdocs.io

-- 
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/120f232d-8cdf-4b52-acc3-4f48bdc172f3%40www.fastmail.com.

Re: Finding relevant jelly for branch-api

[Jesse Glick]

On Wed, Jan 22, 2020 at 9:48 AM Raihaan Shouhell
 wrote:
> when core calls getItems() in jelly
>  you can get the size and therefore skip the need for permissions checks

`getItems` would still need to run permission checks, regardless of
where it is implemented.

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

Re: What is the best approach for mutually exclusive permissions - re: proposed Jenkins.CONFIGURE and Jenkins.SYSTEM_READ permissions

[Jesse Glick]

On Tue, Jan 21, 2020 at 8:24 PM Michael Cirioli  wrote:
> Consider the case where a user has both Jenkins.CONFIGURE and 
> Jenkins.SYSTEM_READ - what would the expected experience be?
>
> ..a user may be shown things that can be changed by a user with 
> Jenkins.CONFIGURE, but the changes may not be persisted because of the 
> Jenkins.SYSTEM_READ changes.

If you split parts of the `/configure` page into an `/administer`
page, rather than conditionally hiding them, then I think this could
be solved in a different way that feels more in line with existing
patterns:

· If you have `ADMINISTER`, `/administer` has a *Save* (and *Apply*)
button. Else, if you have `SYSTEM_READ`, it does not. If you have
neither, it cannot be displayed at all.
· If you have `CONFIGURE`, `/configure` has *Save*. If you have
`VIEW_CONFIGURATION` (at global scope?), it does not. If you have
neither, it cannot be displayed at all.

> an ideal solution should support any additional permissions that may find 
> their way into Jenkins in the future

Do we really want to be adding complex new permission options? The
Jenkins permission system is way too complex as it stands, making for
a poor UX, and as for Jenkins developers, I at least can barely keep
the intended behavior straight in my head. Many advanced use cases
would be better handled via `configuration-as-code` plus other
tooling, processes, or policies (GitHub’s `CODEOWNERS`, for example).

-- 
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/CANfRfr1fvvuZiiHRNH7mD6kPMV%3DtuC1EJPb3x8r71SmwR%3DK1kw%40mail.gmail.com.

Re: JIRA Sign Up Issues

[Marky Jackson]

Currently there is an issues being worked on with LDAP

> On Jan 22, 2020, at 1:33 AM, David Hodgkinson  
> wrote:
> 
> Hi there,
> 
> When attempting to sign up for an account here: 
> https://accounts.jenkins.io/signup in order to open a bug report with a 
> plugin I get the following error:
> 
> HTTP ERROR 500
> 
> Problem accessing /doSignup. Reason:
> 
> Server Error
> 
> Caused by:
> 
> javax.servlet.ServletException: javax.servlet.ServletException: 
> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access to 
> parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>   at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>   at org.eclipse.jetty.server.Server.handle(Server.java:503)
>   at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
>   at 
> org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
>   at 
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
>   at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
>   at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
>   at 
> org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
>   at 
> org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: javax.servlet.ServletException: 
> javax.naming.NoPermissionException: [LDAP: error code 50 - no write access to 
> parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
>   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
>   at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>   at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
>   at 
> org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
>   at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
>   at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
>   at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
>   at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
>   at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
>   ... 15 more
> Caused by: javax.naming.NoPermissionException: [LDAP: error code 50 - no 
> write access to parent]; remaining name 
> 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
>   at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3162)
>   at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3100)
>   at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2891)
>   at 

REPOST: setting path in Buildwrapper setup()

[Nikhil Bhoski]

Hi ,

I want to set the PATH variable during setup() of BuildWrapper. and use the 
tools for which i am setting path directly on command line during my build 
step (Builder class). I am trying to set the env variable using below in 
setup() method of Build Wrapper


*initialEnvironment.put("mytoolRoot", getMytoolRoot + nodeSpecificFileSep + 
"bin");*
*initialEnvironment.override("PATH+mytoolRoot",initialEnvironment.get("mytoolRoot")
 
); *

and then just to test i am calling my tool through command line directly 
using Launcher in same setup() method like below 

*launcher.launch().cmdAsSingleString("mytool -batch 
-ver").env(initialEnvironment).stdout(listener).join();*

above command fails to pick up the tool directly through the command line. 
and the build fails with error *Cannot run program "mytool" no such file or 
directory. *

what can i do to set the env variable . the other option i am trying is to 
write batch and shell script file and execute it. but i am not sure if i 
should do that. 

Thanks & Regards
Nikhil 

-- 
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/3f181bc3-61aa-4469-9850-d5344b60af9a%40googlegroups.com.

JIRA Sign Up Issues

[David Hodgkinson]

Hi there,

When attempting to sign up for an account 
here: https://accounts.jenkins.io/signup in order to open a bug report with 
a plugin I get the following error:

HTTP ERROR 500

Problem accessing /doSignup. Reason:

Server Error

Caused by:

javax.servlet.ServletException: javax.servlet.ServletException: 
javax.naming.NoPermissionException: [LDAP: error code 50 - no write access to 
parent]; remaining name 'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:146)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:503)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:364)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260)
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168)
at 
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
at 
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
at 
org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
at java.lang.Thread.run(Thread.java:748)
Caused by: javax.servlet.ServletException: javax.naming.NoPermissionException: 
[LDAP: error code 50 - no write access to parent]; remaining name 
'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:784)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:864)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655)
at 
org.eclipse.jetty.websocket.server.WebSocketUpgradeFilter.doFilter(WebSocketUpgradeFilter.java:215)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at 
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:220)
at 
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126)
... 15 more
Caused by: javax.naming.NoPermissionException: [LDAP: error code 50 - no write 
access to parent]; remaining name 
'cn=outplaydave,ou=people,dc=jenkins-ci,dc=org'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3162)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3100)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2891)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:812)
at 
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:341)
at 

Re: Finding relevant jelly for branch-api

[Raihaan Shouhell]

Thanks for the reply Jesse, my idea was because branch-api wants to show 
the number of items in its view if core should provide that feature and 
that way when core calls getItems() in jelly
 you can get the size and therefore skip the need for permissions checks. 
But I'm not sure if its worth the effort.

On Wednesday, 22 January 2020 08:43:30 UTC+8, Jesse Glick wrote:
>
> On Mon, Jan 20, 2020 at 5:13 AM Raihaan Shouhell 
> > wrote: 
> > I'd like to see if the relevant jelly files that call this has access to 
> items and the use of getItems() (and hasPermission) can be reduced. 
>
> Doubtful since this is just overriding 
>
> https://javadoc.jenkins.io/hudson/model/View.html#getDisplayName-- 
>
> If permission checks are a bottleneck here it might be a problem in 
> the `AuthorizationStrategy`. Alternately, it would probably be fine to 
> wrap the `getItems` call inside `ACL.as(ACL.SYSTEM)` since someone 
> with permission to view the organization folder very likely also has 
> permission to view all the child repositories (it would be an obscure 
> authorization strategy that decided otherwise), and at worst the 
> leaked information would be a count of hidden subfolders. 
>

-- 
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/b6feb5ab-51a9-4be3-b8ca-7c20b9997d1f%40googlegroups.com.

Re: Getting jenkins build user

[Raihaan Shouhell]

Yes the useridcause will have the information you need

On Wednesday, 22 January 2020 17:27:23 UTC+8, selva vignesh wrote:
>
> Hi,
> I have developed Jenkins plugin for my use. In that i am getting 
> *triggerer* of build (i.e build user, who triggered a build). Now i am 
> using Jenkins own database for user. 
> If i migrate to AD, *am i able to get userid from build?.*
>
>> Cause.UpstreamCause upstreamCause = (Cause.UpstreamCause) 
>> run.getCause(Cause.UpstreamCause.class);
>> Run temp = null;
>> while (upstreamCause != null) {
>> Job job = 
>> Jenkins.getInstance().getItemByFullName(upstreamCause.getUpstreamProject(), 
>> Job.class);
>> if (job != null) {
>> temp = job.getBuildByNumber(upstreamCause.getUpstreamBuild());
>> if (temp != null) {
>>upstreamCause = (Cause.UpstreamCause) 
>> temp.getCause(Cause.UpstreamCause.class);
>> }
>> }
>> }
>> if (temp != null) {
>> run = temp;
>> }
>> SCMTrigger.SCMTriggerCause scmTriggerCause = (SCMTrigger.SCMTriggerCause) 
>> run.getCause(SCMTrigger.SCMTriggerCause.class);
>> if (scmTriggerCause != null) {
>> return "SCMTrigger";
>> }
>> UserIdCause cause = (UserIdCause) run.getCause(UserIdCause.class);
>> if (cause == null) {
>> return "System";
>> }
>> return cause.getUserId();
>>
>>
> I am using above code to get build *triggerer. *Kindly assist.
>

-- 
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/40b138dd-79de-41b0-a1c2-51617af617c1%40googlegroups.com.

Re: Proposal: Expanding the Jenkins Core maintainers team

[Raihaan Shouhell]

Sounds good to me

On Wed, 22 Jan 2020, 5:59 AM Victor Martinez, 
wrote:

> +1
> This is really great news!! Thanks for moving forward <3
>
> --
> 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/74dd129f-eca3-4eea-9385-e0a9cd6ecb16%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/CAFoxvgy6MN2SPsrg_yDhWRwJrsgPAv0q5bD-ZjRnrV_Y-_MieQ%40mail.gmail.com.

Getting jenkins build user

[selva vignesh]

Hi,
I have developed Jenkins plugin for my use. In that i am getting *triggerer* of 
build (i.e build user, who triggered a build). Now i am using Jenkins own 
database for user. 
If i migrate to AD, *am i able to get userid from build?.*

> Cause.UpstreamCause upstreamCause = (Cause.UpstreamCause) 
> run.getCause(Cause.UpstreamCause.class);
> Run temp = null;
> while (upstreamCause != null) {
> Job job = 
> Jenkins.getInstance().getItemByFullName(upstreamCause.getUpstreamProject(), 
> Job.class);
> if (job != null) {
> temp = job.getBuildByNumber(upstreamCause.getUpstreamBuild());
> if (temp != null) {
>upstreamCause = (Cause.UpstreamCause) 
> temp.getCause(Cause.UpstreamCause.class);
> }
> }
> }
> if (temp != null) {
> run = temp;
> }
> SCMTrigger.SCMTriggerCause scmTriggerCause = (SCMTrigger.SCMTriggerCause) 
> run.getCause(SCMTrigger.SCMTriggerCause.class);
> if (scmTriggerCause != null) {
> return "SCMTrigger";
> }
> UserIdCause cause = (UserIdCause) run.getCause(UserIdCause.class);
> if (cause == null) {
> return "System";
> }
> return cause.getUserId();
>
>
I am using above code to get build *triggerer. *Kindly assist.

-- 
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/c6890eab-ed67-46ac-8b32-8b0cfec57b99%40googlegroups.com.

Re: Defaulting a jelly optionalBlock checkbox to checked/true

[Ullrich Hafner]

It would help if you would post the relevant part of your jelly file

> Am 21.01.2020 um 23:24 schrieb Khushboo Sancheti :
> 
> Hmm, thanks! Not a jelly expert by any means, trying to use a set_if to set 
> the value of a variable based on instance == null or not, and use that as the 
> checked value. Not very successful yet.
>> Am 21.01.2020 um 22:36 schrieb Khushboo Sancheti >:
>> 
>> How can one default the optionalBlock checkbox to be checked? Jelly doesn't 
>> seem to provide a "default" attribute for optionalBlock like it does for a 
>> normal checkbox ...
>> 
>> -- 
>> 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/8a268659-e210-4d3d-b6c7-681c802401c4%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/f386ee68-cb94-43bb-bcdd-248dd3e26660%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/ADF2AED0-0222-489A-B03D-1D42EA8769FD%40gmail.com.

Re: Help, my plugin could't through jenkins ci.

[Ullrich Hafner]

First of all please make sure that we are allowed to publish the API in our 
public Nexus, I can’t find any English page that references the library.

> Am 22.01.2020 um 09:12 schrieb liuweiGL :
> 
> The jar is sdk of  DingTalk(钉钉) 
> , and it belongs to Alibaba 
> . i don't know the reason also, i will consult 
> them and deploy the artifact in your Nexus instance.
> 
> But, i don't know what to do... Is there any documentation you can refer to, 
> thank you.
> 
> If it is open source then you can deploy the artifact in our Nexus instance
> 
> 在 2020年1月22日星期三 UTC+8下午3:42:55，Ullrich Hafner写道：
> Then it cannot work: other users cannot build your plugin as well.
> 
> Is the jar somehow proprietary and does not use an open source license? Can 
> you please elaborate what this library is about and why it is not in 
> available in a public repository? 
> If it is open source then you can deploy the artifact in our Nexus instance.
> 
>> Am 22.01.2020 um 08:36 schrieb liuweiGL >:
>> 
>> No, the jar locatioin in my project repository, and i had use sh mvnCmd to 
>> install,it doesn't seem to work.
>> 
>> 
>> 
>> 在 2020年1月22日星期三 UTC+8下午3:04:58，Ullrich Hafner写道：
>> All of your dependencies must be available online. Is this jar available 
>> somewhere in a public maven repository? 
>> 
>>> Am 22.01.2020 um 06:26 schrieb liuweiGL >:
>>> 
>>> Jenkinsfile:
>>> 
>>> def mvnCmd = "mvn install:install-file -DgroupId=com.dingtalk.open 
>>> -DartifactId=taobao-sdk-java-auto -Dversion=1.0 -Dpackaging=jar 
>>> -Dfile=./maven/taobao-sdk-java-auto/taobao-sdk-java-auto_1479188381469-20191227.jar"
>>> 
>>> node('maven'){
>>> disableConcurrentBuilds()
>>> checkout scm
>>> 
>>> stage('Install'){
>>> sh mvnCmd
>>> }
>>> 
>>> stage('Build'){
>>> buildPlugin()
>>> }
>>> }
>>> 
>>> Error log:
>>> 
>>>  Failed to execute goal on project dingding-notifications: Could not 
>>> resolve dependencies for project 
>>> io.jenkins.plugins:dingding-notifications:hpi:2.0.1-SNAPSHOT: Could not 
>>> find artifact com.dingtalk.open:taobao-sdk-java-auto:jar:1.0 in 
>>> azure-incrementals (https://repo.azure.jenkins.io/incrementals/ 
>>> )
>>> 
>>> 
>>> Detail log reference: 
>>> 
>>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fdingding-notifications-plugin/detail/master/36/pipeline/16
>>>  
>>> 
>>> 
>>> I've been trying all day, but i still fail. Why? I've installed the 
>>> dependency locally, it's confusing to me.
>>> 
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to jenkin...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/99afdef8-a0aa-4e57-b256-7d0bb729e516%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 jenkin...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b1895bd9-f713-4d84-9528-df4a9e0b687d%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/aba6e51d-eff9-4fb1-ab15-2df05f4d532f%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/87088662-3865-4FBB-8E62-5F0E4FD22280%40gmail.com.

Re: Help, my plugin could't through jenkins ci.

[liuweiGL]

The jar is sdk of  DingTalk(钉钉) 
, and it belongs to 
Alibaba . i don't know the reason also, i 
will consult them and deploy the artifact in your Nexus instance.

But, i don't know what to do... Is there any documentation you can refer 
to, thank you.

If it is open source then you can deploy the artifact in our Nexus instance


在 2020年1月22日星期三 UTC+8下午3:42:55，Ullrich Hafner写道：
>
> Then it cannot work: other users cannot build your plugin as well.
>
> Is the jar somehow proprietary and does not use an open source license? 
> Can you please elaborate what this library is about and why it is not in 
> available in a public repository? 
> If it is open source then you can deploy the artifact in our Nexus 
> instance.
>
> Am 22.01.2020 um 08:36 schrieb liuweiGL 
> >:
>
> No, the jar locatioin in my project repository, and i had use sh mvnCmd to 
> install,it doesn't seem to work.
>
>
>
> 在 2020年1月22日星期三 UTC+8下午3:04:58，Ullrich Hafner写道：
>>
>> All of your dependencies must be available online. Is this jar available 
>> somewhere in a public maven repository? 
>>
>> Am 22.01.2020 um 06:26 schrieb liuweiGL :
>>
>> Jenkinsfile:
>>
>> def mvnCmd = "mvn install:install-file -DgroupId=com.dingtalk.open 
>> -DartifactId=taobao-sdk-java-auto -Dversion=1.0 -Dpackaging=jar 
>> -Dfile=./maven/taobao-sdk-java-auto/taobao-sdk-java-auto_1479188381469-20191227.jar
>> "
>>
>> node('maven'){
>>disableConcurrentBuilds()
>>checkout scm
>>
>> stage('Install'){
>>sh mvnCmd
>>}
>>
>> stage('Build'){
>>buildPlugin()
>>}
>> }
>>
>> Error log:
>>
>> Failed to execute goal on project dingding-notifications: Could not 
>> resolve dependencies for project 
>> io.jenkins.plugins:dingding-notifications:hpi:2.0.1-SNAPSHOT: Could not 
>> find artifact com.dingtalk.open:taobao-sdk-java-auto:jar:1.0 in 
>> azure-incrementals (https://repo.azure.jenkins.io/incrementals/)
>>
>>
>> Detail log reference: 
>>
>>
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fdingding-notifications-plugin/detail/master/36/pipeline/16
>>
>>
>>- 
>>
>>*I've been trying all day, but i still fail. Why? I've installed the 
>>dependency locally, it's confusing to me.*
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/99afdef8-a0aa-4e57-b256-7d0bb729e516%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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b1895bd9-f713-4d84-9528-df4a9e0b687d%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/aba6e51d-eff9-4fb1-ab15-2df05f4d532f%40googlegroups.com.

Re: Help, my plugin could't through jenkins ci.

[liuweiGL]

The jar is sdk of  DingTalk(钉钉) 
, and it belongs to 
Alibaba . i don't know the reason also, i 
will consult them and deploy the artifact in your Nexus instance.

Then, i don't know what to do...

> If it is open source then you can deploy the artifact in our Nexus instance
>

在 2020年1月22日星期三 UTC+8下午3:42:55，Ullrich Hafner写道：
>
> Then it cannot work: other users cannot build your plugin as well.
>
> Is the jar somehow proprietary and does not use an open source license? 
> Can you please elaborate what this library is about and why it is not in 
> available in a public repository? 
> If it is open source then you can deploy the artifact in our Nexus 
> instance.
>
> Am 22.01.2020 um 08:36 schrieb liuweiGL 
> >:
>
> No, the jar locatioin in my project repository, and i had use sh mvnCmd to 
> install,it doesn't seem to work.
>
>
>
> 在 2020年1月22日星期三 UTC+8下午3:04:58，Ullrich Hafner写道：
>>
>> All of your dependencies must be available online. Is this jar available 
>> somewhere in a public maven repository? 
>>
>> Am 22.01.2020 um 06:26 schrieb liuweiGL :
>>
>> Jenkinsfile:
>>
>> def mvnCmd = "mvn install:install-file -DgroupId=com.dingtalk.open 
>> -DartifactId=taobao-sdk-java-auto -Dversion=1.0 -Dpackaging=jar 
>> -Dfile=./maven/taobao-sdk-java-auto/taobao-sdk-java-auto_1479188381469-20191227.jar
>> "
>>
>> node('maven'){
>>disableConcurrentBuilds()
>>checkout scm
>>
>> stage('Install'){
>>sh mvnCmd
>>}
>>
>> stage('Build'){
>>buildPlugin()
>>}
>> }
>>
>> Error log:
>>
>> Failed to execute goal on project dingding-notifications: Could not 
>> resolve dependencies for project 
>> io.jenkins.plugins:dingding-notifications:hpi:2.0.1-SNAPSHOT: Could not 
>> find artifact com.dingtalk.open:taobao-sdk-java-auto:jar:1.0 in 
>> azure-incrementals (https://repo.azure.jenkins.io/incrementals/)
>>
>>
>> Detail log reference: 
>>
>>
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fdingding-notifications-plugin/detail/master/36/pipeline/16
>>
>>
>>- 
>>
>>*I've been trying all day, but i still fail. Why? I've installed the 
>>dependency locally, it's confusing to me.*
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/99afdef8-a0aa-4e57-b256-7d0bb729e516%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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b1895bd9-f713-4d84-9528-df4a9e0b687d%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/caec2c9d-c1e5-4f16-af81-b7a178482c21%40googlegroups.com.

Re: Help, my plugin could't through jenkins ci.

[liuweiGL]

The jar belongs to Alibaba , i don't know 
the reason also, i will consult them.

在 2020年1月22日星期三 UTC+8下午3:42:55，Ullrich Hafner写道：
>
> Then it cannot work: other users cannot build your plugin as well.
>
> Is the jar somehow proprietary and does not use an open source license? 
> Can you please elaborate what this library is about and why it is not in 
> available in a public repository? 
> If it is open source then you can deploy the artifact in our Nexus 
> instance.
>
> Am 22.01.2020 um 08:36 schrieb liuweiGL 
> >:
>
> No, the jar locatioin in my project repository, and i had use sh mvnCmd to 
> install,it doesn't seem to work.
>
>
>
> 在 2020年1月22日星期三 UTC+8下午3:04:58，Ullrich Hafner写道：
>>
>> All of your dependencies must be available online. Is this jar available 
>> somewhere in a public maven repository? 
>>
>> Am 22.01.2020 um 06:26 schrieb liuweiGL :
>>
>> Jenkinsfile:
>>
>> def mvnCmd = "mvn install:install-file -DgroupId=com.dingtalk.open 
>> -DartifactId=taobao-sdk-java-auto -Dversion=1.0 -Dpackaging=jar 
>> -Dfile=./maven/taobao-sdk-java-auto/taobao-sdk-java-auto_1479188381469-20191227.jar
>> "
>>
>> node('maven'){
>>disableConcurrentBuilds()
>>checkout scm
>>
>> stage('Install'){
>>sh mvnCmd
>>}
>>
>> stage('Build'){
>>buildPlugin()
>>}
>> }
>>
>> Error log:
>>
>> Failed to execute goal on project dingding-notifications: Could not 
>> resolve dependencies for project 
>> io.jenkins.plugins:dingding-notifications:hpi:2.0.1-SNAPSHOT: Could not 
>> find artifact com.dingtalk.open:taobao-sdk-java-auto:jar:1.0 in 
>> azure-incrementals (https://repo.azure.jenkins.io/incrementals/)
>>
>>
>> Detail log reference: 
>>
>>
>> https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fdingding-notifications-plugin/detail/master/36/pipeline/16
>>
>>
>>- 
>>
>>*I've been trying all day, but i still fail. Why? I've installed the 
>>dependency locally, it's confusing to me.*
>>
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkin...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/99afdef8-a0aa-4e57-b256-7d0bb729e516%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 jenkin...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b1895bd9-f713-4d84-9528-df4a9e0b687d%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/5e9c2ef9-a3b1-45c4-a9c5-94bc6235ee2c%40googlegroups.com.