date:20121113















































SCM/JIRA link daemon
 commented on  JENKINS-15083


svn-revert-plugin: make dependency to claim plugin optional















Code changed in jenkins
User: Kristian Rosenvold
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
http://jenkins-ci.org/commit/git-plugin/6df02fdd5591f7a895890874217496dcccb78d4b
Log:
  JENKINS-15083 Avoid rebuilds upon intermittent network failures and similar





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15803) git polling mechanism can have build in infinite loop

2012-11-13 Thread jenkins-ci....@michael-prokop.at (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-15803


git polling mechanism can have build in infinite loop















Code changed in jenkins
User: Olivier Lamy
Path:
 src/main/java/hudson/plugins/git/GitSCM.java
http://jenkins-ci.org/commit/git-plugin/af5822b71b8a79f712c0bafeca09b96c5a15e2fb
Log:
  Merge pull request #110 from krosenvold/master

fix for JENKINS-15803


Compare: https://github.com/jenkinsci/git-plugin/compare/58516aeebe9d...af5822b71b8a




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15803) git polling mechanism can have build in infinite loop

2012-11-13 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 commented on  JENKINS-15803


git polling mechanism can have build in infinite loop















not sure to understand when this exception is thrown (your links don't match method calls in current code).
also can't see relation with GitAPI#824 tag() method



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.

2012-11-13 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 commented on  JENKINS-15810


Testlink plugin : generated TAP result files are not used for updating Testlink.















Hi Stéphane, 

Thanks for providing logs, configuration, and all the input values so well organized. That really helps analysing this issue. 

Your job configuration does looks correct, so I guess there might be something in the TestLink configuration. 

Your test cases (Test Current Time, and Test Current Time2) must have the custom field "Test Case Name" configured as "TestCurrentTime", in order to your job work properly.

What the plug-ins does in your job is 1) using the given pattern look for test results, 2) for each results try to match the TAP file name with your key custom field, and then 3) update the results in TestLink.

Can you give a try, please? 

Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.

2012-11-13 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 started work on  JENKINS-15810


Testlink plugin : generated TAP result files are not used for updating Testlink.
















Change By:


Bruno P. Kinoshita
(13/Nov/12 9:13 AM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-5856) Unable to Release a Git Project

2012-11-13 Thread nicolas.del...@gmail.com (JIRA)
















































Nicolas De Loof
 resolved  JENKINS-5856 as Fixed


Unable to Release a Git Project
















git plugin does checkout commits by RefID, not branches. You can force it to use a local branch (advanced section) so that maven release process will be able to commit, tag and push to remote repository





Change By:


Nicolas De Loof
(13/Nov/12 9:18 AM)




Status:


Reopened
Resolved





Assignee:


teilo
NicolasDeLoof





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15811) The Manage Jenkins page lists Jenkins CLI multiple times

2012-11-13 Thread paul.cro...@softwareag.com (JIRA)















































Paul Croome
 created  JENKINS-15811


The Manage Jenkins page lists Jenkins CLI multiple times















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


dashboard-view



Created:


13/Nov/12 9:31 AM



Description:


On the "Manage Jenkins" page, the link to the "System Properties" page is labelled "Jenkins CLI: Access/manage Jenkins from your shell, or from your script." 

The link to the "Log Recorders" page also has the same label. 

The link to the "Jenkins CLI" page also has the same label (but this time it's correct!).




Environment:


Sun/Solaris




Project:


Jenkins



Priority:


Trivial



Reporter:


Paul Croome

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15803) git polling mechanism can have build in infinite loop

2012-11-13 Thread kristian.rosenv...@gmail.com (JIRA)















































Kristia Rosenvold
 commented on  JENKINS-15803


git polling mechanism can have build in infinite loop















Temporarily change base class of GitException to a checked exception and it all becomes clear. Sorry about the line numbers. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15803) git polling mechanism can have build in infinite loop

2012-11-13 Thread kristian.rosenv...@gmail.com (JIRA)













































 
Kristia Rosenvold
 edited a comment on  JENKINS-15803


git polling mechanism can have build in infinite loop
















Temporarily change base class of GitException to a checked exception and it all becomes clear. Sorry about the line numbers, I was a few versions behind when I made the patch/issue



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15812) JAVA_HOME is supperseeded by the JVM used to start the jenkins slave

2012-11-13 Thread nicolas.dels...@gmail.com (JIRA)

Nicolas Delsaux
created JENKINS-15812

JAVA_HOME is supperseeded by the JVM used to start the jenkins slave

Issue Type:

Bug

Affects Versions:

current

Assignee:

Kohsuke Kawaguchi

Components:

slave-setup

Created:

13/Nov/12 9:53 AM

Description:

When starting jenkins slave, used JAVA_HOME is always the java used to start the jenkins slave. In my case, it was C:\Program Files\Java\jre7.
As it's only a JRE, and not a full JDK, it didn't contain the javac executable.
As a consequence, I got

ERROR Unable to locate the Javac Compiler in:
C:\Program Files\Java\jre7\..\lib\tools.jar
Please ensure you are using JDK 1.4 or above and
not a JRE (the com.sun.tools.javac.Main class is required).
In most cases you can change the location of your Java
installation by setting the JAVA_HOME environment variable.

in my maven build log.

Which allowed me to track it to the jenkins-slave.xml file.

As far as i understand, this file is used to configure how the jenkins slave is started, when run using Windows service.

So, in that file, there is this entry :

!--
if you'd like to run Jenkins with a specific version of Java, specify a full path to java.exe.
The following value assumes that you have java in your PATH.
--
executableC:\Program Files\Java\jre7\bin\java.exe/executable

I had to change it to one full JDK to have Jenkins able to compile.
Unfortunatly, i'm quite sure Jenkins will only compile using the JDK I choose (executableC:\Program Files\Java\jdk1.6.0_24\bin\java.exe/executable).

Environment:

Jenkins runs on a Linux server

Jenkins slave runs on a Windows XP machine

Project:

Jenkins

Labels:

windows
slave

Priority:

Major

Reporter:

Nicolas Delsaux

[JIRA] (JENKINS-13771) Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.

2012-11-13 Thread alek...@java.net (JIRA)















































aleksas
 commented on  JENKINS-13771


Jenkins not being triggered on a change to an external with new 1.4 SVN plugin.















I get an empty changelog with subversion 1.7 (plugin v 1.43) but logs show multiple updates and svnkit assertion errors. 

Jenkins ver. 1.489
Environment: Server 2008, 64 bit.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12966) gitTool crashes Jenkins startup

2012-11-13 Thread mot...@gmail.com (JIRA)















































moez awl
 updated  JENKINS-12966


gitTool crashes Jenkins startup
















Change By:


moez awl
(13/Nov/12 9:56 AM)




Status:


Reopened
Open



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15790) Name of Test Case is null

2012-11-13 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 started work on  JENKINS-15790


Name of Test Case is null
















Change By:


Bruno P. Kinoshita
(13/Nov/12 10:21 AM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15813) TAP files considered as binary files are ignored

Michael Prokop
created JENKINS-15813

TAP files considered as binary files are ignored

Issue Type:

Bug

Affects Versions:

current

Assignee:

Bruno P. Kinoshita

Components:

tap

Created:

13/Nov/12 10:25 AM

Description:

If the file type is considered as binary by Jenkins webserver then the TAP plugin doesn't consider this file for inclusion in TAP reports. This can be quite confusing and if you're not aware of this issue it can easily hide problems.

Note: I'm not talking about file permissions but what the Jenkins webserver (Stapler?) considers the file as. If the file extension isn't something which Jenkins serves as plain text then this file is ignored by the TAP plugin.

To reproduce this issue use the following shell execution step:

rm -rf reports
mkdir reports

cat reports/demo EOF
1..1
ok 1 demo OK
EOF

cat reports/demo.pl EOF
1..1
ok 1 demo.pl OK
EOF

cat reports/demo.txt EOF
1..1
ok 1 demo.txt OK
EOF

and enable "reports/*" for TAP results.

Then the following report looks like:

http://michael-prokop.at/screeni/gkrellShoot_12-11-13_110931.png

whereas there are 3 TAP result files available and considered for inclusion:

http://michael-prokop.at/screeni/gkrellShoot_12-11-13_110845.png

When clicking on the "demo" file name (not "view"!) in your browser it's considered as BIN file and download gets enforced. When clicking on demo.pl and demo.txt instead they are provided as plain-text files without forcing download to view them.

It would be nice if such "binary files" could be also considered for TAP reports or if not at least warn in the TAP execution run and mention in the documentation that files should be preferably have suffix .tap.

Project:

Jenkins

Priority:

Major

Reporter:

Michael Prokop

[JIRA] (JENKINS-15811) The Manage Jenkins page lists Jenkins CLI multiple times

2012-11-13 Thread marco.ambu+jenk...@gmail.com (JIRA)















































Marco Ambu
 updated  JENKINS-15811


The Manage Jenkins page lists Jenkins CLI multiple times
















Change By:


Marco Ambu
(13/Nov/12 11:09 AM)




Component/s:


core





Component/s:


dashboard-view



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14212) dashboard-view build fails using JDK 7

2012-11-13 Thread marco.ambu+jenk...@gmail.com (JIRA)
















































Marco Ambu
 resolved  JENKINS-14212 as Fixed


dashboard-view build fails using JDK 7
















Change By:


Marco Ambu
(13/Nov/12 11:14 AM)




Status:


Open
Resolved





Assignee:


PeterHayes
MarcoAmbu





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts

2012-11-13 Thread marco.ambu+jenk...@gmail.com (JIRA)















































Marco Ambu
 commented on  JENKINS-14045


Add ability to change dashboard diagrams time-scale grain for Trend charts















Dirk, can you open another issue as it is different than this one and then we can easily see your suggestion in JIRA.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13968) Dashboard plugin: request for failing jobs portlet

2012-11-13 Thread marco.ambu+jenk...@gmail.com (JIRA)















































Marco Ambu
 commented on  JENKINS-13968


Dashboard plugin: request for failing jobs portlet















Maybe we can make the unstable jobs portlet configurable so that you can specify the 'unstable' condition.
Something like:

	show all unstable
	show only failed



Actually I'm thinking of having only one configurable portlet such as the jobs grid which can be configured to specify what condition the jobs mustsatisfy to be displayed there.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15814) Make it possible to define start and end of a day

2012-11-13 Thread kuypers.d...@googlemail.com (JIRA)















































Dirk Kuypers
 created  JENKINS-15814


Make it possible to define start and end of a day















Issue Type:


Improvement



Assignee:


Peter Hayes



Components:


dashboard-view



Created:


13/Nov/12 11:45 AM



Description:


I would like to be able to define start and end of a day.

Use case: We are running a huge regression test campaign during night starting at 20:00 h and lasting until the early morning around 4:00 h. Currently this means that the test trend charts show half of the tests of a campaign on one day, the other tests are shown for the next day. The exact time a test is executed is quite random and depends on node availability etc. So there is always a mixture of two campaigns per day and the graphs are misleading for us...




Project:


Jenkins



Priority:


Major



Reporter:


Dirk Kuypers

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts

2012-11-13 Thread kuypers.d...@googlemail.com (JIRA)















































Dirk Kuypers
 commented on  JENKINS-14045


Add ability to change dashboard diagrams time-scale grain for Trend charts















Done: JENKINS-15814

And Thanks!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.

2012-11-13 Thread sbent...@akio.com (JIRA)















































stéphane benteux
 updated  JENKINS-15810


Testlink plugin : generated TAP result files are not used for updating Testlink.
















Hello Bruno,

Your indications really helped solving this configuration problem.
Actually, I misunderstood content of those Custom fiedls and usage made by TestLink plugin.

I've provided 2 screen captures with both my Testlink and Jenkins configurations. I hope this may help others.

Best regards 
Stéphane





Change By:


stéphane benteux
(13/Nov/12 11:52 AM)




Attachment:


00-TestLinkConfiguration.PNG





Attachment:


01-JenkinsTestLinkTAPConfiguration.PNG



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15815) Shortcut to navigate between Next/Previous Build

2012-11-13 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 created  JENKINS-15815


Shortcut to navigate between Next/Previous Build















Issue Type:


New Feature



Assignee:


jieryn



Components:


keyboard-shortcuts



Created:


13/Nov/12 12:14 PM



Description:


Since you can't always keep your mouse in the same place and click "Next Build" or "Previous Builds", as the number of actions for a build can change, it would be nice to have a keyboard shortcut for it.




Project:


Jenkins



Priority:


Minor



Reporter:


Christopher Orr

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-2550) Email should be sent when build node is taken offline.

2012-11-13 Thread m...@nordicsemi.no (JIRA)















































Markus Hjerto
 commented on  JENKINS-2550


Email should be sent when build node is taken offline.















I've now created my own Groovy script that does this. It is based on this script from the Jenkins wiki, but I don't let it restart nodes automatically. I assume there's a reason why the node online so I'd like to look at it first. I think it's a great template for other states/parameters that we need to monitor.

For example I've added a small check to ensure that the nodes are in sync since we recently had that problem when switching to winter time. Also, my version does not send e-mails if the node is "Disconnected by ..." since I assume that there's a reason why someone disconnected the node manually.

My modifications are so small that there's no point posting the script here. If you want the same solution/workaround, check out the link above and adopt to your needs. It was very easy to expand even without much Groovy knowledge



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11875) Launcher mixes stdout and stderr of dot















































SCM/JIRA link daemon
 commented on  JENKINS-11875


Launcher mixes stdout and stderr of dot















Code changed in jenkins
User: Stefan Wolf
Path:
 src/main/java/hudson/plugins/depgraph_view/AbstractDependencyGraphAction.java
http://jenkins-ci.org/commit/depgraph-view-plugin/cc12902ef1fae4191aa9b8990ef49fa4a80023ed
Log:
  FIXED JENKINS-11875 Use -q1 to switch of verbose output of graphviz


Compare: https://github.com/jenkinsci/depgraph-view-plugin/compare/7dd8527af25a...cc12902ef1fa




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11875) Launcher mixes stdout and stderr of dot
















































SCM/JIRA link daemon
 resolved  JENKINS-11875 as Fixed


Launcher mixes stdout and stderr of dot
















Change By:


SCM/JIRA link daemon
(13/Nov/12 1:27 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15366) Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.

2012-11-13 Thread ognjen.bub...@gmail.com (JIRA)















































Ognjen Bubalo
 commented on  JENKINS-15366


Problem displaying Jacoco coverage data in Jenkins for very large number of classes and methods.















What do you think about bignums2.jpg?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080















































wolfs
 started work on  JENKINS-13446


Dependency graph points to localhost:8080
















Change By:


wolfs
(13/Nov/12 1:29 PM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15035) cobertura plugin don't validate report files and later fail to parse them

2012-11-13 Thread y...@shurup.com (JIRA)
















































Yury Zaytsev
 resolved  JENKINS-15035 as Fixed


cobertura plugin dont validate report files and later fail to parse them
















Fixed in the latest plugin versions, reported issues in comments had to do with serialization (JENKINS-15518).





Change By:


Yury Zaytsev
(13/Nov/12 1:38 PM)




Status:


Open
Resolved





Assignee:


stephenconnolly
NicolasDeLoof





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-9430) zip of workspace folders does garble filenames with german characters.

2012-11-13 Thread johannes.schmie...@eads.com (JIRA)















































Johannes Schmieder
 commented on  JENKINS-9430


zip of workspace folders does garble filenames with german characters.















Tested again.
Using jenkins 1.489 and setting the file encoding to UTF-8 did work.
In hudson.xml I added as arguments "-Dfile.encoding=UTF-8"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13446) Dependency graph points to localhost:8080
















































wolfs
 resolved  JENKINS-13446 as Fixed


Dependency graph points to localhost:8080
















Should be solved in version 0.5. Please confirm.





Change By:


wolfs
(13/Nov/12 2:25 PM)




Status:


InProgress
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11875) Launcher mixes stdout and stderr of dot















































wolfs
 commented on  JENKINS-11875


Launcher mixes stdout and stderr of dot















I think the warnings are written so stdout, not stderr. This is because in theory stderr is already handled differently. To fix the issue I added -q1 to the command line. Please test, this should be fixed in version 0.5.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12112) Graph link is incorrect under Reverse Proxy. (Dependency graph view)















































wolfs
 started work on  JENKINS-12112


Graph link is incorrect under Reverse Proxy. (Dependency graph view)
















Change By:


wolfs
(13/Nov/12 2:27 PM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































Jesse Glick
 created  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


13/Nov/12 2:58 PM



Description:


If you change the timezone while Jenkins is running, the value of Run.ID_FORMATTER in some threads will reflect the new TZ while that in other threads reflects the old TZ. (Apparently SimpleDateFormat copies the TZ in effect when it was constructed.)

In particular, executor threads (which create the ID) are likely to use the old value while HTTP service threads are likely to use the new value. The result is that Run.rootDir when evaluated from an HTTP thread refers to a nonexistent directory, so the console appears to be empty, etc.

Since the format string omits Z the build’s ID is also ambiguous—must be interpreted according to the server’s local TZ.




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12500) clang scan-build plugin should allow options to be passed directly to scan-build

2012-11-13 Thread ghorv...@etsy.com (JIRA)















































Greg horvath
 commented on  JENKINS-12500


clang scan-build plugin should allow options to be passed directly to scan-build















Ready to close?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































SCM/JIRA link daemon
 commented on  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/Run.java
 core/src/test/java/hudson/model/RunTest.java
 core/src/test/java/hudson/model/StubJob.java
http://jenkins-ci.org/commit/jenkins/d84eca4510f2b259273571ebcc46387f2e88944f
Log:
  FIXED JENKINS-15816 Run.ID_FORMATTER caches stale timezone values.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14665) Quality center plugin for Hudson does not work properly

2012-11-13 Thread nadjim.chetb...@bnpparibas.com (JIRA)















































chetbani nadjim
 commented on  JENKINS-14665


Quality center plugin for Hudson does not work properly















Hi Danielle,

Firstly thank you for your solution. currently, I have the same problem. 

I use the Jenkins QC plugin since a Windows machine. Since this machine, I lunsh the plugin to execute tests which are on the QC machine (another Windows machine). I would thus like to know on whom of the two machines must I install /perfom ALM Client registration ? on the QC plugin machine or on the QC machine. 

By advance thank you for your answer,

Regards,



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































SCM/JIRA link daemon
 commented on  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/ea13e2aed8b126147b4f24edef2e93d54292761f
Log:
  JENKINS-15816 Noted in wrong section.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12527) Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















































Mariusz Nowacki
 resolved  JENKINS-12527 as Not A Defect


Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















Issue was added to wrong component. Archiving artifacts isn't a job for xcode component.

Besides reporter used wrong pattern in Files to archive field. It should be like this:
"build/**/dSYM.zip, build//.ipa"





Change By:


Mariusz Nowacki
(13/Nov/12 4:21 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


NotADefect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12527) Archived dSYM files do not appear under archived artifacts on the Jenkins build page













































 
Mariusz Nowacki
 edited a comment on  JENKINS-12527


Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















Issue was added to wrong component. Archiving artifacts isn't a job for xcode component.

Besides reporter used wrong pattern in Files to archive field. It should be like this:
"build/**/dSYM.zip, build/ ** /.ipa"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12527) Archived dSYM files do not appear under archived artifacts on the Jenkins build page













































 
Mariusz Nowacki
 edited a comment on  JENKINS-12527


Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















Issue was added to wrong component. Archiving artifacts isn't a job for xcode component.

Besides reporter used wrong pattern in Files to archive field. It should be like this:
"build/** / dSYM.zip, build/ ** /.ipa"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12527) Archived dSYM files do not appear under archived artifacts on the Jenkins build page













































 
Mariusz Nowacki
 edited a comment on  JENKINS-12527


Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















Issue was added to wrong component. Archiving artifacts isn't a job for xcode component.

Besides reporter used wrong pattern in Files to archive field. It should be like this:
"build\/**/dSYM.zip, build//.ipa"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12527) Archived dSYM files do not appear under archived artifacts on the Jenkins build page













































 
Mariusz Nowacki
 edited a comment on  JENKINS-12527


Archived dSYM files do not appear under archived artifacts on the Jenkins build page
















Issue was added to wrong component. Archiving artifacts isn't a job for xcode component.

Besides reporter used wrong pattern in Files to archive field. It should be like this:
"build/**/dSYM.zip, build/ **/.ipa"



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views















































SCM/JIRA link daemon
 commented on  JENKINS-11898


Create view if view doesnt exist doesnt work for dynamic views















Code changed in jenkins
User: Vincent Latombe
Path:
 src/main/java/hudson/plugins/clearcase/ClearToolExec.java
 src/main/java/hudson/plugins/clearcase/action/UcmDynamicCheckoutAction.java
http://jenkins-ci.org/commit/clearcase-plugin/35996f3090bc1eb019f4a46a918231b75c217c51
Log:
  JENKINS-11898 Create view if view doesn't exist doesn't work for
dynamic views































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views

2012-11-13 Thread vinc...@latombe.net (JIRA)















































Vincent Latombe
 commented on  JENKINS-11898


Create view if view doesnt exist doesnt work for dynamic views















Hi,

the fix for this will be released in 1.3.12.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views

2012-11-13 Thread vinc...@latombe.net (JIRA)
















































Vincent Latombe
 resolved  JENKINS-11898 as Fixed


Create view if view doesnt exist doesnt work for dynamic views
















Change By:


Vincent Latombe
(13/Nov/12 4:28 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15276) Store Groovy Scripts into a local VCS

2012-11-13 Thread d...@fortysix.ch (JIRA)















































domi
 commented on  JENKINS-15276


Store Groovy Scripts into a local VCS















please install this plugin too: https://wiki.jenkins-ci.org/display/JENKINS/Git+Server+Plugin
Unfortunately I marked it as optional in the dependencies, therefore the UpdateCenter does not install it automatically.
Let me know if this solves the issue.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































dogfood
 commented on  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Integrated in  jenkins_main_trunk #2067
 FIXED JENKINS-15816 Run.ID_FORMATTER caches stale timezone values. (Revision d84eca4510f2b259273571ebcc46387f2e88944f)
JENKINS-15816 Noted in wrong section. (Revision ea13e2aed8b126147b4f24edef2e93d54292761f)

 Result = UNSTABLE
Jesse Glick : d84eca4510f2b259273571ebcc46387f2e88944f
Files : 

	changelog.html
	core/src/test/java/hudson/model/RunTest.java
	core/src/test/java/hudson/model/StubJob.java
	core/src/main/java/hudson/model/Run.java



Jesse Glick : ea13e2aed8b126147b4f24edef2e93d54292761f
Files : 

	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15801) Allow root of relative paths to be specified

2012-11-13 Thread joakim.pl...@gmail.com (JIRA)















































Joakim Plate
 commented on  JENKINS-15801


Allow root of relative paths to be specified















Have similar issue. Doing unit tests on submodules of a project with the following structure.

file.c
test/makefile

Where makefile refere to parent directory objects. To start the build i issue something like:

make -C test




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15817) XStream form of projects excessively strict about null fields















































Jesse Glick
 created  JENKINS-15817


XStream form of projects excessively strict about null fields















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


core



Created:


13/Nov/12 5:47 PM



Description:


You might expect that you could create a freestyle project as config.xml simply by writing project/ and allowing all fields to be set to default values. Unfortunately you then get a NullPointerException from various places, such as Project.createTransientActions, which expect fields such as builders to have been set to non-null collections (as the constructor does).

This is annoying when trying to create jobs directly from XML, e.g. when using a templating system. Better to make fields default to the constructor’s value.




Project:


Jenkins



Labels:


serialization




Priority:


Minor



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15801) Allow root of relative paths to be specified

2012-11-13 Thread joakim.pl...@gmail.com (JIRA)















































Joakim Plate
 commented on  JENKINS-15801


Allow root of relative paths to be specified















Having similar issue here.

Want to build unit tests with the following structure:

file.c
test/makefile

makefile refer to ../file.c to build.

jenkings build is kicked off like:
make -C test




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15801) Allow root of relative paths to be specified

2012-11-13 Thread joakim.pl...@gmail.com (JIRA)













































 
Joakim Plate
 edited a comment on  JENKINS-15801


Allow root of relative paths to be specified
















deleted duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































SCM/JIRA link daemon
 commented on  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Run.java
http://jenkins-ci.org/commit/jenkins/7bf6c5ca6e09ce2add22e0685db63da658b5fe17
Log:
  JENKINS-15816 Working around javac bug triggered by d84eca4.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven















































SCM/JIRA link daemon
 commented on  JENKINS-15367


Jenkins kicks off the wrong downstream builds for Maven















Code changed in jenkins
User: alexkoon
Path:
 maven-plugin/src/main/java/hudson/maven/ModuleDependency.java
 maven-plugin/src/test/java/hudson/maven/MavenModuleTest.java
http://jenkins-ci.org/commit/jenkins/4043905580df5bf22cde0eaf3dec103abdc88017
Log:
  JENKINS-15367 Fix for downstream dependencies when we have a specified version (not a version range).





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven















































SCM/JIRA link daemon
 commented on  JENKINS-15367


Jenkins kicks off the wrong downstream builds for Maven















Code changed in jenkins
User: Olivier Lamy
Path:
 maven-plugin/src/main/java/hudson/maven/ModuleDependency.java
 maven-plugin/src/test/java/hudson/maven/MavenModuleTest.java
http://jenkins-ci.org/commit/jenkins/2c469b37b563c5d6ca70ac7841897e1a20083130
Log:
  Merge pull request #609 from alexkoon/master

JENKINS-15367 Fix Maven downstream resolution when declared as a specific version.


Compare: https://github.com/jenkinsci/jenkins/compare/7bf6c5ca6e09...2c469b37b563




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven















































SCM/JIRA link daemon
 commented on  JENKINS-15367


Jenkins kicks off the wrong downstream builds for Maven















Code changed in jenkins
User: Olivier Lamy
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/2dbf8c5bce22f557834f5802cc379566addb9b7a
Log:
  changelog entry for JENKINS-15367































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13790) Subversion externals fail

2012-11-13 Thread dsear...@siginnovations.com (JIRA)















































Dan Searles
 commented on  JENKINS-13790


Subversion externals fail















Oct 29 there was a new svnkit released which mentions it is fixed for SVN 1.7 server and working directories  Will there be a Jenkins upgrade soon that uses the latest svnkit?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15816) Run.ID_FORMATTER caches stale timezone values















































dogfood
 commented on  JENKINS-15816


Run.ID_FORMATTER caches stale timezone values















Integrated in  jenkins_main_trunk #2068
 JENKINS-15816 Working around javac bug triggered by d84eca4. (Revision 7bf6c5ca6e09ce2add22e0685db63da658b5fe17)

 Result = UNSTABLE
Jesse Glick : 7bf6c5ca6e09ce2add22e0685db63da658b5fe17
Files : 

	core/src/main/java/hudson/model/Run.java





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks

2012-11-13 Thread karlie.spam...@gmail.com (JIRA)













































 
karlie verkest
 edited a comment on  JENKINS-1640


Environment variables not passed through to Ant tasks
















This is happening to me too.  I have some projects where the environment variables pass through just fine and others in which the same variables do not.  Here's the output of one that's not working:


[echo] Workspace Directory: ${env.WORKSPACE}
[echo] Build Number: ${env.BUILD_NUMBER}


Differences between the 2 projects?


	Broken project builds periodically
	Broken project discards old builds
	Working project is parameterized



Quite perplexed =)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15817) XStream form of projects excessively strict about null fields















































SCM/JIRA link daemon
 commented on  JENKINS-15817


XStream form of projects excessively strict about null fields















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/hudson/model/Project.java
 test/src/test/java/hudson/model/FreeStyleProjectTest.java
http://jenkins-ci.org/commit/jenkins/7d2c0efa7bad8f2a0a47f7dcc395a5a4baee99cd
Log:
  FIXED JENKINS-15817 XStream form of projects excessively strict about null fields.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15817) XStream form of projects excessively strict about null fields
















































SCM/JIRA link daemon
 resolved  JENKINS-15817 as Fixed


XStream form of projects excessively strict about null fields
















Change By:


SCM/JIRA link daemon
(13/Nov/12 7:09 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15627) Using iOS slave in 1.487 - Can't connect to window server - not enough permissions

2012-11-13 Thread org-jenkins...@bumppo.net (JIRA)















































Nathaniel Irons
 commented on  JENKINS-15627


Using iOS slave in 1.487 - Cant connect to window server - not enough permissions















Thanks for the workaround. We saw the same failure after updating from 1.486 to 1.490. Our 10.7.5 build nodes were dead in the water.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-5697) CppNCSS 1.0-beta-4 plugin not working

2012-11-13 Thread peter.gerstm...@gmail.com (JIRA)















































Peter Gerstmann
 reopened  JENKINS-5697


CppNCSS 1.0-beta-4 plugin not working
















I am still experiencing this issue with the most current version of CppNcss (1.1):

	No report is generated.
	No errors are logged. I know the plugin must be getting invoked because I can trigger an error by giving an invalid path to the xml data file.



Can someone please investigate this?





Change By:


Peter Gerstmann
(13/Nov/12 7:42 PM)




Resolution:


CannotReproduce





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1640) Environment variables not passed through to Ant tasks

2012-11-13 Thread karlie.spam...@gmail.com (JIRA)













































 
karlie verkest
 edited a comment on  JENKINS-1640


Environment variables not passed through to Ant tasks
















This is happening to me too.  I have some projects where the environment variables pass through just fine and others in which the same variables do not.  Here's the output of one that's not working:


[echo] Workspace Directory: ${env.WORKSPACE}
[echo] Build Number: ${env.BUILD_NUMBER}


Differences between the 2 projects?


	Broken project builds periodically
	Broken project discards old builds
	Working project is parameterized



Quite perplexed =)



UPDATE

I feel stupid.  That's what happens when you forget


property environment="env" /


My bad!  Sorry I cluttered up the comment feed.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13381) Jenkins stopped after updating plugins

2012-11-13 Thread mcon...@gamesalad.com (JIRA)















































Michael Conlon
 commented on  JENKINS-13381


Jenkins stopped after updating plugins















I'm still seeing this in Jenkins 1.487.
I've had Git Plugin installed for a very long time. When I installed Git-parameter plugin, things went haywire. However, manually removing Git parameter plugin did not fix the problem. Only removing Git plugin fixes it.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15817) XStream form of projects excessively strict about null fields















































dogfood
 commented on  JENKINS-15817


XStream form of projects excessively strict about null fields















Integrated in  jenkins_main_trunk #2070
 FIXED JENKINS-15817 XStream form of projects excessively strict about null fields. (Revision 7d2c0efa7bad8f2a0a47f7dcc395a5a4baee99cd)

 Result = UNSTABLE
Jesse Glick : 7d2c0efa7bad8f2a0a47f7dcc395a5a4baee99cd
Files : 

	core/src/main/java/hudson/model/Project.java
	test/src/test/java/hudson/model/FreeStyleProjectTest.java
	core/src/main/java/hudson/model/AbstractProject.java
	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14255) java.io.InvalidClassException:















































SCM/JIRA link daemon
 commented on  JENKINS-14255


java.io.InvalidClassException:















Code changed in jenkins
User: kbrandt
Path:
 src/main/java/hudson/plugins/sloccount/SloccountPublisher.java
 src/main/java/hudson/plugins/sloccount/model/SloccountParser.java
http://jenkins-ci.org/commit/sloccount-plugin/098949d472c108ab02ab13de10f9c5064f4817d9
Log:
  Merge pull request #8 from kbrandt/master

FIXED JENKINS-14255 java.io.InvalidClassException


Compare: https://github.com/jenkinsci/sloccount-plugin/compare/fa00c9329554...098949d472c1




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14255) java.io.InvalidClassException:















































SCM/JIRA link daemon
 commented on  JENKINS-14255


java.io.InvalidClassException:















Code changed in jenkins
User: Karsten Brandt
Path:
 src/main/java/hudson/plugins/sloccount/SloccountPublisher.java
 src/main/java/hudson/plugins/sloccount/model/SloccountParser.java
http://jenkins-ci.org/commit/sloccount-plugin/f2577af289dcd5d4fa6d114b9b2ccedc7d2e5629
Log:
  FIXED JENKINS-14255 java.io.InvalidClassException





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14255) java.io.InvalidClassException:
















































SCM/JIRA link daemon
 resolved  JENKINS-14255 as Fixed


java.io.InvalidClassException:
















Change By:


SCM/JIRA link daemon
(13/Nov/12 8:54 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14135) NPE

2012-11-13 Thread spam_schluc...@web.de (JIRA)
















































Karsten Brandt
 closed  JENKINS-14135 as Fixed


NPE
















https://github.com/jenkinsci/sloccount-plugin/pull/8

has been merged into the master repo





Change By:


Karsten Brandt
(13/Nov/12 9:12 PM)




Status:


Open
Closed





Fix Version/s:


current





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14998) Cannot do si comands from shell or batch file (MKS Integrity CLI)

2012-11-13 Thread istvan.ba...@gmail.com (JIRA)















































Istvan Baksa
 commented on  JENKINS-14998


Cannot do si comands from shell or batch file (MKS Integrity CLI)















This is an MKS configuration problem.
To fix this problem edit the "IntegrityClientSite.rc" file in the IntegrityClient root folder client_install_dir\IntegrityClientSite.rc and add the following line:

IntegrityClient.port=0



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results















































Jesse Glick
 created  JENKINS-15818


Display exceedingly slow for large test results















Issue Type:


Bug



Assignee:


Jesse Glick



Attachments:


AppTest.java



Components:


junit



Created:


13/Nov/12 9:48 PM



Description:


When there are a lot of test cases in a single suite, rendering the summary page is dreadfully slow. Most of the time is taken in TestObject.uniquifyName, which can be called thousands of times, each taking several msec.




Project:


Jenkins



Labels:


performance




Priority:


Major



Reporter:


Jesse Glick

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results















































Jesse Glick
 commented on  JENKINS-15818


Display exceedingly slow for large test results















Other bottlenecks: CaseResult.getPreviousResult; and getSafeName called from other threads (context menu).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results
















































SCM/JIRA link daemon
 resolved  JENKINS-15818 as Fixed


Display exceedingly slow for large test results
















Change By:


SCM/JIRA link daemon
(13/Nov/12 10:18 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results















































SCM/JIRA link daemon
 commented on  JENKINS-15818


Display exceedingly slow for large test results















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/tasks/junit/CaseResult.java
 core/src/main/java/hudson/tasks/junit/ClassResult.java
 core/src/main/java/hudson/tasks/junit/PackageResult.java
 core/src/main/java/hudson/tasks/junit/SuiteResult.java
 core/src/main/java/hudson/tasks/test/TestObject.java
http://jenkins-ci.org/commit/jenkins/734e7e01306e1696655e619d8902a7e6e98b4315
Log:
  FIXED JENKINS-15818 Display exceedingly slow for large test results.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12765) ChromeDriver won't install on slave

2012-11-13 Thread swestc...@gmail.com (JIRA)















































Simon Westcott
 commented on  JENKINS-12765


ChromeDriver wont install on slave















Same issue for me,


Installing chromedriver to /var/lib/jenkins/slaves/tools/chromedriver
ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins.
java.lang.NullPointerException
	at org.jenkinsci.plugins.chromedriver.DownloadableImpl.getType(DownloadableImpl.java:91)
	at org.jenkinsci.plugins.chromedriver.DownloadableImpl.select(DownloadableImpl.java:78)
	at org.jenkinsci.plugins.chromedriver.DownloadableImpl.resolve(DownloadableImpl.java:35)
	at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.process(ComputerListenerImpl.java:43)
	at org.jenkinsci.plugins.chromedriver.ComputerListenerImpl.preOnline(ComputerListenerImpl.java:34)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:370)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:317)
	at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:454)
	at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:293)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)
ERROR: Connection terminated





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results















































SCM/JIRA link daemon
 commented on  JENKINS-15818


Display exceedingly slow for large test results















Code changed in jenkins
User: Jesse Glick
Path:
 test/src/test/java/hudson/tasks/junit/SuiteResultTest.java
http://jenkins-ci.org/commit/jenkins/9e205379fb1b2a62c391ceab993e03a4a5539ec6
Log:
  JENKINS-15818 Adding safeName fields takes a bit more heap.































This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13279) Interface with Crowd embedded that runs in Jira

2012-11-13 Thread snyder....@gmail.com (JIRA)















































Tim Snyder
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















Hi Thorston, I'm running into this behavior and I'm going to digg into the plugin code a bit and see if I can figure out what's going wrong. Just wanted to see if there are any updates before I start looking.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15818) Display exceedingly slow for large test results