Re: Hosting && Gavin Schedule

[Robert Sandell]

I understand the case that we wan't to make sure users/administrators can
somehow trust what is offered in the public/official update center.
But I don't like the idea of restricting or putting up barriers for new
contributors to join the project, or hindering the potential innovation
coming in from the outside.
It was the welcoming and open approach of "just ask and you shall receive"
that made me like this community so much and stay around for 11 years and
hopefully many more.
There must be some way we can address both without sacrificing one?
So by all means, run the script to find the issues, but please don't block
a contribution based on the findings from it.

/B

Den lör 18 sep. 2021 kl 05:20 skrev 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com>:

> I can run them before approving  / reviewing them
>
> In addition, i would like to help manage end users expectation about what
> kind of support a plugin might have (Core, Community, Professional, etc).
> Just one more thing to do on the todo list.
>
> Gavin
>
> On Fri, Sep 17, 2021 at 8:16 PM Gavin Mogan  wrote:
>
>> I Lost track of where you did the ping to me. Sounds out I need to be
>> clearer. if I get more scripts to run, I can run them before
>>
>> On Thu, Sep 16, 2021 at 10:10 PM Gavin Mogan 
>> wrote:
>>
>>> I'm sorry I thought you were offering them up. I didn't realize you were
>>> asking if I wanted them. I can certainly try them out
>>>
>>> As for the banner. It might be worth some sort of verified publisher or
>>> something else that indicates when the company maintains the plugin and you
>>> should contact thier support, vs community maintained plugins with
>>> community support avenues.
>>>
>>> On Thu., Sep. 16, 2021, 9:16 p.m. 'Daniel Beck' via Jenkins Developers, <
>>> jenkinsci-dev@googlegroups.com> wrote:
>>>
>>>>
>>>>
>>>> > On 17. Sep 2021, at 04:32, 'Gavin Mogan' via Jenkins Developers <
>>>> jenkinsci-dev@googlegroups.com> wrote:
>>>> >
>>>> > So sure, someone other than you can do more in-depth reviews of the
>>>> code. I've been doing absolute basic checks with the expertise I have. I
>>>> was very clear when I took over the hosting lead position that I wasn't
>>>> going to be spending much time doing reviews. I'm absolutely happy for
>>>> someone to step up and do more code reviews.
>>>>
>>>> Thanks for starting this conversation.
>>>>
>>>> My preferred option (that I mentioned in Jira) is to have a basic
>>>> review of the plugin. My offer from August to give you access to the code
>>>> scanning rules for plugins to quickly identify the low hanging fruit at
>>>> least still stands. I haven't heard back from you about that.
>>>>
>>>> Another option could be not have reviews, instead to do something
>>>> similar to what Mozilla does[1], and prominently display that plugins are
>>>> not reviewed for security. At least then we let admins know what they're
>>>> getting. This would require criteria for other badges that need maintaining
>>>> however, and certainly will take time to set up.
>>>>
>>>> I'm sure there are other approaches we can take, but admitting code
>>>> with very obvious security flaws doesn't seem like a great approach given
>>>> how critical Jenkins is for many of its users.
>>>>
>>>>
>>>> 1: https://support.mozilla.org/en-US/kb/add-on-badges
>>>>
>>>> --
>>>> 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/8E216E2D-EA35-4A21-99C8-44A026BFD592%40beckweb.net
>>>> .
>>>>
>>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dusvy%3D0f_XCDrGpZ8FS5HmOdck4xORvtjdScfzc43iu3gQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dusvy%3D0f_XCDrGpZ8FS5HmOdck4xORvtjdScfzc43iu3gQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.
<http://www.cloudbees.com>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3g-9xxNYc_MQRMwJVb%2BUbnJuc6hNHRwxE7VEJz7zE9EQ%40mail.gmail.com.

Re: ASM in core

[Robert Sandell]

Some historical context to know where we "old timers" are coming from :)
https://kohsuke.org/2012/03/03/potd-package-renamed-asm/

There are several times where I've needed to shade asm in plugins because 
of some transitive dependency. Las time I think it was a dependency on ASM7 
that blew up for me and I had to repackage that dependency to not break 
other plugins that depended on my plugin.
That's why me and James and others are very very wary of bumping the asm 
dependencies, I think even more wary than for Guava, because there isn't 
enough code coverage due to how the classpath is during unit testing.
I am not fully read up on the JNI situation so I can't comment on that 
situation, but it sounds like a damned if we do, damned if we don't kind of 
situation?

/B

On Friday, June 11, 2021 at 9:49:51 AM UTC+2 kuisat...@gmail.com wrote:

> Hi,
>
> I would like to add an issue related to not bump the ASM library, I 
> recently hit an issue with stapler (see 
> https://groups.google.com/g/jenkinsci-dev/c/JppfFwqIrCU) and it is 
> related to compile the plugin for JDK 11 only,
> new plugins use new libraries and more and more libraries use JDK 11 
> nowadays for obvious reasons. 
> So bump the ASM version is something completely necessary. Break thing is 
> fine and more when those things are 10 years old stuff, in general, the 
> Jenkins Core has a few forked libraries that are a pain to maintain 
> updated, most of them are 10 yo pains. Thus, I think it is a matter of 
> making a damage control of the plugins affected by the change and fix those 
> that are still maintained or in use, Do we know which plugins are affected 
> by the change on ASM?
>
> BTW the ASM/JNR/JNA update is part of the JEP-211 
> 
>  and JENKINS-40689  so 
> stuff longtime ago exposed
> El jueves, 10 de junio de 2021 a las 21:58:38 UTC+2, m...@basilcrow.com 
> escribió:
>
>> On Thu, Jun 10, 2021 at 11:28 AM Tim Jacomb  wrote: 
>> > 
>> > It would be good to see a more recent report given we’re on version 9 
>> in core to see if anything has changed in recent versions 
>>
>> Great point, Tim. Core 2.273 shipped with ASM 5.0.3, prior to the 
>> upgrade of JNR (and therefore the accidental upgrade of ASM) in 2.274. 
>> Here are the differences between ASM 5.0.3 and ASM 9.1: 
>>
>>
>> https://diff.revapi.org/?groupId=org.ow2.asm=asm=5.0.3=9.1
>>  
>>
>> https://diff.revapi.org/?groupId=org.ow2.asm=asm-analysis=5.0.3=9.1
>>  
>>
>> https://diff.revapi.org/?groupId=org.ow2.asm=asm-commons=5.0.3=9.1
>>  
>>
>> https://diff.revapi.org/?groupId=org.ow2.asm=asm-tree=5.0.3=9.1
>>  
>>
>> https://diff.revapi.org/?groupId=org.ow2.asm=asm-util=5.0.3=9.1
>>  
>>
>> The library seems quite stable between 5.0.3 and 9.1. Apart from new 
>> classes and the addition of generics, nothing seems to have been 
>> removed or renamed. (Similarly, recent versions of Guava are more 
>> stable than older versions.) 
>>
>> In any case, I doubt we would roll back the JNR changes made in 2.274 
>> at this point. For better or for worse, ASM 9.1 is here to stay as 
>> part of the core API, so we might as well own it in the short term. 
>> (In the long term, removing or hiding Guice/JNR and therefore 
>> Guava/ASM would be nice, of course.) 
>>
>

-- 
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/9c2d0cbb-2972-4e88-a51b-c53a5f39f5e4n%40googlegroups.com.

Re: NTLM Authentication

[Robert Sandell]

https://plugins.jenkins.io/kerberos-sso/

/B

Den tis 17 nov. 2020 kl 12:50 skrev Ivan Fernandez Calvo <
kuisathave...@gmail.com>:

> I guess that it is because nobody has an interest in developing a plugin
> for NTLM authentication because there are better ways to authenticate
> against windows, for example, Active directory that has support for
> authentication and authorization, also NTLM is pretty old and insecure. If
> after all that you continue thinking to use it you can use an Apache HTTP
> server in front of Jenkins and configure there the NTLM authentication.
>
> https://en.wikipedia.org/wiki/NT_LAN_Manage
> https://docs.moodle.org/310/en/NTLM_authentication#APACHE_Configuration
>
> https://plugins.jenkins.io/active-directory/
>
> El lunes, 16 de noviembre de 2020 a las 16:55:36 UTC+1,
> chrisb...@gmail.com escribió:
>
>>
>> Hello everyone,
>>
>> I'd like to know why Jenkins does not consider NTLM authentication on
>> Windows.
>>
>> Many thanks.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/d6fde3a9-ca08-48f1-ae77-2fbdc31b10e6n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/d6fde3a9-ca08-48f1-ae77-2fbdc31b10e6n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.
<http://www.cloudbees.com>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: repo-plugin: stalled pull requests

[Robert Sandell]

I'm having less and less time to handle pull requests on the repo-plugin.
So it's OK for me to have Typz added as a maintainer.

@Typz add yourself to this file and make a PR so the admins can do their
thing:
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-repo.yml


/B

Den ons 16 sep. 2020 kl 11:14 skrev Typz :

> Hello,
>
> I made a 2 pull requests to repo-plugin
> <https://github.com/jenkinsci/repo-plugin> a few months back, to
> correctly handle multiple checkout from a single job (
> https://github.com/jenkinsci/repo-plugin/pull/62) and fix changelog when
> shallow checkout is used (https://github.com/jenkinsci/repo-plugin/pull/63
> )
>
> Can anybody give some feedback, or merge the pull requests?
>
> If needed, I can also participate in maintenance of the plugin (my GitHub
> username is *Typz*, and Jenkins infrastructure account is *typz*)
>
> Best regards,
>
> --
> Francois
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.
<http://www.cloudbees.com>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3oCxbYBLdCtn7SvO%2Bdc123sUZBE9FD6JwcYba2KKnNOQ%40mail.gmail.com.

Re: Terminology Updates

[Robert Sandell]

Good suggestions overall so far, so I can't really contribute to more
suggestions.

Just that Blocklist reminds me too much of Blockchain, so I want to add my
veto to that term :)

/B

Den fre 10 juli 2020 kl 20:31 skrev 'Martin Schmude' via Jenkins Developers
:

> My proposals for "master":
>
>
>- central
>- main
>
> Besides this I'm find with "Jenkins server" or simply "server".
>
> James Nord schrieb am Dienstag, 30. Juni 2020 um 22:06:29 UTC+2:
>
>> how about monolith 樂 for the 'master'
>>
>> it may be modular in terms of plugins and architecture but it's not micro
>> services.
>> whilst some parts (fingerprint storage, artifact storage) are pluggable
>> we still have the one big thing.
>>
>> other equally bizarre / useful suggestions include:
>>
>> * comptroller
>> * orchestrator (may have already been suggested apologies if it has)
>> * sneer (it's the collective noun for butlers) it would be good if used
>> for the master node to disuade stop people using it
>> * trustee
>> * 'legacy_unsafe' (for the master node/executor label)
>> * "M" (as in James bond, head of all the agents)
>> * case officer (handles agents)
>> * director (tells the agents what to do)
>> * "C" the head of MI6 (not "M" as the bond movie make you believe)
>>
>>
>> /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/9c289226-7882-4c9d-a816-6e813ef9c7b4n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/9c289226-7882-4c9d-a816-6e813ef9c7b4n%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Senior Software Engineer
CloudBees, Inc.
<http://www.cloudbees.com>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: Git plugin 5.0 require Jenkins 2.190.3

[Robert Sandell]

I think 2.204.x is the current favorite, but I don't think there is 
anything against 2.190 more than age.

/B

On Thursday, March 26, 2020 at 2:43:45 PM UTC+1, Mark Waite wrote:
>
> The git plugin and git client plugin currently require Jenkins 2.138.4.  I 
> chose that Jenkins version almost 18 months ago while working on the 
> transition from JGit 4 to JGIt 5.
>
> I think it is time to switch the minimum Jenkins version for the git 
> plugin and the git client plugin.  I propose that the minimum Jenkins 
> version for git plugin 5.0 and git client plugin 5.0 will be Jenkins 
> 2.190.3.
>
> We can still release versions of the git plugin and git client plugin for 
> Jenkins releases older than 2.190.3 by basing those releases on earlier 
> branches.
>
> I frequently test the git plugin and git client plugin with the current 
> Jenkins LTS line.  I sometimes test with the prior Jenkins LTS line.  
> Choosing 2.190.3 seems conservative enough to me and is much closer to what 
> I'm actually testing than Jenkins 2.138.4.
>
> Are there pitfalls or problems that I have not considered in making the 
> Jenkins version required by git plugin 5.0 be Jenkins 2.190.3?
>
> Fran and Bobby, what do you think of the idea?
>
> 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/dff7cc14-6220-4e1d-bc4d-0cb8de893c98%40googlegroups.com.

Re: Q: rename a variable without breaking compatibility in the declarative pipeline

[Robert Sandell]

Ah yes, that's gonna be a tricky one.

The problem is that the databound constructor no longer has a parameter
named "glob". changeset "something*" should still work fine I guess, but
since there is no databound constructor with that parameter or a databound
setter with the name setGlob it fails. But just adding a @DataboundSetter
setGlob(String glob) {pattern = glob;} won't solve it either since there is
now another mandatory parameter named "pattern" that must be passed. And
removing the databound constructor will break the changeset "something*"
calls.

Maybe there is something in the descriptor that can be overridden to
manually handle the various scenarios, like overriding configure or
newInstance but I don't remember if that is possible on the top of my head.

Den tis 10 dec. 2019 kl 20:45 skrev Victor Martinez <
victormartinezru...@gmail.com>:

> Hi there,
>
> I thought the readResolve
> <https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility>
> might be the way to go but apparently I missed something and then there are
> no backward compatible for the when changeset
> <https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/366> and
> likely the same for the
> <https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/366>when
> branch
> <https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/351> in
> the declarative pipeline syntax. See the comment in
> https://issues.jenkins-ci.org/browse/JENKINS-60217?focusedCommentId=381168=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-381168
>  as
> it did report a breaking change.
>
> I'd like to ask you what are the bits and pieces I missed and some
> suggestions to validate this somehow automatically with some testing.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/6cd3a4d5-8b36-4fd3-91e2-b0629d0f6856%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/6cd3a4d5-8b36-4fd3-91e2-b0629d0f6856%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2AG04vvYOqo49a9T%2B3-UwCqXOSyjuCCOayfuVA3pmuAw%40mail.gmail.com.

Re: 2019 Elections: voting is delayed

[Robert Sandell]

> Have you checked in your spam folder in your corporate email address?

Yes, twice and searched through the rest of my account in case it was
routed to some strange folder.
And then I searched again with a closer look and it turned out it had been
hidden in the middle of the cert team's conversation :)
Sorry for the false alarm.

/B

Den ons 13 nov. 2019 kl 13:06 skrev Olblak :

> I haven't received any email to register for voting, at least not a
> personal one. I've received two to various group mailing lists but not one
> connected to my Jenkins account.
>
>
> Have you checked in your spam folder in your corporate email address?
> I see that your account uses your corporate email address and also that
> you didn't confirm your participation
> Did you receive an email from 'electi...@jenkins.io'
>
> ---
> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
> On Wed, Nov 13, 2019, at 12:29 PM, Robert Sandell wrote:
>
> I haven't received any email to register for voting, at least not a
> personal one. I've received two to various group mailing lists but not one
> connected to my Jenkins account.
>
> /B
>
> Den mån 11 nov. 2019 kl 20:50 skrev Tracy Miranda  >:
>
> Marky - thanks for the kind words.
>
> Olivier - thanks for the detailed stats - 730 registered, 
> Somehow I also find the 0.01% spam reports strangely comforting - we spend
> a non-zero amount of time worrying how best not to be spammy - good to see
> it is worth worrying about but the numbers put it in the right perspective.
>
> Tracy
>
> On Sat, Nov 9, 2019 at 11:34 AM Olblak  wrote:
>
>
> Hey,
> Some updates with the actual campaign to identify contributors interested
> by participating to the election
>
> Currently they are 730 people who successfully registered for the next
> stage
>
> And here some stats from Sendgrid regarding all the emails sent since
> yesterday, obviously those numbers should still evolve.
> So it's too early to take conclusion
>
> 90,684: Requests
> 9,316: Bounces
> 80,971: Delivered
> 13,734: Unique Opens
> 974: Unique Clicks
> 611: Unsubscribes
> 6: Spam Reports
>
>
> ---
> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
>
> On Fri, Nov 8, 2019, at 7:54 PM, Marky Jackson wrote:
>
> This is an admirable thing to do Tracy and speaks immensely to your
> dedication to this project and as a leader, *I HUGELY ADMIRE YOU*
>
> On Friday, November 8, 2019 at 6:28:29 AM UTC-8, Tracy Miranda wrote:
>
> Hi all,
>
> Here's a post on jenkins.io with election update
> https://jenkins.io/blog/2019/11/08/board-elections/ and what to expect
> next.
> Thanks to Mark Waite for helping with this & Oleg for reviews.
>
> Also I have withdrawn my candidacy for a board seat as I am doing a bunch
> behind the scenes with voter registration, etc and would like to stay
> focussed on overseeing the election process fairly.
> I expect in my role as CDF board member to work closely with the new board
> and help out wherever I can to keep things moving forward in Jenkins.
>
> Tracy
>
> On Mon, Nov 4, 2019 at 2:37 PM Tracy Miranda 
> wrote:
>
> Hi all,
>
> We're now in a good position to start sending out voter registration
> emails. Please look out for an email from electi...@jenkins.io with the
> title ‘2019 Jenkins Election - Invitation to Participate’.
> The email will have details on how to register to vote for the elections.
> Please note we will likely be sending out emails in batches so over the
> course of the next few days.
> Once they are all sent I will confirm on the dev list so we can
> troubleshoot for anyone who has not received an email.
> Thanks again to Olivier for pulling together a lot of the pieces to make
> this happen!
>
> Thanks,
> Tracy
>
>
> On Fri, Nov 1, 2019 at 11:47 AM Olblak  wrote:
>
> Hi Daniel,
>
> As far as I know, there is no jira ticket and it's a good point that we
> should have that
> As I said several days ago, I wrote a simple application to collect email
> and we are testing that approach at the moment with a a small group of
> people. Basically they received an email inviting them to participate to
> the election
>
> To recall the process
>
> Step 1:
> We send an email to every jenkins account containing a link to '
> https://polls.jenkins.io/#/participate', mentioning your email account,
> your unique token, and and poll id
> Step2:
> After a period, every members who confirmed there participation, are
> invited in the Condorcet tool to participate to the election.
>
>
> ---
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D
> ---
>
> On Fri, Nov 1, 2019, at 2:30 PM,

Re: How to get TaskListener or BuildListener

[Robert Sandell]

There is no specific one to get. A TaskListener is created for a build when
it starts, so from the job or item level there isn't one to use.
If you need an instance to send as a parameter to some api call you can for
example use something like TaskListener.NULL
<https://javadoc.jenkins-ci.org/hudson/model/TaskListener.html#NULL> or
instantiate a new LogTaskListener
<https://javadoc.jenkins-ci.org/hudson/util/LogTaskListener.html>.

/B

Den ons 13 nov. 2019 kl 11:30 skrev selva vignesh :

> Hi,
> Can anyone please help me to get TaskListener or BuildListerner from job
> object or item Object
>
> Any sample snippet available.
>
> 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/2d555f5d-ce9f-4ec0-a194-22fbf4df84dd%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/2d555f5d-ce9f-4ec0-a194-22fbf4df84dd%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: 2019 Elections: voting is delayed

[Robert Sandell]

ibe 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/C7E0248E-9F74-4010-87CD-7D1408537AFD%40beckweb.net
>> .
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkin...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/546d4625-4965-4da4-b6d5-358fe5284ffd%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/61ab3138-2467-456f-8c66-5fb4e12adf1c%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/61ab3138-2467-456f-8c66-5fb4e12adf1c%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/baa0d19b-10d4-4d66-8b72-02d30800d859%40www.fastmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/baa0d19b-10d4-4d66-8b72-02d30800d859%40www.fastmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6p%3D-OkW0YGm0fcH%3DuiZGHWeBPH-nka4gJPN4FhzGOqa2w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6p%3D-OkW0YGm0fcH%3DuiZGHWeBPH-nka4gJPN4FhzGOqa2w%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2sxXPrwyC3LcxVxqQ9p%3D4eUsBb%2BxGQhev_xL71Ro8AAA%40mail.gmail.com.

Re: How to expose WebJars with Stapler

[Robert Sandell]

You could make your own simple AdjunctManager and expose a web method in a
descriptor or hidden root action that uses for example Stapler.serveFile.
Just be careful not to expose the entire class hierarchy :)
And possibly provide an etag or expiration date so the browser doesn't
continuously hammer your method.

/B

Den tors 31 okt. 2019 kl 00:01 skrev Ullrich Hafner <
ullrich.haf...@gmail.com>:

> In stapler-adjunct-jquery
> <https://github.com/stapler/stapler-adjunct-jquery> the JS file is part
> of the main plugin jar. That works for me as well:
> I can access all my JS files using the prefix ${resURL}/plugin/warnings-ng
>
> However, if I have resources in a library of my project, I seems to be
> that I can’t access them with ${resURL}/plugin/warnings-ng
> So what works is to extract the dependency and copy the containing JS
> files to the target folder and then pack them with the main jar. This is
> how  stapler-adjunct-jquery
> <https://github.com/stapler/stapler-adjunct-jquery> does it, but it
> is somewhat cumbersome, it would be much simpler if I can refer to the
> resources in one of my dependencies jars (i.e. in the webjar).
>
>
> Am 30.10.2019 um 16:57 schrieb Robert Sandell :
>
> Stapler has a mechanism called adjuncts that works similarly.
> For example https://github.com/stapler/stapler-adjunct-jquery
>
> /B
>
> Den lör 26 okt. 2019 kl 13:03 skrev Ullrich Hafner <
> ullrich.haf...@gmail.com>:
>
>> Has someone already used WebJars (https://www.webjars.org) in a plugin
>> to refer to JS libraries?
>>
>> While it seems to be simple to bundle it with my HPI file (it is then
>> part of the WEB-INF/lib folder) I do not see an easy way to refer to the
>> containing css/js files afterwards, since they are located in a jar file
>> that seems to be not accessible in Jenkins UI.
>>
>> I can reference my local plugin web resources with
>>
>> > ="${resURL}/plugin/warnings-ng/css/font-awesome/css/fontawesome.min.css"
>> />
>>
>> But the same does not work when the fontawesome.min.css is part of the
>> other webjar. (Or which path do I need here?)
>>
>>
>>
>>
>> --
>> 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/740C8BC3-AD97-4A4B-9148-8DF5547480F7%40gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/740C8BC3-AD97-4A4B-9148-8DF5547480F7%40gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> 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/CALzHZS3qvKA2uOSNk8thvhOxtgMAKpYMDCqrLK2V-FshvcSqYQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS3qvKA2uOSNk8thvhOxtgMAKpYMDCqrLK2V-FshvcSqYQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/26DA20F2-A3FC-477D-A6A2-D7C853ACE277%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/26DA20F2-A3FC-477D-A6A2-D7C853ACE277%40gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3Xdg-NBwCahXaXK2ykVq%2B_ZeaLgdYqCaEmXfHaJQeGew%40mail.gmail.com.

Re: How to expose WebJars with Stapler

[Robert Sandell]

Stapler has a mechanism called adjuncts that works similarly.
For example https://github.com/stapler/stapler-adjunct-jquery

/B

Den lör 26 okt. 2019 kl 13:03 skrev Ullrich Hafner :

> Has someone already used WebJars (https://www.webjars.org) in a plugin to
> refer to JS libraries?
>
> While it seems to be simple to bundle it with my HPI file (it is then part
> of the WEB-INF/lib folder) I do not see an easy way to refer to the
> containing css/js files afterwards, since they are located in a jar file
> that seems to be not accessible in Jenkins UI.
>
> I can reference my local plugin web resources with
>
>  ="${resURL}/plugin/warnings-ng/css/font-awesome/css/fontawesome.min.css"/>
>
> But the same does not work when the fontawesome.min.css is part of the
> other webjar. (Or which path do I need here?)
>
>
>
> --
> 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/740C8BC3-AD97-4A4B-9148-8DF5547480F7%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/740C8BC3-AD97-4A4B-9148-8DF5547480F7%40gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: [Jenkins-infra] wiki.jenkins.io is now effectively in read-only mode

[Robert Sandell]

And how do I mark a plugin as up for adoption without the wiki labels?

/B

Den fre 18 okt. 2019 kl 14:52 skrev Jesse Glick :

> On Fri, Oct 18, 2019 at 6:27 AM Daniel Beck  wrote:
> > I propose that we restore write access for plugin maintainers at least
> for a time, to allow them to clear out wiki pages after migrating the
> content elsewhere.
>
> Makes sense, but is there some plan to notify maintainers of plugins
> who have not done this? There are a couple thousand pages out there,
> and many people will not see mailing list notifications reliably.
>
> --
> 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/CANfRfr1k8X17Z3P%2Bs89%2BmUnUXtJW%2BiM2zMc09hPu9_AQ08_k6A%40mail.gmail.com
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: JENKINS-37557: Allow passing variables to repo SCM inside pipeline

[Robert Sandell]

I have been reviewing PRs to the repo plugin in the past, since the former
maintainers left the project. But lately I've had limited time and when I
sit down to do reviews other plugins that I maintain get higher priority
and then my time runs out again :'(
That's why I put the plugin up for adoption a few years ago hoping that
someone with more dedicated time could take over, but so far none has
volunteered.
Hopefully I can set aside some time in the coming weeks as time allows.

/B

Den fre 4 okt. 2019 kl 16:39 skrev Typz :

> Hello,
>
> I made a pull request to improve support for pipeline to the repo plugin,
> to support passing environment variable, but I still got no feedback. The
> patch is here: https://github.com/jenkinsci/repo-plugin/pull/54
>
> Can anybody give some feedback?
>
> Best regards,
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAKEkdc5JTYF7p74RentweqUzzpKh%3DaXbWrOBjC0oxhLNgJAw9Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAKEkdc5JTYF7p74RentweqUzzpKh%3DaXbWrOBjC0oxhLNgJAw9Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3iUHZxJsBtoxYcT0oxo5mAcr2zFF%2B3LKrrNRMpHu3SfQ%40mail.gmail.com.

Re: Catching a job cancel

[Robert Sandell]

If you are doing a lot of on master calculations you should either consider
moving that out to the agent (workspace.act) or, once in a while, check if
the current thread is interrupted for example on the top of every loop.

Examples of extensionpoint implementations can be found among the
documentation:
https://jenkins.io/doc/developer/extensions/jenkins-core/#runlistener

/B

Den ons 2 okt. 2019 kl 02:36 skrev John Westcott <
john.westcott...@redhat.com>:

> Thanks for the tip on this. Unfortunately, my code does more than just
> sleep its also gathering log information as well as running status checks.
> Is there anyway to put a larger try/catch block around all of that code
> rather than just the sleep method? Or a way to register an action on the
> builder itself for an on-cancel event? Or would that have to be a request
> to Jenkins core?
>
> Does anyone have an example of implementing the RunListener extension
> point?
>
> -John
>
> On Sep 30, 2019, at 5:06 AM, Robert Sandell 
> wrote:
>
> When a build is canceled the executor threads will be interrupted. So if
> your plugin is doing a remote call, waiting on something, or sleeping an
> InterruptedException will be thrown.
> Otherwise you can check the status of the current
> thread: Thread.currentThread().isInterrupted()
>
> /B
>
> Den tors 26 sep. 2019 kl 22:20 skrev Jeff Pearce :
>
>> You can probably get the info if you implement the RunListener extension
>> point
>>
>>
>>
>> *From: * on behalf of John Westcott IV <
>> jowes...@redhat.com>
>> *Reply-To: *"jenkinsci-dev@googlegroups.com" <
>> jenkinsci-dev@googlegroups.com>
>> *Date: *Thursday, September 26, 2019 at 1:17 PM
>> *To: *Jenkins Developers 
>> *Subject: *Catching a job cancel
>>
>>
>>
>> Notice: This email is from an external sender.
>>
>>
>>
>> Is it possible for a plugin to get a notification if a Jenkins job is
>> cancelled while the plugin is working?
>>
>> i.e. is there some kind of "public void on_job_cancel()" method I can
>> implement to take some action if my plugin is actively running when a job
>> is canceled?
>>
>> I'm not seeing anything in the docs but wanted to double check in case I
>> am missing something.
>>
>>
>>
>> -John
>>
>>
>>
>> --
>> 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/6296320b-1e84-4caa-9686-475650e8d334%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/6296320b-1e84-4caa-9686-475650e8d334%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/AEC405E5-912A-46E2-9FD2-84836E31A08E%40godaddy.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/AEC405E5-912A-46E2-9FD2-84836E31A08E%40godaddy.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-dev/bD22cVOyp60/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2RPku1jJR39z1_%3DLUkrKgsSvrZkBsgnMtaPZnYCmYPUA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2RPku1jJR39z1_%3DLUkrKgsSvrZkBsgnMtaPZnYCmYPUA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To vie

Re: Catching a job cancel

[Robert Sandell]

When a build is canceled the executor threads will be interrupted. So if
your plugin is doing a remote call, waiting on something, or sleeping an
InterruptedException will be thrown.
Otherwise you can check the status of the current
thread: Thread.currentThread().isInterrupted()

/B

Den tors 26 sep. 2019 kl 22:20 skrev Jeff Pearce :

> You can probably get the info if you implement the RunListener extension
> point
>
>
>
> *From: * on behalf of John Westcott IV <
> jowes...@redhat.com>
> *Reply-To: *"jenkinsci-dev@googlegroups.com" <
> jenkinsci-dev@googlegroups.com>
> *Date: *Thursday, September 26, 2019 at 1:17 PM
> *To: *Jenkins Developers 
> *Subject: *Catching a job cancel
>
>
>
> Notice: This email is from an external sender.
>
>
>
> Is it possible for a plugin to get a notification if a Jenkins job is
> cancelled while the plugin is working?
>
> i.e. is there some kind of "public void on_job_cancel()" method I can
> implement to take some action if my plugin is actively running when a job
> is canceled?
>
> I'm not seeing anything in the docs but wanted to double check in case I
> am missing something.
>
>
>
> -John
>
>
>
> --
> 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/6296320b-1e84-4caa-9686-475650e8d334%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/6296320b-1e84-4caa-9686-475650e8d334%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/AEC405E5-912A-46E2-9FD2-84836E31A08E%40godaddy.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/AEC405E5-912A-46E2-9FD2-84836E31A08E%40godaddy.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: Doubt in Scheduling freestyle project

[Robert Sandell]

project.getTrigger(TimerTrigger.class) != null


Den ons 18 sep. 2019 kl 15:02 skrev selva vignesh :

> Hi,
> Is there any method available to check to find whether cron has been
> enabled in freestyle project.
> 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/3fe4d6f8-ed02-46a1-8d6f-5cecd2bf3dc6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/3fe4d6f8-ed02-46a1-8d6f-5cecd2bf3dc6%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

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

Re: Preparing to Hacktoberfest 2019 in Jenkins. Join us!

[Robert Sandell]

com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Area Meetup Coordination" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-jam+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-jam/CAPiUgVcU%2BP_ocDxSCV-w6HJFdV8yxHWFMX3_dOULWUix8ONGGw%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-jam/CAPiUgVcU%2BP_ocDxSCV-w6HJFdV8yxHWFMX3_dOULWUix8ONGGw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Zhao Xiaojie (Rick)
>> Blog: https://github.com/LinuxSuRen
>> Twitter: https://twitter.com/suren69811254
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Advocacy and Outreach SIG" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkins-advocacy-and-outreach-sig+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAMM7nTFD_4NFv1eskg09jYzaFRhF380xkE2gJrtc1t2RFQJ14g%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkins-advocacy-and-outreach-sig/CAMM7nTFD_4NFv1eskg09jYzaFRhF380xkE2gJrtc1t2RFQJ14g%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
>
> *Vernin Olivier* Senior Operation Engineer CloudBees, Inc.
>
> <http://goog_803972313>
>
> [image: CloudBees-Logo.png] <http://www.cloudbees.com>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Area Meetup Coordination" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-jam+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-jam/CANOy8r-7uPt%3DpWUVVS-4Ho_UUbq%2BU3nn%2BJbsU7ZNYsw-JSYT%3Dg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-jam/CANOy8r-7uPt%3DpWUVVS-4Ho_UUbq%2BU3nn%2BJbsU7ZNYsw-JSYT%3Dg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0OYY%3DkaTnWd-FHG1ZNb%2Bhz5NduXsmjvLi6n%2BCn3bG8gQ%40mail.gmail.com.

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

[Robert Sandell]

t;>> we also use https://www.jsdelivr.com/ as a CDN for images. If you hit
>>>> any issue, please file a ticket in the WEBSITE-637 EPIC.
>>>> >
>>>> > How to enable GitHub documentation for your plugin?
>>>> >
>>>> > Move documentation from Wiki to GitHub README if you have not done it
>>>> yet. Both Markdown and Asciidoc are supported
>>>> > Change the  field in pom.xml so that it points to GitHub
>>>> (example PR)
>>>> > Release a new plugin version
>>>> > Wait for few hours till the change gets propagated
>>>> >
>>>> > Code? If you want to see the changes under the hood of the plugin
>>>> site, please see the links in Plugin Site API v1.6.0 (yes, now we have
>>>> changelog there!). So far we needed only the backend changes to add the
>>>> feature, but there will be front-end changes for other stories inside the
>>>> EPIC. If you are a Java or JavaScript/React developer, any contributions
>>>> will be appreciated. The plugin site is really easy to develop.
>>>> >
>>>> > Credits. I would like to thank Zbynek Konecny and Olivier Vernin for
>>>> their work on these stories. They have done the vast majority of changes to
>>>> make it happen.
>>>> >
>>>> > If you have any questions/feedback, please do not hesitate to answer
>>>> in this thread or to join the https://gitter.im/jenkinsci/docs chat.
>>>> We will also have sync-ups and demos at the regular Documentation SIG
>>>> meetings.
>>>> >
>>>> > Best regards,
>>>> > Oleg Nenashev
>>>> >
>>>> > --
>>>> > You received this message because you are subscribed to the Google
>>>> Groups "Jenkins Developers" group.
>>>> > To unsubscribe from this group and stop receiving emails from it,
>>>> send an email to jenkin...@googlegroups.com.
>>>> > To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com
>>>> .
>>>>
>>>>
>>>>
>>>> --
>>>> Matt Sicker
>>>> Senior Software Engineer, CloudBees
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Jenkins Developers" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to jenkin...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com
>>>> .
>>>>
>>>
>>>
>>> --
>>> Zhao Xiaojie (Rick)
>>> Blog: https://github.com/LinuxSuRen
>>> Twitter: https://twitter.com/suren69811254
>>>
>>> --
>>> 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/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.

Re: How to get current running job name without build number?

[Robert Sandell]

If your code is running in an http request thread, which it normally is
when a user is visiting a config page you can ask Stapler for the current
ancestor path;

Stapler.getCurrentRequest().findAncestorObject(Job.class)


/B

Den sön 11 aug. 2019 kl 09:57 skrev Navnath Kumbhar :

> Thank you Gavin. But I want this job name when I am in job config page.
> And there I do not have "run" object. This is the scenario. Is there any
> other alternative that I use to get job name when I am inside the config
> page?
>
> On Sunday, 11 August 2019 12:43:41 UTC+5:30, Gavin Mogan wrote:
>>
>> Inside of
>> https://github.com/jenkinsci/reqtify-plugin/blob/master/src/main/java/io/jenkins/plugins/ReqtifyGenerateReport.java#L220-L280
>>
>> You can call run.getId() will give you the build Id
>> run.getParent().getId()
>>
>> https://javadoc.jenkins-ci.org/hudson/model/Run.html#getId--
>>
>> I'm not sure where you are not having the build number.
>>
>>
>> On Sat, Aug 10, 2019 at 11:54 PM Navnath Kumbhar 
>> wrote:
>>
>>> No, it is not a pipeline plugin. It is simple plugin with which adds a
>>> custom build step. Link to wiki :
>>> https://wiki.jenkins.io/display/JENKINS/Reqtify+Plugin
>>>
>>> On Saturday, 10 August 2019 21:58:35 UTC+5:30, Gavin Mogan wrote:
>>>>
>>>> In what context? Are you building a pipeline plugin? You should have
>>>> access to just about everything.
>>>>
>>>> On Sat., Aug. 10, 2019, 5:04 a.m. Navnath Kumbhar, 
>>>> wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I want to get my current running job name without build number.
>>>>> [Because I do not have build number]
>>>>> How can I do that?
>>>>>
>>>>> Thank you 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 jenkin...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/cc54491c-6123-4517-a016-615c209e7a1e%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/cc54491c-6123-4517-a016-615c209e7a1e%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkin...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/217e7825-fda6-420b-ba5f-b640ab6cf1a4%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/217e7825-fda6-420b-ba5f-b640ab6cf1a4%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/1dd02966-7c54-4e56-8fda-c18f8b4b0aaf%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1dd02966-7c54-4e56-8fda-c18f8b4b0aaf%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS27y6-_Ebb7iqPX19QXK-sLtVQzbvb4sw7d9MFp6W%2BxVg%40mail.gmail.com.

Re: FilePath.act question

[Robert Sandell]

Probably missed the generics on FileCallable

 implements FileCallable> {

though you should probably use MasterToSlaveFileCallable instead of the
base one.

/B

Den ons 12 juni 2019 kl 11:22 skrev varun vikas :

> @old hooky
>>
> what should be return type of
>
> public List invoke(File ws, VirtualChannel channel) function.
> Here it is throwing error , attempting to use incompatible return type.
>
> I have defined a inner class
>  private static final class  AttachmentLister implements FileCallable{
> @override
> public List invoke(File ws, VirtualChannel channel){
> }
> }
>
> Note: I want to return invoke function a list, but it is giving
> error...how to handle it.
>
> --
> 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/bd7502bb-8376-45fd-86c4-87c6ebfb2747%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/bd7502bb-8376-45fd-86c4-87c6ebfb2747%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1Fuw7TbhNsEbLQmguGgVAsyJtQoZ%3DsP7VswRAgu1h%3D-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal - Phasing out Java 7 support in Jenkins Dev tools

[Robert Sandell]

+1
I thought we already had dropped Java 7 support in the tooling :/

/B

Den mån 3 juni 2019 kl 15:58 skrev Mark Waite :

>
>
> On Mon, Jun 3, 2019 at 7:38 AM Jesse Glick  wrote:
>
>> On Mon, Jun 3, 2019 at 9:27 AM Oleg Nenashev 
>> wrote:
>> > a green light to whomever wants to drop old Java version support from
>> Dev tools
>>
>> +1. I see no reason to waste core dev time handling obsolete
>> platforms. If some plugin maintainer insists on providing support for
>> very old core lines for whatever reason, they can create a backport
>> branch, or simply decline to update tool versions, but it is
>> appropriate for all plugins in the Setup wizard’s recommended list to
>> use a 2.60.x or newer baseline and use current tooling.
>>
>>
> +1 from me as well.
>
>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr17qrqwOuzQu27U-WHxmjKqYuYFbdxRGKooj4ovfZRmQQ%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> 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/CAO49JtEmSgUwOx236tCPTa1tWu-6PFef22%3DCw%3DX5_WfSZSTkAQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEmSgUwOx236tCPTa1tWu-6PFef22%3DCw%3DX5_WfSZSTkAQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1FX_h5P0pEEKhnnNh2m9HmzVkAfGJkSfmi1pL8cZY%2Bkw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal - Introducing Global Probot configuration for Release Drafter and other tools

[Robert Sandell]

+1 I've been hoping we do something like this for a while now but haven't
come up with anything myself :)

Though it states on the Release Draft App page
<https://github.com/apps/release-drafter>: "Release Drafter requires full
write, because GitHub does not offer a limited scope for only writing
releases. *Don't install Release Drafter to your entire GitHub account* —
only add the repositories you want to draft releases on."

/B

Den tors 23 maj 2019 kl 10:38 skrev Oleg Nenashev :

> Hi all,
>
> Just another GitHub infrastructure thread is here. There is a number of
> components which started using Release Drafter
> <https://github.com/toolmantim/release-drafter> to automate management of
> releases notes. Basically, this tool generates changelog drafts using pull
> request metadata (commit headers, links, etc.). It is one of examples of
> many Probot-based GitHub applications <https://probot.github.io/apps/>
> which could help plugin maintainers and improve the contributor experience
> within the organization.
>
> Release Drafter usage examples:
>
>- Configuration As Code Plugin
><https://github.com/jenkinsci/configuration-as-code-plugin/releases>
>- BlueOcean Plugin
><https://github.com/jenkinsci/blueocean-plugin/releases>
>- Slack Plugin <https://github.com/jenkinsci/slack-plugin/releases>
>- BitBucket Branch Source Plugin
><https://github.com/jenkinsci/bitbucket-branch-source-plugin/releases>
>- Jenkinsfile Runner
>
> <https://github.com/jenkinsci/jenkinsfile-runner/blob/master/CHANGELOG.md#10-beta-8---2019-05-18>
>
> All components use pretty similar configuration files and labeling
> strategies. For example, here is a Jenkinsfile Runner configuration file
> <https://github.com/jenkinsci/jenkinsfile-runner/blob/master/.github/release-drafter.yml>.
> You may see that this file defines labels, replacement logic for Jenkins
> JIRA and CVE references, etc. Copy-paste across repositories is
> problematic.Good news is that we could define configs on the org-wide basis.
>
> Release Drafter is based on the Probot framework
> <https://probot.github.io/> for GitHub apps. Probot allows managing
> application configs on the org-level by introducing a new system config
> repository (documentation
> <https://github.com/probot/probot-config/blob/master/README.md>).
> Configurations can be then overridden by repositories if needed.
>
> What do I propose?
>
>1. Create a Probot global configuration repository
>2. Add a sample Release Drafter configuration there. It will be
>reviewed together with all current users so that we come up with a
>convenient Release Drafter configuration
>3. Open discussion for other GitHub applications being used in
>jenkinsci. We could have global configs there as well
>
> Would appreciate any feedback. If there is a consensus about having such
> global configuration repo, I am happy to implement it.
>
> BR, Oleg
>
>
>
>
>
>
>
>
>
> --
> 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/CAPfivLDA%3DmXpKMz%3Dmo6qTYaAcrj56d0xJjQzOV2MtewdeCpgWA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLDA%3DmXpKMz%3Dmo6qTYaAcrj56d0xJjQzOV2MtewdeCpgWA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2%3DaU8EOdjbpDVRsnfx2CWCsdNyKoyQR1WmbtNLJpD5Vw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Pipeline snippet generator: How to format generated snippet text?

[Robert Sandell]

You need a config.jelly (and help-field.html) file for your step and the
rest should be done for you by magic.

/B

Den tis 21 maj 2019 kl 22:33 skrev Martin Weber :

> Hi all,
>
> I see the snippet generator prints a nicely formatted code for the withEnv
> step.
> How can I tell the snippet generator to do that for my pipeline step, too?
> Any pointer to docs or code are welcome.
>
> Martin
>
> --
> Cd wrttn wtht vwls s mch trsr.
>
>
>
>
> --
> 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/2361528.TRu7gUjnlG%40linux
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1QO7fTE7zmJD901ZHYkBPauWVvAAEgSewu_GkN88TC4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Seeking information about GitHub Branch Source Plugin

[Robert Sandell]

I'd suggest you first take inspiration from the Gitea plugin
<https://github.com/jenkinsci/gitea-plugin>, last time I checked it had the
most clean branch-api implementation. GitHub Branch Source and Bitbucket
Branch Source are suffering from a couple of branch-api/scm-api generations
of rewrites that can "muddy the waters a bit" when looking at writing a new
plugin :)

/B

Den sön 19 maj 2019 kl 18:19 skrev Parichay Barpanda <
parichay.barpa...@gmail.com>:

> Thanks batmat for the answers.
>
> On Sun 19 May, 2019, 21:27 Baptiste Mathus,  wrote:
>
>>
>>
>> Le mer. 15 mai 2019 à 22:17, Parichay Barpanda <
>> parichay.barpa...@gmail.com> a écrit :
>>
>>> Hi all,
>>>
>>> I was reading the GitHub Branch Source Plugin documentation here -
>>> https://go.cloudbees.com/docs/plugins/github-branch-source/ trying to
>>> take some inspiration from *GitHub Branch Source Plugin* for a similar 
>>> *GitLab
>>> Branch Source Plugin*.
>>>
>>> Here are a few questions I would like to ask:
>>>
>>> 1) An excerpt from the GitHub PR section:
>>>
>>>  “Pull requests will be added to Jenkins as long as the pull request
>>> originates from a remote repository, contains a Pipeline script in a
>>> Jenkinsfile, and is mergable.
>>> *Even when you make changes to your Jenkinsfile, the checked out code is
>>> at the revision as the script.*”
>>>
>>> What does the last line mean?
>>>
>>
>> Not sure TBH.
>>
>>
>>> 2) While running a GitHub folder organisation on my GitHub Account,
>>> build log shows the following:
>>>
>>> “...*19:25:39 GitHub API Usage: Current quota has 51 remaining (2 over
>>> budget). Next quota of 60 in 59 min. Sleeping for 6 min 48 sec*.”
>>>
>>> And the build simply pauses. What is the possible issue here?
>>>
>>
>> Not an issue. More a feature IIUC your question.
>> GitHub API has a quota. So if you hammer it too much, your code will
>> simply start failing (and it did).
>> So like 1 year ago, the code was optimized (thanks Stephen and CloudBees
>> sponsoring this) to do less calls and to introduce waits when quota was
>> about to be reached.
>>
>>>
>>> 3) Are there any important additions made to the plugin since the
>>> documentation was written? A list of classes would also do, I specifically
>>> want to look at their codes.
>>> I can find some UI changes in behaviours (recent plugin wrt
>>> documentation pictures), don't see the folder computation option etc.
>>> Looking for any interesting changes which can be leveraged by new Branch
>>> Source Plugins?
>>>
>>
>> Not sure for this. I'd recommend you check PRs since then and check how
>> much/if docs were added alongside code additions. And don't hesitate to ask
>> for clarifications in these merged PRs to be able to possibly file related
>> docs PRs.
>>
>> Thanks!
>>
>>>
>>> Thanks.
>>>
>>> Regards,
>>> Parichay (baymac)
>>>
>>>
>>> --
>>> 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/d4215d95-55d5-4322-b945-1b272fc512df%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d4215d95-55d5-4322-b945-1b272fc512df%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Nvj_%2B_pw-rqS36tgb7JwPcAnKpAQuT9WLDyYwxFyU2Q%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS6Nvj_%2B_pw-rqS36tgb7JwPcAnKpAQuT9WLDyYwxFyU2Q%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" gro

Re: PR build for crawler has been running for 16+ hours

[Robert Sandell]

You might get better response on the infra mailing list or IRC channel.
https://jenkins.io/mailing-lists/

/B

Den tis 14 maj 2019 kl 18:34 skrev Mads Mohr Christensen :

> Looks like it’s Oracle that has introduced an error on
> http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
>  and
> this is causing the jdk crawler to stall the build.
>
> /M
>
>
> On 14 May 2019, at 15.43, Mads Mohr Christensen  wrote:
>
> I’ve been granted rights to execute the initial release of my new plugin
> that uses this crawler, https://github.com/jenkinsci/adoptopenjdk-plugin,
> but the PR build still appears to be stalled.
>
> Once the crawler PR has been merged I will execute the initial release.
>
> /M
>
> On 13 May 2019, at 10.44, Mads Mohr Christensen  wrote:
>
> I opened a PR for the crawler yesterday and the test job has been running
> for 16+ hours now.
>
>
> https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fcrawler/detail/PR-81/1/pipeline
> <https://ci.jenkins.io/blue/organizations/jenkins/Infra/crawler/detail/PR-81/1/pipeline>
>
> Can somebody please have a look?
>
> /M
>
>
>
> --
> 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/F9524F5F-15D1-4E44-B433-C8AD5B6DDE91%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/F9524F5F-15D1-4E44-B433-C8AD5B6DDE91%40gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2%2BFfGbdQEc5UTG%2B12%2B1%2B0NOQPOok97utJ9ky8BJzWe%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failsafe test reports for my Jenkins plugin are ignored on ci.jenkins.io

[Robert Sandell]

That repository is open to pull requests ;)

/B

Den ons 15 maj 2019 kl 10:39 skrev Ullrich Hafner :

> I simply copied the buildPlugin step content into my JenkinsFile and
> modified it accordingly. This was also the only way to enable the warnings
> next generation plugin and some other tools (like coverage and pitest).
>
> Examples:
> https://github.com/jenkinsci/analysis-model/blob/master/Jenkinsfile
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/Jenkinsfile
>
>
> Am 14.05.2019 um 19:42 schrieb Chris Kilding <
> chris+jenk...@chriskilding.com>:
>
> The standard ‘buildPlugin()’ Jenkinsfile directive appears to capture
> Surefire test reports, but not Failsafe test reports. This means that
> failing integration tests in my plugin are (a) unreported and (b) don’t
> break the build. This might be happening to other plugins too.
>
> The line of code in question is probably this:
> https://github.com/jenkins-infra/pipeline-library/blob/66a14842e350bd5364a1a70ca4287535cacc0390/vars/buildPlugin.groovy#L118
>
> I’ve worked around it by saving the Failsafe reports to the Surefire
> directory but this is extremely fragile: if I have an integration test
> class with the same name and package as a unit test class (which could
> happen if integration tests are stored in a different test source
> directory), then the report for one could overwrite the other.
>
> Could someone confirm whether this is indeed a limitation in the current
> buildPlugin.groovy script or whether there is a different (robust) way to
> pick up Failsafe reports on ci.jenkins.io?
>
> Regards
>
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/448e67fa-aef8-48bd-9ce7-cdbf7a7d5b7f%40www.fastmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/448e67fa-aef8-48bd-9ce7-cdbf7a7d5b7f%40www.fastmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/465C7830-6BA3-4EEA-B3BE-964F455E9F3D%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/465C7830-6BA3-4EEA-B3BE-964F455E9F3D%40gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3Zzxdx0eT2FpCPAY6OyaWg24-T-98FyJaiFgBZrXsV%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Included and Excluded Regions/Paths in a Multi Branch Pipeline

[Robert Sandell]

Den tis 14 maj 2019 kl 22:55 skrev Peter Goodman :

> Searching for implementations I've found one that was first released 12
> days ago
>
> https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin
> https://plugins.jenkins.io/multibranch-build-strategy-extension
>
> Looks like I can just use this one.
>
> Do you know of a way that I can make a plugin like this configurable from
> a declarative pipeline?
>

No, all the multibranch stuff is part of discovering and creating jobs for
Jenkinsfiles, so it all runs before any Jenkinsfile. If you want that
configuration in source control it's either the Configuration as Code
plugin or Job DSL.



>
> On Tuesday, 14 May 2019 22:38:56 UTC+12, Robert Sandell wrote:
>>
>> Then perhaps implementing a BranchBuildStrategy
>> <https://javadoc.jenkins.io/plugin/branch-api/jenkins/branch/BranchBuildStrategy.html>
>> is what you are looking for?
>>
>> Implementation examples are in basic-branch-build-strategies-plugin, ex:
>> https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/047ecb6fb183179221361072daf4ecc27dcfdbe0/src/main/java/jenkins/branch/buildstrategies/basic/BranchBuildStrategyImpl.java
>>
>> /B
>>
>> Den tis 14 maj 2019 kl 02:20 skrev Peter Goodman :
>>
>>> Thanks so much for your reply.
>>>
>>> We have a number of mono-repos which have multiple pipelines in them.
>>> For any one pipeline I want to only trigger if the files that are changed
>>> are beneath certain paths. Imagine many microservices in each repo. Though
>>> I'm not here to debate this approach.
>>>
>>> I have created an *SCMHeadFilter* which works well in some scenarios.
>>> For a pull request I can just cast the SCMHead as "*PullRequestSCMHead*"
>>> and figure out what files were changed in the Pull Request. It's not
>>> necessarily checking every commit since the last build but this works
>>> pretty well for us.
>>> For the master branch, I really want to check all the commits since the
>>> last build on this branch rather than just the current HEAD commit, how
>>> could I get that list of commits and perform that check?
>>>
>>> The original git plugin seems to have a feature that it calls "included
>>> and excluded regions" which seems like it would do the thing that i need
>>> but this isn't available in the Multi Branch Git version.
>>> https://medium.com/@abhijeetahuja/jenkins-polling-ignores-commits-in-certain-paths-aeb2927b0e7a
>>> I was hoping I could set this by configuring the GitSCMBuilder but the
>>> properties are not available.
>>>
>>> I also looked at adding a BuildChooser but this gets overwritten in the
>>> builder.
>>>
>>> I also looked at implementing *isRevExcluded* in a *GitSCMExtension* but
>>> that gets me to the same place of evaluating a single commit at HEAD rather
>>> than the commits since last build.
>>>
>>> Pete
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Monday, 13 May 2019 23:09:41 UTC+12, Robert Sandell wrote:
>>>>
>>>> I'm not sure I understand what you are trying to achieve with "Included
>>>> and Excluded Regions (paths)"?
>>>> SCMHeadFilter filters if the supplied SCMHead should be there or not.
>>>> In your case if you would return false for the master branch it would not
>>>> create a job for that branch. And if it already had a job it will be marked
>>>> as dead and removed when the orphaned item strategy kicks in.
>>>>
>>>> /B
>>>>
>>>> Den sön 12 maj 2019 kl 15:56 skrev Peter Goodman :
>>>>
>>>>> Hi,
>>>>> I'm trying to add an extension which will enable Included and Excluded
>>>>> Regions (paths) for Multi Branch GitHub pipelines.
>>>>>
>>>>> I can do this relatively simply using a *SCMHeadFilter* which works
>>>>> for pull requests because I can get the files changed in the entire pull
>>>>> request. For master though I would really only want to consider those
>>>>> commits since the last build.
>>>>>
>>>>> How can I figure that out in the
>>>>> SCMHeadFilter.isExcluded(SCMSourceRequest scmSourceRequest, SCMHead
>>>>> scmHead) method? Or is there another way to somehow set this on the
>>>>> underlying GitSCMBuilder when it is being built?
>>>>>
>>>>> Thanks,
>>>>> Pete
>

Re: Included and Excluded Regions/Paths in a Multi Branch Pipeline

[Robert Sandell]

Then perhaps implementing a BranchBuildStrategy
<https://javadoc.jenkins.io/plugin/branch-api/jenkins/branch/BranchBuildStrategy.html>
is what you are looking for?

Implementation examples are in basic-branch-build-strategies-plugin, ex:
https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/047ecb6fb183179221361072daf4ecc27dcfdbe0/src/main/java/jenkins/branch/buildstrategies/basic/BranchBuildStrategyImpl.java

/B

Den tis 14 maj 2019 kl 02:20 skrev Peter Goodman :

> Thanks so much for your reply.
>
> We have a number of mono-repos which have multiple pipelines in them. For
> any one pipeline I want to only trigger if the files that are changed are
> beneath certain paths. Imagine many microservices in each repo. Though I'm
> not here to debate this approach.
>
> I have created an *SCMHeadFilter* which works well in some scenarios.
> For a pull request I can just cast the SCMHead as "*PullRequestSCMHead*"
> and figure out what files were changed in the Pull Request. It's not
> necessarily checking every commit since the last build but this works
> pretty well for us.
> For the master branch, I really want to check all the commits since the
> last build on this branch rather than just the current HEAD commit, how
> could I get that list of commits and perform that check?
>
> The original git plugin seems to have a feature that it calls "included
> and excluded regions" which seems like it would do the thing that i need
> but this isn't available in the Multi Branch Git version.
> https://medium.com/@abhijeetahuja/jenkins-polling-ignores-commits-in-certain-paths-aeb2927b0e7a
> I was hoping I could set this by configuring the GitSCMBuilder but the
> properties are not available.
>
> I also looked at adding a BuildChooser but this gets overwritten in the
> builder.
>
> I also looked at implementing *isRevExcluded* in a *GitSCMExtension* but
> that gets me to the same place of evaluating a single commit at HEAD rather
> than the commits since last build.
>
> Pete
>
>
>
>
>
>
> On Monday, 13 May 2019 23:09:41 UTC+12, Robert Sandell wrote:
>>
>> I'm not sure I understand what you are trying to achieve with "Included
>> and Excluded Regions (paths)"?
>> SCMHeadFilter filters if the supplied SCMHead should be there or not. In
>> your case if you would return false for the master branch it would not
>> create a job for that branch. And if it already had a job it will be marked
>> as dead and removed when the orphaned item strategy kicks in.
>>
>> /B
>>
>> Den sön 12 maj 2019 kl 15:56 skrev Peter Goodman :
>>
>>> Hi,
>>> I'm trying to add an extension which will enable Included and Excluded
>>> Regions (paths) for Multi Branch GitHub pipelines.
>>>
>>> I can do this relatively simply using a *SCMHeadFilter* which works for
>>> pull requests because I can get the files changed in the entire pull
>>> request. For master though I would really only want to consider those
>>> commits since the last build.
>>>
>>> How can I figure that out in the
>>> SCMHeadFilter.isExcluded(SCMSourceRequest scmSourceRequest, SCMHead
>>> scmHead) method? Or is there another way to somehow set this on the
>>> underlying GitSCMBuilder when it is being built?
>>>
>>> Thanks,
>>> Pete
>>>
>>> --
>>> 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/0c5e2277-a35d-4d6c-a342-45cb6d6951c1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/0c5e2277-a35d-4d6c-a342-45cb6d6951c1%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> *Robert Sandell*
>> Software Engineer
>> CloudBees, Inc.
>> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
>> E: rsan...@cloudbees.com
>> Twitter: robert_sandell
>>
> --
> 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/d77a17af-2880-43e0-9bc9-f1963b4ed043%40googlegroups.c

Re: Included and Excluded Regions/Paths in a Multi Branch Pipeline

[Robert Sandell]

I'm not sure I understand what you are trying to achieve with "Included and
Excluded Regions (paths)"?
SCMHeadFilter filters if the supplied SCMHead should be there or not. In
your case if you would return false for the master branch it would not
create a job for that branch. And if it already had a job it will be marked
as dead and removed when the orphaned item strategy kicks in.

/B

Den sön 12 maj 2019 kl 15:56 skrev Peter Goodman :

> Hi,
> I'm trying to add an extension which will enable Included and Excluded
> Regions (paths) for Multi Branch GitHub pipelines.
>
> I can do this relatively simply using a *SCMHeadFilter* which works for
> pull requests because I can get the files changed in the entire pull
> request. For master though I would really only want to consider those
> commits since the last build.
>
> How can I figure that out in the SCMHeadFilter.isExcluded(SCMSourceRequest
> scmSourceRequest, SCMHead scmHead) method? Or is there another way to
> somehow set this on the underlying GitSCMBuilder when it is being built?
>
> Thanks,
> Pete
>
> --
> 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/0c5e2277-a35d-4d6c-a342-45cb6d6951c1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/0c5e2277-a35d-4d6c-a342-45cb6d6951c1%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0WTbAoSGyk0%2BFz%3D-d6oxZHx3_6sLPTrwRhKD9N0zouqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [INFRA-2086] - Switching ci.jenkins.io builds to AdoptOpenJDK

[Robert Sandell]

If I read the migration guide on the AdoptOpenJDK correctly it states that
there is no Java Web start replacement for Java 8. don't we have some Java
Web Start code at least in core for agent launching? Or maybe that's not a
compile time dependency?

/B

Den fre 3 maj 2019 kl 08:36 skrev Joseph P :

> Sounds perfectly reasonable to me 
> We use AdoptOpenJDK at work too.
>
> --
> 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/4ded0ddd-9966-4467-bae4-df573c17a38e%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0O44DTiPBOJCbPX49KHugMGk3HasQghnJd4eXzFCaz9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrate a token stored in plain text to one that uses Secret

[Robert Sandell]

Maybe you can try and report the job to the old data monitor somehow?
That way an admin can batch save the affected jobs, I think :)

/B

Den tors 18 apr. 2019 kl 12:44 skrev Slide :

> Did you mark the old field as transient in your code? If you mark it as
> transient and have a readResolve, it shouldn't get resaved once the upgrade
> happens.
>
> On Wed, Apr 17, 2019 at 11:53 PM Mez Pahlan  wrote:
>
>> Morning
>>
>> I'm trying to migrate a plugin that used to use plain text for handling
>> tokens to one that uses Secret. I am following
>> https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility
>>  and
>> have converted all my field types to Secret from String for the token in
>> question.
>>
>> This all works fine when I run the plugin (I think the readResolve method
>> is doing some magic at runtime) and if I create a new job configuration (I
>> can see an encrypted form of my entered token in the config.xml file).
>> However for existing jobs that already that an unencrypted plain text token
>> in the config.xml it remains that way and appears never to get resaved in
>> the encrypted form. So whilst the plugin uses Secrets, there is still old
>> data that is persisted in plain text form.
>>
>> What's the best way to migrate those over without asking the user to go
>> into each of their jobs updating it?
>>
>> --
>> 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/f532cd94-4af2-4c13-bdb9-7a94e024620d%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/f532cd94-4af2-4c13-bdb9-7a94e024620d%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Website: http://earl-of-code.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/CAPiUgVfFWwkECj9FSFToVGnATFasOAVr2iBrE%3DiZnFi5YVePgg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfFWwkECj9FSFToVGnATFasOAVr2iBrE%3DiZnFi5YVePgg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1%3DzFERENWFA7O8MEiY7Y_NZ%3DQMziz5FriyUY4aC8g48g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: When using the dir step in a Jenkins pipeline is there any way to get that value from a step within?

[Robert Sandell]

I'm not sure I understand the question completely. But the FilePath object
in the step context will be what the current working directory is. So if
your step is called inside a dir step then the FilePath will be that
directory otherwise it will be the workspace, or null if the step gets
called outside of a node step.
So you don't need to know if you are inside a dir step, just that there is
a FilePath to use.
https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java#L90-L93

/B

Den ons 17 apr. 2019 kl 12:22 skrev Daniel Anechitoaie <
daniels0...@gmail.com>:

> I'm working on Jenkins pipeline plugin that generates some paths relative
> to the workspace at the moment.
> But sometimes I need to wrap my plugin with dir -
> https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/PushdStep.java
>  step.
> Is there any way from within my plugin to know if it was wrapped by the
> "dir" step plugin so I can use that dir as a relative path vs if it was not
> in which case I should use the workspace as a relative path?
>
> --
> 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/5ce71f78-8765-4471-b9b1-31d118c43e83%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/5ce71f78-8765-4471-b9b1-31d118c43e83%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2p%3DvW5f3zdK-1%3DrAGRJSiE%2BEB6X5RZrsm7MyZSfM6Kjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Calling Java from jenkinsfile to parse XML

[Robert Sandell]

A quick google search revealed the following interesting articles

https://www.mkyong.com/java/sax-error-content-is-not-allowed-in-prolog/
https://stackoverflow.com/questions/3030903/content-is-not-allowed-in-prolog-when-parsing-perfectly-valid-xml-on-gae

In your plugin are you performing the parsing on the master or on the agent
(via for example file.act(...)) It shouldn't make any difference but maybe
some dirty data is suffixed in the transfer or something?

/B

Den tors 11 apr. 2019 kl 17:50 skrev Matt Q :

> I am trying to call some Java code in our plugin from the jenkinsfile to
> parse XML (I have been able to parse it in the jenkinsfile but would like
> to abstract the implementation from the pipeline). I am passing an XML file
> to a method that works fine when this file is passed from within the plugin
> code but fails when I pass the very same file from the pipeline:
>
> Exception: Content is not allowed in prolog.
>
> There is no content in the prolog:
>
> 
> 
>   
>   ...
>
> I have checked that the file is encoded in UTF-8 and several other
> suggestions but this error persists. Is this a known issue when trying to
> invoke Java from the pipeline? I can't figure out why the same code is
> behaving differently when invoked this way.
>
> -Matt
>
> --
> 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/279d5d75-cad5-4abe-82d0-ab438b82c056%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/279d5d75-cad5-4abe-82d0-ab438b82c056%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3iVryZKU-3ik8GAdgGWmucjqaBw8kXi8EknaqSUBnZdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blueocean generator for Blueocean plugin development

[Robert Sandell]

Perhaps someone could take over the BO archetype PR and get it merged?
https://github.com/jenkinsci/archetypes/pull/24

/B

Den tis 19 mars 2019 kl 18:15 skrev Parichay Barpanda <
parichay.barpa...@gmail.com>:

> Hi Keith,
>
> Thanks for the help. I needed this for one of my stretch goals for GSoC
> '19 which is to implement an artifact that extends *GitLab* branch source
> plugin into Blue ocean.
>>
>>
> Regards,
> Parichay (baymac)
>
> --
> 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/ae003cf8-3e23-4120-8e57-ab89a55cfe7f%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/ae003cf8-3e23-4120-8e57-ab89a55cfe7f%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2kq_WvA%2Bk3ZHNfYKYCkqF4XuCSCSZTTYr1rwmZMqToMw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Update center contains git release candidate that is not good enough

[Robert Sandell]

Adding -rc releases to the experimental update center might be a thing we
should do?

/B

Den tors 7 feb. 2019 kl 13:05 skrev Mark Waite :

> Thanks very much!  Change reviewed and approved
>
> On 2/7/19, Baptiste Mathus  wrote:
> > Hello Mark,
> >
> > I've filed the PR on your behalf:
> > https://github.com/jenkins-infra/update-center2/pull/258
> > If you have a quick look to approve, to check I didn't forget anything.
> >
> > Please enjoy your vacation. We all know the hard work you're putting from
> > your personal time into the git plugins. I am deeply sorry about the bad
> > behavior of some entitled users who report their issue in an unacceptable
> > way.
> >
> > Thanks!
> >
> > Le jeu. 7 févr. 2019 à 08:35, Mark Waite  a
> > écrit :
> >
> >> I am on a much needed family vacation. Before leaving on that vacation,
> I
> >> wanted to deliver the latest pre-release of the git client plugin and
> the
> >> git plugin.  I chose a version string 3.0.0-rc for the git client and
> >> 4.0.0-rc for the git plugin.
> >>
> >> Unfortunately, that version string caused the release to appear in the
> >> update center in addition to the experimental update center.
> >>
> >> I'm grateful for the feedback from early adopters, even if some of the
> >> sarcasm feels a bit heavy handed.
> >>
> >> If it is feasible, I would like to pull git plugin 4.0.0-rc and git
> >> client
> >> plugin 3.0.0-rc from the update center. Is that feasible?
> >>
> >> My sincere apologies to the users suffering due to my choice of version
> >> string and my failure to read the experimental update center
> >> documentation
> >> closely enough.
> >>
> >> 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/CAO49JtF1DWabYBGT9fHz%3D81cZd0vTy-yd7Xw_V3eQTRb5Bno2g%40mail.gmail.com
> >> <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtF1DWabYBGT9fHz%3D81cZd0vTy-yd7Xw_V3eQTRb5Bno2g%40mail.gmail.com?utm_medium=email_source=footer
> >
> >> .
> >> For more options, visit https://groups.google.com/d/optout.
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Jenkins Developers" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to jenkinsci-dev+unsubscr...@googlegroups.com.
> > To view this discussion on the web visit
> >
> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7Tj5Er_fnDNteC1fQoOpYRXfhJ7ikFNRsmmpKdSCjhFg%40mail.gmail.com
> .
> > For more options, visit https://groups.google.com/d/optout.
> >
>
>
> --
> 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/CAO49JtHxJqPO%2BKTnse%3D5MQ%3DXy1n-AqA9FMNGTSbkZ3eaGmw5uw%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1HOYzQhj%2Bp3Vh2%2BK8JoRJhvF%3Dwf1cF%2B1sQJwr68765xw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Localization plugins: Where do we go from here?

[Robert Sandell]

Is the intention to move all translations from core and plugins into these
new localisation plugins? Looking at
https://github.com/jenkinsci/jenkins/pull/3729 it seems so?

I started the other day to update plugin pom and core versions on one of my
older plugins and got some "illegal access compilation errors" because the
plugin was using hudson.model.Messages for some of its UI strings. I assume
this was added because it can break compatibility in case of refactoring in
core and suddenly the key is renamed or something.
But that access guard is now then somewhat void since it will be very
cumbersome to change a resource bundle key as you then need to change it in
30 odd localization plugins to not have them break, and changing them will
break older versions broken anyway.

So I'm a bit confused as to the practicality of this as the assumption
seems to be that keys are not guaranteed to be set in stone?

/B

Den ons 14 nov. 2018 kl 18:00 skrev Jon Brohauge :

> I'd go with option C. I'd love to help in Danish where needed.
>
> --
> 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/49d4147c-e984-4871-9515-59d5b423d018%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/49d4147c-e984-4871-9515-59d5b423d018%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2_aX0hRkLhFRgmLDkwMGJOkkyDV89YJV3OZEEXvhKYXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Build failure analyzer] Request commit access

[Robert Sandell]

I've been very busy with other things the last few months so I've been
neglecting my maintainer duties, but I'm slowly coming back and working off
my code review backlog.

/B

Den tis 13 nov. 2018 kl 21:36 skrev Tim Jacomb :

> CC maintainers
>
> On Tue, 13 Nov 2018 at 20:31, Tim Jacomb  wrote:
>
>> Hi
>>
>> I would like to request commit access for the build failure analyzer
>> plugin
>>
>> I would like to clean it up and do some more development on it
>>
>> Github: timja
>> Jenkins infra: timja
>>
>> Thanks
>> Tim
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/9b7b01f8-5252-4af7-ba9f-c303c130209c%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/9b7b01f8-5252-4af7-ba9f-c303c130209c%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2VF69gNCJhjDybNHc5aHT6NqNTBvgd%3DO8PkJ8Wd-HZLA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Making specific jenkins request as public request without authentication

[Robert Sandell]

Use UnprotectedRootAction
<https://jenkins.io/doc/developer/extensions/jenkins-core/#unprotectedrootaction>
.
You will probably also need to define a CrumbExclusion
<https://jenkins.io/doc/developer/extensions/jenkins-core/#crumbexclusion>.

Though we normally consider unprotected read access to agent information a
security issue, so you should go the other way and add some permission
checks and then have whatever consumer of that API provide login
credentials in form of a token connected to an actual user.

/B

Den mån 24 sep. 2018 kl 13:52 skrev Mukesh Singal :

> Hi Everyone,
>
> I have implemented a Remote API which tells slaves *healthCheck *status.
> But Jenkins redirect users to authenticate first. I want to skip
> authentication for on a specific below URL.
>
> *http://localhost:8080/jenkins/healthCheckPlugin/api/xml
> <http://localhost:8080/jenkins/healthCheckPlugin/api/xml>*
>
> I have tried to create Filter and but failed in achieving this flow.
>
> if anyone can help me here, how to achieve this flow?
>
> --
> 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/4c3fda95-5869-4092-9dab-75b622ff2ab1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/4c3fda95-5869-4092-9dab-75b622ff2ab1%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0ZX%2BZqqZx_vrKdXDBgyWTDJJN9nCAJ-wiwQhvGAnT5NQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Support for Gerrit 2.15 WIP and private changes?

[Robert Sandell]

I released a new version of the gerrit-events module yesterday with support
for WiP and Private changes. So someone "just" needs to do the additional
changes in the Gerrit Trigger plugin.

/B

Den mån 10 sep. 2018 kl 14:05 skrev Andreas Lederer :

> Hi,
>
> it seems that there is already the following open issue
> https://issues.jenkins-ci.org/browse/JENKINS-50547 about support for
> Gerrit WIP and Private changes, which are introduced in Gerrit 2.15.
>
> Do you have a time frame, till when this will be implemented in the
> jenkins gerrit trigger plugin?
>
> Regards,
> Andreas
>
> --
> 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/1ccb008b-2f3c-47c4-ba31-e7f1409532b2%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1ccb008b-2f3c-47c4-ba31-e7f1409532b2%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0iP%2Bkya%3DCKnY0HZhuP%3D%3DO8ABZ1CRzGJzYr8gcM99PZxw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Proposal: Modify Plugin Adoption process to use JIRA to track adoption status

[Robert Sandell]

I don't think jenkins-infra/repository-permissions-updater should be the
starting point. It's hard to find and harder to remember, at least for me.
And once found it's hard to find stuff in it. And the couple of times that
I've done changes in there it takes me a while to figure out if I have
messed something up or not before filing the PR.
So if the repo is a bit intimidating for me how is it for new contributors?
And from what I've seen so far usernames seems to only be appended to the
permissions, so it's not a good source of finding the actual current
maintainer in there.

/B

Den tis 28 aug. 2018 kl 09:07 skrev Craig Rodrigues :

> On Mon, Aug 27, 2018 at 3:03 PM Daniel Beck  wrote:
>
>>
>> I only read the finished JEP and earlier messages in this thread, so may
>> have missed further out of band communication.
>>
>>
> Thanks for the feedback.  I have had no out of band communication
> regarding this JEP other than this e-mail thread.
> This is not really a "finished JEP" as you have stated.  As per the JEP
> process, it has only been accepted as a Draft JEP:
>
> https://github.com/jenkinsci/jep/tree/master/jep/1#approval-as-draft-jep
>
> At this point in the process, the JEP can be refined:
>
> https://github.com/jenkinsci/jep/tree/master/jep/1#refining-a-draft-jep
>
> I'm OK with refining the JEP.
>
> Liam and Jesse have made direct annotations to the draft JEP.
> If you have permissions to make annotations directly to the draft JEP,
> feel free to provide feedback that way if you want.
>
> --
> Craig
>
>
> --
> 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%3DrPVcmjTx%2B21sJEL1LWMa7imOW3kdPzx5%2BOyAt2dHxoJNgBQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3DrPVcmjTx%2B21sJEL1LWMa7imOW3kdPzx5%2BOyAt2dHxoJNgBQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0_HgG%2B8_Gb6ew00wGGvf5un39icQSGhz4q5AyOU9X9Lg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin development : extension to add custom options in declarative pipeline

[Robert Sandell]

I think

 options {
 // Declare the Foo
 withFoo(fooParams)
 }

Should work as is. Have you tried it?

/B

2018-05-17 18:44 GMT+02:00 Bill Dennis <bill.den...@gmail.com>:

> I am developing a Jenkins pipeline plugin that provides some custom block
> scoped steps something like this:
>
> withFoo( fooParams ) {
>// Some code block that uses the declared "Foo" thing
> }
>
>
> My *withFoo* step creates some object "Foo" that is made available in the
> code block to my other custom steps.
>
> I have all this sort of thing working with custom block-scoped steps and
> simple steps and it is going well in my declarative pipelines and providing
> the functionality I need.
>
> However the "foo" is only available in a pipeline code block in a single
> declarative stage and it won't be available in a post handler unless I
> re-declare it ( think).
>
> I am envisioning some scenarios where I want my "Foo" object to be
> available to the whole job in the pipeline context using something like
> "options" (or possibly at the stage options level).
>
> So I am looking at the possibility of some custom option like this:
>
> pipeline {
>
>  agent none
>
>  options {
>  // Declare the Foo
>  foo(fooParams)
>  }
>
>
>  // Rest of pipeline uses the Foo in stages or post sections
> }
>
>
> To give some context, the "Foo" is some sort of connection to a remote system 
> so it could be expensive to keep tearing it down and re-establishing it.
>
>
> Is there a way to provide custom options like this to have an object is 
> created and put in the pipeline context for the whole pipeline and can be 
> consumed by my other custom steps?
>
>
> I had a look at the existing Jenkins extension point documents and around 
> some plugins in GitHub but I cannot tell whether these options are generally 
> extendable in this way.
>
>
> Thanks for any suggestions or pointers anyone here may have!
>
>
> --Bill
>
> --
> 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/92d6270f-7da0-4aea-b7ba-5f41eb1be190%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/92d6270f-7da0-4aea-b7ba-5f41eb1be190%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1%3DRT1DujCDuu6H1PtbCpaCEPY%2BeaXL7%3DbeKeVaPybaiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: .getExtensionList('org.jfrog.hudson.ArtifactoryPlugin') returns empty list

[Robert Sandell]

org.jfrog.hudson.ArtifactoryPlugin
<https://github.com/jenkinsci/artifactory-plugin/blob/master/src/main/java/org/jfrog/hudson/ArtifactoryPlugin.java>
 is not implementing an extension point (is not annotated by @Extension) so
it's not in the extension list. So jenkins.getPlugin(org.jfrog.
hudson.ArtifactoryPlugin) is what you should use for that class.

/B

2018-04-26 1:03 GMT+02:00 Calvin <calvinsp...@gmail.com>:

> import org.jfrog.hudson.*
> import org.jfrog.hudson.ArtifactoryBuilder.*
>
> jenkins = Jenkins.get()
>
> def art = jenkins.getPlugin(org.jfrog.hudson.ArtifactoryPlugin)
> println(art)  // org.jfrog.hudson.ArtifactoryPlugin@2d181762
> println(art.getWrapper().isActive())  // true
>
>
>
> println(jenkins.getExtensionList(org.jfrog .hudson.ArtifactoryPlugin)) //
> []
> println(jenkins.getExtensionList('org.jfrog.hudson.ArtifactoryPlugin'))
> // []
>
>
>
> println(jenkins.getExtensionList('org.jenkinsci.plugins.github.config.GitHubPluginConfig'))
> // [org.jenkinsci.plugins.github.config.GitHubPluginConfig@4508049f]
>
>
>
> Artifactory Plugin is installed and active, yet I am unable to get its
> instance.
>
> I've been using .getExtensionList(String) for customizing plugins via
> Groovy. It's been successful for GitLab, GitHub, and many other plugins,
> but Artifactory seems to be unique.
>
> What's the correct way to configure Artifactory Plugin via Groovy?
>
> --
> 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/13af2a23-babe-4021-bc70-732fe824e742%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/13af2a23-babe-4021-bc70-732fe824e742%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS1Bt4TULSL4U_i_sCt0e3%3DBh-p4P97gHnmx4i0JNQw4Aw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Where does the code for pipeline's 'agent' live?

[Robert Sandell]

If it is the `agent` in declarative syntax you're after here are some
starting points maybe, depending on what it is you want to learn:

https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTAgent.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Agent.groovy
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-extensions/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgent.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy#L486

/B


2018-04-17 15:30 GMT+02:00 Joe Fair <j...@fairanswers.com>:

> I'm looking at how jobs in pipelines work, but I'm having trouble
> searching for the code for the 'agent' tag in a pipeline.  I haven't found
> any "Symbol" for agent, but I may not have looked in the right package
> yet.  I understand there may be something about 'Stapler', but I'm not
> clear.
>
> Where can I learn about 'agent'?
> Thanks,
> Joe
>
> --
> 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/CAHhz2bcHZCbFdAvMYci4d70SUZBB3
> NDyDaoGKCTHdRC%2ByL%3DtUA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAHhz2bcHZCbFdAvMYci4d70SUZBB3NDyDaoGKCTHdRC%2ByL%3DtUA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS36fU2r5cx8gf0B_1N-eG8SGmQWCXZzgmQAaJFCcd7dOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [DISCUSS] Two new basic pipeline steps: forBranch() and forChangesIn()

[Robert Sandell]

Yes declarative has both of these in a way via the when directive's branch
and changeset conditions. If I've interpreted forBranch and forChangesIn
correctly :)

https://jenkins.io/doc/book/pipeline/syntax/#when

/B


2018-04-11 23:39 GMT+02:00 Jesse Glick <jgl...@cloudbees.com>:

> Declarative Pipeline certainly can easily do the same as `forBranch`,
> and from Scripted you can trivially write the same thing, so I think
> no new step is warranted.
>
> Not quite sure I follow what `forChangesIn` is about, but sounds like
> a candidate for a new plugin.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr0jXNj9-XCTWXERUQz%2B7Vx9sVrPor%2BraJU-
> GSHvaoMsWw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0U0Sq6CbJjm4PksVtcP2XfCUBgjMqXSd5yc7Q-fGZakQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Starting an asynchronous step

[Robert Sandell]

Perhaps you've already read this guide?
https://github.com/jenkinsci/workflow-step-api-plugin/blob/master/README.md#creating-an-asynchronous-step

/B

2018-04-06 16:30 GMT+02:00 Jeff Wilson <geek.macb...@gmail.com>:

> I'm trying to write a new pipeline plugin for a build step that is
> long-running and prone to network delays and timeouts, so it would appear
> that an asynchronous step is the best way to implement this. However, I
> have questions about how to implement the StepExecution.start() method to
> start this asynchronous step. I can't find a (canonical) example -- does
> anyone have a pointer to such? Alternatively, a good development guide that
> shows how to implement this type of step?
>
> --
> 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/1652f66e-46bc-4d94-8e30-dac8993e817c%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1652f66e-46bc-4d94-8e30-dac8993e817c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0Sg_DEXZGfNV2%2BiVMZBjLRVHwezaGSXPaWNUtCFANm1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: having trouble with releasing to jenkins-ci.org

[Robert Sandell]

I see a checked in release.properties in the root
https://github.com/jenkinsci/apprenda-plugin/blob/master/release.properties
that shouldn't be there. Probably accidentally checked in from some earlier
botched release.
Since the file is there I'm guessing the release plugin assumes :prepare
has already run and :release uses the data in that file to perform the
release. It has a svn url for scm.url so is probably the culprit here.

/B

2018-03-09 4:48 GMT+01:00 Michael Michael <michm...@gmail.com>:

> i added the distribution management section while i was troubleshooting to
> see if i could find what was wrong.
> i tried everything i would read online..and this was one of them.
>
> On Friday, March 9, 2018 at 6:37:33 AM UTC+3, Daniel Beck wrote:
>>
>>
>> > On 9. Mar 2018, at 03:03, Michael Michael <mich...@gmail.com> wrote:
>> >
>> > may i ask what these commands do then in the output trail? It seems
>> that SVN is called in here, and this is the command that is failing
>> > <<
>> > [INFO] Resuming release from phase 'scm-commit-release'
>> > [INFO] Checking in modified POMs...
>> > [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin && svn
>> --non-interactive commit --file /tmp/maven-scm-1675137483.commit
>> --targets /tmp/maven-scm-9172792877660663843-targets
>> > [INFO] Working directory: /root/apprenda-plugin
>> > >>
>> >
>>
>> Are you working in a Git repository (working copy), or did you download
>> the sources? Perhaps it checks if you're in a Git repo, and if not, falls
>> back to SVN? IOW, in the directory that also contains pom.xml, does `git
>> status` show an error?
>>
>> Besides that, https://github.com/jenkinsci/a
>> pprenda-plugin/blob/b0e8592ba5b83f3ee63802bdf9a83ee14c84d3bc/pom.xml#L54
>> should be long obsolete, so it's unclear to me how you managed to deploy a
>> snapshot with that. (Unrelated to SCM problems though.)
>>
>> --
> 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/9dbd768f-c3c8-47f5-a59a-d394f2bb0220%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/9dbd768f-c3c8-47f5-a59a-d394f2bb0220%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3_9_nCZSAB6j6ysX79aGDb%2BtN7_tJyXWCv24zdoY1F2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thoughts on sending error telemetry for Jenkins Essentials

[Robert Sandell]

Or if you've ever seen one of these panels at the checkout counter in a
store somewhere

http://customerstrategy.net/customer-experience-improvement-systems-part-1/

2018-02-21 17:14 GMT+01:00 Robert Sandell <rsand...@cloudbees.com>:

> How do you feel about Jenkins today? 
>
> :)
>
> 2018-02-21 16:58 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>:
>
>> On Wed, Feb 21, 2018 at 9:44 AM, R. Tyler Croy <ty...@monkeypox.org>
>> wrote:
>> >> How about also a less automated /form/ in the Jenkins UI itself, to be
>> used by
>> >> human in case something is clearly wrong but didn't cause logs or
>> outages.
>> >
>> > I like the idea theory, but in practice I believe we would get a
>> tremendous
>> > amount of low-signal "bug reports" through any such functionality and I
>> don't
>> > have the capacity to triage and handle that kind of feedback from users
>>
>> Maybe a simple “sad face” or “bug” button somewhere in a standard footer?
>>
>> If a user clicks it, we send back just the top-level Stapler view
>> being rendered (since a full URL would pose privacy concerns), e.g.:
>> `hudson/model/Run/console.jelly`
>>
>> Not very precise feedback, but would at least alert us to sudden
>> spikes in problems encountered (according to the user’s evaluation) in
>> certain kinds of pages.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CANfRfr3NM5oNkgqHP-8-jNbr%3DvM9WNsRE1AksXD
>> Z39aJDKKY_Q%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
> E: rsand...@cloudbees.com
> Twitter: robert_sandell
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2k%2BBO0sz22iPRM9oDxW4Pwjhkbno4OvG37nXbOggd3XA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thoughts on sending error telemetry for Jenkins Essentials

[Robert Sandell]

How do you feel about Jenkins today? 

:)

2018-02-21 16:58 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>:

> On Wed, Feb 21, 2018 at 9:44 AM, R. Tyler Croy <ty...@monkeypox.org>
> wrote:
> >> How about also a less automated /form/ in the Jenkins UI itself, to be
> used by
> >> human in case something is clearly wrong but didn't cause logs or
> outages.
> >
> > I like the idea theory, but in practice I believe we would get a
> tremendous
> > amount of low-signal "bug reports" through any such functionality and I
> don't
> > have the capacity to triage and handle that kind of feedback from users
>
> Maybe a simple “sad face” or “bug” button somewhere in a standard footer?
>
> If a user clicks it, we send back just the top-level Stapler view
> being rendered (since a full URL would pose privacy concerns), e.g.:
> `hudson/model/Run/console.jelly`
>
> Not very precise feedback, but would at least alert us to sudden
> spikes in problems encountered (according to the user’s evaluation) in
> certain kinds of pages.
>
> --
> 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/CANfRfr3NM5oNkgqHP-8-jNbr%3DvM9WNsRE1AksXDZ39aJDKKY_Q%
> 40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2X%2BC9hzmz39_GCJE0LwkAbS1fohN9Om67HvKM47UjWuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Thoughts on sending error telemetry for Jenkins Essentials

[Robert Sandell]

Well IIUC since the evergreen master (and possibly also agents) are
specially produced docker images where you control how Jenkins starts why
not just provide a custom JUL configuration file? Either via the java
property -Djava.util.logging.config.file=myLoggingConfigFilePath  or just
put it in JDK_HOME/jre/lib/logging.properties in the container.
That way you can get the error logs all the way from jetty startup to the
end.

/B

2018-02-16 15:51 GMT+01:00 R. Tyler Croy <ty...@monkeypox.org>:

>
> One of the necessary details, in my opinion, to make Jenkins Essentials [0]
> successful is providing near-real-time error telemetry. Coupled with the
> "Evergreen" distribution system [1], error telemetry "post-deploy" will be
> absolutely crucial to determine whether or not we have just pushed out bad
> code
> worthy of reverting.
>
> I currently define "error telemetry" to include:
>
>  * Uncaught exceptions which cause the Evil Jenkins 500 page
>  * Logged ERROR messages, with or without exceptions
>  * Logged WARN messages, with or without exceptions
>
> This list is by no means set in stone, and it is expected that there's
> going to
> be some "noise" in the system, so tooling upstream of this error telemetry
> won't be looking for the presence of errors but rather tracking patterns
> over
> time [2].
>
>
> The big challenge that we have, for which I wanted feedback, is *how* we
> can
> acquire this error telemetry
>
>
> My first prototype in this area was a plugin which integrates with the
> Sentry[3] error reporting service: https://github.com/jenkinsci/
> sentry-plugin
> This approach basically spins up a background busy-waiting thread which
> loops
> over all the loggers in the JVM, and adds the SentryHandler to loggers.
> Not the
> prettiest solution but it mostly works. There is an opportunity to miss
> logged errors before the SentryHandler is added, but it's hard to quantify
> how
> serious a gap that might be.
>
> I am not /thrilled/ with this approach, but it meets a very important
> criteria in
> that it's non-invasive to core and other plugins and can simply be
> installed in
> a Jenkins instance in order to work.
>
>
> I wanted to ask for more thoughts on alternative approaches, if they exist,
> which would enable the collection of the error telemetry discussed above.
> I'm
> sure there's something I'm missing.
>
>
>
>
> [0] https://github.com/jenkinsci/jep/tree/master/jep/300
> [1] https://github.com/jenkinsci/jep/tree/master/jep/300#auto-update
> [2] For example: https://itmonitor.zenoss.com/is-your-performance-normal-
> how-do-you-know/
> [3] https://sentry.io
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20180216145116.yizslgftmjgnhwmn%40blackberry.
> coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3MNdjmxkAHs%2BzKJVAuqo3c7WgkNkz15WMMt8_b0QyQjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How do I set Build status

[Robert Sandell]

http://javadoc.jenkins-ci.org/hudson/model/Run.html#setResult-hudson.model.Result-

On the run instance you got as a parameter in the perform method.

/B

2018-01-26 2:24 GMT+01:00 Rijo Simon <r...@rijosimon.com>:

> I have a Builder plugin. In this plugin I check the status of the build
> that was initiated using an api call. I want to received a filed status of
> from the api and then set the Build step status as failed. But I am not
> able to figure out how. Can someone help me with this please.
>
> I am talking about this status at the end of the build:
>
> [Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS
>
> --
> 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/4615d62e-ffcb-4544-8051-d5c8a5ad8385%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/4615d62e-ffcb-4544-8051-d5c8a5ad8385%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS2f237D5ZoQXY_MZSNricP7hY8LEu%2BN3po9LT%2BPuqzfXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: can not login after i reset the password

[Robert Sandell]

File a ticket in the INFRA project in Jira.

/B

2018-01-18 8:45 GMT+01:00 <chuckl...@gmail.com>:

> I have register an account on website https://issues.jenkins-ci.org/
> login.jsp,you send me an email with password 【password1】
> and I want to change my password after login.
>
> I try to use the random password like this $#x9wHd$4pMXF2L3.
> After I update the profile with password changed,when I logt out and try
> to log in again.
>
> I got error info,the username or password is not correct.
>
> so, I reset my password by the feature forgot password,and got the new
> password【password2】 from my email box.
> Then I log in again, and update the password.
>
> After log out , I still can not log in with the new password.
>
> I tried to login with the password2, I log in successfully.
>
>
> So,the change password feature is not working.
>
>
>
>
> --
> 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/d3a47ce6-d139-487f-a3f2-7ae7554bf976%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/d3a47ce6-d139-487f-a3f2-7ae7554bf976%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS10wyBJ-kbDzwJQMcZFJXfRGSkH8%3DwhHo7jrLt7NpA79g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: using Kotlin inside Jenkins Plugins

[Robert Sandell]

Does Kotlin have a deprecation/compatibility policy that is compatible with
Jenkins? i.e. would a plugin compiled and tested against kotlin 1.3 work
with kotlin 2,3,4 etc?

If that is the case then I think a kotlin-stdlib-plugin would be the best
choice.

regarding the build step, we haven't even added the groovy build step to it
yet so I don't know :)

/B

2018-01-17 20:02 GMT+01:00 Joseph P <joseph...@gmail.com>:

> Also there's the question of should Kotlin build steps be added to parent
> pom?
> https://github.com/jenkinsci/plugin-pom
>
> Den onsdag den 17. januar 2018 kl. 19.56.44 UTC+1 skrev Joseph P:
>>
>> Hey there,
>>
>> We need to solve a problem for those wanting to use Kotlin "stdlib-jre8"
>> I see two solutions
>>
>>1. Create a Jenkins Kotlin plugin for Kotlin standard library.
>>2. Each plugin that uses Kotlin standard library can set plugin first
>>class loader to true.
>>
>> Looking at existing Kotlin plugins.
>>
>> Some decided for plugin first class loader.
>> https://github.com/jenkinsci/doktor-plugin/blob/master/build.gradle.kts
>> https://github.com/casz/accurev-client-plugin/blob/master/
>> build.gradle.kts
>> https://github.com/SimpleFinance/jenkins-firebase-test-
>> plugin/blob/master/build.gradle.kts
>>
>> others are living a dangerous life:
>> https://github.com/michaelsiepmann/Jenkinsstate-Plugin/blob/
>> master/build.gradle
>> https://github.com/koral--/android-gradle-jenkins-plugin/blo
>> b/master/plugin/build.gradle
>> https://github.com/aaron-vaz/github-release-helper-plugin/bl
>> ob/master/build.gradle.kts
>>
>> This would hopefully help others in adopting Kotlin inside the Jenkins
>> plugin community.
>>
>> Best regards
>> Joseph
>>
> --
> 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/51d5e829-d4a8-4e86-9393-47ef74088714%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/51d5e829-d4a8-4e86-9393-47ef74088714%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3uH9zvA4vxju3dh8gc9dNkCoJm-Ho3zYW_aLOZwM76tA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Defining my own project type

[Robert Sandell]

A much more involved alternative would be to implement your own
AuthorizationStrategy and deny regular users create permission on specific
TopLevelItemdescriptor types.
http://javadoc.jenkins-ci.org/hudson/security/ACL.html#hasCreatePermission-org.acegisecurity.Authentication-hudson.model.ItemGroup-hudson.model.TopLevelItemDescriptor-

-V

2018-01-15 17:54 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>:

> Right, you can use `DescriptorVisibilityFilter` if you are in a collegial
> environment.
>
> --
> 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/CANfRfr0YJiyrd6xPUu3jB4sqPH02q
> bA7vSxqPJkiomBC89gP9g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0YJiyrd6xPUu3jB4sqPH02qbA7vSxqPJkiomBC89gP9g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS0POD%2B%3Dn4bizWY7R%2B5%2B6zNvyMT38iubcayCdPo%3DK%2B6rDw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Renaming credentials classes

[Robert Sandell]

System credentials seems to be using Jenkins.XSTREAM2 at least
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java#L126


User credentials is "just" stored in a user's properties
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/UserCredentialsProvider.java#L463

The default store implementation delegates to the store's context
https://github.com/jenkinsci/credentials-plugin/blob/master/src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java#L573

So you seem to be using the correct XStream instances.

/B

2017-12-29 13:01 GMT+01:00 Carlos Sanchez <car...@apache.org>:

> Hi
>
> Trying to get this PR to work on upgrades
> https://github.com/jenkinsci/kubernetes-plugin/pull/268/files#diff-
> 14316beac1f1489a56a52e21cf8e0ee6R506
>
> but none of the XSTREAM2.addCompatibilityAlias options listed in
> https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+
> compatibility seem to work, the credentials are never deserialized
>
> Any suggestions?
>
> --
> 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/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%
> 2B3Zd6Bstk3qtbvcBAQoq-7OOA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CALHFn6Mo4zFSfMTi%2Bt%2BQQssS4%2B3Zd6Bstk3qtbvcBAQoq-7OOA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] <http://www.cloudbees.com/>
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS3PP_v7Q9sZC1JPZOR%2B2N%3D-jet293vD6ACb_rh0ob6ZFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to persist data in BuildStep's perform method?

[Robert Sandell]

Both Run (the base class for most build types) and Job (the base class for
most Project types) implements Actionable
<http://javadoc.jenkins.io/hudson/model/Actionable.html> which is the base
class for anything that can store Actions.

/B

2017-12-02 13:34 GMT+01:00 司芳源 <sify1...@gmail.com>:

> Hi Robert, the link you gave describes how to add an action to a build.
> but I can't store this field in a build's action, because I might lose
> track of this field. For example, if a build fails before it gets to my
> plugin, or at some time the user decides to delete all previous build.
>
> So it's better to store this field at the project's level, whose value
> may(or may not) change over each build.
>
> Does "the job" in your answer means "project"? If so, How do you add
> action to a project and change it over build?
>
> On Friday, December 1, 2017 at 7:23:53 PM UTC+8, Robert Sandell wrote:
>
>> You add an action to the build or the job.
>> https://jenkins.io/doc/developer/tutorial/extend/
>>
>> /B
>>
>> 2017-12-01 4:31 GMT+01:00 司芳源 <sify...@gmail.com>:
>>
>>> In my builder class I have a Integer field, which will increase by 1 in
>>> the perform method. I tested it, this field did increase after each build
>>> as expected. However, after jenkins reboot, this field returned to its
>>> initial value, because its value is not changed in the job's config.xml. I
>>> don't know how jenkins remembered this field's last state when
>>> running(maybe in memory?).
>>>
>>> My question is how can I persist the change in the job's config.xml? So
>>> that I'll not lose the change even after jenkins reboot?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/12fc6bba-7d43-467c-8b53-5195badecda5%40goo
>>> glegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/12fc6bba-7d43-467c-8b53-5195badecda5%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/72ff46df-ba8d-405d-a9d5-f240ec85e6ef%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/72ff46df-ba8d-405d-a9d5-f240ec85e6ef%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: How to persist data in BuildStep's perform method?

[Robert Sandell]

You add an action to the build or the job.
https://jenkins.io/doc/developer/tutorial/extend/

/B

2017-12-01 4:31 GMT+01:00 司芳源 <sify1...@gmail.com>:

> In my builder class I have a Integer field, which will increase by 1 in
> the perform method. I tested it, this field did increase after each build
> as expected. However, after jenkins reboot, this field returned to its
> initial value, because its value is not changed in the job's config.xml. I
> don't know how jenkins remembered this field's last state when
> running(maybe in memory?).
>
> My question is how can I persist the change in the job's config.xml? So
> that I'll not lose the change even after jenkins reboot?
>
> --
> 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/12fc6bba-7d43-467c-8b53-5195badecda5%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/12fc6bba-7d43-467c-8b53-5195badecda5%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Creation of the remoteFs for a slave

[Robert Sandell]

One example I found
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AbstractProject.java#L1200

/B

2017-11-30 12:30 GMT+01:00 Francis UPTON IV <franc...@gmail.com>:

> For a slave, is the remoteFs (like /var/jenkins) supposed to be created by
> the user or by Jenkins? I can't find any code where Jenkins creates it, and
> the description in the ec2 plugin is not clear. Should the ec2-plugin
> create this if it's not present (this seems wrong to me)? If the user is
> supposed to create it, then I need to make sure that's documented in the
> ec2-plugin.
>
> In my testing, the remote FS does not appear to be created by Jenkins
> anywhere. If Jenkins is supposed to create it, can someone point me to the
> code that does this?
>
> Thanks,
> Francis
>
> --
> 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/9a902585-860b-4e28-b660-3a3c2f1c26b9%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/9a902585-860b-4e28-b660-3a3c2f1c26b9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Removing the Everyone team in the jenkinsci GitHub org

[Robert Sandell]

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/C5B832CF-81CD-4E41-A332-02835A4904A9%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/C5B832CF-81CD-4E41-A332-02835A4904A9%40gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Coexistence of two equal plugins

[Robert Sandell]

Class full name and artifact id, changing group id has no effect.

/B

2017-11-29 4:53 GMT+01:00 Slide <slide.o@gmail.com>:

> Please don't double post.
>
> On Tue, Nov 28, 2017, 16:50 Virginia Mesa <v.mesaget...@gmail.com> wrote:
>
>> Hi, I modified a Jenkins plugin in which there was a drop-down and I
>> wanted a textbox. Once modified, my idea was to upload this version of
>> plugin and at the same time keep the previous one unchanged, so as not to
>> disrupt the execution of other jobs that use it. I have changed the
>> idartifactory, the name of the Display ... in short, all the possible
>> identifiers that I have found. But I do not know why, even though I install
>> it as two different plugins ... when I'm going to add the step, it just
>> finds me one ... it's like I know it's the same and it's overwritten. Does
>> anyone know how it is that Jenkins identifies the plugins? Thank you very
>> much, A greeting.
>>
>> --
>> 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/8231fd62-0a0b-44b4-b3ac-9eac4141230e%
>> 40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/8231fd62-0a0b-44b4-b3ac-9eac4141230e%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAPiUgVcA7BBSByFpLYbhF6kLc2P5j
> -2hJ_x1H7y35zndFTq55g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcA7BBSByFpLYbhF6kLc2P5j-2hJ_x1H7y35zndFTq55g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Removing the Everyone team in the jenkinsci GitHub org

[Robert Sandell]

-
> 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/CAN4CQ4xLdArgFQDYw0weXhZpmzgdz
> Gs0sDvKG%2Ba9xy%3DeTD7-9g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4xLdArgFQDYw0weXhZpmzgdzGs0sDvKG%2Ba9xy%3DeTD7-9g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: WORKSPACE permission and viewing workspace files using plugins

[Robert Sandell]

IIRC the intention of the permission was to hinder users who don't have
access to read the repo to retrieve the source code by "other means" i.e.
through the Jenkins workspace browser.

/B

2017-11-21 13:46 GMT+01:00 Ullrich Hafner <ullrich.haf...@gmail.com>:

> I have a question on how to interpret the permission WORKSPACE in
> plug-ins. As far as I understand the changed documentation in [1] this
> permission should only be evaluated when trying to view workspace files
> using the workspace browser.
>
> However, in my static analysis plug-ins I implemented a more restrict rule
> (since this part of my plugins has been implemented before the changes in
> [1]): if the current user does not have the permission WORKSPACE, then the
> source code of affected files is not shown (just the warning). See [2] as
> an example, here you see the warning but not the source code. On the other
> hand, jacoco and the git plugin show the sources even if the permission is
> not set. So I wonder, how we (as plugin authors) should treat this
> situation? Does it make sense to check for this permission? Then other
> plugins need to implement that permission check as well. Or should I remove
> this restriction from my plugins? Or should there be an additional global
> permission in Jenkins? Or is this just plugin specific and I can handle it
> in my way? What do you think?
>
> Or more specifically, what is the idea behind the WORKSPACE permission?
> What do we want to prevent with this permission? Currently, our CI builds
> have this permission disabled for anonymous users, so I can’t see the
> warning details for PRs.
>
> [1] https://issues.jenkins-ci.org/browse/JENKINS-20148?
> focusedCommentId=320330=com.atlassian.jira.plugin.
> system.issuetabpanels%3Acomment-tabpanel#comment-320330
> [2] https://ci.jenkins.io/job/Plugins/job/analysis-model/
> job/coverage/5/findbugsResult/package.91569697/
> [3] https://ci.jenkins.io/job/Plugins/job/analysis-model/
> job/coverage/5/jacoco/edu.hm.hafner.analysis/FastRegexpLineParser/
>
> --
> 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/F233B486-499C-43A8-AEAA-C24411587234%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Propose a workaround of missing multiple security realm feature

[Robert Sandell]

2017-11-20 16:25 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>:

> On Sat, Nov 18, 2017 at 9:57 AM,  <tycre...@gmail.com> wrote:
> > The idea is simple: create a new security realm (composite) which
> delegates
> > methods calls to some chosen security realms (components).
>
> The idea is indeed simple. Last I looked into it, the obstacle was
> code in concrete security realm plugins which called
> `Jenkins.getInstance().getSecurityRealm()` and checked if the result
> was an instance of the type defined in the same plugin, and behaved
> differently according to that check. Maybe that is no longer the case
> and there is no problem, but it needs to be verified.
>

The LDAP plugin does that :/

>
> --
> 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/CANfRfr0C4rpQ3PSY66zvY%2BZqnsdqrz53VqygCL_6XA1%
> 2BicZM-Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Failed to transfer file: Return code is: 401, ReasonPhrase: Unauthorized. Please, assist

[Robert Sandell]

The id of the distribution repository in the blazemeter pom is "
repo.jenkins-ci.org" but the id in your settings.xml is "
maven.jenkins-ci.org" .

/B

2017-11-20 12:00 GMT+01:00 Dzmitry Kashlach <dzmitry.kashl...@blazemeter.com
>:

> Hi,
>
> Need assistance with
> mvn release:prepare release:perform
>
> Used this guide:
> https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins
>
> ~/.m2/settings.xml
> http://maven.apache.org/SETTINGS/1.0.0;
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>   http://maven.apache.org/xsd/settings-1.0.0.xsd;>
>
>   
> 
>   maven.jenkins-ci.org 
>   zmicerkashlach
>   {validpassword}
> 
>   
>
> 
>
>
> GITHUB is configued:
> ssh -T g...@github.com
> Hi dzmitrykashlach! You've successfully authenticated, but GitHub does not
> provide shell access.
>
> I have upload permissions:
> https://github.com/jenkins-infra/repository-permissions-updater/blob/
> 2b1627e571d15a4b5836236288c77f91613b47cc/permissions/plugin-
> BlazeMeterJenkinsPlugin.yml
>
> I've also tried
> mvn release:prepare release:perform -Dusername=zmicerkashlach
> -Dpassword={validpassword}
> but with the same result.
>
> Thank you!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/7f66a081-3eee-4977-8ba3-e89a0f8e9f38%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/7f66a081-3eee-4977-8ba3-e89a0f8e9f38%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Proposed BDFL-Delegate for JEP-2: Daniel Beck

[Robert Sandell]

+1

2017-11-13 20:09 GMT+01:00 Oleg Nenashev <o.v.nenas...@gmail.com>:

> I am fine with that.
>
> понедельник, 13 ноября 2017 г., 17:46:16 UTC+1 пользователь R Tyler Croy
> написал:
>>
>>
>> JEP-2 is an informational JEP to capture the initial plugin suggestion
>> criteria
>> we included in Jenkins 2 for posterity.
>> https://github.com/jenkinsci/jep/tree/master/jep/2
>>
>> Since Daniel originally led this, and it's just an informational JEP, I
>> propose
>> that he act as the BDFL-Delegate to bang the gavel once JEP-2 properly
>> captures
>> what we originally agreed upon in those olden days before Jenkins 2 :)
>>
>>
>> Cheers
>> - R. Tyler Croy
>>
>> --
>>  Code: <https://github.com/rtyler>
>>   Chatter: <https://twitter.com/agentdero>
>>  xmpp: rty...@jabber.org
>>
>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>> --
>>
> --
> 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/93654ab5-c9c4-431f-9401-8df59398bc26%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/93654ab5-c9c4-431f-9401-8df59398bc26%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

[Robert Sandell]

I wasn't suggesting anything as comprehensive as an API spec, nor
suggesting that it would be needed for the review process.
But as I've understood the JEP is that it should, among other things, serve
as an archive for why something looks and behaves like it does.
So for people browsing that future archive, a quick list of what was added,
removed or deprecated would be useful to quickly know if the JEP is going
to be interesting read or not.

Something Like
Added
 Extension Point: CustomClassFilter
 System Property: hudson.remoting.ClassFilter
 redirect https://jenkins.io/redirect/class-filter/
Deprecated
 The crude blacklist extension API in Remoting (perhaps should be a bit
more specific :) )
etc.

2017-11-01 1:06 GMT+01:00 Stephen Connolly <stephen.alan.conno...@gmail.com>
:

> animal sniffer could be adapted to assist, for example
>
> On 31 October 2017 at 16:32, Jesse Glick <jgl...@cloudbees.com> wrote:
>
>> On Tue, Oct 31, 2017 at 11:43 AM, Robert Sandell <rsand...@cloudbees.com>
>> wrote:
>> > Not having to
>> > also browse through potentially thousands of lines of code in one or
>> more
>> > PRs
>>
>> I fully agree that this can be painful; my suggestion was however that
>> the list of API changes be mechanically verified in a PR build. Do you
>> really trust that a textual JEP has been kept exactly up to date with
>> the API spec after dozens of commits? To be a good reviewer you would
>> need to double-check the API in the PRs anyway.
>>
>> As a strawman proposal, suppose that you can optionally add a file to
>> the sources of Jenkins core or your plugin which specifies the
>> complete expected signature of all `public` and `protected` members in
>> the module, in a compact text file. A build-time process would verify
>> that the actual signature matches the expected signature. There would
>> also be a second file in the same format listing the signature as of
>> the last release (perhaps the release profile would enforce that the
>> two files are identical?); and a CI build would also verify that the
>> current signature is binary-compatible with the previous signature.
>>
>> Thus if you proposed a PR which added to the API, you would need to
>> reflect those changes in the current signature file in order to get a
>> passing build, and PR reviewers could easily glance at this part of
>> the diff to confirm that the additions are reasonable. If you proposed
>> to remove an API (under dire circumstances!), you would delete that
>> member from the release signature file, and that would be quite
>> apparent in the PR.
>>
>> AFAICT `clirr-maven-plugin` does not support such a workflow, but I
>> believe https://docs.oracle.com/javacomponents/sigtest-3-1/user-
>> guide/part1.htm
>> would, and there are probably other suitable tools.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CANfRfr3jndHrP0AeytpGmyBqMu55%3DB8yihfjCrW
>> Ur%3DP9oSdS8w%40mail.gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CA%2BnPnMyXpRKg%2BYF0mwVt6YjQE%
> 2BHwHpMB0iP21zD7Q-zUCcsOPw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyXpRKg%2BYF0mwVt6YjQE%2BHwHpMB0iP21zD7Q-zUCcsOPw%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

[Robert Sandell]

I was mostly thinking of it as an aid to the reader so that you don't have
to do a ton of detective work when browsing the list of JEPs. Not having to
also browse through potentially thousands of lines of code in one or more
PRs and perhaps wiki docs etc. linked from the JEP.
In Jesse's case it would be a quick bullet list of what was already
mentioned in the text, in other's it might be a summary added when the JEP
is finalized and some others nothing.

/B

2017-10-31 14:22 GMT+01:00 Jesse Glick <jgl...@cloudbees.com>:

> On Tue, Oct 31, 2017 at 8:28 AM, Daniel Beck <m...@beckweb.net> wrote:
> > quite a bit of what's in Jesse's JEP exists there only because the
> implementation is basically already done.
>
> In this case, yes, excepting whatever might be turned up by further
> testing or discussion.
>
> > I think that's not a goal of the JEP process, and should not be.
>
> Well, as I understand it you are expected to have at least a working
> proof of concept in hand, but it is true that a finalized list of API
> changes would not be expected in general.
>
> If we need to see the aggregate impact of changes on an API, I would
> suggest implementing this at a mechanical level, available in PR
> builds, using tools like CLIRR. @andresrc experimented with this at
> one point but it was not moved into production.
>
> --
> 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/CANfRfr2z-B2cM3eL17deqnR4pawFvMR4affANhf
> 3xaSxO5gGpg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

[Robert Sandell]

tings and rely on asynchronous mediums like email.
>>>>>>>
>>>>>>> If you have an example structure for technical decision-making from
>>>>>>> another
>>>>>>> project, which you think is applicable, please chime in!
>>>>>>>
>>>>>>>
>>>>>>> Personally, what I'm thinking right now is to flip the Python model
>>>>>>> upside
>>>>>>> down: when the JEP Author creates a draft they (or a JEP Editor)
>>>>>>> list a
>>>>>>> "Delegate" who would be somebody with good standing as the
>>>>>>> maintainer of that
>>>>>>> subject area, other than themselves.
>>>>>>>
>>>>>>> For example, if I were proposing a design on Remoting, Oleg would be
>>>>>>> the
>>>>>>> obvious Delegate. If Andrew were proposing some design around
>>>>>>> Pipeline, Jesse
>>>>>>> would be a reasonable Delegate. Rather than expecting a BDFL to be
>>>>>>> "plugged
>>>>>>> into" each JEP, we self-select more (which I think we're all capable
>>>>>>> of doing).
>>>>>>> For the times when we might have conflcit, then we can use the
>>>>>>> Governance
>>>>>>> Meeting process to resolve who the appropriate Delegate for a
>>>>>>> proposal may be.
>>>>>>> To help new comers, including a list of "Suggested Delegates" in the
>>>>>>> JEP repo
>>>>>>> could also be helpful.
>>>>>>>
>>>>>>> I think that could avoid the problems with the current BDFL
>>>>>>> proposal, while
>>>>>>> reducing the need to run every JEP through the Governance Meeting
>>>>>>> process,
>>>>>>> where not all the stakeholders will necessarily be present.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Of course, I'm open to more suggestions and discussion. Like I said
>>>>>>> at the
>>>>>>> beginning of the email, I think getting this right is important.
>>>>>>>
>>>>>>>
>>>>>>> Cheers
>>>>>>> - R. Tyler Croy
>>>>>>>
>>>>>>> --
>>>>>>>  Code: <https://github.com/rtyler>
>>>>>>>   Chatter: <https://twitter.com/agentdero>
>>>>>>>
>>>>>>  xmpp: rty...@jabber.org
>>>>>>>
>>>>>>
>>>>>>>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
>>>>>>> --
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Jenkins Developers" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to jenkinsci-de...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/78ac83c8-629
>>>>>> 0-41f9-98f9-7e977ec6004b%40googlegroups.com
>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/78ac83c8-6290-41f9-98f9-7e977ec6004b%40googlegroups.com?utm_medium=email_source=footer>
>>>>>> .
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>>> Kohsuke Kawaguchi
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/adc45ded-07c6-4d7d-b1ef-2cac80165796%40goo
>>> glegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/adc45ded-07c6-4d7d-b1ef-2cac80165796%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Kohsuke Kawaguchi
>>
> --
> 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/2b9ec3bb-96d0-46bb-8cc8-eaddbbfad3ae%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/2b9ec3bb-96d0-46bb-8cc8-eaddbbfad3ae%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: How to hide files in WorkSpace

[Robert Sandell]

Use the credentials plugin for that.
https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc

/B

2017-10-26 17:48 GMT+02:00 phanikumar <phanikumardadi.ku...@gmail.com>:

> I had a requirement where I need to hide the Secret key files with Jenkins
> plugin. On the other hand, I need workspace files to be available for
> access. I found .git files visible in the workspace which are hidden files.
> Any suggestion is really appreciated.
>
>
>
> --
> Sent from: http://jenkins-ci.361315.n4.nabble.com/Jenkins-dev-f387835.html
>
> --
> 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/1509032922785-0.post%40n4.nabble.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: How to utilize maven configurations in custom plugin.

[Robert Sandell]

Not exactly version, but Jenkins has a thing called ToolInstallers [1] that
is used for users to select what tool (and version) to install.
There is one of those implemented for Maven, the first usage example that
came to mind is in the withMaven step [2], but htere might be easier
examples to refer to.

/B

[1] http://javadoc.jenkins.io/hudson/tools/ToolInstallation.html
[2]
https://github.com/jenkinsci/pipeline-maven-plugin/blob/master/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStep.java#L216


2017-10-04 15:13 GMT+02:00 phanikumar <phanikumardadi.ku...@gmail.com>:

> Hello team,
>
> I have developed a plugin for Google App Engine Deployment. I would like to
> customize it furthermore by providing the users to select the maven version
> for compilation and deployment. Is there a way by which I can provide the
> users to select specific maven version.
>
>
>
>
> --
> Sent from: http://jenkins-ci.361315.n4.nabble.com/Jenkins-dev-f387835.html
>
> --
> 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/1507122823703-0.post%40n4.nabble.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Speeding up the ATH

[Robert Sandell]

people confuse my
> interaction style I am going to try and clarify) I’m bowing out unless
> someone specifically asks me for clarification on my recommendations or I
> see people miss-representing my opinion... this is normally the way I
> interact... just people have a real habit of dragging me back in and that
> makes me look like someone who rabbits on and on.
>
>
>> > Alternately, could we add a layering concept to the acceptance test
>>> harness?
>>> > There could be "precious" tests which run every time and there could be
>>> > other tests which are part of a collection from which a few tests are
>>> > selected randomly for execution every time.
>>>
>>> Yes this is possible.
>>>
>>> > is there a way to make the acceptance test harness run
>>> > in a massively parallel fashion
>>>
>>> Yes. Does not help with the flakiness, and still wastes a tremendous
>>> amount of cloud machine time.
>>>
>>>
>> Would we consider a policy that flaky tests are deleted, rather than
>> tolerated?  Possibly with an email notification to each committer that
>> modified any line in the deleted test?
>>
>> I've understood that Kent Beck has mentioned that they delete flaky tests
>> at facebook, rather than just tolerating them.  Seems dramatic, but
>> increases trust in the acceptance test results, and encourages moving tests
>> from the ATH into JenkinsRule or other locations where they may be easier
>> to diagnose.
>>
>> Mark Waite
>>
>>
>>> > As a safety check of that concept, did any of the current acceptance
>>> tests
>>> > detect the regression when run with Jenkins 2.80 (or Jenkins 2.80 RC)?
>>>
>>> Yes.
>>>
>>> > Is there a JenkinsRule test which could reasonably be written to test
>>> for
>>> > the conditions that caused the bug in Jenkins 2.80?
>>>
>>> Not really; that particular issue was unusual, since it touched on the
>>> setup wizard UI which is normally suppressed by test harnesses.
>>>
>>> --
>>> 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/CANfRfr0LJ6z%3DTiQe8Rt9P_
>>> D7RpZDEHt3XAWQxoq%3Dd0dVAD%2BG%3Dw%40mail.gmail.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.
>> com/d/msgid/jenkinsci-dev/CAO49JtG5DGH3vHt_bwN972EeHeEcPSJekd0dZ%2BQKx%
>> 2Bu%2BzdH0Zg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtG5DGH3vHt_bwN972EeHeEcPSJekd0dZ%2BQKx%2Bu%2BzdH0Zg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Sent from my phone
>
> --
> 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/CA%2BnPnMxRdYEOxD4gn7CxDS5nRK9PPD
> _tCzwGzsTS_2gg%2BRvqdg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxRdYEOxD4gn7CxDS5nRK9PPD_tCzwGzsTS_2gg%2BRvqdg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/716A4677-29EF-45CB-A895-2F9EC1BD66C4%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/716A4677-29EF-45CB-A895-2F9EC1BD66C4%40gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

[Robert Sandell]

A 500 server error is an indication that an exception was thrown in the
backend when the http request was made.
You should see another stacktrace in the log just before the
FailingHttpstatusCodeException.

/B

2017-09-27 22:53 GMT+02:00 'Alexandra Goultiaeva' via Jenkins Developers <
jenkinsci-dev@googlegroups.com>:

> I am working on Jenkins Unit tests, and am trying to add a round trip test
> <https://wiki.jenkins.io/display/JENKINS/Unit+Test#UnitTest-Configurationround-triptesting>
> .
> Unfortunately, I keep getting errors.
>
> Here is a branch with my (broken) changes
> <https://github.com/agoulti/google-storage-plugin/tree/brokenUnitTest>.
>
> I've added the roundtrip test ClassicUploadStepTest
> <https://github.com/agoulti/google-storage-plugin/blob/brokenUnitTest/src/test/java/com/google/jenkins/plugins/storage/ClassicUploadStepTest.java>
> When I run the test, I get the following error:
> *com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 500 Server
> Error for http://localhost:33657/jenkins/job/test0/configure
> <http://localhost:33657/jenkins/job/test0/configure>*
>
> I've played with the test a bit, and found that if I comment out my setUp,
> the test works. It seems that the test breaks as soon as I add the
> following line:
>
> SystemCredentialsProvider.getInstance().getCredentials().add(credentials);
>
> I'm somewhat at a loss as to how to debug this further.
> Stack traces seem to point to where the exception is thrown (
> throwFailingHttpStatusCodeExceptionIfNecessary), and not where the error
> occurred. The error itself is quite generic.
>
> Any hints on how to approach this?
> How can I try to get at the root cause for the 500?
>
> Thanks!
>
>
> PS. This is the stack trace I'm getting:
> *testRoundtrip(com.google.jenkins.plugins.storage.ClassicUploadStepTest)
> Time elapsed: 6.1 sec  <<< ERROR!*
> *com.gargoylesoftware.htmlunit.FailingHttpStatusCodeException: 500 Server
> Error for http://localhost:37367/jenkins/job/test0/configure
> <http://localhost:37367/jenkins/job/test0/configure>*
> * at
> com.gargoylesoftware.htmlunit.WebClient.throwFailingHttpStatusCodeExceptionIfNecessary(WebClient.java:535)*
> * at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:360)*
> * at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:415)*
> * at com.gargoylesoftware.htmlunit.WebClient.getPage(WebClient.java:400)*
> * at
> org.jvnet.hudson.test.JenkinsRule$WebClient.goTo(JenkinsRule.java:2148)*
> * at
> org.jvnet.hudson.test.JenkinsRule$WebClient.goTo(JenkinsRule.java:2128)*
> * at
> org.jvnet.hudson.test.JenkinsRule$WebClient.getPage(JenkinsRule.java:2084)*
> * at
> org.jvnet.hudson.test.JenkinsRule.configRoundtrip(JenkinsRule.java:1077)*
> * at
> org.jvnet.hudson.test.JenkinsRule.configRoundtrip(JenkinsRule.java:1087)*
> * at
> com.google.jenkins.plugins.storage.ClassicUploadStepTest.ConfigurationRoundTripTest(ClassicUploadStepTest.java:82)*
> * at
> com.google.jenkins.plugins.storage.ClassicUploadStepTest.testRoundtrip(ClassicUploadStepTest.java:89)*
>
> --
> 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/587d5c60-f702-4621-942c-6688b6a8d58b%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/587d5c60-f702-4621-942c-6688b6a8d58b%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Reading Hudson and job environment variables from ParameterDefinition plugin

[Robert Sandell]

At build time your ParameterValue gets the build as a parameter to
buildEnvironment(Run build, EnvVars env), so you get it from
build.getParent() but maybe the vars are already added to env so you might
not need the code I showed above.

If you need the job at job schedule time, e.g. when clicking build now it
get's a bit trickier. You can use the StaplerRequest to find the job from
the ancestor path.

Job job = request.findAncestor(Job.class)

But I don't think there is any good way to get it when constructing the
value from CliCommand, maybe the following could work

if (command instanceof BuildCommand) {
Job job = (BuildCommand)command.job;
}

/B


2017-09-20 16:38 GMT+02:00 Paulo Eduardo Neves <paulone...@gmail.com>:

> Thanks for your answer, Robert. Almost there!
>
>
> How would you create the job instance variable with the current job? I
> see that there is a model.Job class, but I'm too newbie and can't find
> how to instantiate it.
>
>
>
> Em quarta-feira, 20 de setembro de 2017 06:51:26 UTC-3, Robert Sandell
> escreveu:
>>
>> Something like this I'd guess
>>
>> SetEnvBuildWrapper wrapper = 
>> job.getBuildWrappers().get(Jenkins.getInstance().getDescriptorByType(SetEnvBuildWrapper.DescriptorImpl.class))
>> Map<String,String> vars = wrapper.getLocalVarMap()
>>
>> /B
>>
>> 2017-09-19 20:53 GMT+02:00 Paulo Eduardo Neves <paulo...@gmail.com>:
>>
>>> Earlier today I post this message to Jenkin Users mailing list. I
>>> mistakenly though that it were the place for plugin questions. Sorry for
>>> the crosspost,
>>>
>>> I have a prebuild plugin that extends ParameterDefinition class. It just
>>> give me some options to prepare the build.
>>>
>>> It is an old installation and uses the deprecated SetEnv plugin
>>> <https://wiki.jenkins.io/display/JENKINS/Setenv+Plugin> to setup a
>>> bunch of environment variables.
>>>
>>> Is it possible to access the environment variables defined in the *SetEnv
>>> plugin* from my plugin? It just creates the build object when the
>>> submit button is pressed, so I don't have access to it from my form.
>>>
>>> If I can access the configuration file, I can also parse these
>>> variables. Maybe this is easier to do.
>>>
>>> I also would like to access the Jenkins global variable values. If I do
>>> a System.getenv("JAVA_HOME") I get the value, but if I try with a variable
>>> defined in the SetEnv plugin or in the global configuration, it comes null.
>>>
>>> If you can point me an example or reference, it would be great.
>>>
>>> Thanks in advance for any 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-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/917dbdc6-d11d-4277-87d8-f85468213903%40goo
>>> glegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/917dbdc6-d11d-4277-87d8-f85468213903%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Robert Sandell
>> *Software Engineer*
>> *CloudBees Inc.*
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/53457ddc-e051-49a7-846f-7c26b85c8b3a%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/53457ddc-e051-49a7-846f-7c26b85c8b3a%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Reading Hudson and job environment variables from ParameterDefinition plugin

[Robert Sandell]

Something like this I'd guess

SetEnvBuildWrapper wrapper =
job.getBuildWrappers().get(Jenkins.getInstance().getDescriptorByType(SetEnvBuildWrapper.DescriptorImpl.class))
Map<String,String> vars = wrapper.getLocalVarMap()

/B

2017-09-19 20:53 GMT+02:00 Paulo Eduardo Neves <paulone...@gmail.com>:

> Earlier today I post this message to Jenkin Users mailing list. I
> mistakenly though that it were the place for plugin questions. Sorry for
> the crosspost,
>
> I have a prebuild plugin that extends ParameterDefinition class. It just
> give me some options to prepare the build.
>
> It is an old installation and uses the deprecated SetEnv plugin
> <https://wiki.jenkins.io/display/JENKINS/Setenv+Plugin> to setup a bunch
> of environment variables.
>
> Is it possible to access the environment variables defined in the *SetEnv
> plugin* from my plugin? It just creates the build object when the submit
> button is pressed, so I don't have access to it from my form.
>
> If I can access the configuration file, I can also parse these variables.
> Maybe this is easier to do.
>
> I also would like to access the Jenkins global variable values. If I do
> a System.getenv("JAVA_HOME") I get the value, but if I try with a variable
> defined in the SetEnv plugin or in the global configuration, it comes null.
>
> If you can point me an example or reference, it would be great.
>
> Thanks in advance for any 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/917dbdc6-d11d-4277-87d8-f85468213903%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/917dbdc6-d11d-4277-87d8-f85468213903%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Request for feedback: Jenkins Enhancement Proposal (JEP)

[Robert Sandell]

I didn't get the sense that the BDFL would be a bottle neck when you
explained it to us at the contributor summit.
To me it seemed like the BDFL would only have to get involved if consensus
between the author, editors and other reviewers can't be reached, or if he
needs to put in a veto to stop something (in his mind) crazy from happening.

That said having Subject Matter Experts on hand to either serve as a
"Deputy BDFL" for a specific area, or just someone that gets an explicit
ping when a JEP affecting "their" area comes in might be good to have.

/B

2017-09-19 19:12 GMT+02:00 R. Tyler Croy <ty...@monkeypox.org>:

> (replies inline)
>
> On Wed, 13 Sep 2017, R. Tyler Croy wrote:
>
> > https://github.com/jenkinsci/jep/tree/jep-1/jep/1
>
>
> Since I'm sure not everybody has been following along with some of the pull
> requests and changes while we've been hammering out JEP-1, I would like to
> provide a little bit of an update and solicit some help. This topic is very
> important, so please read this email!
>
> First, thanks to reviews from a number of folks including Oleg, Owen,
> Daniel,
> and others, we have been able to tighten the proposal up quite a bit.
> Mostly
> thanks to Liam's diligent slicing and dicing of text :)
>
> While I had hoped we might be able to get some consensus in time for
> tomorrow's
> project meeting, I don't think we are quite there yet. There has been lots
> of
> helpful feedback on the review and decision-making process
> (BDFL/BDFL-delegate):
> https://github.com/jenkinsci/jep/tree/jep-1/jep/1#review
>
>
> To summarize the primary, and valid, criticisms if I may:
>
>  1. Kohsuke as the BDFL introduces a problematic bottleneck to the process
> (there are way more of us, than there are of him).
>
>  2. JEP-1 introduces a different way of decision making than has been
> traditionally followed with the Governance Meeting
> (https://jenkins.io/project/governance/#meeting)
>
>
> I would like to guide the discussion towards addressing these. I also want
> to
> ensure our process is sensitive to contributors around the world,
> especially
> those in Australia and Asia who are typically asleep during the scheduled
> project meetings and rely on asynchronous mediums like email.
>
> If you have an example structure for technical decision-making from another
> project, which you think is applicable, please chime in!
>
>
> Personally, what I'm thinking right now is to flip the Python model upside
> down: when the JEP Author creates a draft they (or a JEP Editor) list a
> "Delegate" who would be somebody with good standing as the maintainer of
> that
> subject area, other than themselves.
>
> For example, if I were proposing a design on Remoting, Oleg would be the
> obvious Delegate. If Andrew were proposing some design around Pipeline,
> Jesse
> would be a reasonable Delegate. Rather than expecting a BDFL to be "plugged
> into" each JEP, we self-select more (which I think we're all capable of
> doing).
> For the times when we might have conflcit, then we can use the Governance
> Meeting process to resolve who the appropriate Delegate for a proposal may
> be.
> To help new comers, including a list of "Suggested Delegates" in the JEP
> repo
> could also be helpful.
>
> I think that could avoid the problems with the current BDFL proposal, while
> reducing the need to run every JEP through the Governance Meeting process,
> where not all the stakeholders will necessarily be present.
>
>
>
> Of course, I'm open to more suggestions and discussion. Like I said at the
> beginning of the email, I think getting this right is important.
>
>
> Cheers
> - R. Tyler Croy
>
> --
>  Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20170919171212.j3sjo4fawhisfieb%40blackberry.
> coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Request to join Jenkins Security Team

[Robert Sandell]

+1

2017-08-28 19:29 GMT+02:00 Christopher Orr <ch...@orr.me.uk>:

> Hi there,
>
> I'd like to request to join the security team.
> I've got all the prerequisites listed (2FA, CLA, nickname on IRC).
>
> Thanks,
> Chris
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/1503941343.3112205.1087569072.66BA5581%40webmail.
> messagingengine.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Is it possible to use git/https to release a plugin?

[Robert Sandell]

Yes you should be able to do that, but you need to update the scm section
of your pom.

/B

2017-08-23 17:36 GMT+02:00 Ivo Bellin Salarin <ivo.bellinsala...@gmail.com>:

> Hi all,
>
> My credentials differ (jenkins-ci.org, GitHub) and I would like that mvn
> use the repository remote rather the one specified in the pom. (Since I can
> push without problems from it, while mvn has several problems)
>
> May I use git over https to perform a new plugin release?
>
> Thanks in advance,
> Ivo
>
> --
> 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/CAPc4eF88Hnp3tjRa73fGdJpmvwr2h
> OKfro%2BA4mJ%2BqJ-LjYdkDg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPc4eF88Hnp3tjRa73fGdJpmvwr2hOKfro%2BA4mJ%2BqJ-LjYdkDg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: View event/trigger/callback

[Robert Sandell]

Views are mainly just "properties" of other itemgroups, so when you save a
view you save the owner of the view.
So you should get an event on Jenkins or the Folder that the view is in.
Figuring out that the save operation was due to a view update could be a
bit tricky.

/B

2017-08-23 22:00 GMT+02:00 Reginald Ealey -X (realey - AEROTEK INC at
Cisco) <rea...@cisco.com>:

> Hi all,
>
>
>
> Is there event trigger that is emitted when a “View” configuration has
> been saved/updated?
>
>
>
> I'm creating a plugin to extend SaveableListener. When a "View" object
> configuration is updated and saved; This listener is not triggered.
>
>
> What's the best practice to detect when a "View" object saved?
>
>
>
>
>
> [image: banner14]
>
>
>
> *Reginald Ealey*
>
> Engineer - Software
>
> rea...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> United States
> cisco.com
>
>
>
> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html> for
> Company Registration Information.
>
>
>
> --
> 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/70a0e7661be44c46a8d0690ec302f1
> 6f%40XCH-RTP-003.cisco.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/70a0e7661be44c46a8d0690ec302f16f%40XCH-RTP-003.cisco.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Plugin idea: publish the analysis result (reading from the jxlint xml format)

[Robert Sandell]

Unit test reports and static analysis reports are not the same thing.
Analysis-core would be the way to go iiuc.

/B

2017-08-18 14:18 GMT+02:00 Victor Martinez <victormartinezru...@gmail.com>:

> Maybe https://wiki.jenkins.io/display/JENKINS/xUnit+Plugin could be
> extended to support this use case?
>
> --
> 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/187c0802-8500-4365-87fb-b788fc074c25%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/187c0802-8500-4365-87fb-b788fc074c25%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[Robert Sandell]

>>
>> (Where:
>> - https://gerrit-review.example.com would be the Gerrit URL
>> - mycredentialsid would be the id of the credentials to access Gerrit)
>>
>> One key-aspect will be: stateless, configuration-less (apart from the
>> credentials stored in Jenkins keychain)
>> That means that multiple Jobs, multiple branches of the same Job, can
>> have their own Gerrit integration defined and working out-of-the-box.
>>
>> No more people asking "how do I configure the Gerrit integration"?
>> You'll just define a gerrit.withServer() { } and ... it will just work.
>>
>> *When?*
>> I am planning to showcase the first prototype of the new plugin at the
>> Jenkins World Conference in San Francisco inside my "Data-Driven Pipeline
>> workshop."
>> (https://jenkinsworld20162017.sched.com/event/APTd/data-driv
>> en-pipeline-workshop-free)
>> Shortly afterward, I will publish the plugin on the GerritForge's GitHub
>> account and will start the integration process into the Jenkins CI
>> organization.
>>
>> *Next steps?*
>> A second iteration of the plugin would have a Declarative pipeline
>> equivalent as well, which would require even less code required.
>> A third iteration of the plugin would support BlueOcean as well, to have
>> a fully UX-integrated experience.
>> The goal is to have *Gerrit Code Review to be a 1st class citizen in the
>> Jenkins ecosystem* :-)
>>
>> *So what happens to the Gerrit Trigger Plugin?*
>> The new plugin is not going to replace the current Gerrit Trigger Plugin,
>> but would rather represent an alternative to simpler scenarios when you
>> just require a standard Jenkinsfile Gerrit validation workflow. For all the
>> current users of the Gerrit Trigger Plugin things wouldn't change, unless
>> they need a more Jenkisfile-integrated experience.
>>
>> Feedback? Like it? Hate it? Have your say :-)
>>
>> Luca.
>>
>>
>>
> --
> --
> To unsubscribe, email repo-discuss+unsubscr...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Repo and Gerrit Discussion" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to repo-discuss+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
>
>


-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: */api/json fails for a new Jenkins plugin

[Robert Sandell]

But it looks like your action is attached to a job. So instead you
could/should just put @Exported on the getters in the action that you want
exposed and then get it via the /job/test/api/json endpoint instead.

/B

2017-08-10 22:55 GMT+02:00 Daniel Mercier <damer...@gmail.com>:

> Thank you very much.
>
> Daniel Mercier
>
>
> On Thursday, 10 August 2017 15:49:52 UTC-4, Markus Winter wrote:
>
>> you need a method getApi() that returns an Api [1]
>>
>> public Api getApi() {
>> return new Api(this);
>> }
>>
>>
>> [1] http://javadoc.jenkins.io/hudson/model/Api.html
>>
>> On 10.08.2017 21:28, Daniel Mercier wrote:
>>
>> Hi everyone,
>>
>> I created a new Jenkins plugin and while everything seems to work. The
>> API/JSON fails consistently. The same behavior can be experienced with the
>> pugin: Test_Analyzer_Plugin.
>>
>> The answer on my plugin comes as a 404:
>>
>> 404 Not Found
>>
>> Stapler processed this HTTP request as follows, but couldn't find the
>> resource to consume the request
>>
>> -> evaluate(<hudson.model.Hudson@a25d803> 
>> :hudson.model.Hudson,"/job/test/BenchmarkTable/api/json")
>> -> 
>> evaluate(((StaplerProxy)<hudson.model.Hudson@a25d803>).getTarget(),"/job/test/BenchmarkTable/api/json")
>> -> 
>> evaluate(<hudson.model.Hudson@a25d803>.getJob("test"),"/BenchmarkTable/api/json")
>> -> evaluate(<hudson.model.FreeStyleProject@6135ae8a[test]> 
>> :hudson.model.FreeStyleProject,"/BenchmarkTable/api/json")
>> -> 
>> evaluate(<hudson.model.FreeStyleProject@6135ae8a[test]>.getDynamic("BenchmarkTable",...),"/api/json")
>> -> 
>> evaluate(<org.jenkinsci.plugins.benchmark.BenchmarkProjectAction@5dcde26d> 
>> :org.jenkinsci.plugins.benchmark.BenchmarkProjectAction,"/api/json")-> No 
>> matching rule was found on 
>> <org.jenkinsci.plugins.benchmark.BenchmarkProjectAction@5dcde26d> for 
>> "/api/json"
>>
>> <org.jenkinsci.plugins.benchmark.BenchmarkProjectAction@5dcde26d> has
>> the following URL mappings, in the order of preference:
>>
>>1. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.setResultSelected(...)
>>for url=/setResultSelected/...
>>2. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.ResetClock(...)
>>for url=/ResetClock/...
>>3. TOKEN.groovy for url=/TOKEN
>>4. VIEW.jelly for url=/VIEW
>>5. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getDisplayName()
>>for url=/displayName/...
>>6. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getProject()
>>for url=/project/...
>>7. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getUrlName()
>>for url=/urlName/...
>>8. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getIconFileName()
>>for url=/iconFileName/...
>>9. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getResultPageURL()
>>for url=/resultPageURL/...
>>10. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getRootPageURL()
>>for url=/rootPageURL/...
>>11. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getNumberOfHeads()
>>for url=/numberOfHeads/...
>>12. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getRawTable()
>>for url=/rawTable/...
>>13. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getCondensedTable()
>>for url=/condensedTable/...
>>14. 
>> org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getContentAvailable()
>>for url=/contentAvailable/...
>>15. org.jenkinsci.plugins.benchmark.BenchmarkProjectAction.getCore()
>>for url=/core/...
>>16. java.lang.Object.getClass() for url=/class/...
>>
>>
>> If anyone faced the same issue, any help will be greatly appreciated.
>>
>> Best regards,
>>
>> Daniel Mercier
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/e1c4bec7-99e0-4c37-bd8e-d8a84043490b%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/e1c4bec7-99e0-4c37-bd8e-d8a84043490b%40googlegroups.co

Re: jenkins jpi plugin problems

[Robert Sandell]

Not sure how the gradle plugin works, but createMavenProject was removed
from the jenkins test harness some time ago since MavenProject wasn't part
of core any more.

you should use createProject(MavenProject.class) instead.

/B

2017-07-07 14:36 GMT+02:00 Jeremy Marshall <jeremystuartmarsh...@gmail.com>:

> I upgraded my groovy plugin to jpi 0.22.0 but now I get a strange error in
> the tests
>
> ```
> org.jenkinsci.plugins.GroovyScriptMESSpec > two axis success script FAILED
> groovy.lang.MissingMethodException: No signature of method:
> org.jvnet.hudson.test.JenkinsRule.createMatrixProject() is applicable for
> argument types: () values: []
> at org.jenkinsci.plugins.GroovyScriptMESSpec.configure(
> GroovyScriptMESSpec.groovy:26)
> at org.jenkinsci.plugins.GroovyScriptMESSpec.two axis success
> script(GroovyScriptMESSpec.groovy:84)
> ```
>
> As far as I can tell the method is there. Am I missing a test plugin?  Its
> all very odd
>
> repo https://github.com/jenkinsci/matrix-groovy-execution-strategy-plugin/
> tree/groovy3.2.1
>
> I tried it with the very latest Java 8 and its using a gradlew wrapper
>
> Thanks in advance
> Jeremy
>
> --
> 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/14be113f-5fc9-497f-969b-f0769fc30c7c%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/14be113f-5fc9-497f-969b-f0769fc30c7c%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: [Proposal] Making all things Stapler more declarative

[Robert Sandell]

> new
>>>annotations in those cases)
>>>- If the class is @StaplerObject annotated we can do additional
>>>checks for overlapping facets, for example where an action method or a
>>>getter will hide a facet (it's ok to hide the facet for non HEAD/GET
>>>requests though)
>>>
>>> There are probably additional checks that we can add as we figure them
>>> out.
>>>
>>>
>>> Now there are some open questions:
>>>
>>>- Does it make sense to start all these annotations with Stapler? My
>>>initial stab at this was to use @Staple in place of @StaplerPath and
>>>to re-use the @GET / @POST / @PUT / @DELETE verbs but mandating the
>>>@Staple annotation so that you would have:
>>>
>>> @Staple @POST
>>>
>>> public HttpResponse doActivate(StaplerRequest req) { ... }
>>>
>>>
>>> rather than
>>>
>>> @StaplerPOST
>>>
>>> public HttpResponse doActivate(StaplerRequest req) { ... }
>>>
>>>
>>> One of the issues I found with that is class conflicts when back-porting
>>> the @GET / @POST / etc annotations, so we could only use those if we
>>> were prepared to mark 2.7 as the oldest core that could use the
>>> annotations, whereas we can make new annotations in a separate package
>>> available as far back as Stapler 1.180 == Jenkins 1.455 (or worst case
>>> Stapler 1.237 == Jenkins 1.651)
>>>
>>> Now we could introduce new annotations without the @Stapler prefix, but
>>> then your code complete would confuse you between
>>> @org.kohsuke.stapler.annotations.GET and @org.kohsuke.stapler.verbs.GET
>>> plus we still need something to give a hint that the annotation is implying
>>> Stapler's involvement (at least from my perspective)
>>>
>>>
>>>- I had thought about saying that the class level @StaplerObject
>>>should be enough of a flag that you should expect the other 
>>> annotations...
>>>but the class annotation will be inherited, so you may not see it until 
>>> you
>>>look at the super-class... and @Path will conflict with
>>>java.nio.file.Path... that might work with @Staple (and @Staples as
>>>the container) but while cute they do not scream to the new developers 
>>> that
>>>these are involved in url binding.
>>>
>>> NOTE: In this context I see this change as being entirely opt-in. Plugin
>>> developers should not have to go adding the annotations - though we would
>>> probably apply them in Jenkins core to assist new developers.
>>>
>>>
>>>- If we go with the Stapler prefix, would it make sense to
>>>consolidate all the annotations with that prefix?
>>>
>>>- I am not convinced for the case of @ExportedBean and @Exported,
>>>   these reflect a different cross-cutting concern and as such the pair 
>>> seem
>>>   named well from my PoV
>>>   - The @JavaScriptMethod / @WithWellKnownURL annotations might be
>>>   worthy of consolidation if we can determine better names.
>>>   - The parameter binding annotations such as @AncestorInPath,
>>>   @Header, @QueryParameter and @InjectedParameter I think are fine
>>>   where they are as they will only be on an action method which already 
>>> has
>>>   the @StaplerPOST etc indicator.
>>>   - The meta-annotation @InterceptorAnnotation should not be
>>>   consolidated, in any case we could not consolidate it and retain usage
>>>   against older cores
>>>   - The other annotations are likely rarely used, but if we can
>>>   find good names and people think they are generically useful rather 
>>> than
>>>   single use-case hacks added into the stapler API, I think 
>>> consolidation
>>>   might make the features more widely used.
>>>
>>> So, over to you the community of Jenkins developers:
>>>
>>>1. Would this change have helped you get started quicker?
>>>2. Would this change help you even now?
>>>3. How ugly are my proposed annotation names? Can you provide a less
>>>ugly scheme of names?
>>>4. Anything else?
>>>
>>> Stephen
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-dev/CA%2BnPnMz-m49TK7Em%2BxBNb%2BV98dBCz9CrrP
>>> Xg3uW6%2B_x3KX5gOQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMz-m49TK7Em%2BxBNb%2BV98dBCz9CrrPXg3uW6%2B_x3KX5gOQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> Kohsuke Kawaguchi
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CAN4CQ4wDS34DE-PQVK6tsCQD5AXWcxCMEVkCgh5MN
>> ymRNVcLPw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4wDS34DE-PQVK6tsCQD5AXWcxCMEVkCgh5MNymRNVcLPw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CA%2BnPnMwio9PeC3uhC_i4XqQ_7OY2dN2Hx34e6hSmHVAeG7RiRA%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMwio9PeC3uhC_i4XqQ_7OY2dN2Hx34e6hSmHVAeG7RiRA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: [Proposal] Making all things Stapler more declarative

[Robert Sandell]

   @StaplerPATCH / @StaplerDELETE annotated methods must be public and
>match one of the allowed action method signatures. The method name must
>match the convention for action method inference (subject to
>@WebMethod(name="...") overriding when *compiling against older
>versions of Stapler* - but it would be an error to use @WebMethod if
>compiling against newer versions of Stapler because we can move to the new
>annotations in those cases)
>- If the class is @StaplerObject annotated we can do additional checks
>for overlapping facets, for example where an action method or a getter will
>hide a facet (it's ok to hide the facet for non HEAD/GET requests though)
>
> There are probably additional checks that we can add as we figure them out.
>
>
> Now there are some open questions:
>
>- Does it make sense to start all these annotations with Stapler? My
>initial stab at this was to use @Staple in place of @StaplerPath and
>to re-use the @GET / @POST / @PUT / @DELETE verbs but mandating the
>@Staple annotation so that you would have:
>
> @Staple @POST
>
> public HttpResponse doActivate(StaplerRequest req) { ... }
>
>
> rather than
>
> @StaplerPOST
>
> public HttpResponse doActivate(StaplerRequest req) { ... }
>
>
> One of the issues I found with that is class conflicts when back-porting
> the @GET / @POST / etc annotations, so we could only use those if we were
> prepared to mark 2.7 as the oldest core that could use the annotations,
> whereas we can make new annotations in a separate package available as far
> back as Stapler 1.180 == Jenkins 1.455 (or worst case Stapler 1.237 ==
> Jenkins 1.651)
>
> Now we could introduce new annotations without the @Stapler prefix, but
> then your code complete would confuse you between @org.kohsuke.stapler.
> annotations.GET and @org.kohsuke.stapler.verbs.GET plus we still need
> something to give a hint that the annotation is implying Stapler's
> involvement (at least from my perspective)
>
>
>- I had thought about saying that the class level @StaplerObject
>should be enough of a flag that you should expect the other annotations...
>but the class annotation will be inherited, so you may not see it until you
>look at the super-class... and @Path will conflict with
>java.nio.file.Path... that might work with @Staple (and @Staples as
>the container) but while cute they do not scream to the new developers that
>these are involved in url binding.
>
> NOTE: In this context I see this change as being entirely opt-in. Plugin
> developers should not have to go adding the annotations - though we would
> probably apply them in Jenkins core to assist new developers.
>
>
>- If we go with the Stapler prefix, would it make sense to consolidate
>all the annotations with that prefix?
>
>- I am not convinced for the case of @ExportedBean and @Exported,
>   these reflect a different cross-cutting concern and as such the pair 
> seem
>   named well from my PoV
>   - The @JavaScriptMethod / @WithWellKnownURL annotations might be
>   worthy of consolidation if we can determine better names.
>   - The parameter binding annotations such as @AncestorInPath, @Header,
>   @QueryParameter and @InjectedParameter I think are fine where they
>   are as they will only be on an action method which already has the
>   @StaplerPOST etc indicator.
>   - The meta-annotation @InterceptorAnnotation should not be
>   consolidated, in any case we could not consolidate it and retain usage
>   against older cores
>   - The other annotations are likely rarely used, but if we can find
>   good names and people think they are generically useful rather than 
> single
>   use-case hacks added into the stapler API, I think consolidation might 
> make
>   the features more widely used.
>
> So, over to you the community of Jenkins developers:
>
>1. Would this change have helped you get started quicker?
>2. Would this change help you even now?
>3. How ugly are my proposed annotation names? Can you provide a less
>ugly scheme of names?
>4. Anything else?
>
> Stephen
>
> --
> 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/CA%2BnPnMz-m49TK7Em%2BxBNb%2BV98dBCz9CrrPXg3uW6%2B_
> x3KX5gOQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMz-m49TK7Em%2BxBNb%2BV98dBCz9CrrPXg3uW6%2B_x3KX5gOQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Anyone else seeing a -SNAPSHOT deployed as a release for gradle plugin?

[Robert Sandell]

Yes, I saw that yesterday as well when I installed 2.60.1

/B

2017-06-30 11:49 GMT+02:00 Stephen Connolly <stephen.alan.conno...@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/CA%2BnPnMzBxooXbih8Vek96xHU%
> 3D2eZLB1BV15rGbAXjtTjbxXNAA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMzBxooXbih8Vek96xHU%3D2eZLB1BV15rGbAXjtTjbxXNAA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline Build Wrapper

[Robert Sandell]

https://jenkins.io/doc/developer/extensions/jenkins-core/#globalconfiguration
http://javadoc.jenkins.io/jenkins/model/GlobalConfiguration.html

/B

2017-06-30 11:00 GMT+02:00 Steven F <stevengfos...@gmail.com>:

>
>
> On Wednesday, June 28, 2017 at 3:39:20 PM UTC+1, Jesse Glick wrote:
>>
>> cf. JENKINS-28822
>>
>
>  Sorry for another basic question, but do you have the name of a class I
> should look into to add a global configuration (from Manage Jenkins) that
> would be accessible to my RunListener? I've used Descriptors with other
> extension points but it doesn't seem to apply here since there is only one
> instance. I've also looked into OptionalJobProperty but that wouldn't be on
> a global level.
>
> --
> 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/cb4724c6-1138-4739-94e5-cd245573fd60%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/cb4724c6-1138-4739-94e5-cd245573fd60%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline Build Wrapper

[Robert Sandell]

https://jenkins.io/doc/developer/extensions/jenkins-core/#globalconfiguration
http://javadoc.jenkins.io/jenkins/model/GlobalConfiguration.html

/B

2017-06-30 11:00 GMT+02:00 Steven F <stevengfos...@gmail.com>:

>
>
> On Wednesday, June 28, 2017 at 3:39:20 PM UTC+1, Jesse Glick wrote:
>>
>> cf. JENKINS-28822
>>
>
>  Sorry for another basic question, but do you have the name of a class I
> should look into to add a global configuration (from Manage Jenkins) that
> would be accessible to my RunListener? I've used Descriptors with other
> extension points but it doesn't seem to apply here since there is only one
> instance. I've also looked into OptionalJobProperty but that wouldn't be on
> a global level.
>
> --
> 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/cb4724c6-1138-4739-94e5-cd245573fd60%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/cb4724c6-1138-4739-94e5-cd245573fd60%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Plugin compatibility when adding a class

[Robert Sandell]

2017-06-16 12:19 GMT+02:00 Christian McHugh <christian.mch...@gmail.com>:

> On Friday, June 16, 2017 at 11:12:27 AM UTC+1, Robert Sandell wrote:
>>
>> The XStream deserialization from config.xml to the object graph don't use
>> the DataboundConstructor et.al. It is only interested in mapping xml
>> data to fields (in most cases).
>>
>> DataboundConstructor is only used for formbinding from the UI and
>> pipeline step definitions etc.
>>
>
> So a ConverterImpl should be able to update the config properly? At the
> end of my example from the first part of the thread I had a
> system.out.println which displays the desired config, but when hitting the
> convert button in Jenkins, those config.xml files are written without a
> build step. Would this mean I just need to make a better ConverterImpl?
>

Maybe, or you might just haven't registered the converter in the correct
places. But I would urge you to first try using plain old readResolve to
handle the conversion from old data before attempting implementing an
XStream converter.

> --
> 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/3db7ba8c-7f22-4e06-88ba-8bb048e0720d%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/3db7ba8c-7f22-4e06-88ba-8bb048e0720d%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Plugin compatibility when adding a class

[Robert Sandell]

The XStream deserialization from config.xml to the object graph don't use
the DataboundConstructor et.al. It is only interested in mapping xml data
to fields (in most cases).

DataboundConstructor is only used for formbinding from the UI and pipeline
step definitions etc.

/B

2017-06-16 12:03 GMT+02:00 Christian McHugh <christian.mch...@gmail.com>:

> Great example, thanks!
>
> Let's say that a release had already been made which changed the
> databoundconstructor. In that case, the constructor's api is already
> modified. In this theoretical example, is there a mechanism by which the
> job config.xml could be updated to match the new constructor layout before
> the initialization call?
>
> --
> 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/6d3e9c5d-69a2-4535-8444-2f1dab44f9b2%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/6d3e9c5d-69a2-4535-8444-2f1dab44f9b2%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Extension indexer restored to jenkins.io

[Robert Sandell]

+1 biiilion
Thank you!!

/B

2017-06-11 20:53 GMT+02:00 Daniel Beck <m...@beckweb.net>:

>
> > On 11. Jun 2017, at 20:02, Oleg Nenashev <o.v.nenas...@gmail.com> wrote:
> >
> > As always, there is some polishing which could be done
>
> To clarify, feature and improvement requests should of course also be
> filed in Jira.
>
> --
> 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/BC059688-7629-4F93-AC77-50882286C075%40beckweb.net.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: [Jenkins-infra] Confluence maintenance window tomorrow (2017-06-07) from 15:30 - 17:30 UTC

[Robert Sandell]

Yepp, I'm getting [1] when trying to login

[1] org.springframework.dao.ConcurrencyFailureException: Hibernate
operation: Could not execute JDBC batch update; SQL []; Lock wait
timeout exceeded; try restarting transaction; nested exception is
java.sql.BatchUpdateException: Lock wait timeout exceeded; try
restarting transaction



2017-06-07 20:32 GMT+02:00 R. Tyler Croy <ty...@monkeypox.org>:

>
> The wiki is back online, but some users may have difficulty logging in with
> fresh sessions. Confluence is still syncing user data from LDAP and is
> likely
> going to be doing so for the next couple hours.
>
>
>
> - R. Tyler Croy
>
> --
>  Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>  xmpp: rty...@jabber.org
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> --
>
> --
> 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/20170607183211.6ijht2y3kfij5hnz%40blackberry.
> coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Opening Plugin Compatibility Tester

[Robert Sandell]

that is strange, I remember copying something from a freestyle job on one
of the Jenkins project's masters for the initial draft of our internal PCT
job. But I think it was disabled at the time probably due to it being flaky
and using up too much resources for the project.
Perhaps it got lost in the migration to ci.jenkins.io?

/B

On Tue, May 9, 2017 at 10:11 AM, Oliver Gondža <ogon...@gmail.com> wrote:

> Hi,
>
> For a period of time I see several people from CB contributing to PCT
> itself and addressing problem in plugins pointing out PCT related problems.
> However, last time I checked, I have not found a compelling documentation
> on how to run it or any public Jenkins job where people can check the
> results. Hence I presume CB is running those tests internally.
>
> While I do appreciate people are working on improving the testing and the
> code itself, I would like all that could be opened for people to reuse and
> run it on ci.jenkins.io (ideally) where everybody can check for the
> results. (Consider your are the maintainer that received a PR that purports
> to fix something you have no evidence of being broken referring to a
> TLA-named testsuite you have never heared of and have no easy way to
> checking for yourself...)
>
> Is there any chance you can update the wiki and share your Jenkinsfiles?
>
> Thanks
> --
> oliver
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/95cc19a3-b5ce-ae51-8366-c3faf840887d%40gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline Shared Groovy Libraries and system groovy script classpath

[Robert Sandell]

I'm not really sure what you are asking here, how did you call these
scripts before?

A Pipeline Shared Groovy Librariy that is trusted is able to call any
Jenkins api since it is not running in the sandbox, although still running
in CPS, but should still be able to call for example
RemotingDiagnostics.executeGroovy even though it is a biig security risk to
do so.

The scriptler plugin has a library feature iirc that can also be run as a
build step.

/B

On Sun, May 7, 2017 at 3:09 PM, 'Bruno P. Kinoshita' via Jenkins Developers
<jenkinsci-dev@googlegroups.com> wrote:

> +1 Andreas
>
>
> Wanting the same right now. Started a small sandbox [1] some time ago to
> try understand everything I would need for active-choices, but got
> distracted by security and performance issues.
>
> * Execute a Groovy script
> * Allow user to add extra jars
> * Graple dependency management support
> * Option to enable script-security integration (on by default)
>
> The Groovy execution layer in active-choices came from
> dynamicparameter-plugin, then was a bit tweaked. Later we added
> script-security. Now need to look into extra jars (right now integrating
> ImageJ).
>
> Cheers
> Bruno
> [1] https://github.com/kinow/groovy-script-lib
>
> 
> From: Andreas Mandel <andreas.man...@gmail.com>
> To: Jenkins Developers <jenkinsci-dev@googlegroups.com>
> Sent: Sunday, 7 May 2017 10:14 PM
> Subject: Pipeline Shared Groovy Libraries and system groovy script
> classpath
>
>
>
> Hi List,
>
> since the last security updates, a common practice to work with system
> groovy scripting does not work any more. It might be easily resolvable with
> a small(?) change in the Pipeline Shared Groovy Libraries plugin.
>
> We have a lot of system groovy scripts in Jenkins jobs that take care for
> cleanup, monitoring, etc. These jobs check out certain scripts from SCM and
> then call them as a system groovy script. With the recent changes, you
> cannot simply add and call something "dynamic" in the workspace as system
> groovy script anymore. I do not want to go a step back and put the whole
> code inside the Jenkins job definition.
>
> On the other hand with the Pipeline Shared Groovy Libraries plugin we now
> have a quite powerful library management plugin for groovy libraries.
> Unfortunately as of now this only works for pipeline jobs and not for the
> use in system groovy scripts.
>
> Would it be possible to add a functionality to mark a library in the
> Pipeline Shared Groovy Libraries plugin as "system groovy library" and so
> make it available on the class path of any system groovy script?
>
> Could this work out? How are other resolving this topic?
>
>
> Thanks,
> Kind Regards,
> Andreas.
>
> --
> 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/c3537dfe-c206-428d-9e3a-7a298d98a785%
> 40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/800881429.5606274.1494162579878%40mail.yahoo.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Job Configuration Code Questions

[Robert Sandell]

There are plenty of examples beneeth the "Implementations" tap on the
Extension Points page on the wiki
https://wiki.jenkins-ci.org/display/JENKINS/Extension+points#Extensionpoints-hudson.tasks.BuildWrapper
Pick a plugin that you are somewhat familiar with to start.

On Fri, May 5, 2017 at 4:44 PM, Goran Dev <developer.go...@gmail.com> wrote:

> Can you give me an example of a BuildWrapper please? Not familiar with it.
>
> Cheers, Goran.
>
> On May 5, 2017, 4:48 AM -0400, Robert Sandell <rsand...@cloudbees.com>,
> wrote:
>
> Answers inline
>
>
> On Fri, May 5, 2017 at 9:09 AM, Goran Dev <developer.go...@gmail.com>
> wrote:
>
>> I'm writing a plugin, it's already released as zap-plugin.
>> GitHub.com/jenkinsci/zap-plugin
>>
>> On jenkins LTS, in a Job Configuration you have various tabs (sections)
>> such as General, Source Code Management, Build Triggers, Build Environment,
>> Bindings, Build, Post-build Actions.
>>
>> 1) is it possible for me to add a tab/section called "ZAP Environment" or
>> no? If it's possible, how do I go about adding another section/tab.
>>
>
> JopProperty <http://javadoc.jenkins-ci.org/hudson/model/JobProperty.html>
> goes under General, SCM
> <http://javadoc.jenkins-ci.org/hudson/scm/SCM.html> under Source Code
> Management, Trigger
> <http://javadoc.jenkins-ci.org/hudson/triggers/Trigger.html> under Build
> Triggers, BuildWrapper
> <http://javadoc.jenkins-ci.org/hudson/tasks/BuildWrapper.html> under
> Build Environment etc.
> Maybe a JobProperty with an  would
> add another tab I'm not sure.
>
>
>>
>> 2) under the tab Build, you click on the drop down and you can add your
>> plugins build step which in my case is called Execute ZAP. Once it's added,
>> how do prevent the user from adding another Execute ZAP build step.
>>
>
> No, Build Steps are intended to be added as many as the user needs, IIRC a
> Recorder or Publisher can only be added once for Freestyle, but that
> "limitation" is gone for pipelines. Sounds like it is more like a
> BuildWrapper that you want to do.
>
>
>> Does that clarify it? If not, what else can I do to clarify the question.
>> Thanks :)
>>
>> Cheers, Goran.
>>
>> On May 5, 2017, 2:31 AM -0400, Baptiste Mathus <m...@batmat.net>, wrote:
>>
>> Please use the users list for such questions.
>> If your question is about writing a plugin for this, I guess you need to
>> be more specific.
>>
>> Cheers
>>
>>
>> Le 5 mai 2017 8:21 AM, "JordanGS" <developer.go...@gmail.com> a écrit :
>>
>>
>>1. I can add my Job Build step which is called "Run ABC" from the
>>drop down list, after it's added. How do i prevent the user from adding
>>another Build Step "Run ABC"?
>>2. How do i add a job configuration. Not a Post build step or a build
>>step but rather a some options which are above the build step? It would be
>>a text box for example and a checkbox, both of which could accessible from
>>a build step / post build step. Would it be possible have these become
>>environment variables / globally accessible variables throughout this 
>> job's
>>config.
>>
>> Thanks
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/e78dd486-3b40-406b-baf0-41a31193c3c9%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/e78dd486-3b40-406b-baf0-41a31193c3c9%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/jenkinsci-dev/L39Mu7drhDI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/jenkinsci-dev/CANWgJS43Y3mgsaxxdLpgFAy90%3DFWwF5wD%
>> 2BF8zxwz0D9i5rk2Vw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS43Y3mgsaxxdLpgFAy90%3DFWwF5wD%2BF8

Re: Job Configuration Code Questions

[Robert Sandell]

Answers inline


On Fri, May 5, 2017 at 9:09 AM, Goran Dev <developer.go...@gmail.com> wrote:

> I'm writing a plugin, it's already released as zap-plugin.
> GitHub.com/jenkinsci/zap-plugin
>
> On jenkins LTS, in a Job Configuration you have various tabs (sections)
> such as General, Source Code Management, Build Triggers, Build Environment,
> Bindings, Build, Post-build Actions.
>
> 1) is it possible for me to add a tab/section called "ZAP Environment" or
> no? If it's possible, how do I go about adding another section/tab.
>

JopProperty <http://javadoc.jenkins-ci.org/hudson/model/JobProperty.html>
goes under General, SCM <http://javadoc.jenkins-ci.org/hudson/scm/SCM.html>
under Source Code Management, Trigger
<http://javadoc.jenkins-ci.org/hudson/triggers/Trigger.html> under Build
Triggers, BuildWrapper
<http://javadoc.jenkins-ci.org/hudson/tasks/BuildWrapper.html> under Build
Environment etc.
Maybe a JobProperty with an  would
add another tab I'm not sure.


>
> 2) under the tab Build, you click on the drop down and you can add your
> plugins build step which in my case is called Execute ZAP. Once it's added,
> how do prevent the user from adding another Execute ZAP build step.
>

No, Build Steps are intended to be added as many as the user needs, IIRC a
Recorder or Publisher can only be added once for Freestyle, but that
"limitation" is gone for pipelines. Sounds like it is more like a
BuildWrapper that you want to do.


> Does that clarify it? If not, what else can I do to clarify the question.
> Thanks :)
>
> Cheers, Goran.
>
> On May 5, 2017, 2:31 AM -0400, Baptiste Mathus <m...@batmat.net>, wrote:
>
> Please use the users list for such questions.
> If your question is about writing a plugin for this, I guess you need to
> be more specific.
>
> Cheers
>
>
> Le 5 mai 2017 8:21 AM, "JordanGS" <developer.go...@gmail.com> a écrit :
>
>
>1. I can add my Job Build step which is called "Run ABC" from the drop
>down list, after it's added. How do i prevent the user from adding another
>Build Step "Run ABC"?
>2. How do i add a job configuration. Not a Post build step or a build
>step but rather a some options which are above the build step? It would be
>a text box for example and a checkbox, both of which could accessible from
>a build step / post build step. Would it be possible have these become
>environment variables / globally accessible variables throughout this job's
>config.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/jenkinsci-dev/e78dd486-3b40-406b-baf0-41a31193c3c9%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/e78dd486-3b40-406b-baf0-41a31193c3c9%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/L39Mu7drhDI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANWgJS43Y3mgsaxxdLpgFAy90%
> 3DFWwF5wD%2BF8zxwz0D9i5rk2Vw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS43Y3mgsaxxdLpgFAy90%3DFWwF5wD%2BF8zxwz0D9i5rk2Vw%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/86679e96-0e85-4de2-be02-5e8dd97277cd%40Spark
> <https://groups.google.com/d/msgid/jenkinsci-dev/86679e96-0e85-4de2-be02-5e8dd97277cd%40Spark?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Post Build Step Console Output?

[Robert Sandell]

The perform
<http://javadoc.jenkins-ci.org/jenkins/tasks/SimpleBuildStep.html#perform-hudson.model.Run-hudson.FilePath-hudson.Launcher-hudson.model.TaskListener->
method gets the TaskListener
<http://javadoc.jenkins-ci.org/hudson/model/TaskListener.html> as a
parameter.

So listener.getLogger().println("Hello World")

/B

On Fri, May 5, 2017 at 5:07 AM, JordanGS <developer.go...@gmail.com> wrote:

> If i have a post build step, how do i get it to output to the Builds  *Console
> Output *or at least to the terminal window which started jenkins? Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/a7363e76-acd9-4351-b010-1e7c2fc707f0%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/a7363e76-acd9-4351-b010-1e7c2fc707f0%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Pipeline gdsl for ci.jenkins.io

[Robert Sandell]

http://www.tothenew.com/blog/gdsl-awesomeness-understanding-context-and-contributors-in-detail/

But I refrained from associating it with the Jenkinsfile regexp pattern
because at the time I wasn't writing any pipeline scripts in Jenkinsfile
files so for me at the time it would have rendered the gdsl useless :)

/B

On Thu, May 4, 2017 at 4:59 PM, Jesse Glick <jgl...@cloudbees.com> wrote:

> On Thu, May 4, 2017 at 10:32 AM, Oliver Gondža <ogon...@gmail.com> wrote:
> > pardon my ignorance but is there any way to associate
> > `Jenkinsfile*` pattern with it?
>
> You will need to ask someone who uses IDEA.
>
> --
> 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/CANfRfr0bCUBdF9QwbN%2B_1ESpAciKkT%3D7pj8wrHyp-
> veyDc5K5Q%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: How could I share, on main page, a sidebar link who address to F:\ ? (Secundary HDD)

[Robert Sandell]

RootAction is the extensionpoint that adds a side bar link, on it's index
view your plugin can serve whatever content you like

https://wiki.jenkins-ci.org/display/JENKINS/Extension+points#Extensionpoints-hudson.model.RootAction
https://wiki.jenkins-ci.org/display/JENKINS/Action+and+its+family+of+subtypes
https://jenkins.io/doc/developer/views/

/B


On Thu, May 4, 2017 at 12:54 PM, Manuel Mariscal <mariscal.ma...@gmail.com>
wrote:

> Hi everyone!
>
> I was looking for some help, but never found any answer, there's some
> plugin or some trick to share it? If cannot by sidebar plugin, i accept
> some advises ;)
>
> Thank you very much
>
> Regards
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/1814ed3b-9f76-4ec7-b137-bb24b51dbebc%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/1814ed3b-9f76-4ec7-b137-bb24b51dbebc%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Add icons 'disable project' & 'configure' to be on tap at dashboard

[Robert Sandell]

There already is a button to disable all jobs on a Jenkins instance, it's
called "Prepare for shutdown" ;)

/B

On Fri, Apr 28, 2017 at 2:18 PM, Kanstantsin Shautsou <
kanstantsin@gmail.com> wrote:

> As we are talking in maillist for developers could you provide Pull
> Request with your changes, then we will be able to discuss it?
>
> On Apr 28, 2017, at 15:15, Manuel Mariscal <mariscal.ma...@gmail.com>
> wrote:
>
> Better for both (jenkins & blue ocean) and please, could be a button to
> disable all jobs of the jenkins? It's really interesting to disconnect
> these jobs once clicked, thank you very much.
>
> Regards
> El vie., 28 de abril de 2017 14:10, Manuel Mariscal <
> mariscal.ma...@gmail.com> escribió:
>
>> Normal jenkins (Jenkins 2.57 nowadays)
>>
>> Thank you
>>
>> Regards
>>
>> El vie., 28 de abril de 2017 0:52, Kanstantsin Shautsou <
>> kanstantsin@gmail.com> escribió:
>>
>>> Workflow that still doesn't have disable button? ;)
>>>
>>>
>>> On Friday, April 28, 2017 at 1:46:30 AM UTC+3, Oleg Nenashev wrote:
>>>>
>>>> Could you please clarify what you mean?
>>>> BlueOcean UI or what?
>>>>
>>>> четверг, 27 апреля 2017 г., 11:15:33 UTC+2 пользователь Manuel Mariscal
>>>> написал:
>>>>>
>>>>> Hi everyone!
>>>>>
>>>>> First of all, thank you very much for your job, it's really
>>>>> interesting and useful.
>>>>>
>>>>> I'd like to ask for if it's possible to change the state of jobs at
>>>>> the right, and at the left set the most important icons (CONFIGURE, BUILD
>>>>> NOW, DISABLE) in addition to the drop-down list (on Dashboard). Thank you
>>>>> very much
>>>>>
>>>>> Kind regards
>>>>>
>>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Jenkins Developers" group.
>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>> topic/jenkinsci-dev/TCwsGotrvYc/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/jenkinsci-dev/f46f5014-c9a5-4d04-a13f-3f3f6aaf9870%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/f46f5014-c9a5-4d04-a13f-3f3f6aaf9870%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/TCwsGotrvYc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAFEXo0qFfJ_ZA97rVr9SPy7ZR23XHXgdqD8iWPQH8
> eC8a%3Dexig%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFEXo0qFfJ_ZA97rVr9SPy7ZR23XHXgdqD8iWPQH8eC8a%3Dexig%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/A413AEAF-A2EE-4D2F-9D91-F3725F99BECA%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/A413AEAF-A2EE-4D2F-9D91-F3725F99BECA%40gmail.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Script Security Plugin

[Robert Sandell]

The init scripts should not be guarded by script security. From the stack
trace it looks like you are running your script in a Freestyle project with
a script build step, and those are guarded by script security.
You should ask on the Jenkins users list for these kinds of questions.

/B

On Tue, Apr 25, 2017 at 3:43 PM, Tomasz Szandała <tomasz.szand...@gmail.com>
wrote:

> Greetings,
> I have started working on a Jenkins configuration as a code - create a
> bunch of init scripts, put them to JENKINS_HOME and run Jenkins.war (2.32+)
>
> But I've met a problem:
>
> ERROR: Build step failed with exception
> org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException 
> <http://stacktrace.jenkins-ci.org/search?query=org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException>:
>  script not yet approved for use
> at 
> org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:459)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using=method>
> at 
> org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:170)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate=method>
> at hudson.plugins.groovy.SystemGroovy.run(SystemGroovy.java:95) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.groovy.SystemGroovy.run=method>
> at hudson.plugins.groovy.SystemGroovy.perform(SystemGroovy.java:59) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.plugins.groovy.SystemGroovy.perform=method>
> at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.tasks.BuildStepMonitor$1.perform=method>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
>  
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.perform=method>
> at hudson.model.Build$BuildExecution.build(Build.java:206) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.build=method>
> at hudson.model.Build$BuildExecution.doRun(Build.java:163) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Build$BuildExecution.doRun=method>
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run=method>
> at hudson.model.Run.execute(Run.java:1728) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute=method>
> at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.FreeStyleBuild.run=method>
> at 
> hudson.model.ResourceController.execute(ResourceController.java:98) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute=method>
> at hudson.model.Executor.run(Executor.java:405) 
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run=method>
> Build step 'Execute system Groovy script' marked build as failure
>
>
>
>
> I have tried writting a script, that installs plugins to also enable
> Permissive whitelist, but error still occurs:
>
> import jenkins.model.Jenkins
>
> def pm = Jenkins.instance.pluginManager
> def uc = Jenkins.instance.updateCenter
> uc.updateAllSites()
> def deployed = false
>
> def plugins = [
> // list of plugins
> ]
>
> plugins.each {
> println "Checking ${it}"
>   if (! pm.getPlugin(it)) {
> deployment = uc.getPlugin(it).deploy()
> deployment.get()
> deployed = true
>   }
> }
>
> if (deployed) {
> Jenkins.instance.restart()
> }
> org.jenkinsci.plugins.permissivescriptsecurity.PermissiveWhitelist.enabled=true
>
>
>
> But this doesn't help...
>
> How to get rid of this problem?
>
> --
> 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/96659875-4d1b-4bc8-85ff-fc43537805ac%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/96659875-4d1b-4bc8-85ff-fc43537805ac%40googlegroups.com?utm_medium=email_source=footer>
> .
> For mo