Re: Request to host plug-in: Flaky Tests Handler

2014-08-05 Thread Vincent Latombe
Hello Quingzhou,

I have just created https://github.com/jenkinsci/flaky-test-handler for you
and granted commit access.

Welcome aboard!

Vincent


2014-08-05 1:25 GMT+02:00 Qingzhou Luo qingzhou...@google.com:

 Thanks for supporting, Bruno. Still waiting for approval..


 On Saturday, August 2, 2014 12:02:04 PM UTC-7, Bruno Meneguello wrote:

 Amazing idea! In my company we have developed a RunConfiguration to do
 exactly that and implemented a plugin to do the same thing (but haven't
 opened it because it become a very specific implementation)

 Thumbs up for the initiative!
 Em 01/08/2014 21:44, Qingzhou Luo qingz...@google.com escreveu:

  Hi,

 I'd like to host our new plug-in.

 Plugin name: flaky-test-handler
 My github account: qingzhouluo/seriousamlqz (Please add both, thanks).

 Description:

 This plugin is designed to handle flaky tests. Currently it aims for Git
 and Maven.

 1. We recently made some contribution to Maven Surefire to add the new
 option -rereunFailingTestsCount. It was already accepted, and may be
 released with 2.18 in the near future:

 https://github.com/apache/maven-surefire/commit/
 fefaae7f0534a59f52c046a64c96987e8561dd48

 It basically let users to choose to re-run failing tests up to N times,
 and if it passes any of those N times, it will be marked as a Flake and
 the build will be marked as successful. The generated test report will
 contain each re-run information.

 So the first part of our plugin is to integrate with this new feature
 from Maven Surefire. It will parse the report and display flaky tests,
 output information of all the re-runs(stacktrace, output, etc) on test
 result page.

 https://drive.google.com/file/d/0Bzfyw2NYCLFBV2lnMVlrWVhueGc
 https://drive.google.com/file/d/0Bzfyw2NYCLFBZXFxSThlMWlaeVU

 2. For each failing build we provide a Deflake action. It is different
 from rebuilding the project, as it will:

 1) Checkout the exact revision of that failing build (GIT)
 2) Only run all those failed tests.

 So this will give developer a good idea about how many tests are flaky
 for this build.

 https://drive.google.com/file/d/0Bzfyw2NYCLFBR3RDM3psQjhIRUk/
 https://drive.google.com/file/d/0Bzfyw2NYCLFBeTFjQk5sQW5XR3M/

 3. Aggregate information from both 1 and 2, and display them to the
 users.

 For each git revision and each test, we count how many times it passed,
 how many times it failed. So if a test passed and failed for the both
 revision, we count it as a flake; if it always failed, then it's a fail,
 otherwise it's a pass.

 https://drive.google.com/file/d/0Bzfyw2NYCLFBRlI2SHpubTltd28/
 https://drive.google.com/file/d/0Bzfyw2NYCLFBVWJNWFAweEl1Y28/

 So this help users to see what are my most flaky tests (they can compute
 some kind of flakiness), so they can fix them first. It basically serves as
 the test health page.

 We have a repo on github, however it was empty right now.
 https://github.com/google/jenkins-flaky-test-report

 Will push our code to it very soon. So here I want to get a repo from
 Jenkins so we can push our code to Jenkins too.

 Thank you very much!

 Regards,

 Qingzhou

 --
 You received this message because you are subscribed to the Google
 Groups Jenkins Developers group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-de...@googlegroups.com.

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


Subversion plug-in:

2014-08-05 Thread Fabio Farronato

Hi all,
  I'm in trouble with the Subversion plug-in, here the scenario:

My job have a parameter SOURCE to pass svn location in format 
http://svnserv/repo/myproject/branches/7.20.0@506192;.

In job configuration I defined the SCM location using a variable $SOURCE.
The first time the job ran out compiling successfully.
Because the build was a test, the branch has been removed and is no 
longer available in the latest revision.
Now if i try to require a build with the same parameter the job fail to 
check out:


Location 'http://svnserv/repo/myproject/branches/7.20.0@506192' does not exist
Cleaning local Directory .
Checking out http://svnserv/repo/myproject/branches/7.20.0@506192 at revision 
506192
ERROR: Failed to check out http://svnserv/repo/myproject/branches/7.20.0@506192
org.tmatesoft.svn.core.SVNException  
http://stacktrace.jenkins-ci.org/search?query=org.tmatesoft.svn.core.SVNException:
 svn: E160013: '/repo/!svn/bc/521195/myproject/branches/7.20.0' path not found: 404 
Not Found (http://svnserv)

atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc.SVNErrorManager.errorentity=method

atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc.SVNErrorManager.errorentity=method

atorg.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLocationsImpl(DAVRepository.java:1068)
  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLocationsImplentity=method
atorg.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1088)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.io.SVNRepository.getLocationsentity=method
atorg.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1516)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.io.SVNRepository.getLocationsentity=method

atorg.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:178)
  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocationsentity=method

atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryForentity=method

atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:706)
  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkoutentity=method
atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:14) 
 
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.runentity=method
atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:9)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.runentity=method

atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20)
  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.runentity=method

atorg.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.runentity=method

atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.wc2.SvnOperationFactory.runentity=method
atorg.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.wc2.SvnOperation.runentity=method
atorg.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:777)  
http://stacktrace.jenkins-ci.org/search/?query=org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckoutentity=method
athudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:99)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.scm.subversion.CheckoutUpdater$1.performentity=method

athudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) 
 
http://stacktrace.jenkins-ci.org/search/?query=hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateToentity=method
athudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:1006)  
http://stacktrace.jenkins-ci.org/search/?query=hudson.scm.SubversionSCM$CheckOutTask.performentity=method
athudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:987)  

Re: Workflow plugin - Questions, Bugs and Features

2014-08-05 Thread Jesse Glick
On Mon, Aug 4, 2014 at 2:02 PM, Sagi Sinai-Glazer sagisi...@gmail.com wrote:
 I see that you've merged pull #8 for the plugin - are you updating
 the docker image demo file to reflect the new changes?

The merge did include matching changes to the demo job, but I have not
yet rebuilt the Docker image.

 Untested but probably something like:

 parallel((1..maxValue).collect {ctr - ctr: {- doSomethingWith(ctr)}})

 (The ‘parallel’ step in Workflow takes “thread names” as the parameter
 keys and closures as values.)

 Tried this - didn't work!

I am not sure of the Groovy syntax offhand for building a Map this
way, but I am sure you can look it up. You do need to ensure that
every key is a String—and currently GString (e.g., with
${substitutions}) does not count.

 the ending prints of the flow (prefixed with timestamp) precede
 the prints of the actual threads it invoked.

Cannot really evaluate without the flow source. If you were using
Groovy’s built-in ‘println’, try using the ‘echo’ step instead.
println support is currently minimal and due to be rewritten.

 this was a simple example of Groovy syntax that doesn't work:
 def a=[1,2,3]
 println a[0] // [] for some reason is not supported and triggers the above
 exception which hangs the build

Ah yes, array index lookups are not yet implemented in the Groovy CPS
library, along with a variety of other miscellaneous operators. PRs to
kohsuke/groovy-cps welcome. In the meantime just restrict flow scripts
to the corresponding plain method calls, like get(int).

 when compilation/run-time errors are received, it's hard to find the right 
 erroneous line.

 I believe that this should be implemented for simple flows as well.

Well more useful than line numbers in the text area (which is
nonstandard and would not be supported even when we implement Code
Mirror support for this textarea, as is planned) would be error
messages that actually show some kind of context. Cannot recall if
Kohsuke already implemented proper stack traces.

Generally speaking there is a great deal of work to be done in
cleaning up corner cases in the CPS engine and better reporting error
conditions which we have deferred until a later time, possibly after
“1.0”. The focus is on making sure that you *can* write working
scripts that implement the major use cases.

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


Modernize icons animations

2014-08-05 Thread Bruno Kühnen Meneguello

Hello,

Recently I've submitted the PR #1332 
https://github.com/jenkinsci/jenkins/pull/1332 to modify the status 
orbs. That generated a discussion about using CSS animations to fade 
in/out these orbs but have ended due to performance issues (mainly in OS x).


Based on that, I would ask the community ideas to replace the GIF 
animations without performance issues (or how to fix then).


There are some JSFiddles in the PR with performance tests so anyone can 
try from the point it stopped.


Thanks in advance for all

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


Re: RSS for all / RSS for failures

2014-08-05 Thread Jesse Glick
On Sat, Aug 2, 2014 at 12:53 PM, Kevin Burke kburke...@gmail.com wrote:
 does the performance hit occur when you load the job page, or just
 when you load the actual list of RSS items (/rssAll, /rssFailed)?

Just when you load the RSS, at least as far as I know.

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


Re: SSH slave performance degradation

2014-08-05 Thread Jesse Glick
Cf.: https://issues.jenkins-ci.org/browse/JENKINS-20108

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


plugin ConsoleLogFilter class not loaded suddenly

2014-08-05 Thread sdetweil
I am extending one of the existing plugins.  back in May I added a 
ConsoleLogFilter class and it worked great. no issues.  up thru Jenkins 
1.572.

the developer has released new source, so I have ported my changes over..  
rebuilt the hpi and reloaded from my local system as always. 
the installed plugins view shows my version signature with the proper 
timestamp. 

but my logfilter class does not get invoked. I am building here on the 
master machine. I usd 7zip to look inside the hpi package, and the 
proper classes are present.

I have LOGGER.fine(.) clauses in the filter code to show it operating..
no log entries are captured. (the logger name did NT start with jenkins 
(nor back in may either when it last worked).. but even if I add that, 
still nothing. 

its almost like the public version is downloaded over mine. (the last good 
build is at 83, I am now at build 126. 
I have rebooted the local system (virtual machine)
stopped an restarted jenkins..

the failure stated on August 1. up til then it was ok. (for 10 days 
before)..
the only thing of note is that I had a compile error on that day and got a 
java.lang.NoSuchMethodException:  during execution of the job using that 
plugin.

jenkins is running under apache tomcat6, on ubuntu linux. 12.04 64bit. 

I reloaded my may version of the hpi, and it works properly. 
so, what did I do, and how do I fix it or debug 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.
For more options, visit https://groups.google.com/d/optout.


Jenkins doesn't launch when debugging with hpi:run

2014-08-05 Thread michaelalex3
I'm trying to debug my plugin as described in the Jenkins plugin tutorial.  I
follow all the instructions for creating the default plugin.  Everything
works fine until I try debugging using mvn hpi:run.  The jetty server starts
and allows me to reload it, but Jenkins never launches.  I've tried
debugging other plugins that I've taken from github, and they usually debug
fine (Jenkins launches).  I looked at my pom.xml and compared it to working
plugins, but couldn't seem to get it to work.  Any recommendations?  I'm
using Maven 3.2.1.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Jenkins-doesn-t-launch-when-debugging-with-hpi-run-tp4713146.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

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


Re: How to build a SSO plugin in Jenkins?

2014-08-05 Thread melnik
Hi

I'm looking for the exact same solution.
Need to implement SSO with Jenkins and AD.

can you share the source?

thanks



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/How-to-build-a-SSO-plugin-in-Jenkins-tp4685472p4713499.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

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


Re: Modernize icons animations

2014-08-05 Thread Tom Fennelly
Hey Bruno.

We experimented with JS based animations a few weeks ago.  Perhaps you 
remember.  There's a branch 
here: https://github.com/tfennelly/jenkins/tree/orbs-with-plugin.

I think this work could be resurrected and combined with the work you've 
been doing, now that we have the l:icon tag in place.  On that branch 
you'll see there's a progress-circle.js 
https://github.com/tfennelly/jenkins/tree/orbs-with-plugin/war/src/main/webapp/scripts
 
file, as well as an icons.css 
https://github.com/tfennelly/jenkins/tree/orbs-with-plugin/war/src/main/webapp/css
 
file.  My plan was to redo that css file and use the css class specs 
introduced by the l:icon tag (e.g. icon-terminal icon-xlg).  Then, for 
devices that support canvas, we can use progress.js to draw nice smooth 
animations (fairly sure progress-circle.js uses canvas).  As we found from 
your experiments (and mine)... CSS animation performance sucks on some 
popular OSs :)

T.


On Tuesday, August 5, 2014 2:31:27 PM UTC+1, Bruno Kühnen Meneguello wrote:

  Hello,

 Recently I've submitted the PR #1332 
 https://github.com/jenkinsci/jenkins/pull/1332 to modify the status 
 orbs. That generated a discussion about using CSS animations to fade in/out 
 these orbs but have ended due to performance issues (mainly in OS x).

 Based on that, I would ask the community ideas to replace the GIF 
 animations without performance issues (or how to fix then).

 There are some JSFiddles in the PR with performance tests so anyone can 
 try from the point it stopped.

 Thanks in advance for all
  

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


Re: Should we come up with a browser support matrix?

2014-08-05 Thread Tom Fennelly
Hi Emeric.  Thanks for the response.  +1 to everything you said there.


On Friday, August 1, 2014 9:37:54 AM UTC+1, evernat wrote:

 Hi Tom,

 In my opinion, we should not try to support IE8 in UI refresh, because it 
 would be foolish for a user to still use IE8 even on WinXP.

 Perhaps some slow companies still pretend that IE8 is their mandatory 
 browser [1] (and never respect that themselves). But in my opinion, your UI 
 refresh should not be blocked or slowed down by the mandate of these slow 
 companies, for which they just need to acknowledge a better mandate or 
 exemptions.

 [1] 
 https://issues.jenkins-ci.org/browse/JENKINS-14749?focusedCommentId=198375page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198375

 Emeric

 Le jeudi 31 juillet 2014 14:26:05 UTC+2, Tom Fennelly a écrit :

 In particular... how far back do we want to support Internet Explorer.  I 
 think IE9 for sure, but what about IE8?  It's a real PITA :)



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


Using JobConfigHistory Plugin

2014-08-05 Thread Karthik V S
Hi,

The Jenkins Plugin that I create updates a job by Job Configuration. When I 
use the JobConfigHistory Plugin to view the config changes, it throws an 
error as described below. Any pointers on where I am going wrong here?

404 Not Found

Stapler processed this HTTP request as follows, but couldn't find the 
resource to consume the request

- evaluate(hudson.model.Hudson@1ca83821 
:hudson.model.Hudson,/job/kshantaraman/jobConfigHistory)
- 
evaluate(((StaplerProxy)hudson.model.Hudson@1ca83821).getTarget(),/job/kshantaraman/jobConfigHistory)
- 
evaluate(hudson.model.Hudson@1ca83821.getJob(kshantaraman),/jobConfigHistory)
- evaluate(hudson.model.FreeStyleProject@22f7b6dc[kshantaraman] 
:hudson.model.FreeStyleProject,/jobConfigHistory)
- 
evaluate(hudson.model.FreeStyleProject@22f7b6dc[kshantaraman].getDynamic(jobConfigHistory,...),)

hudson.model.FreeStyleProject@22f7b6dc[kshantaraman].getDynamic(jobConfigHistory,...)==null.
 Back tracking.- No matching rule was found on 
hudson.model.FreeStyleProject@22f7b6dc[kshantaraman] for /jobConfigHistory

hudson.model.FreeStyleProject@22f7b6dc[kshantaraman] has the following 
URL mappings, in the order of preference:

   1. hudson.model.AbstractProject.doDoDelete(...) for url=/doDelete/...
   2. hudson.model.AbstractProject.doWs(...) for url=/ws/...
   3. hudson.model.AbstractProject.doCheckRetryCount(...) for 
   url=/checkRetryCount/...
   4. hudson.model.AbstractProject.doBuild(...) for url=/build/...
   5. hudson.model.AbstractProject.doBuild(...) for url=/build/...
   6. hudson.model.AbstractProject.doBuildWithParameters(...) for 
   url=/buildWithParameters/...
   7. hudson.model.AbstractProject.doBuildWithParameters(...) for 
   url=/buildWithParameters/...
   8. hudson.model.AbstractProject.doPolling(...) for url=/polling/...
   9. hudson.model.AbstractProject.doCancelQueue(...) for 
   url=/cancelQueue/...
   10. hudson.model.AbstractProject.doDoWipeOutWorkspace(...) for 
   url=/doWipeOutWorkspace/...
   11. hudson.model.AbstractProject.doDisable(...) for url=/disable/...
   12. hudson.model.AbstractProject.doEnable(...) for url=/enable/...
   13. hudson.model.AbstractProject.doRssChangelog(...) for 
   url=/rssChangelog/...
   14. hudson.model.AbstractProject.doConfigSubmit(...) for 
   url=/configSubmit/...
   15. hudson.model.Job.doRssAll(...) for url=/rssAll/...
   16. hudson.model.Job.doRssFailed(...) for url=/rssFailed/...
   17. hudson.model.Job.doBuildStatus(...) for url=/buildStatus/...
   18. hudson.model.Job.doDescription(...) for url=/description/...
   19. hudson.model.Job.doDoRename(...) for url=/doRename/...
   20. hudson.model.AbstractItem.doConfigDotXml(...) for url=/config.xml/...
   21. hudson.model.AbstractItem.doSubmitDescription(...) for 
   url=/submitDescription/...
   22. hudson.model.Actionable.doContextMenu(...) for url=/contextMenu/...
   23. TOKEN.groovy for url=/TOKEN
   24. VIEW.jelly for url=/VIEW
   25. hudson.model.FreeStyleProject.DESCRIPTOR for url=/DESCRIPTOR/...
   26. hudson.model.Item.PERMISSIONS for url=/PERMISSIONS/...
   27. hudson.model.Item.CREATE for url=/CREATE/...
   28. hudson.model.Item.DELETE for url=/DELETE/...
   29. hudson.model.Item.CONFIGURE for url=/CONFIGURE/...
   30. hudson.model.Item.READ for url=/READ/...
   31. hudson.model.Item.DISCOVER for url=/DISCOVER/...
   32. hudson.model.Item.EXTENDED_READ for url=/EXTENDED_READ/...
   33. hudson.model.Item.BUILD for url=/BUILD/...
   34. hudson.model.Item.WORKSPACE for url=/WORKSPACE/...
   35. hudson.model.Item.WIPEOUT for url=/WIPEOUT/...
   36. hudson.model.Item.CANCEL for url=/CANCEL/...
   37. hudson.model.Saveable.NOOP for url=/NOOP/...
   38. hudson.model.Item.PERMISSIONS for url=/PERMISSIONS/...
   39. hudson.model.Item.CREATE for url=/CREATE/...
   40. hudson.model.Item.DELETE for url=/DELETE/...
   41. hudson.model.Item.CONFIGURE for url=/CONFIGURE/...
   42. hudson.model.Item.READ for url=/READ/...
   43. hudson.model.Item.DISCOVER for url=/DISCOVER/...
   44. hudson.model.Item.EXTENDED_READ for url=/EXTENDED_READ/...
   45. hudson.model.Item.BUILD for url=/BUILD/...
   46. hudson.model.Item.WORKSPACE for url=/WORKSPACE/...
   47. hudson.model.Item.WIPEOUT for url=/WIPEOUT/...
   48. hudson.model.Item.CANCEL for url=/CANCEL/...
   49. hudson.model.Saveable.NOOP for url=/NOOP/...
   50. hudson.model.Saveable.NOOP for url=/NOOP/...
   51. hudson.model.AbstractProject.ABORT for url=/ABORT/...
   52. hudson.model.AbstractProject.BUILD_NOW_TEXT for 
   url=/BUILD_NOW_TEXT/...
   53. hudson.model.Item.PERMISSIONS for url=/PERMISSIONS/...
   54. hudson.model.Item.CREATE for url=/CREATE/...
   55. hudson.model.Item.DELETE for url=/DELETE/...
   56. hudson.model.Item.CONFIGURE for url=/CONFIGURE/...
   57. hudson.model.Item.READ for url=/READ/...
   58. hudson.model.Item.DISCOVER for url=/DISCOVER/...
   59. hudson.model.Item.EXTENDED_READ for url=/EXTENDED_READ/...
   60. hudson.model.Item.BUILD for url=/BUILD/...
   61. 

How can I create a view through XML?

2014-08-05 Thread XuLj
Hello, I'd like to create a view by calling method createViewFromXML(String 
name, InputStream xml) in the View class. How can I achieve that?
It appears that each time I pass a StringInputStream object to this method, it 
throws an Unable to read exception.
My test code is as follows:
String xml = hudson.plugins.nested__view.NestedView  
   +   owner 
class=\hudson\ reference=\../../..\/  
+   name1/name 
   +   
filterExecutorsfalse/filterExecutors   
   +   filterQueuefalse/filterQueue   
   +  
 properties class=\hudson.model.View$PropertyList\/ 
   +   views
   +  
   au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView
   +   owner 
class=\hudson.plugins.nested_view.NestedView\ reference=\../../..\/   
+   name1/name 
   +   
filterExecutorsfalse/filterExecutors   
   +   filterQueuefalse/filterQueue
  +   
properties class=\hudson.model.View$PropertyList\/ 
   +   
noOfDisplayedBuilds1/noOfDisplayedBuilds   
   +   buildViewTitle/buildViewTitle   
  +   
triggerOnlyLatestJobfalse/triggerOnlyLatestJob 
   +   
alwaysAllowManualTriggertrue/alwaysAllowManualTrigger  
   +   
showPipelineParameterstrue/showPipelineParameters  
   +   refreshFrequency3/refreshFrequency  
  +   
showPipelineDefinitionHeaderfalse/showPipelineDefinitionHeader 
   +   
displayProgressBarfalse/displayProgressBar 
   + 
/au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView 
 +   /views  
+   
columns  
   + columns/   
   +  
 /columns 
   + /hudson.plugins.nested__view.NestedView
;  InputStream xx=new 
StringInputStream(xml, utf-8); try {  
 View.createViewFromXML(aa, xx);   } catch (IOException e) {  
 // TODO Auto-generated catch block  
e.printStackTrace();}

  

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


Plugin for generating Test Reports in the 'Bar chart' format

2014-08-05 Thread Gururaj
I want to develop a plugin that will generate the test reports in the 'Bar 
chart' format. Please let me know to start with this.

Regards,
Gururaj P 

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


Re: Discussion: Refactoring of JENKINS project in JIRA

2014-08-05 Thread Oleg Nenashev
Summary from the previous Project meeting (thanks to Daniel Beck for the 
notification).

   1. *JIRA components* (jglick 
   
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-59,
 
   18:18:39) 
  1. 
  
https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring 
  (danielbeck 
  
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-62,
 
  18:19:33)
  2. *ACTION*: oleg-nenashev to report on status of JIRA component 
  change (jglick 
  
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-72,
 
  18:22:31)
  3. *ACTION*: kohsuke to implement JIRA component change (jglick 
  
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-73,
 
  18:22:39)
  4. *AGREED*: want unsorted component empty, but maybe need a more 
  descriptive name (jglick 
  
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-99,
 
  18:27:51)
   
   2. *JIRA components* (jglick 
   
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-106,
 
   18:29:07) 
  1. *ACTION*: oleg-nenashev to document intended usage of unsorted (
  jglick 
  
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-07-23-18.02.log.html#l-113,
 
  18:31:13)
   
I'll try to send a summary on my actions in advance.

BR, Oleg Nenashev

вторник, 24 июня 2014 г., 21:37:43 UTC+4 пользователь Oleg Nenashev написал:

 Since there's no additional input on the components modification, I 
 propose to apply changes on JIRA.
 Thanks to R. Tyler and OSUOSL, Jenkins JIRA is stable enough for such 
 changes now.

 If everyone agrees, it would be great if somebody with JIRA administration 
 rights takes the action point.

 Actions backlog:

- Describe the workflow modification for JIRA project 
   - Untriaged state for new issues (see Kohsuke's clarification 
   above)
   - [New] - Waiting on user state - for incomplete issues

 Best regards, Oleg Nenashev




 2014-06-10 18:41 GMT+04:00 Jesse Glick jgl...@cloudbees.com:

 On Tue, Jun 10, 2014 at 3:34 AM, Daniel Beck m...@beckweb.net wrote:
  Confused it with the Maven build step that's part of core.

 (but which ought to be a plugin too)

 --
 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/luOqm4Qj4sc/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 jenkinsci-dev+unsubscr...@googlegroups.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.
For more options, visit https://groups.google.com/d/optout.


Re: Should we come up with a browser support matrix?

2014-08-05 Thread Oleg Nenashev
+1
The browser support matrix would be great. In addition to IE, it will allow 
to limit the fun with custom browsers. Firefox, Chrome, Safari and IE 
would be enough.

Unfortunately, many plugins have their own browser compatibility issues 
(especially with IE11).
It could be useful to somehow store and publish this information (e.g. via 
pom.xml properties) 

 Perhaps some slow companies still pretend that IE8 is their mandatory 
 browser (and never respect that themselves)

My company uses IE8 (and I also know companies with IE6 X_X), but I also 
vote to increase the minimal supported version to IE9 or even IE10.

Actually, the IE8's JavaScript interpreter performance kills the Jenkins 
user experience in any case. 

Best regards,
Oleg Nenashev

среда, 6 августа 2014 г., 0:53:10 UTC+4 пользователь Tom Fennelly написал:

 Hi Emeric.  Thanks for the response.  +1 to everything you said there.


 On Friday, August 1, 2014 9:37:54 AM UTC+1, evernat wrote:

 Hi Tom,

 In my opinion, we should not try to support IE8 in UI refresh, because it 
 would be foolish for a user to still use IE8 even on WinXP.

 Perhaps some slow companies still pretend that IE8 is their mandatory 
 browser [1] (and never respect that themselves). But in my opinion, your UI 
 refresh should not be blocked or slowed down by the mandate of these slow 
 companies, for which they just need to acknowledge a better mandate or 
 exemptions.

 [1] 
 https://issues.jenkins-ci.org/browse/JENKINS-14749?focusedCommentId=198375page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198375

 Emeric

 Le jeudi 31 juillet 2014 14:26:05 UTC+2, Tom Fennelly a écrit :

 In particular... how far back do we want to support Internet Explorer. 
  I think IE9 for sure, but what about IE8?  It's a real PITA :)



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