Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

I'm glad my mega-reply did turn up after all (just belatedly), anyway, replies inline! The existing Metrics plugin is using the Dropwizard interface, so: > say, there isn't a world in which I wouldn't use statsd for this :) My > current > thinking is to incorporate the Metrics plugin >

Re: [JENKINS-45892] How to identify jobs

On Mon, Mar 19, 2018 at 5:52 PM, Ullrich Hafner wrote: > I would like to keep a reference to a Run of another Job in one of my actions. Normally `Run.toExternalizableId` is used for this purpose. > if someone renames the job, then my references will break. Is there an

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

Some technical notes: On Mon, Mar 19, 2018 at 4:19 PM, Samuel Van Oort wrote: >> distinct built-in step invocations (i.e. not counting Global Variable >> invocations) > > This can't be measured easily from the flow graph due to the potential to > create multiple block

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

(replies inline) On Mon, 19 Mar 2018, Samuel Van Oort wrote: > Late to the party because I was heads-down on Pipeline bugs a lot of > Friday, but this is a subject near-and-dear to my heart and in the past > I've discussed what metrics might be interesting since this was an explicit > intent

[JENKINS-45892] How to identify jobs

I would like to keep a reference to a Run of another Job in one of my actions. Due to [JENKINS-45892] I’m not allowed to reference the Run as an object anymore, the object needs to be transient. In order to restore the reference after deserialization, I rather need to store an ID. Which ID can

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

I think Google Groups somehow managed to eat a *very* long and detailed reply here, possibly as a result of a message deletion somewhere (or it somehow got kicked into the spam filter) *sigh* so I'm going to give just the TLDR of it. Something on this has been on my want-to-have list for a

Re: Nullable single constructor parameter with declarative pipeline

I watched the ticket, thanks! Le lundi 19 mars 2018 12:51:13 UTC+1, Andrew Bayer a écrit : > > So, there is a ticket for this in Declarative - > https://issues.jenkins-ci.org/browse/JENKINS-42772 - but I have yet to be > happy with a solution. I can’t, so far as I’m aware, check the >

Re: [Essentials] Collecting usage telemetry from Jenkins Pipeline

Late to the party because I was heads-down on Pipeline bugs a lot of Friday, but this is a subject near-and-dear to my heart and in the past I've discussed what metrics might be interesting since this was an explicit intent to surface from my Bismuth (Pipeline Graph Analysis APIs). Some of

Re: Programmatically enable multiple Reporter instances

On Mon, Mar 19, 2018 at 12:55 PM, Ullrich Hafner wrote: > Isn’t it possible to create multiple Reporter or Publisher instances in a job? Not in freestyle projects. It is trivial in Pipeline projects. -- You received this message because you are subscribed to the

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

On Fri, Mar 16, 2018 at 9:11 PM, martinda wrote: > I have the impression that you are saying that this > GSoC project idea is a bit too shallow on the quantity of code for GSoC. Perhaps. Depends on what approach you want the feature to take—adding a convenience veneer

[GSoC 2018] Timeslots for Code Coverage API project discussion

Hi all, Since there is a lot of interest about the Code Coverage API project in the developer mailing list, we are going to set up a meeting during this week. We have created Doodle to get your feedback regarding the preferred time. Please cast your

Programmatically enable multiple Reporter instances

Isn’t it possible to create multiple Reporter or Publisher instances in a job? I’m writing a new publisher for the static analysis plugins but it seems that I can select it just once in a job. (I can wrap the publisher in another object and use a repeatable but that seems somewhat cumbersome

Re: [GSoC 2018] UPDATE for CODE Coverage API Plugin

I have reached out to the project mentors. IIUC they are going to setup a meeting to this week, stay tuned. BR, Oleg On Mon, Mar 19, 2018 at 3:07 PM, Rajgure Abhishek Sanjay Abhishek Sanjay < iit2014...@iiita.ac.in> wrote: > can you guys suggest me some time slots according to your schedule ,

Re: [GSoC 2018] UPDATE for CODE Coverage API Plugin

can you guys suggest me some time slots according to your schedule , i wish you too show my work and discuss about the another possible solution for this problem. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this

Re: Multibranch event listener for Github PR labels

On Monday, March 19, 2018 at 8:13:59 AM UTC, Stephen Connolly wrote: > > > What did I do in Gitea plugin? > > If I made the constructor public there, then that’s what we should > probably be doing in GitHub/ Bitbucket > In Gitea, it seems the SCMHead has a public constructor but the

Re: Nullable single constructor parameter with declarative pipeline

So, there is a ticket for this in Declarative - https://issues.jenkins-ci.org/browse/JENKINS-42772 - but I have yet to be happy with a solution. I can’t, so far as I’m aware, check the DescribableModel for the class in question, and see it’s got a sole required argument *and* see that it could be

Re: Nullable single constructor parameter with declarative pipeline

Though it's possibly a bug, why use @DataBoundConstructor instead of @DataBoundSetter? I generally use the constructor for required params, and setters for optional ones. 2018-03-19 11:48 GMT+01:00 Julien HENRY : > Hi folks, > > Our SonarQube plugin has a build step

Nullable single constructor parameter with declarative pipeline

Hi folks, Our SonarQube plugin has a build step that contains a "single nullable parameter": @DataBoundConstructor public OurStep(@Nullable String param) { // } This allows users to use one of the two syntaxes in their scripted pipelines: ourStep { } or ourStep('value') { } With

Re: [GSOC 2018] Code Coverage API Plugin

Hi, Thank you so much for taking your time to respond. I have a doubt?. Am i too late for preparing the project idea? Thanks Pavan On Saturday, 17 March 2018 23:44:00 UTC-7, Pavan Hegde wrote: > > Hi, > > I'm Pavan Hegde i'm currently pursuing my 3rd year of B.E. in computer > science in City

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 08:39, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On Mon 19 Mar 2018 at 08:13, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> >> On Mon 19 Mar 2018 at 00:50, Steven F wrote: >> >>> I locally modified GHBS to make

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 08:13, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > > On Mon 19 Mar 2018 at 00:50, Steven F wrote: > >> I locally modified GHBS to make the constructors for PullRequestSCMHead >> and PullRequestSCMRevision public which has seemingly

Re: Multibranch event listener for Github PR labels

On Mon 19 Mar 2018 at 00:50, Steven F wrote: > I locally modified GHBS to make the constructors for PullRequestSCMHead > and PullRequestSCMRevision public which has seemingly solved the problem. > What did I do in Gitea plugin? If I made the constructor public there,

Re: [GSOC 2018] [Student Introduction & query] Simple Pull-Request Job Plugin

I have made changes according to your comments. Thank you very much. On Sunday, March 18, 2018 at 9:55:44 PM UTC+5:30, martinda wrote: > > Hello Abhishek, > > Thank you for sharing the proposal. I have added some comments for your > consideration. > > Best, > Martin > > On Sunday, March 18, 2018