[BlueOcean] Roadmap/Issues for contribution

2016-06-18 Thread Sundar 
Hey BlueOcean Devs,


It is really exciting to see new BlueOcean which brings new UX for Jenkins 
users.

I am looking for Blueocean roadmap/bugracking system to explore ways to 
contribute. Can some one give some pointer where to start?

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/22964ffc-ea84-4336-854a-64e7a29b1ab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Failing on first trial to release plugin to jenkins-ci.org

2016-06-18 Thread Moshe Cohen 
Hi,

I have created a plugin (that works locally) and I am following 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins in order to 
have it hosted.
Today it was forked and I reached the command "mvn release:prepare 
release:perform -Dusername=... -Dpassword=..." .

Unfortunately, this fails and I have no clue how to continue.
The first error line is   "*[ERROR] Failed to execute goal 
org.codehaus.mojo:findbugs-maven-plugin:3.0.3:check (findbugs) on project 
aqua-security-scanner: failed with 1 bugs and 0 errors -> [Help 1]*"

Attached are the full output of the above command and also my pom.xml file .

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/4497d2b2-ed6a-43f1-a505-66ab49bb1f1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
mvn release:prepare release:perform -Dusername=norbyltd -Dpassword=
[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
 with a thread count of 1
[INFO]
[INFO] 
[INFO] Building Aqua Security Scanner 1.1-SNAPSHOT
[INFO] 
[INFO]
[INFO] --- maven-release-plugin:2.5.3:prepare (default-cli) @ 
aqua-security-scanner ---
[INFO] Resuming release from phase 'run-preparation-goals'
[INFO] Executing goals 'clean install'...
[INFO] Executing: /bin/sh -c cd 
/home/ubuntu/jenkins-plugin/aqua-security-scanner-plugin && 
/usr/share/maven3/bin/mvn -s /tmp/release-settings755910864127685.xml clean 
install --no-plugin-updates
[WARNING] Command line option -npu is deprecated and will be removed in 
future Maven versions.
[INFO] Scanning for projects...
[INFO]
[INFO] Using the builder 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
 with a thread count of 1
[INFO]
[INFO] 

[INFO] Building Aqua Security Scanner 1.1-SNAPSHOT
[INFO] 

[INFO]
[INFO] --- maven-clean-plugin:2.6:clean (default-clean) @ 
aqua-security-scanner ---
[INFO] Deleting 
/home/ubuntu/jenkins-plugin/aqua-security-scanner-plugin/target
[INFO]
[INFO] --- maven-hpi-plugin:1.115:validate (default-validate) @ 
aqua-security-scanner ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
aqua-security-scanner ---
[INFO] Maven Version: 3.2.1
[INFO] JDK Version: 1.7.0_101 normalized as: 1.7.0-101
[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 
3.13.0-74-generic
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
aqua-security-scanner ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.7.2.201409121644:prepare-agent (default) @ 
aqua-security-scanner ---
[INFO] argLine set to 
-javaagent:/home/ubuntu/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.7.2.201409121644-runtime.jar=destfile=/home/ubuntu/jenkins-plugin/aqua-security-scanner-plugin/target/jacoco.exec,excludes=**/Messages.class
[INFO]
[INFO] --- maven-localizer-plugin:1.23:generate (default) @ 
aqua-security-scanner ---
[INFO]
[INFO] >>> maven-javadoc-plugin:2.10.1:javadoc (default) @ 
aqua-security-scanner >>>
[INFO]
[INFO] --- maven-hpi-plugin:1.115:validate (default-validate) @ 
aqua-security-scanner ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
aqua-security-scanner ---
[INFO] Maven Version: 3.2.1
[INFO] JDK Version: 1.7.0_101 normalized as: 1.7.0-101
[INFO] OS Info: Arch: amd64 Family: unix Name: linux Version: 
3.13.0-74-generic
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
aqua-security-scanner ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.7.2.201409121644:prepare-agent (default) @ 
aqua-security-scanner ---
[INFO] argLine set to 
-javaagent:/home/ubuntu/.m2/repository/org/jacoco/org.jacoco.agent/0.7.2.201409121644/org.jacoco.agent-0.7.2.201409121644-runtime.jar=destfile=/home/ubuntu/jenkins-plugin/aqua-security-scanner-plugin/target/jacoco.exec,excludes=**/Messages.class
[INFO]
[INFO] --- maven-localizer-plugin:1.23:generate (default) @ 
aqua-security-scanner ---
[INFO]
[INFO] <<< maven-javadoc-plugin:2.10.1:javadoc (default) @ 
aqua-security-scanner <<<
[INFO]
[INFO] --- maven-javadoc-plugin:2.10.1:javadoc (default) @ 
aqua-security-scanner ---
[INFO]
Loading source files for package

Re: [Blue Ocean] failed to write CommitId

2016-06-18 Thread Vivek Pandey 
Hi Marc,

Thanks for encouragement:) 

Looks like you have the fix so do you mind sending a PR our way?

vivek.

> On Jun 19, 2016, at 5:25 AM, Marc Esher  wrote:
> 
> Will do, thanks Vivek.
> 
> FWIW, I was able to fix this myself and now understand what caused the issue. 
> Huge props to all of you involved in making this thing "just work". It's 
> still rare when I can get clone a GH repo, follow the README, and have 
> everything work as advertised. Great job, everyone.
> 
> Marc 
> 
> On Saturday, June 18, 2016 at 3:04:31 AM UTC-4, vivek wrote:
> Line number is different as this class has gone thru some changes recently 
> but there is one place that could possibly cause NPE, I will get fix going 
> for this. Please open an Issue under blueocean-plugin at 
> issues.jenkins-ci.org .
> 
> Caused by: java.lang.NullPointerException
>  at 
> io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getCommitId(AbstractRunImpl.java:176)
>  ... 94 more
> 
> thanks for reporting.,
> 
> Vivek.
> 
> On Sat, Jun 18, 2016 at 7:00 AM, Marc Esher  > wrote:
> Hey all,
> 
> I've installed all the blue ocean hpis, and all dependencies, into an 
> existing Jenkins 2.9 server running on RHEL.
> 
> Jenkins starts fine, and I get the "try blue ocean" button at the top of the 
> screen.
> 
> However, when I go to /blue, I get "no pipelines found", and if I go to the 
> XHR that failed (http://myjenkins/blue/rest/search/?q=type:pipeline 
> ), I see the following 
> stack trace.
> 
> Any ideas?
> 
> thanks!
> 
> Marc
> 
> 
> 
> 
> java.io.IOException: Failed to write commitId
>  at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151)
>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:126)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
>  at org.kohsuke.stapler.export.Model.writeTo(Model.java:198)
>  at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285)
>  at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273)
>  at hudson.model.Api.doJson(Api.java:211)
>  at 
> io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:55)
>  at 
> org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124)
>  at 
> org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69)
>  at org.kohsuke.stapler.Function.renderResponse(Function.java:119)
>  at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102)
>  at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
>  at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
>  at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
>  at 
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
>  at 
> org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:209)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
>  at 
> com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
>  at 
> hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
>  at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
>  at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)

Re: [Blue Ocean] failed to write CommitId

2016-06-18 Thread Marc Esher 
Will do, thanks Vivek.

FWIW, I was able to fix this myself and now understand what caused the 
issue. Huge props to all of you involved in making this thing "just work". 
It's still rare when I can get clone a GH repo, follow the README, and have 
everything work as advertised. Great job, everyone.

Marc 

On Saturday, June 18, 2016 at 3:04:31 AM UTC-4, vivek wrote:
>
> Line number is different as this class has gone thru some changes recently 
> but there is one place that could possibly cause NPE, I will get fix going 
> for this. Please open an Issue under blueocean-plugin at 
> issues.jenkins-ci.org.
>
> Caused by: java.lang.NullPointerException
>  at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getCommitId
> (AbstractRunImpl.java:176)
>  ... 94 more
>
> thanks for reporting.,
>
> Vivek.
>
> On Sat, Jun 18, 2016 at 7:00 AM, Marc Esher  > wrote:
>
>> Hey all,
>>
>> I've installed all the blue ocean hpis, and all dependencies, into an 
>> existing Jenkins 2.9 server running on RHEL.
>>
>> Jenkins starts fine, and I get the "try blue ocean" button at the top of 
>> the screen.
>>
>> However, when I go to /blue, I get "no pipelines found", and if I go to 
>> the XHR that failed (http://myjenkins/blue/rest/search/?q=type:pipeline), 
>> I see the following stack trace.
>>
>> Any ideas?
>>
>> thanks!
>>
>> Marc
>>
>>
>>
>>
>> java.io.IOException: Failed to write commitId
>>  at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151)
>>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:126)
>>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
>>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
>>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
>>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
>>  at org.kohsuke.stapler.export.Model.writeTo(Model.java:198)
>>  at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285)
>>  at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:
>> 273)
>>  at hudson.model.Api.doJson(Api.java:211)
>>  at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.
>> generateResponse(PagedResponse.java:55)
>>  at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(
>> HttpResponseRenderer.java:124)
>>  at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(
>> HttpResponseRenderer.java:69)
>>  at org.kohsuke.stapler.Function.renderResponse(Function.java:119)
>>  at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.
>> java:102)
>>  at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
>>  at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.
>> java:58)
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
>>  at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>>  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812
>> )
>>  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
>> ServletHandler.java:1669)
>>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
>> 135)
>>  at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.
>> doFilter(Endpoint.java:209)
>>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
>> 132)
>>  at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.
>> doFilter(LessCSS.java:47)
>>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
>> 132)
>>  at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter
>> .java:95)
>>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
>> 132)
>>  at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
>>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
>> 132)
>>  at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126
>> )
>>  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
>> ServletHandler.java:1652)
>>  at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
>>  at

Adoption Request For Slave Setup Plugin

2016-06-18 Thread Baptiste Mathus 
Hi,

While chatting on HOSTING-101
, we came to agreement
with Giuseppe Landolfi that he would take over maintainership of the Slave
Setup Plugin [1].

FWICT this plugin looks like it's orphaned. It was created by Kohsuke
originally, and the last emails about it may not be clearly people taking
over the maintenance (putting them in CC [3]).

In this situation, and as Giuseppe opened a PR [2] almost 10 days ago, I'll
make him maintainer some time next week if nobody objects in the meantime.

Thanks

-- Baptiste

[1] https://wiki.jenkins-ci.org/display/JENKINS/Slave+Setup+Plugin
[2] https://github.com/jenkinsci/slave-setup-plugin/pull/8
[3] https://groups.google.com/forum/#!topic/jenkinsci-dev/nEOVs-zpetw and
http://jenkins-ci.361315.n4.nabble.com/Pull-Request-for-slave-setup-plugin-created-td4373399.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/CANWgJS4P1N-w%3DqPeZ%3DNvyGM4JMwG4XNS65gW8jAdky1hft724Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

2016-06-18 Thread Daniel Beck 

> On 14.06.2016, at 22:02, Gus Reiber  wrote:
> 
>So I have on and off pushed the idea that the Jenkins community could 
> benefit greatly from an overhaul of the wiki based plugins site. As an 
> ultimate goal, I don't see any reason we couldn't build something that 
> approach a modern app store, like https://play.google.com/store, but for the 
> short run, it seems like we should be able to improove upon the browsing 
> experience of the existing list page and detail view.
> 

As this thread appears to have been veered off into (mostly) unrelated topics, 
I am restarting the plugins site discussion here:
https://groups.google.com/d/msg/jenkinsci-dev/a8rqIYaoEWA/TtkKBNaIBgAJ

I'd appreciate if the plugins index related discussion would continue there.

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

Re: Plugin site overhaul?

2016-06-18 Thread Daniel Beck 

> On 18.06.2016, at 13:01, Tomas Bjerre  wrote:
> 
> I also noticed it when I tried to get git-releasenotes-plugin published:
> https://groups.google.com/d/msgid/jenkinsci-dev/06fbe64c-c228-47da-a5cd-b8d070dc16a0%40googlegroups.com?utm_medium=email_source=footer
> Its now merged into git-changelog-plugin and is causing confusion among users 
> who install the plugin and get 2 similar post build steps.

I'm sorry that your hosting request experience was so bad. At no point was your 
request denied. That thread looks to me like you took us up on the suggestion. 
In fact, my message in that thread only makes sense if your plugin is still on 
track to be hosted, but a day and two messages from you later you posted the 
PR, effectively (at least as far as I understood it at the time) revoking the 
hosting request.

In addition to not refusing to host your plugin, we did not ask for a 'merge' 
of two plugins in the form of just copying the sources of one over to the 
other. AFAICT this could easily have been one post build step with a mode 
switch of some sort, or whatever makes sense for the related functionality in 
these two plugins.

Regarding the earlier week long delay -- hosting request emails getting ignored 
or getting no response for weeks is the reason we moved to JIRA for these half 
a year ago, so this doesn't happen anymore. As it's still all volunteers (and 
only a few as well), there are delays of a few days here and there, but overall 
hosting requests are now handled more quickly.

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

The plugins site, a replacement for the 'Plugins' wiki page

2016-06-18 Thread Daniel Beck 
The other thread has been derailed a bit, so I'm restarting this discussion 
here. Thanks for your understanding.

---

Hi everyone,

We've been talking about a new plugins site/index of some kind on and off for a 
while now.

It's been part of the Jenkins.io site redesign discussions last fall, and part 
of the 'vision' I posted to the wiki back then to move the discussions forward:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0+Website+vision+from+Daniel+Beck#Jenkins2.0WebsitevisionfromDanielBeck-Plugins

Just like we're moving fairly static content out of the wiki, into jenkins.io, 
we should do so with the plugins index. Right now, it's pretty terrible:
https://wiki.jenkins-ci.org/display/JENKINS/Plugins

And FWIW the plugin manager's "Available" tab in Jenkins isn't much better…

We've been busy with Jenkins.io (the rest of it) and Jenkins 2 since those 
first discussions, so not much has happened in this area. But now, it's time we 
looked at this again. Gus is working on making this a reality, but we need 
input from you:

What are you looking for in a plugins index? What information should it 
contain? What are typical use cases that should be covered?

Please note that while we'll soon get some way to have plugin documentation on 
jenkins.io from the GSoC project, let's please not make this a discussion of 
the implementation details of how the plugin documentation gets sourced. Tons 
of plugins will continue to have their docs on the wiki, and I imagine we'll 
need to support that, as well as e.g. GitHub (and possibly more) locations in 
some way.


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

[WARNING] Failed to getClass for org.apache.maven.plugin.javadoc.JavadocReport in build logs

2016-06-18 Thread Mike Caspar 
I've noticed this showing up in the build logs

Any idea what is causing this so I can fix it?

I checked. I don't appear to get this error locally.



[INFO] --- maven-localizer-plugin:1.23:generate (default) @ ironmq-notifier 
---
[WARNING] Failed to getClass for org.apache.maven.plugin.javadoc.
JavadocReport
[INFO] 
[INFO] <<< maven-javadoc-plugin:2.10.1:javadoc (default) @ ironmq-notifier 
<<<

Thanks

Mike



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

Re: Stop process started by MasterToSlaveCallable when connection to master is lost

2016-06-18 Thread Rouke Broersma 
Does anyone have any idea if this is possible in any way?

On Friday, June 10, 2016 at 7:20:33 PM UTC+2, Rouke Broersma wrote:
>
> I am a maintainer of the selenium grid plugin, and as part of our plugin 
> we start potentially multiple processes on slaves (selenium nodes, as part 
> of a distributed selenium grid).
> We have implemented the RestartListener to shutdown all our selenium nodes 
> on the slaves when Jenkins is restarting, but I am unable to find how to do 
> this when the master becomes unavailable for some reason.
>
> As in, when the master becomes unavailable to a slave, I want to be able 
> to have the slave shut down it's selenium node processes. This is necessary 
> because selenium contains an automatic reconnect mechanism,
> so if the connection to master is lost for unexpected reasons, we would 
> end up with duplicate selenium nodes on the slaves (plugin tries to create 
> new node on all slaves that become available and match the criteria).
> This is undesirable.
>
> So I would like to know, is there a way to tell Jenkins slaves to clean up 
> any processes I started when it no longer has a connection to master?
>

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

Re: Plugin site overhaul?

2016-06-18 Thread Tomas Bjerre 
I first noticed the problem when I tried to fix violations-plugin:

https://groups.google.com/d/msgid/jenkinsci-dev/ba38fabe-ff19-4828-a737-d2320ea5681f%40googlegroups.com?utm_medium=email_source=footer

I also noticed it when I tried to get git-releasenotes-plugin published:
https://groups.google.com/d/msgid/jenkinsci-dev/06fbe64c-c228-47da-a5cd-b8d070dc16a0%40googlegroups.com?utm_medium=email_source=footer
Its now merged into git-changelog-plugin and is causing confusion among
users who install the plugin and get 2 similar post build steps.

Why would you not get the solution published anywhere? While we do
encourage people to fix issues in existing plugins or add features to
existing plugins, we don't keep people from contributing. I'm saying this
as a member of the hosting team that reviews plugin submissions.

On Sat, Jun 18, 2016, 01:11 Tomas Bjerre  wrote:

> Have you seen Jucies? And this issue:
> https://github.com/jucies/releases/issues/15 ?
>
> I think it would be much better if competition among plugins were allowed.
> Many times I've lost interest in fixing a problem when I've browsed the
> code of plugins. Simply because there are too many bad decisions made, to
> much ugly code to fix... and it feels that the solutions should be to just
> rework the whole implementation. But if I would do that, I would not get
> the new implementation published anywhere. So I don't, and the code quality
> remains in a crappy state.
>
>
> Den tisdag 14 juni 2016 kl. 22:02:43 UTC+2 skrev Gus Reiber:
>>
>> Hey all,
>>So I have on and off pushed the idea that the Jenkins community could
>> benefit greatly from an overhaul of the wiki based plugins site. As an
>> ultimate goal, I don't see any reason we couldn't build something that
>> approach a modern app store, like https://play.google.com/store, but for
>> the short run, it seems like we should be able to improove upon the
>> browsing experience of the existing list page and detail view.
>>
>> Existing:
>>
>>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>>- detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>>
>> I think as a minimum, we ought to be able to provide a reasonable search
>> interface and means of filtering plugins by maintainer, Jenkins core
>> requirement, plugins labels, and installation count. Plugins should also be
>> assigned to categories that map to Jenkins user expectations a bit better
>> than the current list of ~30ish maintainer assigned labels do today.
>> Ideally the user ought to be able to manage the list of all plugins by
>> specific features of the plugin and by some suggestion of quality or
>> currentness of the plugin.
>>
>> At various points, my interest in bringing this value to the community
>> has been great enough to assemble a couple of different prototypes and
>> wireframes, attempting to generate interest. I have also had a chance to
>> play with some prototypes from others all with what seems to me to be
>> reasonable implementation paths. Attached are a few more recent sketches
>> showing the gist of how we might handle searching and filtering as well as
>> the plugin details.
>>
>> Anyway, at the moment, the plugin site is maintained by our
>> representatives here in the community. So it is really the will of the
>> community that should be reflected in any efforts that are actually
>> deployed and later maintained by our community. Thus again, I am looking
>> for grass roots support for the effort, support that potentially includes
>> some avenue for long term hosting and support.
>>
>> So my questions are these: Is enhancing the plugin site really worth that
>> degree of effort to the community? If you think it is, would you be willing
>> to join the effort, both for the immediate development needs, but also for
>> longer term support? Do you have any experience with other communities who
>> manage to accomplish this sort of ends?
>>
>> ...and finally, could you help articulate a set of minimum requirements
>> that would make overhauling the plugin site worth while?
>>
>> Thanks in advance,
>> Gus
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/72056174-8325-4e19-8a58-7afd15fc5c1d%40googlegroups.com
> 
> .
> 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/2nqWoE1FfOo/unsubscribe.
To unsubscribe from this group and

Re: Plugin site overhaul?

2016-06-18 Thread Slide 
Why would you not get the solution published anywhere? While we do
encourage people to fix issues in existing plugins or add features to
existing plugins, we don't keep people from contributing. I'm saying this
as a member of the hosting team that reviews plugin submissions.

On Sat, Jun 18, 2016, 01:11 Tomas Bjerre  wrote:

> Have you seen Jucies? And this issue:
> https://github.com/jucies/releases/issues/15 ?
>
> I think it would be much better if competition among plugins were allowed.
> Many times I've lost interest in fixing a problem when I've browsed the
> code of plugins. Simply because there are too many bad decisions made, to
> much ugly code to fix... and it feels that the solutions should be to just
> rework the whole implementation. But if I would do that, I would not get
> the new implementation published anywhere. So I don't, and the code quality
> remains in a crappy state.
>
>
> Den tisdag 14 juni 2016 kl. 22:02:43 UTC+2 skrev Gus Reiber:
>>
>> Hey all,
>>So I have on and off pushed the idea that the Jenkins community could
>> benefit greatly from an overhaul of the wiki based plugins site. As an
>> ultimate goal, I don't see any reason we couldn't build something that
>> approach a modern app store, like https://play.google.com/store, but for
>> the short run, it seems like we should be able to improove upon the
>> browsing experience of the existing list page and detail view.
>>
>> Existing:
>>
>>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>>- detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>>
>> I think as a minimum, we ought to be able to provide a reasonable search
>> interface and means of filtering plugins by maintainer, Jenkins core
>> requirement, plugins labels, and installation count. Plugins should also be
>> assigned to categories that map to Jenkins user expectations a bit better
>> than the current list of ~30ish maintainer assigned labels do today.
>> Ideally the user ought to be able to manage the list of all plugins by
>> specific features of the plugin and by some suggestion of quality or
>> currentness of the plugin.
>>
>> At various points, my interest in bringing this value to the community
>> has been great enough to assemble a couple of different prototypes and
>> wireframes, attempting to generate interest. I have also had a chance to
>> play with some prototypes from others all with what seems to me to be
>> reasonable implementation paths. Attached are a few more recent sketches
>> showing the gist of how we might handle searching and filtering as well as
>> the plugin details.
>>
>> Anyway, at the moment, the plugin site is maintained by our
>> representatives here in the community. So it is really the will of the
>> community that should be reflected in any efforts that are actually
>> deployed and later maintained by our community. Thus again, I am looking
>> for grass roots support for the effort, support that potentially includes
>> some avenue for long term hosting and support.
>>
>> So my questions are these: Is enhancing the plugin site really worth that
>> degree of effort to the community? If you think it is, would you be willing
>> to join the effort, both for the immediate development needs, but also for
>> longer term support? Do you have any experience with other communities who
>> manage to accomplish this sort of ends?
>>
>> ...and finally, could you help articulate a set of minimum requirements
>> that would make overhauling the plugin site worth while?
>>
>> Thanks in advance,
>> Gus
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/72056174-8325-4e19-8a58-7afd15fc5c1d%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/CAPiUgVdYji0F6FPwYL66HD4eFPPv8aQ3K71nWHU7d0iPXL5rTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Plugin site overhaul?

2016-06-18 Thread Tomas Bjerre 
Have you seen Jucies? And this 
issue: https://github.com/jucies/releases/issues/15 ?

I think it would be much better if competition among plugins were allowed. 
Many times I've lost interest in fixing a problem when I've browsed the 
code of plugins. Simply because there are too many bad decisions made, to 
much ugly code to fix... and it feels that the solutions should be to just 
rework the whole implementation. But if I would do that, I would not get 
the new implementation published anywhere. So I don't, and the code quality 
remains in a crappy state.


Den tisdag 14 juni 2016 kl. 22:02:43 UTC+2 skrev Gus Reiber:
>
> Hey all,
>So I have on and off pushed the idea that the Jenkins community could 
> benefit greatly from an overhaul of the wiki based plugins site. As an 
> ultimate goal, I don't see any reason we couldn't build something that 
> approach a modern app store, like https://play.google.com/store, but for 
> the short run, it seems like we should be able to improove upon the 
> browsing experience of the existing list page and detail view.
>
> Existing: 
>
>- list: https://wiki.jenkins-ci.org/display/JENKINS/Plugins
>- detail: https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin
>
> I think as a minimum, we ought to be able to provide a reasonable search 
> interface and means of filtering plugins by maintainer, Jenkins core 
> requirement, plugins labels, and installation count. Plugins should also be 
> assigned to categories that map to Jenkins user expectations a bit better 
> than the current list of ~30ish maintainer assigned labels do today. 
> Ideally the user ought to be able to manage the list of all plugins by 
> specific features of the plugin and by some suggestion of quality or 
> currentness of the plugin.
>
> At various points, my interest in bringing this value to the community has 
> been great enough to assemble a couple of different prototypes and 
> wireframes, attempting to generate interest. I have also had a chance to 
> play with some prototypes from others all with what seems to me to be 
> reasonable implementation paths. Attached are a few more recent sketches 
> showing the gist of how we might handle searching and filtering as well as 
> the plugin details.
>
> Anyway, at the moment, the plugin site is maintained by our 
> representatives here in the community. So it is really the will of the 
> community that should be reflected in any efforts that are actually 
> deployed and later maintained by our community. Thus again, I am looking 
> for grass roots support for the effort, support that potentially includes 
> some avenue for long term hosting and support.
>
> So my questions are these: Is enhancing the plugin site really worth that 
> degree of effort to the community? If you think it is, would you be willing 
> to join the effort, both for the immediate development needs, but also for 
> longer term support? Do you have any experience with other communities who 
> manage to accomplish this sort of ends?
>
> ...and finally, could you help articulate a set of minimum requirements 
> that would make overhauling the plugin site worth while?
>
> Thanks in advance,
> Gus
>

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

Re: [Blue Ocean] failed to write CommitId

2016-06-18 Thread Vivek Pandey 
Line number is different as this class has gone thru some changes recently
but there is one place that could possibly cause NPE, I will get fix going
for this. Please open an Issue under blueocean-plugin at
issues.jenkins-ci.org.

Caused by: java.lang.NullPointerException
 at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getCommitId(
AbstractRunImpl.java:176)
 ... 94 more

thanks for reporting.,

Vivek.

On Sat, Jun 18, 2016 at 7:00 AM, Marc Esher  wrote:

> Hey all,
>
> I've installed all the blue ocean hpis, and all dependencies, into an
> existing Jenkins 2.9 server running on RHEL.
>
> Jenkins starts fine, and I get the "try blue ocean" button at the top of
> the screen.
>
> However, when I go to /blue, I get "no pipelines found", and if I go to
> the XHR that failed (http://myjenkins/blue/rest/search/?q=type:pipeline),
> I see the following stack trace.
>
> Any ideas?
>
> thanks!
>
> Marc
>
>
>
>
> java.io.IOException: Failed to write commitId
>  at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151)
>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:126)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
>  at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
>  at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
>  at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
>  at org.kohsuke.stapler.export.Model.writeTo(Model.java:198)
>  at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285)
>  at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:
> 273)
>  at hudson.model.Api.doJson(Api.java:211)
>  at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.
> generateResponse(PagedResponse.java:55)
>  at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(
> HttpResponseRenderer.java:124)
>  at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(
> HttpResponseRenderer.java:69)
>  at org.kohsuke.stapler.Function.renderResponse(Function.java:119)
>  at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.
> java:102)
>  at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
>  at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.
> java:58)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
>  at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>  at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
>  at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>  at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
>  at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
>  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
> ServletHandler.java:1669)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
> 135)
>  at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.
> doFilter(Endpoint.java:209)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
> 132)
>  at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.
> doFilter(LessCSS.java:47)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
> 132)
>  at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.
> java:95)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
> 132)
>  at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
>  at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:
> 132)
>  at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
>  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
> ServletHandler.java:1652)
>  at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
>  at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
> ServletHandler.java:1652)
>  at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
> java:84)
>  at hudson.security.UnwrapSecurityExceptionFilter.doFilter(
> UnwrapSecurityExceptionFilter.java:51)
>  at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.
> java:87)
>  at jenkins.security.ExceptionTranslationFilter.doFilter(
> ExceptionTranslationFilter.java:117)
>  at