Re: Simple Jenkins Example Project

[Daniel Beck]

> On 11.04.2017, at 08:30, Goran Dev  wrote:
> 
> Jelly or groovy UI I mean, or maybe one simple to understand project for 
> each. Not something too massive.
> 

UI Samples Plugin? It's only Jelly, but still should be useful. No hacks around 
dealing with backwards compatibility etc. you sometimes see in real plugins 
that give a false impression.

https://github.com/jenkinsci/ui-samples-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/FECB8FAF-E626-4B2A-9386-1EB823074253%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: [PROPOSAL] Change core logging from Java Utils Logging

[Stephen Connolly]

Even if you buffer the loggers you still are 50% slower due to poor message
formatting and always capturing the stack trace for every log message to be
able to report the call site

On 11 April 2017 at 15:25, Jesse Glick  wrote:

> On Tue, Apr 11, 2017 at 9:14 AM, Stephen Connolly
>  wrote:
> > Java Utils Logging is horrible in terms of performance.
>
> All I see from a quick read is that unbuffered handlers are a problem
> if you are in fact logging tons of messages. In normal operation
> Jenkins does _not_ logs tons of messages—unless you have set up a
> `FINE` logger in `support-core`, but that has its own handlers, which
> we can trivially buffer if they are not already.
>
> So why would we waste precious developer time, and risk
> incompatibilities? Is there some actual significant performance issue
> *in Jenkins* (not a microbenchmark) that you are trying to fix?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CANfRfr2GsqAt3Xme5vutbUC%3D3PmoHCjuatRMwPJUGB-4R__Npg%
> 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%2BnPnMz57h4zFuShN%3DobWO9wHUXJzqe2ie4ByS5Lm2wAvXwLDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PROPOSAL] Change core logging from Java Utils Logging

[Jesse Glick]

On Tue, Apr 11, 2017 at 9:14 AM, Stephen Connolly
 wrote:
> Java Utils Logging is horrible in terms of performance.

All I see from a quick read is that unbuffered handlers are a problem
if you are in fact logging tons of messages. In normal operation
Jenkins does _not_ logs tons of messages—unless you have set up a
`FINE` logger in `support-core`, but that has its own handlers, which
we can trivially buffer if they are not already.

So why would we waste precious developer time, and risk
incompatibilities? Is there some actual significant performance issue
*in Jenkins* (not a microbenchmark) that you are trying to fix?

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

Re: Wiki Page Layout

[Daniel Beck]

> On 11.04.2017, at 15:49, JordanGS  wrote:
> 
> You're removing the info, tip and warning macros? :(

No, just the table typically at the top of the page, as that information is 
shown elsewhere already.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0D586EC8-90BA-449D-BF0D-8426674ABE93%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Wiki Page Layout

[JordanGS]

Ahh okay, misunderstood. Thanks for the clarification :)

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

Re: Simple Jenkins Example Project

[Baptiste Mathus]

Find one or two plugins you know well from a user perspective, and does not
seem too big, then look for it in https://github.com/jenkinsci/ IMO

As for creating a plugin, use the documentation
 I guess. And
we're happy to hear from you on how/where to improve it.

2017-04-11 8:30 GMT+02:00 Goran Dev :

> Jelly or groovy UI I mean, or maybe one simple to understand project for
> each. Not something too massive.
>
> Cheers, Goran.
>
> On Apr 11, 2017, 2:03 AM -0400, JordanGS ,
> wrote:
>
> Can someone please point me in the direction of a simple Jenkins Project,
> either jenkins or groovy UI config files. I'm trying to understand all the
> little nuances and properly create a plugin. Thanks.
>
> --
> 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/H8dTH_MWVfw/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/b6d8eaec-296c-49ff-86c2-e4b864127c3a%
> 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/bd104fd0-25b9-4639-89b6-9270c8b6ff3c%40Spark
> 
> .
>
> 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/CANWgJS7uxgwhA2KBJ4nu3Wd3nzN8XyGh-4Ydg7BeM%2Bb1Rf_hdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Tutorial Request / An idiots guide to Jenkins

[JordanGS]

When someone from the development team has time, could they please write 
and finish a proper How to Jelly and Jenkins and a How to Groovy With 
Jenkins Plugin tutorial.

There are "some" doc's, most are unfinished, have broken links or sections 
that say TODO.

So far the best tutorial for jelly i've found is the following: 
https://wiki.jenkins-ci.org/display/JENKINS/Create+a+new+Plugin+with+a+custom+build+Step

but it's not done, supposed to be 5 part but it's only 2 ish.

Next we have: https://jenkins.io/doc/developer/

Which has incomplete sections as well: 
https://jenkins.io/doc/developer/architecture/model/ and i haven't seen any 
code examples.

--

A large tutorial isn't even needed. If there were a couple dummy plugins 
that just showed you what to do and how it worked it would be great. All 
that would be needed is a Jelly Plugin that adds a build step, or a Jelly 
Plugin that adds a post build step, or a little more and a Jelly Plugin 
that does both a Build Step, a Post Build Step and draws a dummy chart. 
Then do the same with Groovy. If i knew enough about Jenkins i would write 
these myself

Thanks for your consideration.

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

Re: Wiki Page Layout

[JordanGS]

*Currently Wiki pages are being pulled to https://plugins.jenkins.io/ 
,
 
and I am not sure that newly introduced layouts will work correctly there*I 
didn't know that, i have a lot to fix then haha


*It doesn't even work currently, because the plugin info macro is supposed 
to be removed from the main content :-(*You're removing the info, tip and 
warning macros? :(

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

Re: Bug Triage "Team"

[Slide]

Any time that people can give is great. Even a spare 10 minutes here and
there would be helpful if you spread it across a large number of people.

On Tue, Apr 11, 2017 at 4:01 AM Mark Waite 
wrote:

> My situation is similar to Oleg's.  My first priority is to review bugs
> submitted against the plugins I maintain, and to reproduce bugs for those
> plugins, and to create automated environments to reproduce those bugs.
> Helping with other projects will come as a second priority.
>
> Mark Waite
>
> On Tue, Apr 11, 2017 at 3:13 AM Oleg Nenashev 
> wrote:
>
> Hi all,
>
> I am in.
>
> Right now I dedicate time for reviewing incoming issues in the core,
> Remoting, "_unsorted", a couple of other modules and a bunch of plugins I
> am supposed to maintain. I can unlikely dedicate more time to review other
> components (would prefer to do bugfixing in core/remoting), but at least I
> am ready to keep working on the current stuff.
>
> BR, Oleg
>
> 2017-04-11 10:07 GMT+02:00 Daniel Beck :
>
>
> > On 10.04.2017, at 22:44, Slide  wrote:
> >
> > if you are interested!
>
> I am.
>
>
> --
> 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/XToix3QpL_k/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/2F5B15D7-B147-4F4B-B8CE-04760B1F9A7D%40beckweb.net
> .
> 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/CAPfivLAypc6o5YBYDAVNKqD0euqGhLJ%2B-Z929s8fkZU51ZZv%2BA%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/CAO49JtHqHF8aboPTWkGQYx%2BF_qCHPd2bMGZ8HChVauPuk6NbGQ%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/CAPiUgVfbWcwsZGyA4N1BEp_XiE%2Byb7_caP674h_-HyA8fmgFCg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [PROPOSAL] Change core logging from Java Utils Logging

[Jesse Glick]

On Tue, Apr 11, 2017 at 11:35 AM, Stephen Connolly
 wrote:
> you still are 50% slower due to poor message
> formatting and always capturing the stack trace

But again what is the actual impact on a typical instance producing on
the order of one log message per minute? A millisecond here or there?
If you are looking for performance optimizations I am guessing there
are much lower-hanging fruit.

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

Re: Simple Jenkins Example Project

[JordanGS]

@Baptiste Mathus I really don't know, outside of the plugin i am working 
on, i don't use any Build Plugins. Maybe you can point me in the right 
direction? I just need some simple that adds a Build Step and that Build 
step does something but also uses values set in the Admin Configurations.

My plugin is: https://github.com/jenkinsci/zap-plugin

I am trying to trace a serialization error. I'll be more than happy to make 
a list for how documentation can be improved. I found a few dead links or 
unfinished tutorials that are being linked as developer guides which makes 
it rather hard to learn. Thanks for the feedback :)

@Daniel Beck

Those helped me a great deal when i was learning :) The documentation 
around jelly is somewhat sparse.

Example of my current code.


  


and i want to change this to:


  

  ${%Title}
  

  


from my understand of jelly, this should be an acceptable change but it's 
not. It throws NPE exceptions on unrelated boolean (Not Boolean) values. 
See this post 
if 
interested. So i'm trying to figure out what i'm doing wrong, even if i 
remove the plugin or rename it, it still breaks. So it doesn't make me 
believe it's a backwards compatibility issue. I thought maybe it was 
because i suppressed warnings and errors, so i spent 3 hours fixing all of 
them and i still can't make this simple change. Thanks for your help, much 
appreciated.

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

Groovy Save Exception after run

[pallen]

Hi Guys,

I'm getting an exception after running my own DSL task 'P4Groovy':

The extension is here 
,
 
in 'GetP4' I extend Builder and implement SimpleBuildStep to execute the 
task and then create the step by extending 'Step' in 'GetP4Step' (that bit 
of code has been updated from 'AbstractStepImpl').  However, the exception 
remains the same regardless of my recent updates.  The build step runs and 
I can see the output in the log, however on close of the workflow it throw 
the exception below...

In Jenkins 1.642.3 I get no NPE, however with 2.32 I see the NPE?  

If I mark my use of TaskListener listener as transient then no exception? 
 However no logs for my DSL task :-(

Any pointers would be greatly appreciated.

Kind regards,
Paul



Apr 11, 2017 5:30:01 PM org.jenkinsci.plugins.workflow.cps.CpsThreadGroup 
saveProgramIfPossible
WARNING: program state save failed
java.io.IOException: Failed to persist 
/Users/pallen/Workspaces/main.p4-jenkins/dev/work/jobs/groovy/builds/10/program.dat
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:461)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:427)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgramIfPossible(CpsThreadGroup.java:415)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:360)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240)
at 
org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228)
at 
org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at 
jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
hudson.remoting.RemoteOutputStream.writeObject(RemoteOutputStream.java:82)
at sun.reflect.GeneratedMethodAccessor294.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:271)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at 
org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
at 
org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
at 
org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50)
at 
org.jboss.marshalling.river.RiverObjectOutputStream.writeObjectOverride(RiverObjectOutputStream.java:179)
at 
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
at 
hudson.util.StreamTaskListener.writeObject(StreamTaskListener.java:163)
at sun.reflect.GeneratedMethodAccessor293.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at 
org.jboss.marshalling.reflect.SerializableClass.callWriteObject(SerializableClass.java:271)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:976)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
at 
org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
at 
org.jboss.marshalling.river.BlockMarshaller.doWriteObject(BlockMarshaller.java:65)
at 
org.jboss.marshalling.river.BlockMarshaller.writeObject(BlockMarshaller.java:56)
at 
org.jboss.marshalling.MarshallerObjectOutputStream.writeObjectOverride(MarshallerObjectOutputStream.java:50)
at 

Re: Groovy Save Exception after run

[Jesse Glick]

On Tue, Apr 11, 2017 at 12:47 PM, pallen  wrote:
> If I mark my use of TaskListener listener as transient then no exception?

Yes the `TaskListener` field must be `transient`. It cannot be
serialized as part of the program state. (While it is marked
`Serializable`, that is only for serializing over a Remoting
`Channel`—very different.)

> However no logs for my DSL task

I am afraid I do not follow.

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

Internationalized Help files?

[JordanGS]

We can internationalize the job config page. After following: these 
instructions 
.
 
I got that working for the ones Jenkins didn't automatically pick up.

I was wondering though, can we also internationalize the help files? For 
example i have a help file called *help-myproject.html*, i tried changing 
it to 

*help-myproject_fr.html*That was my first thought but it didn't work. I 
haven't seen any documentation to show that it can't be done, but i also 
haven't seen any that shows how to do it. I have seen the Mailer plugin 
attempt the same thing as i but it doesn't work in it, so maybe this was a 
feature that's not longer supported?

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/76df38c1-edcd-4709-ae86-21d49ec52f35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Simple Jenkins Example Project

[Goran Dev]

Jelly or groovy UI I mean, or maybe one simple to understand project for each. 
Not something too massive.

Cheers, Goran.

On Apr 11, 2017, 2:03 AM -0400, JordanGS , wrote:
> Can someone please point me in the direction of a simple Jenkins Project, 
> either jenkins or groovy UI config files. I'm trying to understand all the 
> little nuances and properly create a plugin. Thanks.
>
>
>
> --
> 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/H8dTH_MWVfw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-dev+unsubscr...@googlegroups.com 
> (mailto:jenkinsci-dev+unsubscr...@googlegroups.com).
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/b6d8eaec-296c-49ff-86c2-e4b864127c3a%40googlegroups.com
>  
> (https://groups.google.com/d/msgid/jenkinsci-dev/b6d8eaec-296c-49ff-86c2-e4b864127c3a%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/bd104fd0-25b9-4639-89b6-9270c8b6ff3c%40Spark.
For more options, visit https://groups.google.com/d/optout.

Re: Bug Triage "Team"

[Daniel Beck]

> On 10.04.2017, at 22:44, Slide  wrote:
> 
> if you are interested!

I am.

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

Re: Jenkins Users, Jenkins Issues banned from Google Groups?

[Arnaud Héritier]

Thus if you are already deleting them manually after they are submitted it
means that we need to activate the moderation on the list to be sure that
they never arrive ?

On Tue, Apr 11, 2017 at 12:51 AM, R. Tyler Croy  wrote:

> (replies inline)
>
> On Mon, 10 Apr 2017, Arnaud H?ritier wrote:
>
> > The only solution is to moderate the list and avoid spams (if not too
> late)
> > Perhaps an admin can delete spam messages in the group ...
>
>
> I do this every single morning. Over the weekend I didn't, and I guess we
> got
> unlukcy.
>
>
> There are three other moderators who have been coasting while I do all the
> dirty work though... :)
>
>
>
> Arnaud, if you wish to join the spam brigade, that can be arranged :)
>
>
>
>
> - R. Tyler Croy
>
> --
>  Code: 
>   Chatter: 
>  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/20170410225149.bjaldrprxv5dtqc2%40blackberry.
> coupleofllamas.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
-
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier

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

Re: Jenkins Users, Jenkins Issues banned from Google Groups?

[Carlos Sanchez]

There is an option to moderate the first post from users

On Tue, Apr 11, 2017 at 9:42 AM, Arnaud Héritier 
wrote:

> Thus if you are already deleting them manually after they are submitted it
> means that we need to activate the moderation on the list to be sure that
> they never arrive ?
>
> On Tue, Apr 11, 2017 at 12:51 AM, R. Tyler Croy 
> wrote:
>
>> (replies inline)
>>
>> On Mon, 10 Apr 2017, Arnaud H?ritier wrote:
>>
>> > The only solution is to moderate the list and avoid spams (if not too
>> late)
>> > Perhaps an admin can delete spam messages in the group ...
>>
>>
>> I do this every single morning. Over the weekend I didn't, and I guess we
>> got
>> unlukcy.
>>
>>
>> There are three other moderators who have been coasting while I do all the
>> dirty work though... :)
>>
>>
>>
>> Arnaud, if you wish to join the spam brigade, that can be arranged :)
>>
>>
>>
>>
>> - R. Tyler Croy
>>
>> --
>>  Code: 
>>   Chatter: 
>>  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/ms
>> gid/jenkinsci-dev/20170410225149.bjaldrprxv5dtqc2%
>> 40blackberry.coupleofllamas.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> -
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAFNCU--_Ka%3DB8i6-eAzaAyeiJYNBd2LNX_
> asmSJ-WMq_swBarA%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/CALHFn6OdtZmSr5ANUVLK_oAwxYeTG2UZPGNYisxGm2r0YsxJAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Simple Jenkins Example Project

[JordanGS]

Can someone please point me in the direction of a simple Jenkins Project, 
either jenkins or groovy UI config files. I'm trying to understand all the 
little nuances and properly create a plugin. 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/b6d8eaec-296c-49ff-86c2-e4b864127c3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yesterday's security advisory

[Daniel Beck]

Hi everyone,

We now had the situation where the number of vulnerabilities far exceeded what 
the security team could handle.
https://jenkins.io/security/advisory/2017-04-10/

As previously discussed on this list, I've suspended distribution of plugins 
that are currently vulnerable.
https://jenkins.io/blog/2017/04/10/security-advisory/#distributing-vulnerable-plugins

List of affected plugins:
https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L187...L209

Any thoughts about this, now that it has happened?

---

As I wrote in the blog post, I was unable to contact all maintainers. Most 
maintainers of affected plugins with fewer than 500 installations didn't learn 
about this in advance. This is really not how we usually work. I consider this 
to be an exceptional situation.

So, again, to affected plugin maintainers, I really am sorry. I just didn't see 
a feasible alternative to the chosen approach. Perhaps this thread can result 
in some ideas -- What should we do differently in the future, if a situation 
similar to this one ever comes up again?

---

And then there's plugins that needed to be delisted since they have mandatory 
dependencies on delisted plugins:
https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L212...L218

>From a security POV, there's nothing wrong (that I'm aware of) with any of 
>these, other than that they bring along with them an unsafe plugin. Some of 
>these are clearly tied to build-flow, so while that is gone, so are they. 
>Then, there are the others (maintainers in CC):

- uno-choice: This depends on Scriptler. I discussed that plugin with Domi 
(Scriptler's maintainer) when we couldn't get the fixes finished, and plan to 
work with him to fix the various issues over the next several weeks or so. Once 
that gets restored, uno-choice would also be published again.
- externalresource-dispatcher: This depends on Build Flow, whose maintainers 
added a deprecation notice to the plugin wiki last year. I would be surprised 
if that got revived again. So there's probably no good solution, other than 
cutting this dependency, if we keep unsafe plugins delisted.

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

Re: Yesterday's security advisory

['Bruno P. Kinoshita' via Jenkins Developers]

Hi Daniel,

Surprised to see scriptler there, wasn't expecting it given the number of 
people using it. If there is anything I can do to help, just let me know. I am 
a bit busy this week, but can definitely stop a couple of hours two or three 
days this week and maybe during the upcoming holidays to help fixing some 
issues.

I can try to help with scriptler (have been studying it to submit some pull 
requests / RFE's) and possibly with dynamicparameter. uno-choice was created 
based on dynamicparameter, so likely we can compare the code, look at some git 
commits, and try to pull the fix (likely security script plug-in integration?) 
into dynamicparameter.

Happy to test, reproduce bugs, or try to submit one or two pull requests if 
necessary.


>-- What should we do differently in the future, if a situation similar to this 
>one ever comes up again?

Excellent approach. Let's tackle the problem, not the blame :-)

It is not clear from your e-mail if that was a case of a problem in the process 
used to communicate issues to plug-in maintainers, or if it was caused due to 
the number of issues vs. number of people working on the issues. Do we need to 
increase the number of people in the security team, or define some timely 
process, like having a dashboard or notification system, that sends an e-mail 
every week with the number of issues pending notification?
Cheers
Bruno


From: Daniel Beck 
To: Jenkins Developers  
Cc: Bruno P. Kinoshita ; neuralsandw...@gmail.com
Sent: Tuesday, 11 April 2017 9:51 PM
Subject: Yesterday's security advisory



Hi everyone,


We now had the situation where the number of vulnerabilities far exceeded what 
the security team could handle.

https://jenkins.io/security/advisory/2017-04-10/


As previously discussed on this list, I've suspended distribution of plugins 
that are currently vulnerable.

https://jenkins.io/blog/2017/04/10/security-advisory/#distributing-vulnerable-plugins


List of affected plugins:

https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L187...L209


Any thoughts about this, now that it has happened?


---


As I wrote in the blog post, I was unable to contact all maintainers. Most 
maintainers of affected plugins with fewer than 500 installations didn't learn 
about this in advance. This is really not how we usually work. I consider this 
to be an exceptional situation.


So, again, to affected plugin maintainers, I really am sorry. I just didn't see 
a feasible alternative to the chosen approach. Perhaps this thread can result 
in some ideas -- What should we do differently in the future, if a situation 
similar to this one ever comes up again?


---


And then there's plugins that needed to be delisted since they have mandatory 
dependencies on delisted plugins:

https://github.com/jenkins-infra/backend-update-center2/blob/1be044d25a312ca90336044f501e0b9e38ca3b2e/src/main/resources/artifact-ignores.properties#L212...L218


>From a security POV, there's nothing wrong (that I'm aware of) with any of 
>these, other than that they bring along with them an unsafe plugin. Some of 
>these are clearly tied to build-flow, so while that is gone, so are they. 
>Then, there are the others (maintainers in CC):


- uno-choice: This depends on Scriptler. I discussed that plugin with Domi 
(Scriptler's maintainer) when we couldn't get the fixes finished, and plan to 
work with him to fix the various issues over the next several weeks or so. Once 
that gets restored, uno-choice would also be published again.

- externalresource-dispatcher: This depends on Build Flow, whose maintainers 
added a deprecation notice to the plugin wiki last year. I would be surprised 
if that got revived again. So there's probably no good solution, other than 
cutting this dependency, if we keep unsafe plugins delisted.

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

Re: Yesterday's security advisory

['Bruno P. Kinoshita' via Jenkins Developers]

Thanks for the detailed response Daniel.


>And even once the issue is fixed, there's overhead in coordinating release of 
>the fix, writing and publishing the advisory, blog, and warnings, sending 
>notifications, etc.

Perhaps we could create a type of Certified or Supported tag to plugins. 
Plug-ins under this tag/category would

* Use an ~recent LTS version
* Have security issues patches applied by the security team in 15 running days 
if there is no response from the maintainer
* Be released by the security team if a patch has been approved/reviewed but 
there was no response or availability of the plug-in maintainer

As a plugin developer, I would feel bad for others pushing changes and 
releasing the plug-in without notifying me; but if we had this category, then I 
think users/build engineers would favour to install plug-ins listed there, and 
as a plugin maintainer I would accept the items listed above as a way to show 
users updates would be released in a faster way.

Maybe this, combined with number of installations, could be a better indicator 
of how well maintained and production-ready the plug-in is (e.g. I would 
probably submit a plug-in to this category after I had confidence its API was 
ready and I had enough tests, fixed enough bugs, etc). Just food for thought.

>It's not enough to just assign an issue in SECURITY to plugin maintainers

Using what was suggested above, we would still assign the issue to them, but 
the security team could also work on a fix and propose the fix. Then the author 
of the plug-in could simply approve or provide further feedback.
 

> (...) (well, for me -- maybe I just suck at this)

I believe we worked on the active-choices plug-in issue, where we had to 
include the security script plug-in (SECURITY-255?). So having worked directly 
with you in the Jenkins security team, and having already dealt with CVE's in 
other libraries/projects in some companies, I must say that from the moment the 
issue was assigned to me, until we had the review, release schedule, and 
finally the review, everything was very professional and simple - from a plugin 
maintainer POV.

I felt quite bad for having a security issue in my code, but at no moment I 
felt like I was being blamed or pressured to release it as fast as possible 
(just to not disclose or leak anything about the issue at hand and carefully 
test the fix :). So kudos and thank you and all those involved in the security 
team! You definitely do not suck at this.

>We're always looking for more volunteers! Membership is open to most active 
>contributors. Prerequisites and process at https://jenkins.io/security/#team

Not the most active contributor, but will take a look to see if I can enlist, 
and maybe try to help in some way :)

Cheers
Bruno

From: Daniel Beck 
To: jenkinsci-dev@googlegroups.com 
Sent: Tuesday, 11 April 2017 10:55 PM
Subject: Re: Yesterday's security advisory




> On 11.04.2017, at 12:03, 'Bruno P. Kinoshita' via Jenkins Developers 
>  wrote:
> 
> Surprised to see scriptler there, wasn't expecting it given the number of 
> people using it. If there is anything I can do to help, just let me know. I 
> am a bit busy this week, but can definitely stop a couple of hours two or 
> three days this week and maybe during the upcoming holidays to help fixing 
> some issues.

Scriptler is also the one I hated most to delist. The advisory lists all the 
things currently wrong with Scriptler that we know of. Some of these I expect 
to be rather straightforward to fix. What needs some thinking is how to 
implement script execution in jobs in a way that's safe to use. Giving 
non-admins Run Scripts is not a good idea (in fact, this quirk of Scriptler is 
a major reason we threw in the changes to the auth strategies in this 
advisory), and build step configuration protection as implemented is rather 
easily circumvented, as demonstrated.

> It is not clear from your e-mail if that was a case of a problem in the 
> process used to communicate issues to plug-in maintainers, or if it was 
> caused due to the number of issues vs. number of people working on the issues.

Both.

It's not enough to just assign an issue in SECURITY to plugin maintainers -- 
many haven't had to deal with a privately reported security issue before, so 
the process required to prepare a fix is unusual, and we need to explain how to 
go about doing that. Then there's the problem that they may not even react, so 
I need to follow up via email, etc.

Once we have maintainers' attention, and they understand the process we'd like 
them to follow, there's the issue of implementation. Especially wrt scripting 
issues, some more advanced features may not map cleanly to sandboxing/approval. 
So these fixes took a lot more supporting effort than usual. And in cases where 
there's no maintainer, or they're not able to spend the time to fix them, 
implementation 

Re: Jenkins Users, Jenkins Issues banned from Google Groups?

[Daniel Beck]

> On 11.04.2017, at 12:22, Ioannis Moutsatsos  wrote:
> 
> but not the Jenkins Issues

It's a read-only list. You're not supposed to post to 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/92F064C6-0FC2-4D15-A929-5D75052362A1%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Yesterday's security advisory

[Daniel Beck]

> On 11.04.2017, at 12:03, 'Bruno P. Kinoshita' via Jenkins Developers 
>  wrote:
> 
> Surprised to see scriptler there, wasn't expecting it given the number of 
> people using it. If there is anything I can do to help, just let me know. I 
> am a bit busy this week, but can definitely stop a couple of hours two or 
> three days this week and maybe during the upcoming holidays to help fixing 
> some issues.

Scriptler is also the one I hated most to delist. The advisory lists all the 
things currently wrong with Scriptler that we know of. Some of these I expect 
to be rather straightforward to fix. What needs some thinking is how to 
implement script execution in jobs in a way that's safe to use. Giving 
non-admins Run Scripts is not a good idea (in fact, this quirk of Scriptler is 
a major reason we threw in the changes to the auth strategies in this 
advisory), and build step configuration protection as implemented is rather 
easily circumvented, as demonstrated.

> It is not clear from your e-mail if that was a case of a problem in the 
> process used to communicate issues to plug-in maintainers, or if it was 
> caused due to the number of issues vs. number of people working on the issues.

Both.

It's not enough to just assign an issue in SECURITY to plugin maintainers -- 
many haven't had to deal with a privately reported security issue before, so 
the process required to prepare a fix is unusual, and we need to explain how to 
go about doing that. Then there's the problem that they may not even react, so 
I need to follow up via email, etc.

Once we have maintainers' attention, and they understand the process we'd like 
them to follow, there's the issue of implementation. Especially wrt scripting 
issues, some more advanced features may not map cleanly to sandboxing/approval. 
So these fixes took a lot more supporting effort than usual. And in cases where 
there's no maintainer, or they're not able to spend the time to fix them, 
implementation falls back to the security team.

And even once the issue is fixed, there's overhead in coordinating release of 
the fix, writing and publishing the advisory, blog, and warnings, sending 
notifications, etc.

Even just getting these ~8 plugin releases out at the same time has required 
some pretty major coordination (well, for me -- maybe I just suck at this). 
Luckily for me, ikedam, Ulli Hafner, and Daniel Spilker were absolutely amazing 
to work with, and also handled fixing their plugins very well. (And the rest of 
the releases were performed by members of the security team, and they of course 
also know what they're doing!)

> Do we need to increase the number of people in the security team

We're always looking for more volunteers! Membership is open to most active 
contributors. Prerequisites and process at https://jenkins.io/security/#team

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

Re: Bug Triage "Team"

[Mark Waite]

My situation is similar to Oleg's.  My first priority is to review bugs
submitted against the plugins I maintain, and to reproduce bugs for those
plugins, and to create automated environments to reproduce those bugs.
Helping with other projects will come as a second priority.

Mark Waite

On Tue, Apr 11, 2017 at 3:13 AM Oleg Nenashev 
wrote:

> Hi all,
>
> I am in.
>
> Right now I dedicate time for reviewing incoming issues in the core,
> Remoting, "_unsorted", a couple of other modules and a bunch of plugins I
> am supposed to maintain. I can unlikely dedicate more time to review other
> components (would prefer to do bugfixing in core/remoting), but at least I
> am ready to keep working on the current stuff.
>
> BR, Oleg
>
> 2017-04-11 10:07 GMT+02:00 Daniel Beck :
>
>
> > On 10.04.2017, at 22:44, Slide  wrote:
> >
> > if you are interested!
>
> I am.
>
>
> --
> 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/XToix3QpL_k/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/2F5B15D7-B147-4F4B-B8CE-04760B1F9A7D%40beckweb.net
> .
> 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/CAPfivLAypc6o5YBYDAVNKqD0euqGhLJ%2B-Z929s8fkZU51ZZv%2BA%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/CAO49JtHqHF8aboPTWkGQYx%2BF_qCHPd2bMGZ8HChVauPuk6NbGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Users, Jenkins Issues banned from Google Groups?

[Ioannis Moutsatsos]

Thanks for your efforts Tyler and the useful tips on this issue everyone. 
The Jenkins Users group seems to be back on line this morning (4/11) but 
not the Jenkins Issues. It would be useful to identify what further needs 
to be done and enlist the help of the community to do it.

Best regards
Ioannis

On Monday, April 10, 2017 at 6:51:59 PM UTC-4, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Mon, 10 Apr 2017, Arnaud H?ritier wrote: 
>
> > The only solution is to moderate the list and avoid spams (if not too 
> late) 
> > Perhaps an admin can delete spam messages in the group ... 
>
>
> I do this every single morning. Over the weekend I didn't, and I guess we 
> got 
> unlukcy. 
>
>
> There are three other moderators who have been coasting while I do all the 
> dirty work though... :) 
>
>
>
> Arnaud, if you wish to join the spam brigade, that can be arranged :) 
>
>
>
>
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>  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/3c3c0036-2ee3-4784-9fd9-90be448bd5ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bug Triage "Team"

[Oleg Nenashev]

Hi all,

I am in.

Right now I dedicate time for reviewing incoming issues in the core,
Remoting, "_unsorted", a couple of other modules and a bunch of plugins I
am supposed to maintain. I can unlikely dedicate more time to review other
components (would prefer to do bugfixing in core/remoting), but at least I
am ready to keep working on the current stuff.

BR, Oleg

2017-04-11 10:07 GMT+02:00 Daniel Beck :

>
> > On 10.04.2017, at 22:44, Slide  wrote:
> >
> > if you are interested!
>
> I am.
>
> --
> 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/XToix3QpL_k/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/2F5B15D7-B147-4F4B-B8CE-04760B1F9A7D%40beckweb.net.
> 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/CAPfivLAypc6o5YBYDAVNKqD0euqGhLJ%2B-Z929s8fkZU51ZZv%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[PROPOSAL] Change core logging from Java Utils Logging

[Stephen Connolly]

I come with evidence, namely my comparison of the performance of JUL,
Log4J2 and Logback:

https://www.sitepoint.com/which-java-logging-framework-has-the-best-performance/

Java Utils Logging is horrible in terms of performance. About the only good
thing I can say about it is that it give a consistent throughput no matter
how many threads you throw at it... consistently crappy throughput ;-)

Given how much logging some Jenkins instances do, switching Core to either
Log4J2 or Logback should have the potential to make a significant
difference to the performance of some instances.

So before we all jump into a fight over whether to pick Log4J 2 or Logback,
there are a number of questions that we need to resolve:

1. Is Kohsuke on-board. In the past this has been a blocker.

2. We should not change the logging format for existing installations. New
installations might get a nicer single-line log message by default, but
existing instances would have to configure the switch-over

3. For compatibility issues, users may need to switch back to JUL if they
have issues. This likely means that we pick SLF4J as the API that we log
with and just configure the back-end on start-up so that you can jump back
to JUL if you really need to

4. Support Core plugin will need some rework, are there any other plugins
that hard-code assumptions that Jenkins Core uses JUL

5. Remoting may need to bundle the logging framework somehow, or at least
"just enough logging framework to bootstrap the real one"

What else do we need to line up before we can bite this one off?

-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%2BnPnMwEZUeQLVwcsG%3DyG_hkLCBJU1gNGdZ%2B%3DNywwA5uVWFWUw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.