date:20120305

[
https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159827#comment-159827
]

kutzi commented on JENKINS-1152:

Since January, there's a JavaMail 1.4.4 already.
I can see no reason, why we shouldn't update to that one.

Mail server rejecting emails from hudson

Key: JENKINS-1152
URL: https://issues.jenkins-ci.org/browse/JENKINS-1152
Project: Jenkins
Issue Type: Bug
Components: mail
Affects Versions: current
Environment: Platform: All, OS: All
Reporter: typerlc

When sending emails from hudson, my mail server (postfix, but I'm sure others
will behave similarly too) rejects the message because the smtp HELO message
isn't being sent.
This is because the system property mail.smtp.localhost hasn't been set before
sending the email. This is described in the javadocs for com.sun.mail.smtp.
See also:
http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508.
The solution is to add some code in hudson.tasks.Mailer.createSession() like:
props.put(mail.smtp.localhost, localServerName);
I guess some code to pull the localServerName out of config would be needed
to.
In theory, a work around might be setting a system property when running
hudson,
but I've not been able to make this work yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-3983) SMTP authentication not working


[ 
https://issues.jenkins-ci.org/browse/JENKINS-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159828#comment-159828
 ] 

kutzi commented on JENKINS-3983:


Seems to be fixed in JavaMail 1.4.3
http://www.oracle.com/technetwork/java/javamail/javamail143-243221.html

 SMTP authentication not working
 ---

 Key: JENKINS-3983
 URL: https://issues.jenkins-ci.org/browse/JENKINS-3983
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Platform: PC, OS: All
Reporter: marcb
 Attachments: stacktrace.txt


 I've tried to use my Exchange 2007 server as an SMTP server for Hudson, which 
 requires SMTP authentication. I configured the standard authentication 
 settings 
 which have been confirmed to work on Outlook, Outlook Express as well as our 
 office printer (which can sending scans by email). When sending a test email, 
 or 
 having emails sent after a build, I get the following:
 com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not 
 authenticated
 See attachment for full stack trace. 
 It would appear the problem is related to the way JavaMail is called in 
 Hudson. 
 The following FAQ entry describes the problem:
 http://java.sun.com/products/javamail/FAQ.html#smtpauth
 I checked hudson.tasks.Mailer in core/src/main/java/hudson/tasks and it seems 
 indeed that JavaMail is being called using Transport.send(msg) instead of the 
 method suggested in the FAQ above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12978) NullPointerException saving jenkins configuration

2012-03-05 Thread nicolas.del...@gmail.com (JIRA)

Nicolas De Loof created JENKINS-12978:
-

 Summary: NullPointerException saving jenkins configuration
 Key: JENKINS-12978
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12978
 Project: Jenkins
  Issue Type: Bug
  Components: maven-repo-cleaner
Reporter: Nicolas De Loof


how to reproduce :

edit jenkins configuration, leave maven-repo-cleaner cron expression empty
save
- NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12978) NullPointerException saving jenkins configuration


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159831#comment-159831
 ] 

SCM/JIRA link daemon commented on JENKINS-12978:


Code changed in jenkins
User: Nicolas De Loof
Path:
 
src/main/java/org/jenkinsci/plugins/mavenrepocleaner/MavenRepoCleanerProperty.java
http://jenkins-ci.org/commit/maven-repo-cleaner-plugin/8432023d8143d419b257a1e07bcf12a910da1388
Log:
  [FIXED JENKINS-12978] NullPoionterException saving jenkins config
use fixEmptyAndTrim that handles null






 NullPointerException saving jenkins configuration
 -

 Key: JENKINS-12978
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12978
 Project: Jenkins
  Issue Type: Bug
  Components: maven-repo-cleaner
Reporter: Nicolas De Loof

 how to reproduce :
 edit jenkins configuration, leave maven-repo-cleaner cron expression empty
 save
 - NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12978) NullPointerException saving jenkins configuration


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SCM/JIRA link daemon resolved JENKINS-12978.


Resolution: Fixed

 NullPointerException saving jenkins configuration
 -

 Key: JENKINS-12978
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12978
 Project: Jenkins
  Issue Type: Bug
  Components: maven-repo-cleaner
Reporter: Nicolas De Loof

 how to reproduce :
 edit jenkins configuration, leave maven-repo-cleaner cron expression empty
 save
 - NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulli Hafner updated JENKINS-12972:
--

Component/s: git

 Add option to run 'git bisect' to find which commit added new bugs 
 ---

 Key: JENKINS-12972
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
 Project: Jenkins
  Issue Type: New Feature
  Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Assignee: Ulli Hafner
Priority: Minor

 Today, when you run find-bugs plug-in triggered by a git commit, you can't 
 know exactly which commit added those bugs.
 It becomes especially difficult to know when a high volume of commits is 
 pushed at once.
 find-bugs plug-in could have a new option to tick in the 'advanced section',
 which will do a 'git bisect' on the git commits that caused a new bug and 
 display/email to commiter who did it.
 that would simply and automate the process of finding who wrote the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulli Hafner updated JENKINS-12972:
--

Component/s: analysis-core
 core

 Add option to run 'git bisect' to find which commit added new bugs 
 ---

 Key: JENKINS-12972
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
 Project: Jenkins
  Issue Type: New Feature
  Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Assignee: Ulli Hafner
Priority: Minor

 Today, when you run find-bugs plug-in triggered by a git commit, you can't 
 know exactly which commit added those bugs.
 It becomes especially difficult to know when a high volume of commits is 
 pushed at once.
 find-bugs plug-in could have a new option to tick in the 'advanced section',
 which will do a 'git bisect' on the git commits that caused a new bug and 
 display/email to commiter who did it.
 that would simply and automate the process of finding who wrote the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12978) NullPointerException saving jenkins configuration


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159833#comment-159833
 ] 

SCM/JIRA link daemon commented on JENKINS-12978:


Code changed in jenkins
User: Nicolas De Loof
Path:
 
src/main/java/org/jenkinsci/plugins/mavenrepocleaner/MavenRepoCleanerProperty.java
http://jenkins-ci.org/commit/maven-repo-cleaner-plugin/90d596ffe1489dfdccab072659c41ca9aa1b2b58
Log:
  [FIXED JENKINS-12978] NullPoionterException saving jenkins config
use fixEmptyAndTrim that handles null






 NullPointerException saving jenkins configuration
 -

 Key: JENKINS-12978
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12978
 Project: Jenkins
  Issue Type: Bug
  Components: maven-repo-cleaner
Reporter: Nicolas De Loof

 how to reproduce :
 edit jenkins configuration, leave maven-repo-cleaner cron expression empty
 save
 - NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

2012-03-05 Thread ee...@redhat.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159834#comment-159834
 ] 

Eyal Edri commented on JENKINS-12972:
-

Not sure i understand what 'extra plugin' is, but i agree it can be useful for 
other plugins as well.
you mean adding an extension point to git plugin (like gerrit-trigger)? 

 Add option to run 'git bisect' to find which commit added new bugs 
 ---

 Key: JENKINS-12972
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
 Project: Jenkins
  Issue Type: New Feature
  Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Assignee: Ulli Hafner
Priority: Minor

 Today, when you run find-bugs plug-in triggered by a git commit, you can't 
 know exactly which commit added those bugs.
 It becomes especially difficult to know when a high volume of commits is 
 pushed at once.
 find-bugs plug-in could have a new option to tick in the 'advanced section',
 which will do a 'git bisect' on the git commits that caused a new bug and 
 display/email to commiter who did it.
 that would simply and automate the process of finding who wrote the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12978) NullPointerException saving jenkins configuration

2012-03-05 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159835#comment-159835
 ] 

dogfood commented on JENKINS-12978:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_maven-repo-cleaner 
#111|http://ci.jenkins-ci.org/job/plugins_maven-repo-cleaner/111/]
 [FIXED JENKINS-12978] NullPoionterException saving jenkins config 
(Revision 90d596ffe1489dfdccab072659c41ca9aa1b2b58)

 Result = SUCCESS
Nicolas De Loof : 
Files : 
* 
src/main/java/org/jenkinsci/plugins/mavenrepocleaner/MavenRepoCleanerProperty.java


 NullPointerException saving jenkins configuration
 -

 Key: JENKINS-12978
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12978
 Project: Jenkins
  Issue Type: Bug
  Components: maven-repo-cleaner
Reporter: Nicolas De Loof

 how to reproduce :
 edit jenkins configuration, leave maven-repo-cleaner cron expression empty
 save
 - NullPointerException

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs

[
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159832#comment-159832
]

Ulli Hafner edited comment on JENKINS-12972 at 3/5/12 10:00 AM:

Wouldn't such a feature make more sense in an additional plug-in? I think this
feature should be available to every item that changes the build status. I.e.,
failing tests, new compiler warnings, new findbugs warnings, etc. Moreover
(since this is only available with git), it should be an extension to the git
plug-in.

was (Author: drulli):
Wouldn't such a feature make more sense in an extra plug-in? I think this
feature should be available to every item that changes the build status. I.e.,
failing tests, new compiler warnings, new findbugs warnings, etc. Moreover
(since this is only available with git), it should be an extension to the git
plug-in.

Add option to run 'git bisect' to find which commit added new bugs
---

Key: JENKINS-12972
URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
Project: Jenkins
Issue Type: New Feature
Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Assignee: Ulli Hafner
Priority: Minor

Today, when you run find-bugs plug-in triggered by a git commit, you can't
know exactly which commit added those bugs.
It becomes especially difficult to know when a high volume of commits is
pushed at once.
find-bugs plug-in could have a new option to tick in the 'advanced section',
which will do a 'git bisect' on the git commits that caused a new bug and
display/email to commiter who did it.
that would simply and automate the process of finding who wrote the bug.

[JIRA] (JENKINS-12972) Add option to run 'git bisect' to find which commit added new bugs


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159836#comment-159836
 ] 

Ulli Hafner commented on JENKINS-12972:
---

I think the best approach would be to have a new plug-in that provides an 
extension point so that other plug-ins like the findbugs plug-in can register. 
This new plug-in has the knowledge on how to do the git bisect. And this 
plug-in needs to get an event from the findbugs plug-in (and all other 
participating plug-ins), when the build status has been changed.

 Add option to run 'git bisect' to find which commit added new bugs 
 ---

 Key: JENKINS-12972
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12972
 Project: Jenkins
  Issue Type: New Feature
  Components: analysis-core, core, findbugs, git
Reporter: Eyal Edri
Assignee: Ulli Hafner
Priority: Minor

 Today, when you run find-bugs plug-in triggered by a git commit, you can't 
 know exactly which commit added those bugs.
 It becomes especially difficult to know when a high volume of commits is 
 pushed at once.
 find-bugs plug-in could have a new option to tick in the 'advanced section',
 which will do a 'git bisect' on the git commits that caused a new bug and 
 display/email to commiter who did it.
 that would simply and automate the process of finding who wrote the bug.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11539) GIT plugin

2012-03-05 Thread da...@orionrobots.co.uk (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159837#comment-159837
 ] 

Danny Staple commented on JENKINS-11539:


Have you tried clearing this workspace and rerunning the job?

 GIT plugin
 --

 Key: JENKINS-11539
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11539
 Project: Jenkins
  Issue Type: Bug
 Environment: Jenkins-Git plugin, Windows Server 2003 SP2, IIS v6.0
Reporter: Murali Srinivasan

 I have configured Jenkins to generate builds for the GIT repository in 
 Windows Server. My Jenkins job is configured to Poll the repository 
 continuously and trigger build if any change is found in the repository. The 
 issue is Jenkins job triggers automatically even there is no change in the 
 repository. When I checked the polling log it printed the following message
 Started on Oct 27, 2011 9:45:54 AM
 Using strategy: Default
 [poll] Last Build : #289
 [poll] Last Built Revision: Revision 7fd9fb8139dd0c449a0382b505c7857c8634f33f 
 (origin/Prod_dev)
 Workspace has a .git repository, but it appears to be corrupt.
 No Git repository yet, an initial checkout is required
 Done. Took 11 sec
 Changes found

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1930) Create Tag (Tag this build) Not working

2012-03-05 Thread jplandr...@nidget.org (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159838#comment-159838
 ] 

Jean-Pol Landrain commented on JENKINS-1930:


I have done a test with one of the latest version of Jenkins to date (1.451). 
The issue is not present.

 Create Tag (Tag this build) Not working
 ---

 Key: JENKINS-1930
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1930
 Project: Jenkins
  Issue Type: Bug
  Components: svn-tag
Affects Versions: current
 Environment: Platform: All, OS: HP-UX
Reporter: wymgaz

 Hudson version 1.227. Stand alone setup running on Winstone.
 When attempting a tag after selecting 'Tag this build', the tag fails with an 
 error:
 Tagging http://subversion/svn/X/web/project/trunk (rev.19085) to
 http://subversion/svn/X/web/project/tags/project-30
 Failed to tag
 org.tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details
 follow):
 svn: CHECKOUT of '/svn/X/!svn/ver/19211/web/project/tags': 403 Forbidden
 (http://subversion)
   at
 org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)
   at 
 org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)
   at
 hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)
   at hudson.model.TaskThread.run(TaskThread.java:77)
 Completed
 The error suggests the user setup within the hudson.scm.SubversionSCM.xml does
 not have the authority to checkout the subversion tags directory revision.
 Further investigation found the user being used for the tag is the user that
 started Hudson in the first instance, and NOT the user declared in the
 hudson.scm.SubversionSCM.xml file. Thus, if the user account that started 
 Hudson
 does not have enough permissions for SVN, then the tagging fails with the 
 above
 error.
 Regards
 Matt Gaunt

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12979) can not upload file to filestore in collabnet teamforge

2012-03-05 Thread jens.haub...@havilog.com (JIRA)

Jens Haubold created JENKINS-12979:
--

 Summary: can not upload file to filestore in collabnet teamforge
 Key: JENKINS-12979
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12979
 Project: Jenkins
  Issue Type: Bug
  Components: collabnet
Affects Versions: current
 Environment: - HP-UX 11.31
- Java 1.6
- tomcat 7.0.21

Reporter: Jens Haubold
Assignee: whsu
 Attachments: catalina.out

The file release upload to collabnet temaforge does not work. Think the root 
cause it the TeamForgeShareDescriptor exception (see attached file).

i use promoted build 2.4 and Collabnet 1.1.6

BR and thx
Jens

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2012-03-05 Thread iker.jime...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159839#comment-159839
 ] 

Iker Jimenez commented on JENKINS-12966:


I can confirm the same issue here.

Last Jenkins release that works is 1.447

 gitTool crashes Jenkins startup
 ---

 Key: JENKINS-12966
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12966
 Project: Jenkins
  Issue Type: Bug
  Components: core, git
 Environment: Jenkins 1.452
 Red Hat Enterprise Linux Server release 6.2 (Santiago)
 Linux HOSTNAME 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 14:50:54 EST 
 2012 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Darren Weber
Assignee: abayer
Priority: Blocker
  Labels: git, startup

 org.jvnet.hudson.reactor.ReactorException: java.lang.Error: 
 java.lang.reflect.InvocationTargetException
   at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
   at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
   at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
   at jenkins.model.Jenkins.init(Jenkins.java:736)
   at hudson.model.Hudson.init(Hudson.java:81)
   at hudson.model.Hudson.init(Hudson.java:77)
   at hudson.WebAppMain$2.run(WebAppMain.java:217)
 Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
   at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
   at 
 hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
   at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
   at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
   at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
   at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
   ... 8 more
 Caused by: java.lang.NullPointerException
   at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74)
   ... 13 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12779) Error when try to run all jobs in a view

2012-03-05 Thread alper.tekin...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159840#comment-159840
 ] 

Alper Tekinap commented on JENKINS-12779:
-

Hi. From the Manage Plugins page the version of bulk builder is 1.4 and the 
name of the view i try to build is nightly-buils. i try Build options  Limit 
to jobs in view  nightly-buils and get this error. my jenkins version 1.451 
and i am using ubuntu 11.05.

 Error when try to run all jobs in a view
 

 Key: JENKINS-12779
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12779
 Project: Jenkins
  Issue Type: Bug
  Components: bulk-builder
Affects Versions: current
 Environment: Ubuntu 10.04 Server
Reporter: Alper Tekinap
Assignee: Simon Westcott

 When try to run all jobs in a view it gives an error like:
 Status Code: 500
 Exception:
 Stacktrace:
 java.lang.IllegalArgumentException: No enum const class 
 org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.ON
   at java.lang.Enum.valueOf(Enum.java:214)
   at 
 org.jvnet.hudson.plugins.bulkbuilder.model.BuildType.valueOf(BuildType.java:31)
   at 
 org.jvnet.hudson.plugins.bulkbuilder.BulkBuilderAction.doBuild(BulkBuilderAction.java:93)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
   at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
   at 
 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
   at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at 
 hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
   at 
 winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
   at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150)
   at java.lang.Thread.run(Thread.java:636)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js

2012-03-05 Thread alexl...@gmail.com (JIRA)

Alex Lehmann created JENKINS-12980:
--

 Summary: With IE8 any page displays a javascript error about 
sortable.js
 Key: JENKINS-12980
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980
 Project: Jenkins
  Issue Type: Bug
  Components: www
Affects Versions: current
 Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, 
tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8
Reporter: Alex Lehmann
Priority: Minor


When accessing Jenkins with IE8, each page displays a javascript error about 
sortable.js

Line 242
Character 9
Object doesn't support this property or method
Code 0
http://(host)/jenkins/static/99210c85/scripts/sortable.js

(the text is roughly translated back to English since I do not have an English 
Windows to test)

When skipping the error message, the page works, but the error shows up on any 
page again.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js

2012-03-05 Thread alexl...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Lehmann updated JENKINS-12980:
---

Description: 
When accessing Jenkins with IE8, each page displays a javascript error about 
sortable.js

Line 242
Character 9
Object doesn't support this property or method
Code 0
http://(host)/jenkins/static/99210c85/scripts/sortable.js

(the text is roughly translated back to English since I do not have an English 
Windows to test)

When skipping the error message, the page works, but the error shows up on any 
page again.

The same page works on IE6, IE7, IE9 and current Firefox without errors


  was:
When accessing Jenkins with IE8, each page displays a javascript error about 
sortable.js

Line 242
Character 9
Object doesn't support this property or method
Code 0
http://(host)/jenkins/static/99210c85/scripts/sortable.js

(the text is roughly translated back to English since I do not have an English 
Windows to test)

When skipping the error message, the page works, but the error shows up on any 
page again.




 With IE8 any page displays a javascript error about sortable.js
 ---

 Key: JENKINS-12980
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980
 Project: Jenkins
  Issue Type: Bug
  Components: www
Affects Versions: current
 Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, 
 tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8
Reporter: Alex Lehmann
Priority: Minor

 When accessing Jenkins with IE8, each page displays a javascript error about 
 sortable.js
 Line 242
 Character 9
 Object doesn't support this property or method
 Code 0
 http://(host)/jenkins/static/99210c85/scripts/sortable.js
 (the text is roughly translated back to English since I do not have an 
 English Windows to test)
 When skipping the error message, the page works, but the error shows up on 
 any page again.
 The same page works on IE6, IE7, IE9 and current Firefox without errors

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1152) Mail server rejecting emails from hudson


[ 
https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159841#comment-159841
 ] 

SCM/JIRA link daemon commented on JENKINS-1152:
---

Code changed in jenkins
User: Christoph Kutzinski
Path:
 core/pom.xml
http://jenkins-ci.org/commit/jenkins/4afaf0bbc2c9f7298c45dc527269fb5c81cc710d
Log:
  Update JavaMail dependency to 1.4.4. Should fix JENKINS-1152 and JENKINS-3983






 Mail server rejecting emails from hudson
 

 Key: JENKINS-1152
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1152
 Project: Jenkins
  Issue Type: Bug
  Components: mail
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: typerlc

 When sending emails from hudson, my mail server (postfix, but I'm sure others
 will behave similarly too) rejects the message because the smtp HELO message
 isn't being sent.
 This is because the system property mail.smtp.localhost hasn't been set before
 sending the email.  This is described in the javadocs for com.sun.mail.smtp.
 See also: 
 http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508.
 The solution is to add some code in hudson.tasks.Mailer.createSession() like:
   props.put(mail.smtp.localhost, localServerName);
 I guess some code to pull the localServerName out of config would be needed 
 to.
 In theory, a work around might be setting a system property when running 
 hudson,
 but I've not been able to make this work yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-3983) SMTP authentication not working


[ 
https://issues.jenkins-ci.org/browse/JENKINS-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159842#comment-159842
 ] 

SCM/JIRA link daemon commented on JENKINS-3983:
---

Code changed in jenkins
User: Christoph Kutzinski
Path:
 core/pom.xml
http://jenkins-ci.org/commit/jenkins/4afaf0bbc2c9f7298c45dc527269fb5c81cc710d
Log:
  Update JavaMail dependency to 1.4.4. Should fix JENKINS-1152 and JENKINS-3983






 SMTP authentication not working
 ---

 Key: JENKINS-3983
 URL: https://issues.jenkins-ci.org/browse/JENKINS-3983
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Platform: PC, OS: All
Reporter: marcb
 Attachments: stacktrace.txt


 I've tried to use my Exchange 2007 server as an SMTP server for Hudson, which 
 requires SMTP authentication. I configured the standard authentication 
 settings 
 which have been confirmed to work on Outlook, Outlook Express as well as our 
 office printer (which can sending scans by email). When sending a test email, 
 or 
 having emails sent after a build, I get the following:
 com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not 
 authenticated
 See attachment for full stack trace. 
 It would appear the problem is related to the way JavaMail is called in 
 Hudson. 
 The following FAQ entry describes the problem:
 http://java.sun.com/products/javamail/FAQ.html#smtpauth
 I checked hudson.tasks.Mailer in core/src/main/java/hudson/tasks and it seems 
 indeed that JavaMail is being called using Transport.send(msg) instead of the 
 method suggested in the FAQ above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1152) Mail server rejecting emails from hudson


[ 
https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159843#comment-159843
 ] 

SCM/JIRA link daemon commented on JENKINS-1152:
---

Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/c4dd892ea3067be942d4a89778029ed1522512ff
Log:
  Changelog for JENKINS-1152 and JENKINS-3983






 Mail server rejecting emails from hudson
 

 Key: JENKINS-1152
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1152
 Project: Jenkins
  Issue Type: Bug
  Components: mail
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: typerlc

 When sending emails from hudson, my mail server (postfix, but I'm sure others
 will behave similarly too) rejects the message because the smtp HELO message
 isn't being sent.
 This is because the system property mail.smtp.localhost hasn't been set before
 sending the email.  This is described in the javadocs for com.sun.mail.smtp.
 See also: 
 http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508.
 The solution is to add some code in hudson.tasks.Mailer.createSession() like:
   props.put(mail.smtp.localhost, localServerName);
 I guess some code to pull the localServerName out of config would be needed 
 to.
 In theory, a work around might be setting a system property when running 
 hudson,
 but I've not been able to make this work yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-3983) SMTP authentication not working


[ 
https://issues.jenkins-ci.org/browse/JENKINS-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159844#comment-159844
 ] 

SCM/JIRA link daemon commented on JENKINS-3983:
---

Code changed in jenkins
User: Christoph Kutzinski
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/c4dd892ea3067be942d4a89778029ed1522512ff
Log:
  Changelog for JENKINS-1152 and JENKINS-3983






 SMTP authentication not working
 ---

 Key: JENKINS-3983
 URL: https://issues.jenkins-ci.org/browse/JENKINS-3983
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Platform: PC, OS: All
Reporter: marcb
 Attachments: stacktrace.txt


 I've tried to use my Exchange 2007 server as an SMTP server for Hudson, which 
 requires SMTP authentication. I configured the standard authentication 
 settings 
 which have been confirmed to work on Outlook, Outlook Express as well as our 
 office printer (which can sending scans by email). When sending a test email, 
 or 
 having emails sent after a build, I get the following:
 com.sun.mail.smtp.SMTPSendFailedException: 530 5.7.1 Client was not 
 authenticated
 See attachment for full stack trace. 
 It would appear the problem is related to the way JavaMail is called in 
 Hudson. 
 The following FAQ entry describes the problem:
 http://java.sun.com/products/javamail/FAQ.html#smtpauth
 I checked hudson.tasks.Mailer in core/src/main/java/hudson/tasks and it seems 
 indeed that JavaMail is being called using Transport.send(msg) instead of the 
 method suggested in the FAQ above.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1152) Mail server rejecting emails from hudson


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kutzi reassigned JENKINS-1152:
--

Assignee: kutzi

 Mail server rejecting emails from hudson
 

 Key: JENKINS-1152
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1152
 Project: Jenkins
  Issue Type: Bug
  Components: mail
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: typerlc
Assignee: kutzi

 When sending emails from hudson, my mail server (postfix, but I'm sure others
 will behave similarly too) rejects the message because the smtp HELO message
 isn't being sent.
 This is because the system property mail.smtp.localhost hasn't been set before
 sending the email.  This is described in the javadocs for com.sun.mail.smtp.
 See also: 
 http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508.
 The solution is to add some code in hudson.tasks.Mailer.createSession() like:
   props.put(mail.smtp.localhost, localServerName);
 I guess some code to pull the localServerName out of config would be needed 
 to.
 In theory, a work around might be setting a system property when running 
 hudson,
 but I've not been able to make this work yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-1152) Mail server rejecting emails from hudson


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-1152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

kutzi resolved JENKINS-1152.


Resolution: Fixed

 Mail server rejecting emails from hudson
 

 Key: JENKINS-1152
 URL: https://issues.jenkins-ci.org/browse/JENKINS-1152
 Project: Jenkins
  Issue Type: Bug
  Components: mail
Affects Versions: current
 Environment: Platform: All, OS: All
Reporter: typerlc
Assignee: kutzi

 When sending emails from hudson, my mail server (postfix, but I'm sure others
 will behave similarly too) rejects the message because the smtp HELO message
 isn't being sent.
 This is because the system property mail.smtp.localhost hasn't been set before
 sending the email.  This is described in the javadocs for com.sun.mail.smtp.
 See also: 
 http://forum.java.sun.com/thread.jspa?threadID=482673messageID=2252508.
 The solution is to add some code in hudson.tasks.Mailer.createSession() like:
   props.put(mail.smtp.localhost, localServerName);
 I guess some code to pull the localServerName out of config would be needed 
 to.
 In theory, a work around might be setting a system property when running 
 hudson,
 but I've not been able to make this work yet.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page

2012-03-05 Thread reynald.bo...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159845#comment-159845
 ] 

Reynald Borer commented on JENKINS-12787:
-

Same happens here with Jenkins 1.452 and FF10, pretty annoying.

 LOADING overlay does not go away on the Configure System page
 -

 Key: JENKINS-12787
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
 Project: Jenkins
  Issue Type: Bug
  Components: gui
Affects Versions: current
 Environment: Jenkins 
Reporter: Joshua Davis
  Labels: gui, jenkins

 After navigating to Manage-Configure System, the LOADING overlay never goes 
 away.  It is impossible to save any configuration changes.
 EXPECTED:
 * You can save your global configuration.
 Here is the stack trace from Chrome's JS console:
 {code}
 Uncaught TypeError: Object #Object has no method 'findMatchingInput'
 (anonymous function)
 e.targetUrl hudson-behavior.js:338
 registerValidator hudson-behavior.js:343
  apply behavior.js:73
 (anonymous function) behavior.js:79
 Behaviour.applySubtree behavior.js:68
 Behaviour.applybehavior.js:54
 (anonymous function)behavior.js:49
 window.onload
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12787) LOADING overlay does not go away on the Configure System page

2012-03-05 Thread reynald.bo...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159847#comment-159847
 ] 

Reynald Borer commented on JENKINS-12787:
-

This seems related to the JIRA Plugin. If I disable it then I can access again 
the configuration page.

 LOADING overlay does not go away on the Configure System page
 -

 Key: JENKINS-12787
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12787
 Project: Jenkins
  Issue Type: Bug
  Components: gui
Affects Versions: current
 Environment: Jenkins 
Reporter: Joshua Davis
  Labels: gui, jenkins

 After navigating to Manage-Configure System, the LOADING overlay never goes 
 away.  It is impossible to save any configuration changes.
 EXPECTED:
 * You can save your global configuration.
 Here is the stack trace from Chrome's JS console:
 {code}
 Uncaught TypeError: Object #Object has no method 'findMatchingInput'
 (anonymous function)
 e.targetUrl hudson-behavior.js:338
 registerValidator hudson-behavior.js:343
  apply behavior.js:73
 (anonymous function) behavior.js:79
 Behaviour.applySubtree behavior.js:68
 Behaviour.applybehavior.js:54
 (anonymous function)behavior.js:49
 window.onload
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

2012-03-05 Thread brunodepau...@yahoo.com.br (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159848#comment-159848
]

Bruno P. Kinoshita commented on JENKINS-12810:
--

Your information has been added to the project Jaroslavas! Thank you for your
support too :-)

https://github.com/jenkinsci/testlink-plugin/blob/master/pom.xml#L110

The ID wasn't necessary, sorry.

Is RC version available for testing?

It is! I attached the latest release candidate here. If no errors are found,
we'll release a new version this week.

Thanks again!

JUnit test results are getting wrongly attached to all the test cases
-

Key: JENKINS-12810
URL: https://issues.jenkins-ci.org/browse/JENKINS-12810
Project: Jenkins
Issue Type: Bug
Components: testlink
Affects Versions: current
Reporter: Vignesh Senapathy
Assignee: Bruno P. Kinoshita
Fix For: current

Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
testlink-3.1-alpha2.hpi

Hi,
I am using the Testlink Jenkins plugin and when i run my jobs in Jenkins the
Junit Test results are getting generated. This in turn calls the Testlink xml
rpc and attaches the results to the test case, but the test results are
attached wrongly. The 1st test case has 6 results, the next has 5 and so on
and the last one has 1 test result attached to it. I dont know if it is bug
which is causing this. Please let me know what seems to be the problems. Also
the execution flags are correctly rendered in this. which ever test case
fails is marked as failed and which passed is marked as passed.
Also I have one custom field which maps to the test suite name and test
classname.

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

2012-03-05 Thread brunodepau...@yahoo.com.br (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bruno P. Kinoshita updated JENKINS-12810:
-

Attachment: testlink-3.1-RC2.hpi

release candidate 2

JUnit test results are getting wrongly attached to all the test cases
-

Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
testlink-3.1-alpha2.hpi, testlink-3.1-RC2.hpi

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

2012-03-05 Thread vigneshsenapa...@gmail.com (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159850#comment-159850
]

Vignesh Senapathy commented on JENKINS-12810:
-

Hey Bruno,

My info:

name: Vignesh Senapathy
e-mail: vignesh.senapa...@gmail.com
GMT time zone: +5

JUnit test results are getting wrongly attached to all the test cases
-

Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
testlink-3.1-alpha2.hpi, testlink-3.1-RC2.hpi

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

2012-03-05 Thread vigneshsenapa...@gmail.com (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159851#comment-159851
]

Vignesh Senapathy commented on JENKINS-12810:
-

Sorry my email is vigneshsenapa...@gmail.com

JUnit test results are getting wrongly attached to all the test cases
-

Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
testlink-3.1-alpha2.hpi, testlink-3.1-RC2.hpi

[JIRA] (JENKINS-9693) maven.build.timestamp.format is not obeyed in maven builds

2012-03-05 Thread allenserve...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-9693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159852#comment-159852
 ] 

allenservedio commented on JENKINS-9693:


I wound up creating this timestamp via the Codehaus Build Number plugin 
(http://mojo.codehaus.org/buildnumber-maven-plugin/create-timestamp-mojo.html). 
Here is the Maven config that I used (in my plugin dependency management):

{code:xml}
  plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
version1.0/version
executions
  execution
phasegenerate-resources/phase
goals
  goalcreate-timestamp/goal
/goals
  /execution
/executions
configuration
  timestampFormatMMddHHmmssSSS/timestampFormat
  
timestampPropertyNamereleaseTimestamp/timestampPropertyName
/configuration
  /plugin
{code}

Am I correct that the reason this was not fixed already is that the point in 
the maven lifecycle where the statically formatted timestamp is created, the 
pom file(s) have not been evaluated. As such, it does not have access to this 
property (maven.build.timestamp.format) and so does not know that the user has 
defined it? If that is true, is there something else that can be used in 
Jenkin's Maven integration that can get access to this property and use it 
correctly?

Thanks!
Allen

 maven.build.timestamp.format is not obeyed in maven builds
 --

 Key: JENKINS-9693
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9693
 Project: Jenkins
  Issue Type: Bug
  Components: maven2
Reporter: Dan C
Priority: Minor

 Since Maven 2.1 it is possible to control the format of the 
 {{maven.build.timestamp}} property [by setting the 
 {{maven.build.timestamp.format}} 
 property|http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Special_Variables].
  This works correctly with mvn version 3.0.3:
 {code:xml|title=pom.xml}
 project xmlns=http://maven.apache.org/POM/4.0.0;
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/maven-v4_0_0.xsd;
 modelVersion4.0.0/modelVersion
 groupIdinvalid.example.test/groupId
 artifactIdtest/artifactId
 version1.0-SNAPSHOT/version
 packagingjar/packaging
 properties
 
 maven.build.timestamp.format-MM-dd'T'HH:mm:ssZ/maven.build.timestamp.format
 build.timestamp${maven.build.timestamp}/build.timestamp
 /properties
 build
 resources
 resource
 directorysrc/main/filtered-resources/directory
 filteringtrue/filtering
 /resource
 /resources
 /build
 /project
 {code}
 {code:title=src/main/filtered-resources/test.properties}
 Build-Timestamp: ${build.timestamp}
 {code}
 {code:title=target/classes/test.properties}
 Build-Timestamp: 2011-05-15T18:56:20+1000
 {code}
 but in Jenkins 1.411 the default timestamp format is used instead:
 {code:title=target/classes/test.properties}
 Build-Timestamp: 20110515-1857
 {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12810) JUnit test results are getting wrongly attached to all the test cases

2012-03-05 Thread brunodepau...@yahoo.com.br (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-12810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159853#comment-159853
]

Bruno P. Kinoshita commented on JENKINS-12810:
--

Hi Vignesh! Added as well
https://github.com/jenkinsci/testlink-plugin/blob/master/pom.xml#L115

Thank you!

JUnit test results are getting wrongly attached to all the test cases
-

Attachments: 1.jpg, 2.jpg, 3.jpg, last_tc.png, schema.jpg,
screenshot20120228152415.jpg, screenshot20120228152511.jpg, tc1.png, tc2.png,
testlink-3.1-alpha2.hpi, testlink-3.1-RC2.hpi

[JIRA] (JENKINS-12981) Notification, when workspace checkout failed

2012-03-05 Thread tho...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

thosor updated JENKINS-12981:
-

   Priority: Minor  (was: Major)
Description: 
Hello there,

today we've got two errors, were jenkins was not able to check svn out.
{code}
Started by an SCM change
Building on master
Checking out a fresh workspace because there's no workspace at 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace
Cleaning local Directory .
java.io.IOException: Unable to delete 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base
 - files in dir: 
[/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base/filename.docx.svn-base,
 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base/filename.docx.svn-base]
at hudson.Util.deleteFile(Util.java:265)
at hudson.Util.deleteRecursive(Util.java:316)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at 
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:71)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
at hudson.FilePath.act(FilePath.java:758)
at hudson.FilePath.act(FilePath.java:740)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1193)
at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:565)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:453)
at hudson.model.Run.run(Run.java:1376)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:175)
Retrying after 10 seconds
Checking out a fresh workspace because there's no workspace at 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace
Cleaning local Directory .
java.io.IOException: Unable to delete 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base
 - files in dir: 
[/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base/filename.docx.svn-base,
 
/opt/srv/jenkins-workdir/jobs/PROJECT/workspace/./project/src/prod/doc/.svn/prop-base/filename.docx.svn-base]
at hudson.Util.deleteFile(Util.java:265)
at hudson.Util.deleteRecursive(Util.java:316)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at hudson.Util.deleteRecursive(Util.java:307)
at hudson.Util.deleteContentsRecursive(Util.java:227)
at 
hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:71)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
at 
hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121)
at 
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:788)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:769)

[JIRA] (JENKINS-12973) Doxygen Plugin shows 404 error. Points to {OUTPUT_DIRECTORY} instead of {OUTPUT_DIRECTORY}/html

2012-03-05 Thread gb...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on JENKINS-12973 started by gbois.

 Doxygen Plugin shows 404 error. Points to {OUTPUT_DIRECTORY} instead of 
 {OUTPUT_DIRECTORY}/html
 ---

 Key: JENKINS-12973
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12973
 Project: Jenkins
  Issue Type: Bug
  Components: doxygen
Affects Versions: current
Reporter: Roland Schulz
Assignee: gbois

 The doxygen plugin parses the doxyfile correctly and also publishes 
 correctly. But when one tries to view the doxygen Jenkins reports a 404 
 error. One has to append /html to the URL to make it work. The plugin 
 detected the output directory correctly from the OUTPUT_DIRECTOR option but 
 didn't append the /html. My Doxyfile has HTML_OUTPUT not set and thus doxygen 
 takes the default html.
  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12973) Doxygen Plugin shows 404 error. Points to {OUTPUT_DIRECTORY} instead of {OUTPUT_DIRECTORY}/html

2012-03-05 Thread gb...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159854#comment-159854
 ] 

gbois commented on JENKINS-12973:
-

Could you attach your Doxyfile?

 Doxygen Plugin shows 404 error. Points to {OUTPUT_DIRECTORY} instead of 
 {OUTPUT_DIRECTORY}/html
 ---

 Key: JENKINS-12973
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12973
 Project: Jenkins
  Issue Type: Bug
  Components: doxygen
Affects Versions: current
Reporter: Roland Schulz
Assignee: gbois

 The doxygen plugin parses the doxyfile correctly and also publishes 
 correctly. But when one tries to view the doxygen Jenkins reports a 404 
 error. One has to append /html to the URL to make it work. The plugin 
 detected the output directory correctly from the OUTPUT_DIRECTOR option but 
 didn't append the /html. My Doxyfile has HTML_OUTPUT not set and thus doxygen 
 takes the default html.
  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12964) Rundeck plugin returns no artifacts

2012-03-05 Thread rack...@hotmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159855#comment-159855
 ] 

Pierre Larsson commented on JENKINS-12964:
--

The problem has been resolved. We were storing our artifacts in a nexus 
repository. Enabling the project to store the artifacts locally has meant they 
are now showing up as options.

Perhaps there could be an added feature to select artifacts from an external 
repository?

 Rundeck plugin returns no artifacts
 ---

 Key: JENKINS-12964
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12964
 Project: Jenkins
  Issue Type: Bug
  Components: rundeck
 Environment: software
Reporter: Pierre Larsson
Assignee: Vincent Behar

 I'm trying to use rundeck to promote builds from Jenkins.
 I'm using Jenkins version 1.452 and rundeck plugin version 2.11
 To make the promotion seamless I'm trying to use the artifact variables to 
 grab the name of the last artifact built but I get no options back.
 I've tried both via the build url:
 {code}
 http://JENKINS:8080/plugin/rundeck/options/artifact?project=jenkins project 
 name
 {code}
 And by passing the options from jenkins:
 warname=$ARTIFACT_NAME{.*\.war}
 The url returns an empty array: 
 {code}[]{code}
 Passing the options returns:
 {code}
 %7B.*.war%7D
 {code}
 Let me know if there is any extra information required.
 Thanks,
 Pierre

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12964) Rundeck plugin returns no artifacts

2012-03-05 Thread v.be...@free.fr (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vincent Behar closed JENKINS-12964.
---

Resolution: Not A Defect

 Rundeck plugin returns no artifacts
 ---

 Key: JENKINS-12964
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12964
 Project: Jenkins
  Issue Type: Bug
  Components: rundeck
 Environment: software
Reporter: Pierre Larsson
Assignee: Vincent Behar

 I'm trying to use rundeck to promote builds from Jenkins.
 I'm using Jenkins version 1.452 and rundeck plugin version 2.11
 To make the promotion seamless I'm trying to use the artifact variables to 
 grab the name of the last artifact built but I get no options back.
 I've tried both via the build url:
 {code}
 http://JENKINS:8080/plugin/rundeck/options/artifact?project=jenkins project 
 name
 {code}
 And by passing the options from jenkins:
 warname=$ARTIFACT_NAME{.*\.war}
 The url returns an empty array: 
 {code}[]{code}
 Passing the options returns:
 {code}
 %7B.*.war%7D
 {code}
 Let me know if there is any extra information required.
 Thanks,
 Pierre

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11938) Jenkins loses builds when restarted

2012-03-05 Thread sk...@gagnavarslan.is (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159858#comment-159858
]

Skuli Arnlaugsson commented on JENKINS-11938:
-

Same problem here, running Jenkins ver. 1.452 Not using the SetEnv and
EnvInject plugins.

Jenkins loses builds when restarted
---

Key: JENKINS-11938
URL: https://issues.jenkins-ci.org/browse/JENKINS-11938
Project: Jenkins
Issue Type: Bug
Components: other, versionnumber
Affects Versions: current
Environment: tomcat 7.0.22
windows server 2008 r2
Reporter: Ben Dean

Jenkins version 1.437
If I stop the Apache Tomcat windows service, a bunch of my builds disappear
from the history of the jobs. The missing builds are still on disk in the
build folder, it just doesn't find them when making the history list.
The jobs that lose history use the version number plugin and I had recently
changed the version format from 4.3.${BUILDS_ALL_TIME} to
4.4.${BUILDS_ALL_TIME}. The builds that disappear are all those after I
changed this format. Also affects jobs that are downstream from those with
version number changes.
I could not find any Component related to the build history for a job. If
someone knows what that should be feel free to change this. Also, sorry if
there's not enough (or to much) information, this is the first Jenkins bug I
have filed.

[JIRA] (JENKINS-8733) Downstream build view does not see Join Trigger

2012-03-05 Thread fleas...@gmx.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-8733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159859#comment-159859
 ] 

Florian Loikasek edited comment on JENKINS-8733 at 3/5/12 3:20 PM:
---

The description in 8733 is better than in 6365 and the screenshot is explaining 
the problem even more. Also, a reason for duplication may be that 6356 is 
stated as minor problem.

  was (Author: fleasoft):
The description in 8733 is better than in 6365 and the screenshot is 
explaining the problem even more.
  
 Downstream build view does not see Join Trigger
 ---

 Key: JENKINS-8733
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8733
 Project: Jenkins
  Issue Type: Bug
  Components: downstream-buildview, join
Affects Versions: current
 Environment: Hudson v1.377, Downstream build view v1.5, Join plugin 
 v1.9
Reporter: robsimon
Assignee: shinodkm
 Attachments: downstream_join.png


 In case you use the join plugin then the Downstream build view will not show 
 the join. Instead it handles everything below the join as separate branches.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12982) Run conditions should be passed Launcher object

2012-03-05 Thread cjo9...@java.net (JIRA)

cjo9900 created JENKINS-12982:
-

 Summary: Run conditions should be passed Launcher object
 Key: JENKINS-12982
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12982
 Project: Jenkins
  Issue Type: Improvement
  Components: run-condition
Reporter: cjo9900
Assignee: bap


Run conditions should be passed Launcher object so that the conditions may be 
allowed to run scripts within the build, e.g call a Shell or groovy script.

Current implementations are 

public abstract boolean runPrebuild(final AbstractBuild?, ? build, final 
BuildListener listener) throws Exception;

public abstract boolean runPerform(final AbstractBuild?, ? build, final 
BuildListener listener) throws Exception;

These should be extended to 
(final AbstractBuild?, ? build, final BuildListener listener, final Launcher 
launcher) 



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12983) Redundat syncs when using matrix jobs

2012-03-05 Thread thomasmfie...@gmail.com (JIRA)

Thomas Fields created JENKINS-12983:
---

 Summary: Redundat syncs when using matrix jobs
 Key: JENKINS-12983
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12983
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
Affects Versions: current
 Environment: Jenkins 1.452
Reporter: Thomas Fields


Hi,

I originally posted this on the mailing list but the lack of replies forced me 
to create this issue. See the post here: 
https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/s1HyARUbfbs

Is there any way the Perforce plugin can be changed so that it doesn't do the 
redundant sync? It can be a real performance killer if the view you're syncing 
to is particularly large.


Regards,
Tom.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12853) The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159862#comment-159862
 ] 

SCM/JIRA link daemon commented on JENKINS-12853:


Code changed in jenkins
User: Ulli Hafner
Path:
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsPlugin.java
 plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java
 plugin/src/test/java/hudson/plugins/findbugs/FindBugsPluginTest.java
http://jenkins-ci.org/commit/findbugs-plugin/2d80d625949524a81794ae0b4249872f94feb556
Log:
  [FIXED JENKINS-12853] Always use findbugsXml.xml when
findbugs-maven-plugin version = 2.4.0 is used.






 The Findbugs XML file is not searched correctly with latest Maven Findbugs 
 plugin
 -

 Key: JENKINS-12853
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12853
 Project: Jenkins
  Issue Type: Bug
  Components: findbugs
Affects Versions: current
 Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, 
 Jenkins Findbugs Plugin 4.33
Reporter: cristalp
Assignee: Ulli Hafner

 When using the Maven2/3 job type, the Findbugs XML file isn't found. However, 
 it is found under the following circumstances:
 * Using a free-style build
 * Adding {{findbugsXmlOutputtrue/findbugsXmlOutput}} to the Maven 
 Findbugs configuration. But this parameter [has been 
 deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html].
  From the Maven site, it's not very clear what its behavior is: {{This has 
 been deprecated and is on by default. Default value is: false.}}
 Even though the generated files are the same, the plugin seems to search for 
 the XML files in a different way.
 Here's the output when the XML files are not found:
 {code}
 [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
 [INFO] Fork Value is true
  [java] Warnings generated: 4
 [INFO] Done FindBugs Analysis
 [FINDBUGS] Parsing 1 files in 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target
 [FINDBUGS] Successfully parsed file 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module 
 Implementation of Base Services with 0 warnings.
 {code}
 Here's the output when the XML files are found:
 {code}
 [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
  [java] Warnings generated: 4
 [INFO] Done FindBugs Analysis
 [FINDBUGS] Parsing 1 files in 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target
 [FINDBUGS] Successfully parsed file 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of 
 module Implementation of Base Services with 4 warnings.
 {code}
 Also see the [discussion on the mailing 
 list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12984) warnings (et.al) per project - add checkbox to filter out projects with issue total of 0? - or to show only the top N based on sort selection?

2012-03-05 Thread monc...@raytheon.com (JIRA)

Greg Moncreaff created JENKINS-12984:


 Summary: warnings (et.al) per project - add checkbox to filter out 
projects with issue total of 0? - or to show only the top N based on sort 
selection?
 Key: JENKINS-12984
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12984
 Project: Jenkins
  Issue Type: Improvement
  Components: warnings
Affects Versions: current
Reporter: Greg Moncreaff
Assignee: Ulli Hafner


CONOPS - reduce information overload by allowing to focus on a subset when 
dashboard view contains many jobs

Options
1. just filter out the zero issue projects
  = most likely they are fine and need no extra attention?  possibly, but less 
likely? that there publishers are not working for some reason
2. put a cap on number of rows, so you can focus on the top (or bottom) N (3, 
10) whatever based on the sort bring projects into/out of the the limited row 
set?

for option 2, (and in general) you would want the sorts to be sticky, so 
whatever sort showed the current interesting job subset would remain until 
actively changed.

either or both options could be done independent of each other



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12853) The Findbugs XML file is not searched correctly with latest Maven Findbugs plugin

2012-03-05 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159863#comment-159863
 ] 

dogfood commented on JENKINS-12853:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_findbugs #388|http://ci.jenkins-ci.org/job/plugins_findbugs/388/]
 [FIXED JENKINS-12853] Always use findbugsXml.xml when (Revision 
2d80d625949524a81794ae0b4249872f94feb556)

 Result = SUCCESS
Ulli Hafner : 
Files : 
* plugin/src/test/java/hudson/plugins/findbugs/FindBugsPluginTest.java
* plugin/src/main/java/hudson/plugins/findbugs/FindBugsReporter.java
* plugin/src/main/java/hudson/plugins/findbugs/FindBugsPlugin.java


 The Findbugs XML file is not searched correctly with latest Maven Findbugs 
 plugin
 -

 Key: JENKINS-12853
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12853
 Project: Jenkins
  Issue Type: Bug
  Components: findbugs
Affects Versions: current
 Environment: Jenkins 1.451, Maven 3.0.4, Maven Findbugs Plugin 2.4.0, 
 Jenkins Findbugs Plugin 4.33
Reporter: cristalp
Assignee: Ulli Hafner

 When using the Maven2/3 job type, the Findbugs XML file isn't found. However, 
 it is found under the following circumstances:
 * Using a free-style build
 * Adding {{findbugsXmlOutputtrue/findbugsXmlOutput}} to the Maven 
 Findbugs configuration. But this parameter [has been 
 deprecated|http://mojo.codehaus.org/findbugs-maven-plugin-2.4.0/findbugs-mojo.html].
  From the Maven site, it's not very clear what its behavior is: {{This has 
 been deprecated and is on by default. Default value is: false.}}
 Even though the generated files are the same, the plugin seems to search for 
 the XML files in a different way.
 Here's the output when the XML files are not found:
 {code}
 [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
 [INFO] Fork Value is true
  [java] Warnings generated: 4
 [INFO] Done FindBugs Analysis
 [FINDBUGS] Parsing 1 files in 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target
 [FINDBUGS] Successfully parsed file 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugs.xml of module 
 Implementation of Base Services with 0 warnings.
 {code}
 Here's the output when the XML files are found:
 {code}
 [INFO] --- findbugs-maven-plugin:2.4.0:findbugs (default) @ base-impl ---
  [java] Warnings generated: 4
 [INFO] Done FindBugs Analysis
 [FINDBUGS] Parsing 1 files in 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target
 [FINDBUGS] Successfully parsed file 
 /ige/jenkins/work/jobs/base/workspace/base-impl/target/findbugsXml.xml of 
 module Implementation of Base Services with 4 warnings.
 {code}
 Also see the [discussion on the mailing 
 list|http://groups.google.com/group/jenkinsci-users/browse_thread/thread/0d4d5d006b93e4d4#].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12984) warnings (et.al) per project - add checkbox to filter out projects with issue total of 0? - or to show only the top N based on sort selection?


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159864#comment-159864
 ] 

Ulli Hafner commented on JENKINS-12984:
---

Can you please provide a fake screenshot or some kind of sketch to make more 
clear what you would like to have?

 warnings (et.al) per project - add checkbox to filter out projects with issue 
 total of 0? - or to show only the top N based on sort selection?
 --

 Key: JENKINS-12984
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12984
 Project: Jenkins
  Issue Type: Improvement
  Components: warnings
Affects Versions: current
Reporter: Greg Moncreaff
Assignee: Ulli Hafner

 CONOPS - reduce information overload by allowing to focus on a subset when 
 dashboard view contains many jobs
 Options
 1. just filter out the zero issue projects
   = most likely they are fine and need no extra attention?  possibly, but 
 less likely? that there publishers are not working for some reason
 2. put a cap on number of rows, so you can focus on the top (or bottom) N (3, 
 10) whatever based on the sort bring projects into/out of the the limited row 
 set?
 for option 2, (and in general) you would want the sorts to be sticky, so 
 whatever sort showed the current interesting job subset would remain until 
 actively changed.
 either or both options could be done independent of each other

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12984) warnings (et.al) per project - add checkbox to filter out projects with issue total of 0? - or to show only the top N based on sort selection?

2012-03-05 Thread monc...@raytheon.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159866#comment-159866
 ] 

Greg Moncreaff commented on JENKINS-12984:
--

I attached an image to the issue.

 warnings (et.al) per project - add checkbox to filter out projects with issue 
 total of 0? - or to show only the top N based on sort selection?
 --

 Key: JENKINS-12984
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12984
 Project: Jenkins
  Issue Type: Improvement
  Components: warnings
Affects Versions: current
Reporter: Greg Moncreaff
Assignee: Ulli Hafner
 Attachments: jenkins-table_per_project-information_reduction.bmp


 CONOPS - reduce information overload by allowing to focus on a subset when 
 dashboard view contains many jobs
 Options
 1. just filter out the zero issue projects
   = most likely they are fine and need no extra attention?  possibly, but 
 less likely? that there publishers are not working for some reason
 2. put a cap on number of rows, so you can focus on the top (or bottom) N (3, 
 10) whatever based on the sort bring projects into/out of the the limited row 
 set?
 for option 2, (and in general) you would want the sorts to be sticky, so 
 whatever sort showed the current interesting job subset would remain until 
 actively changed.
 either or both options could be done independent of each other

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-8883) Build fails because of slave error

2012-03-05 Thread eb...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-8883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159869#comment-159869
 ] 

ebann commented on JENKINS-8883:


Yes it looks like the same issue.

Anyway I'm not having this problem anymore.
(But I have changed a LOT of things in my Hudson configuration/slaves since 
that, so it might still exists)

 Build fails because of slave error
 --

 Key: JENKINS-8883
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8883
 Project: Jenkins
  Issue Type: Bug
  Components: ssh-slaves
Affects Versions: current
 Environment: Jenkins ver. 1.398
 Slave is a RedHat 5.2
 Slave workdir is /tmp/...
 ssh-slave 0.14
Reporter: ebann
Assignee: Kohsuke Kawaguchi

 Some builds randomly fail with this message:
 FATAL: L'exécution de la commande a échoué.
 hudson.util.IOException2: Failed to join the process
   at hudson.Proc$RemoteProc.join(Proc.java:359)
   at hudson.Launcher$ProcStarter.join(Launcher.java:280)
   at hudson.tasks.Ant.perform(Ant.java:216)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:624)
   at hudson.model.Build$RunnerImpl.build(Build.java:176)
   at hudson.model.Build$RunnerImpl.doRun(Build.java:138)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:420)
   at hudson.model.Run.run(Run.java:1362)
   at hudson.matrix.MatrixRun.run(MatrixRun.java:137)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:145)
 Caused by: java.util.concurrent.ExecutionException: 
 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
 termination of the channel
   at hudson.remoting.Request$1.get(Request.java:218)
   at hudson.remoting.Request$1.get(Request.java:172)
   at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
   at hudson.Proc$RemoteProc.join(Proc.java:351)
   ... 11 more
 Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: 
 Unexpected termination of the channel
   at hudson.remoting.Request.abort(Request.java:257)
   at hudson.remoting.Channel.terminate(Channel.java:680)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:971)
 Caused by: java.io.IOException: Unexpected termination of the channel
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:953)
 Caused by: java.io.EOFException
   at 
 java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
   at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
   at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:947)
 Here is the slave log:
 Slave successfully connected and online
 ERROR: Connection terminated
 java.io.IOException: Unexpected termination of the channel
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:953)
 Caused by: java.io.EOFException
   at 
 java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
   at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
   at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:947)
 ERROR: [02/25/11 09:59:47] [SSH] Error deleting file.
 java.io.IOException: Sorry, this connection is closed.
   at 
 com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:637)
   at 
 com.trilead.ssh2.channel.ChannelManager.openSessionChannel(ChannelManager.java:582)
   at com.trilead.ssh2.Session.init(Session.java:40)
   at com.trilead.ssh2.Connection.openSession(Connection.java:1047)
   at com.trilead.ssh2.Connection.exec(Connection.java:1434)
   at 
 hudson.plugins.sshslaves.SSHLauncher.afterDisconnect(SSHLauncher.java:597)
   at hudson.slaves.SlaveComputer$2.onClosed(SlaveComputer.java:320)
   at hudson.remoting.Channel.terminate(Channel.java:695)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:971)
 Caused by: java.net.SocketException: Connection reset
   at java.net.SocketInputStream.read(SocketInputStream.java:168)
   at 
 com.trilead.ssh2.crypto.cipher.CipherInputStream.fill_buffer(CipherInputStream.java:41)
   at 
 com.trilead.ssh2.crypto.cipher.CipherInputStream.internal_read(CipherInputStream.java:52)
   at 
 com.trilead.ssh2.crypto.cipher.CipherInputStream.getBlock(CipherInputStream.java:79)
   at 
 com.trilead.ssh2.crypto.cipher.CipherInputStream.read(CipherInputStream.java:108)
   at

[JIRA] (JENKINS-5753) Standalone install does not work with Apache + mod_proxy_ajp + SSL

2012-03-05 Thread ru...@yahoo.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-5753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159871#comment-159871
 ] 

Curtis Ruck commented on JENKINS-5753:
--

Still having this issue with httpd 2.2.15, w/ 1.452.  We have been using the 
Jenkins RPM so its easier to stay current, any chance of switching winstone out 
with Jetty?

 Standalone install does not work with Apache + mod_proxy_ajp + SSL
 --

 Key: JENKINS-5753
 URL: https://issues.jenkins-ci.org/browse/JENKINS-5753
 Project: Jenkins
  Issue Type: Bug
 Environment: CentOS release 5.4 (Final)
 2.6.18-164.10.1.el5xen (64 bit)
 java version 1.6.0_16
 hudson-1.347-1.1
 httpd-2.2.3-31.el5.centos.2
Reporter: rombert

 I've configured hudson to only use the ajp connector using a command line 
 similar to 
 {noformat}
 /usr/lib/jvm/java-1.6.0/bin/java -Dcom.sun.akuma.Daemon=daemonized 
 -Djava.awt.headless=true -Xmx64m -DHUDSON_HOME=/space/hudson -jar 
 /usr/lib/hudson/hudson.war --logfile=/var/log/hudson/hudson.log --daemon 
 --prefix=hudson --httpPort=-1 --ajp13Port=8109 --debug=5 --handlerCountMax=10 
 --handlerCountMaxIdle=0
 {noformat}
 I'm using the following apache configuration file
 {noformat}
 ProxyRequests Off
 ProxyPreserveHost On
 Proxy *
 Order deny,allow
 Allow from all
 /Proxy
 ProxyPass /hudson ajp://localhost:8109/hudson retry=1
 ProxyPassReverse /hudson ajp://localhost:8109/hudson
 {noformat}
 When accessing https://host/hudson , I get a 503 error page from Apache. The 
 apache logs contain:
 {noformat}
 [Wed Feb 24 23:58:04 2010] [error] ajp_read_header: ajp_ilink_receive failed
 [Wed Feb 24 23:58:04 2010] [error] (120006)APR does not understand this error 
 code: proxy: read response failed from (null) (localhost)
 {noformat}
 while the winstone logs contain:
 {noformat}
 [Winstone 2010/02/24 23:58:04] - Error within request handler thread
 java.lang.StringIndexOutOfBoundsException: String index out of range: 1065
 at java.lang.String.checkBounds(String.java:401)
 at java.lang.String.init(String.java:442)
 at 
 winstone.ajp13.Ajp13IncomingPacket.readString(Ajp13IncomingPacket.java:275)
 at 
 winstone.ajp13.Ajp13IncomingPacket.parsePacket(Ajp13IncomingPacket.java:189)
 at 
 winstone.ajp13.Ajp13Listener.allocateRequestResponse(Ajp13Listener.java:179)
 at winstone.RequestHandlerThread.run(RequestHandlerThread.java:79)
 at java.lang.Thread.run(Thread.java:619)
 {noformat}
 It's worth mentioning that this was working with Tomcat 6.0.20 , but stopped 
 working when I tried to move over to the standalone install. 
 I've tried various combinations with or without prefix, and the only one 
 which seems to work is ajp without any prefix.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12250) Critical block can not be added into conditional step

2012-03-05 Thread d...@fortysix.ch (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159872#comment-159872
 ] 

domi commented on JENKINS-12250:


I have triggered a build for you, please verify with this SNAPSHOT artifact:
http://ci.jenkins-ci.org/job/plugins_exclusion/org.jenkins-ci.plugins$Exclusion/lastSuccessfulBuild/

...and let me know if it works as expected and then I'll do a release for you...


 Critical block can not be added into conditional step
 -

 Key: JENKINS-12250
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12250
 Project: Jenkins
  Issue Type: Bug
  Components: conditional-buildstep, exclusion
 Environment: Jenkins 1.445
 Jenkins Exclusion Plug-in 0.6
 conditional-buildstep 0.2
Reporter: Oleksandr Popov
Assignee: Anthony Roux
Priority: Critical
 Attachments: critical-block.PNG


 I'm not able to add critical block into conditional step. See screen-shot for 
 details

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159870#comment-159870
 ] 

Ulli Hafner commented on JENKINS-12307:
---

@Curtis: This issue is only about an exception in the log that does not 
influence the plug-in behaviour. 

What exactly is not usable in your case? Maybe this is a different issue...

 Stack Trace when going to main configuration page
 -

 Key: JENKINS-12307
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Reporter: mwebber
Assignee: Ulli Hafner
Priority: Minor

 When I go (in the web interface) to the main Jenkins configuration page, a 
 stack trace is generated on the Jenkins console. No adverse results appear on 
 the web page itself. From the stack track, it looks like it is connected to 
 the warnings plugin.
 This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the 
 time of reporting). I have been noticing this stack track for some time now, 
 including under earlier releases (I'm not sure how recently it started).
 The stack trace:
 {noformat}
 05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
 WARNING: Caught exception evaluating: 
 descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason: 
 java.lang.reflect.InvocationTargetException
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
 at 
 org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
 at 
 org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
 at 
 org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
 at 
 org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
 at 
 org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
 at 
 org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
 at 
 org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
 at 
 hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
 at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
 at 
 org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
 at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
 at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 (snip)
 at 
 winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244)
 at

[JIRA] (JENKINS-9864) Test harness sometime fail on OSX with I/O error in channel Channel to child process

2012-03-05 Thread brianhar...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-9864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159873#comment-159873
 ] 

brianharris commented on JENKINS-9864:
--

Suspected duplicate of JENKINS-6817

 Test harness sometime fail on OSX with I/O error in channel Channel to child 
 process
 --

 Key: JENKINS-9864
 URL: https://issues.jenkins-ci.org/browse/JENKINS-9864
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: OSX Snow Leopard, Apple Java 6, Maven 3.0.3
Reporter: Nicolas De Loof
Priority: Minor

 {noformat}
 [INFO] --- maven-junit-plugin:1.9:test (default) @ jenkins-test-harness ---
 channel started
 Ping failed. Terminating
 3 juin 2011 08:47:38 hudson.remoting.Channel$ReaderThread run
 GRAVE: I/O error in channel Channel to child process port:55010
 java.io.IOException: Unexpected termination of the channel
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:998)
 Caused by: java.io.EOFException
   at 
 java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
   at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
   at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:992)
 java.util.concurrent.ExecutionException: 
 hudson.remoting.RequestAbortedException: 
 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
 termination of the channel
   at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:232)
   at java.util.concurrent.FutureTask.get(FutureTask.java:91)
   at com.sun.maven.junit.TestMojo.executeForked(TestMojo.java:333)
   (...)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
 Caused by: hudson.remoting.RequestAbortedException: 
 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
 termination of the channel
   at hudson.remoting.Request.call(Request.java:137)
   at hudson.remoting.Channel.call(Channel.java:643)
   at 
 com.sun.maven.junit.LocalTestCaseRunner.copyTo(LocalTestCaseRunner.java:170)
   at com.sun.maven.junit.TestMojo$1Port.init(TestMojo.java:263)
   at com.sun.maven.junit.TestMojo$1Task.call(TestMojo.java:285)
   at com.sun.maven.junit.TestMojo$1Task.call(TestMojo.java:272)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:680)
 Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: 
 Unexpected termination of the channel
   at hudson.remoting.Request.abort(Request.java:257)
   at hudson.remoting.Channel.terminate(Channel.java:694)
   at com.sun.maven.junit.TestMojo$1.terminate(TestMojo.java:441)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:1016)
 Caused by: java.io.IOException: Unexpected termination of the channel
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:998)
 Caused by: java.io.EOFException
   at 
 java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2553)
   at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1296)
   at java.io.ObjectInputStream.readObject(ObjectInputStream.java:350)
   at hudson.remoting.Channel$ReaderThread.run(Channel.java:992)
 {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

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

2012-03-05 Thread aba...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

abayer reassigned JENKINS-12966:


Assignee: Nicolas De Loof  (was: abayer)

 gitTool crashes Jenkins startup
 ---

 Key: JENKINS-12966
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12966
 Project: Jenkins
  Issue Type: Bug
  Components: core, git
 Environment: Jenkins 1.452
 Red Hat Enterprise Linux Server release 6.2 (Santiago)
 Linux HOSTNAME 2.6.32-220.4.1.el6.x86_64 #1 SMP Thu Jan 19 14:50:54 EST 
 2012 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Darren Weber
Assignee: Nicolas De Loof
Priority: Blocker
  Labels: git, startup

 org.jvnet.hudson.reactor.ReactorException: java.lang.Error: 
 java.lang.reflect.InvocationTargetException
   at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246)
   at jenkins.InitReactorRunner.run(InitReactorRunner.java:43)
   at jenkins.model.Jenkins.executeReactor(Jenkins.java:824)
   at jenkins.model.Jenkins.init(Jenkins.java:736)
   at hudson.model.Hudson.init(Hudson.java:81)
   at hudson.model.Hudson.init(Hudson.java:77)
   at hudson.WebAppMain$2.run(WebAppMain.java:217)
 Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException
   at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124)
   at 
 hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184)
   at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
   at jenkins.model.Jenkins$5.runTask(Jenkins.java:813)
   at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
   at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
 Caused by: java.lang.reflect.InvocationTargetException
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120)
   ... 8 more
 Caused by: java.lang.NullPointerException
   at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74)
   ... 13 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12427) BuildResultTrigger Plug-in not triggering job

2012-03-05 Thread s...@opencloud.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159879#comment-159879
 ] 

S P commented on JENKINS-12427:
---

Sorry for the delay.
Yes I ran it again with a cron of 1 min, and no change. 
 The jobs don't actually do anything, by that I mean they don't have any code 
they compile or tests they run, they are just empty jobs but they do finish 
with success. Do you think that could be the issue? 
 Are you running the same job configs?
We do have a bunch of other plugins in our jenkins. I wonder if something is 
interfering.



 BuildResultTrigger Plug-in not triggering job 
 --

 Key: JENKINS-12427
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12427
 Project: Jenkins
  Issue Type: Bug
  Components: buildresult-trigger, buildresulttrigger
Affects Versions: current
 Environment: Linux, 2.6.26-amd64
 debian_version  5.0.6
 Jenkins BuildResultTrigger Plug-in 0.4
 Jenkins ver. 1.440
Reporter: S P
Assignee: gbois
 Attachments: TEST-Trigger.config.xml, TEST-TRY.config-2.xml, 
 TEST-TRY.config.xml 


 Jenkins with the buildResultTrigger plugin is unable to trigger a job 
 Two jobs are setup, 
 1. TEST-TRIGGER is a basic job that always passes
 (from jenkins log)
 INFO   | jvm 2| 2012/01/17 10:47:31 | 17/01/2012 10:47:31 AM 
 hudson.model.Run run
 INFO   | jvm 2| 2012/01/17 10:47:31 | INFO: TEST-Trigger #7 main build 
 action completed: SUCCESS
  
 2. TEST-TRY is a basic job configured to Monitor build results of 
 TEST-Trigger. This job is able to run with success when trigger manually
 (from jenkins log)
 INFO   | jvm 2| 2012/01/17 10:48:51 | 17/01/2012 10:48:51 AM 
 hudson.model.Run run
 INFO   | jvm 2| 2012/01/17 10:48:51 | INFO: TEST-TRY #2 main build action 
 completed: SUCCESS
 However, a success result from TEST-TRIGGER does not fire the TEST-TRY job.
 Both jobs configurations are attached

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12307) Stack Trace when going to main configuration page

2012-03-05 Thread mweb...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159880#comment-159880
 ] 

mwebber commented on JENKINS-12307:
---

Although I get the stack trace when I go to the system config page, I can still 
make changes on that page, and they appear to be saved correctly. When you say 
I can't modify anything on the Config page, what exactly do you observe?

 Stack Trace when going to main configuration page
 -

 Key: JENKINS-12307
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12307
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Reporter: mwebber
Assignee: Ulli Hafner
Priority: Minor

 When I go (in the web interface) to the main Jenkins configuration page, a 
 stack trace is generated on the Jenkins console. No adverse results appear on 
 the web page itself. From the stack track, it looks like it is connected to 
 the warnings plugin.
 This is Jenkins 1.446 and Warnings plugin 3.26 (the latest available at the 
 time of reporting). I have been noticing this stack track for some time now, 
 including under earlier releases (I'm not sure how recently it started).
 The stack trace:
 {noformat}
 05-Jan-2012 11:35:26 hudson.ExpressionFactory2$JexlExpression evaluate
 WARNING: Caught exception evaluating: 
 descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason: 
 java.lang.reflect.InvocationTargetException
 java.lang.reflect.InvocationTargetException
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at 
 org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
 at 
 org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
 at 
 org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
 at 
 org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
 at 
 org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
 at 
 org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
 at 
 org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
 at 
 org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
 at 
 hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
 at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
 at 
 org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
 at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
 at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
 at 
 org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
 at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
 at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
 at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
 (snip)
 at

[JIRA] (JENKINS-11286) Git plugin does not timeout

2012-03-05 Thread tfo...@willowgarage.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159881#comment-159881
 ] 

Tully Foote commented on JENKINS-11286:
---

Q3. At some point it does need to timeout. We've found hung polling threads 
which were 2 weeks old from when our git repo had some downtime. 

And until this is released, does anyone have a suggested way to clear these 
hung polling threads?  I ended up rebooting the slaves which was obviously 
overkill, but did clear the jobs. 

 Git plugin does not timeout
 ---

 Key: JENKINS-11286
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11286
 Project: Jenkins
  Issue Type: Bug
  Components: git
Reporter: recampbell
Assignee: Karol Depka Pradzinski

 We are seeing hung git processes which seem to be left over from when Jenkins 
 is using Git to poll for changes.  This is likely because there was some IO 
 problem (disk or network) when the polling was attempted. Instead of hanging 
 forever, the fetch should eventually timeout.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12987) Concurrent Modification Exception for CVS

2012-03-05 Thread khus...@java.net (JIRA)

Sagar Khushalani created JENKINS-12987:
--

 Summary: Concurrent Modification Exception for CVS
 Key: JENKINS-12987
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12987
 Project: Jenkins
  Issue Type: Bug
  Components: core, cvs
Affects Versions: current
 Environment: CentOS 6.0 Master, CentOS 5.5 slave, CVS
Reporter: Sagar Khushalani
Priority: Blocker


CVS polling fails on some projects with the following exception (following is 
in the CVS Polling Log): 

{noformat}
ERROR: Failed to record SCM polling
java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:782)
at java.util.ArrayList$Itr.next(ArrayList.java:754)
at hudson.scm.CVSSCM.compareRemoteRevisionWith(CVSSCM.java:356)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject.poll(AbstractProject.java:1323)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
at 
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
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:636)
{noformat}

This causes the polling to fail, and the project to not find any differences, 
therefore not build on update.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12037) CLI - I/O error in channel Chunked connection/Unexpected termination of the channel - still occurring in Jenkins 1.449

2012-03-05 Thread mcs...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159883#comment-159883
 ] 

mcs130 commented on JENKINS-12037:
--

Richard we obtained your 1.450 version of the JAR with heartbeat time interval 
change.  We installed the 1.450 WAR into Tomcat 7.0.22 and run everything from 
jdk1.6.0_30 now - both the Tomcat startup and the JDK from which we run the CLI 
commands.  We even set the connectionTimeout in the Tomcat server.xml from 20 
seconds to as high as 60 seconds.  Nothing is working - we still get the I/O 
chunked connection/Unexpected term of channel error.  For now we have had to 
revert back to 1.441 running on Winstone only...and the original 1.441 CLI jar 
that came with it.  When using this combination - it works but is not ideal.  
We can't get above 1.441 because even using Winstone with a later version fails 
in the same manner.  And to your point, the -s parameter appears to get ignored 
when used.  I will get the similar logs from the last experiment and send them 
as before.

Thanks

Mark

 CLI - I/O error in channel Chunked connection/Unexpected termination of the 
 channel - still occurring in Jenkins 1.449
 --

 Key: JENKINS-12037
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12037
 Project: Jenkins
  Issue Type: Bug
  Components: cli
 Environment: * Running on SLES9 Linux server with 4 CPUs and plenty 
 of diskspace.
 * Tomcat 7.0.22
 * JDK 1.6.0_14
 * Only ONE Master configuration - no slaves are configured
 * 3 Executors - (one less than the max number of CPUs) 
Reporter: mark streit
Priority: Critical
 Attachments: Tomcat7_Jenkins1449_logs.zip


 We reported an issue some time back that was also listed as fixed in Jenkins 
 1.441:
 Log:
 [FIXED JENKINS-11130] SEVERE: I/O error in channel Chunked connection when 
 using jenkins-cli.jar
 Perhaps another bug should NOT be submitted so I have added the following 
 comments below the line to the original defect 11130 comments section in case 
 it can be reviewed/re-opened.
 We did NOT try to make any adjustments to the Tomcat configuration:
 Tomcat Connector connectionUploadTimeout
 but we are also now seeing the same problem with Winstone when at this same 
 1.441 level.  We did revert to the 1.438 version of the CLI (leaving the WAR 
 at 1.441 running in Winstone) and that is serving asthe current workaround.
 
 We have downloaded and installed the LATEST 1.441 release that lists the fix 
 for this problem. Currently we were running 1.438 on Winstone only (since 
 with Tomcat 6 or 7, we had experienced the error HOWEVER yet under Winstone, 
 it worked OK so that was our workaround - while running 1.438).
 Now with Jenkins 1.441 - we are getting the ERROR again and NOW WITH BOTH 
 Winstone and the Tomcat configurations). We have left the Jenkins 1.441 WAR 
 file in place running on Winstone, and reverted the CLI jar file back to the 
 1.438 version for now and that appears to work again with Winstone.
 Checked Manifest of CLI jar downloaded with the 1.441 WAR installation:
 Manifest-Version: 1.0
 Archiver-Version: Plexus Archiver
 Created-By: Apache Maven
 Built-By: kohsuke
 Build-Jdk: 1.6.0_26
 Main-Class: hudson.cli.CLI
 Jenkins-CLI-Version: 1.441
 Under Tomcat 7, we get this stacktrace:
 Started by command line
 [workspace] $ /bin/bash -xe 
 /opt/apache-tomcat-7.0.22_jenkins/temp/hudson3281734817830.sh
 + /opt/Sun/jdk1.6.0_14/bin/java -jar /opt/Sun/jdk1.6.0_14/lib/jenkins-cli.jar 
 -s http://11.22.33.44:8082/jenkins/ build XYZ_Project-SharedLibs -s -p 
 SVN_PATH=trunk
 Dec 5, 2011 12:59:11 PM hudson.remoting.Channel$ReaderThread run
 SEVERE: I/O error in channel Chunked connection to 
 http://11.22.33.44:8082/jenkins/cli
 java.io.IOException: Unexpected termination of the channel
 at hudson.remoting.Channel$ReaderThread.run(Channel.java:1115)
 Caused by: java.io.EOFException
 at 
 java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2554)
 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297)
 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at hudson.remoting.Channel$ReaderThread.run(Channel.java:1109)
 Exception in thread main hudson.remoting.RequestAbortedException: 
 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected 
 termination of the channel
 at hudson.remoting.Request.call(Request.java:149)
 at hudson.remoting.Channel.call(Channel.java:681)
 at 
 hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
 at $Proxy2.main(Unknown Source)
 at

[JIRA] (JENKINS-12980) With IE8 any page displays a javascript error about sortable.js

2012-03-05 Thread alexl...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159884#comment-159884
 ] 

Alex Lehmann commented on JENKINS-12980:


The error is apparently related to the keyboard-shortcut plugin, if I remove 
that, the error goes away.



 With IE8 any page displays a javascript error about sortable.js
 ---

 Key: JENKINS-12980
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12980
 Project: Jenkins
  Issue Type: Bug
  Components: www
Affects Versions: current
 Environment: jenkins 1.452 running on linux sles 11, java 1.6.0-31, 
 tomcat 7.0.25, client is Windows 7 64 with Internet Explorer 8
Reporter: Alex Lehmann
Priority: Minor

 When accessing Jenkins with IE8, each page displays a javascript error about 
 sortable.js
 Line 242
 Character 9
 Object doesn't support this property or method
 Code 0
 http://(host)/jenkins/static/99210c85/scripts/sortable.js
 (the text is roughly translated back to English since I do not have an 
 English Windows to test)
 When skipping the error message, the page works, but the error shows up on 
 any page again.
 The same page works on IE6, IE7, IE9 and current Firefox without errors

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12945) New breadcrumb: relative path should be resolved based on model-link's href