[JIRA] (JENKINS-14102) Unstable main build leads to post steps being executed even if configured not to
Maxime Lemanissier commented on JENKINS-14102 Unstable main build leads to post steps being executed even if configured not to I get the same error with Jenkins 1.473, Maven build unstable but post steps still executed. I have also tried to pass a -Dmaven.test.failure.ignore=false, the build is then failed but post steps are still executed :/ Is there any planned date/version to get a fix for this annoying problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Andreas Zschorn commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Same for use, on windows 2008 RC2 and linux slaves. But the crashes are here all time. All slaves are dead after a short time. If such an unstable mechanism is instruduced, i would have at least the chance to turn it off. Startup time is really a no issue in comparision to not working at all. AbstractLazyLoadRunMap is quite good obfuscated by the programmer. So debugging it is not a suitable option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy created JENKINS-15837 Jenkins takes a lot of time to respond after 2 days Issue Type: Bug Assignee: Unassigned Attachments: dominator-tree-leak-suspects.PNG, gc-log.PNG, leak-supects-details.PNG, leak-supects-graph.PNG Components: core Created: 16/Nov/12 9:23 AM Description: After a first problem of OOM : https://issues.jenkins-ci.org/browse/JENKINS-15491 , I've updated Jenkins to 1.488. But now, Jenkins puts a lot of time to respond after 2 days of use and finally crashes. I've analysed the heap dump and the GC log with IBM Support Assistant. The results are attached. Thanks in advance from any help ! Michaël Pailloncy Environment: Jenkins 1.488 - Aix 5.3 - IBM Java 6 Project: Jenkins Labels: jenkins crash Priority: Major Reporter: Michael Pailloncy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15838) Deleting first (oldest) job from history does not update web UI
Sebastian Schuberth updated JENKINS-15838 Deleting first (oldest) job from history does not update web UI Change By: Sebastian Schuberth (16/Nov/12 9:40 AM) Environment: Jenkins1.488onUbuntu12.04. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15760) java.lang.NullPointerException when starting job
Uladzimir Mihura commented on JENKINS-15760 java.lang.NullPointerException when starting job Same for me. I'll try to look and make a pull request if possible. -vova This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15770) SEVERE: Failed to record SCM polling
Lyubomira Valcheva updated JENKINS-15770 SEVERE: Failed to record SCM polling Change By: Lyubomira Valcheva (16/Nov/12 9:58 AM) Due Date: 10 20 /Nov/12 Component/s: core Component/s: hudson-logaction This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15760) java.lang.NullPointerException when starting job
Uladzimir Mihura commented on JENKINS-15760 java.lang.NullPointerException when starting job This is already fixed in master: https://github.com/jenkinsci/tikal-multijob-plugin/compare/jenkins-multijob-plugin-1.6...master#L4R308 Let's just wait for new version -vova This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15839) Manage Jenkins page has partial encoding problems
Harald Albers created JENKINS-15839 Manage Jenkins page has partial encoding problems Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: manage-jenkins-encoding.gif Components: core Created: 16/Nov/12 10:16 AM Description: Starting with v 1.489, the Manage Jenkins page in german translation shows scrambled german umlauts in some of the function descriptions of the content area (e.g. manage nodes). Not all entries are affected, manage users and prepare shutdown show up with correct umlauts. See attached screenshot: red and green mark two occurrances of the same character, one being scrambled, the other not. Environment: Jenkins on Debian 6 german or Windows 7 german; viewed on Windows 7 german with Chrome 22.0.1229.94 or Internet Explorer 8 Project: Jenkins Priority: Trivial Reporter: Harald Albers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15840) Use variables in URLs
Dridi Boukelmoune
created JENKINS-15840
Use variables in URLs
Issue Type:
Improvement
Assignee:
Gregory Boissinot
Components:
envinject, urltrigger
Created:
16/Nov/12 11:00 AM
Description:
I'm polling a nexus URL to check changes of a SNAPSHOT maven artifact.
I could hardcode the version but it's used in different places...
The URL I want to poll looks like:
http://myhost/service/local/artifact/maven/redirect?r=myrepog=mygroupida=myartifactidv=${MY_VERSION}...
The MY_VERSION variable is defined in Prepare an environment for the run - Properties Content (with the envinject plugin).
Environment:
Jenkins 1.466.1
URLTrigger 0.24
EnvInject 1.57
Project:
Jenkins
Priority:
Major
Reporter:
Dridi Boukelmoune
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15840) Use variables in URLs
Dridi Boukelmoune
commented on JENKINS-15840
Use variables in URLs
[URLTrigger] - Poll with a URL
Inspecting Monitor a change of the content content for URL http://myhost/service/local/artifact/maven/redirect?r=myrepog=mygroupida=myartifactidv=${MY_VERSION}
Polling started on Nov 15, 2012 10:01:39 PM
Polling for the job My_Job
Looking nodes where the poll can be run.
Looking for a candidate node to run the poll.
Looking for a node with no predefined label.
Trying to poll with the last built on node.
Polling on master.
Invoking the url:
http://myhost/service/local/artifact/maven/redirect?r=myrepog=mygroupida=myartifactidv=${MY_VERSION}
[ERROR] - SEVERE - Polling error null
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15841) tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
Jan Mnisi commented on JENKINS-15841 tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V This is what I saw whilst trying to understand the error and look for a workaround/fix... setBuiltOnStr protected void setBuiltOnStr(String builtOn) Allows subtypes to set the value of builtOn. This is used for those implementations where an AbstractBuild is made 'built' without actually running its run() method. Since: 1.429 I do understand that AbstractBuild is the base implementation of Run, but then I don't quite get why this is just being made "built" without running the run method. That seems to be the issue here, and I have no way to bypass this when running on Jenkins. Would a pure jenkins installation handle this better than a one-time Hudson installation that was updated? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy updated JENKINS-15837 Jenkins takes a lot of time to respond after 2 days add monitoring diagram of loaded classes and non heap memory Change By: Michael Pailloncy (16/Nov/12 12:24 PM) Attachment: loaded-classes-count.PNG Attachment: non-heap-memory.PNG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy edited a comment on JENKINS-15837 Jenkins takes a lot of time to respond after 2 days I've added monitoring diagrams of loaded classes and non heap memory. Jenkins has planted this morning at 9am. is this related? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15367) Jenkins kicks off the wrong downstream builds for Maven
tuomas_kiviaho commented on JENKINS-15367 Jenkins kicks off the wrong downstream builds for Maven For me it seems to see itself somehow though version ranges (caused by cyclic dependencies I guess) and stays forever in 'pending - Upstream Job ... in build queue'. This might be more related to JENKINS-12735 because it started to happen at the same time that (upstream and) downstream builds started to contain version ranged dependencies. Funny thing is that the project itself isn't listed in upstream builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Michael Clarke commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Unticking the 'Show all CVS Output' box sets the '-Q' flag on the CVS command; e.g. "cvs -Q up ..." but doesn't hide anything that is returned by CVS (i.e the filtering is done by the CVS server based on the presence of this flag, not be Jenkins). The messages you see during CVS actions are also generated by the CVS Server so you should see the same output in Jenkins as you do in a command line client if all the options are the same. I'll do a bit more investigation as to why -Q on rlog is preventing changelog generation (and presumably polling). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15808) CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Michael Clarke commented on JENKINS-15808 CVS plugin 2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration I've not tried your test case, but I'm surprised this has anything to do with the CVS plugin given you don't have any features of the CVS plugin enabled on the screen and the error is being caused by the Jenkins core being unable to parse a JSON string (which itself doesn't seem to be JSON). Given another defect pointed at the CVS plugin causing problems which turned out not to be true, please check your findings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
Michael Clarke commented on JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs The exception is being thrown whilst trying to load an historic build record given the stack trace at the top of this issue. If this was caused by the initialising of the plugin then I'd expect more people to have had this problem. Do you only get the exception when you try and access a previous run of a job and, if so, does this only affect job histories for jobs that were run before the last server restart, and not those run since then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15525) ProjectSet parser isn't working
SCM/JIRA link daemon commented on JENKINS-15525 ProjectSet parser isnt working Code changed in jenkins User: mc1arke Path: src/main/java/hudson/scm/CvsProjectset.java http://jenkins-ci.org/commit/cvs-plugin/d2c7f2614f98b5814e4dfec5d5bc32ca81dcdeb4 Log: FIXED JENKINS-15525 Allow dashes in module names Add support for modules with dashes in their names for the projectset parse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15525) ProjectSet parser isn't working
SCM/JIRA link daemon resolved JENKINS-15525 as Fixed ProjectSet parser isnt working Change By: SCM/JIRA link daemon (16/Nov/12 1:10 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13115) Same attachment can appear multiple times on Test Result page
Christopher Orr commented on JENKINS-13115 Same attachment can appear multiple times on Test Result page This should be fixed once this pull request is released https://github.com/jenkinsci/junit-attachments-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-7056) On test specific page attachments should be filtered by the test name
Christopher Orr commented on JENKINS-7056 On test specific page attachments should be filtered by the test name This should be fixed once this pull request is released https://github.com/jenkinsci/junit-attachments-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14866) Extra requirement of having output files break TestNG integration and create complex implementation
Christopher Orr commented on JENKINS-14866 Extra requirement of having output files break TestNG integration and create complex implementation It's not really clear what you're trying to do here. You do not have to write files to those locations you can also use the [ATTACHMENT|/path/to/file.txt] syntax mentioned on the wiki page. In any case, Jenkins will show the stderr/stdout info it finds in any testsuites, with or without the attachments plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Andreas Zschorn edited a comment on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Same for us, on windows 2008 RC2 and linux slaves. But the crashes are here all time. All slaves are dead after a short time. If such an unstable mechanism is instruduced, i would have at least the chance to turn it off. Startup time is really a no issue in comparision to not working at all. AbstractLazyLoadRunMap is quite good obfuscated by the programmer. So debugging it is not a suitable option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Andrea Curtoni commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Same issue: Jenkins 1.489, Jenkins Subversion Plug-in 1.43 (it was already bugged in previous versions) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14926) Repo does not implement getAffectedFiles()
SCM/JIRA link daemon commented on JENKINS-14926 Repo does not implement getAffectedFiles() Code changed in jenkins User: Joe Hansche Path: src/main/java/hudson/plugins/repo/ChangeLogEntry.java http://jenkins-ci.org/commit/repo-plugin/39dc567cea2bd9b27ff538b11cb4adb4c745e396 Log: FIXED JENKINS-14926 Implement the parent interface's getAffectedFiles() method. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Ray Cuadra updated JENKINS-15842 Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Change By: Ray Cuadra (16/Nov/12 2:45 PM) Environment: JenkinsisrunningonWindowsServer2008R2Enterprise64bitmachine .JenkinsVersionis1.489 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15844) Allow Jenkins Environment Variables in the URL
Paul Spurr created JENKINS-15844 Allow Jenkins Environment Variables in the URL Issue Type: Improvement Affects Versions: current Assignee: nidaley Components: plot Created: 16/Nov/12 3:18 PM Description: It would be useful to be able to include a Jenkins environment variable in the url entered. The reason for this is that we use this url to link to a html report that contains further information. This report is part of the archive output of the build so we would like to be able to reference each report using the %BUILD_NUMBER% in the url. Full list of variables that could be specified at https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-JenkinsSetEnvironmentVariables Project: Jenkins Priority: Minor Reporter: Paul Spurr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14866) Extra requirement of having output files break TestNG integration and create complex implementation
Sebastien Tardif commented on JENKINS-14866 Extra requirement of having output files break TestNG integration and create complex implementation I raised couple of points. 1 - redirectTestOutputToFile option should not exist, I don't see the point of it, and Junit plug-ins works fine without that. 2 - junit-attachments should also work with TestNG without any need of customization. 3 - [ATTACHMENT|/path/to/file.txt] syntax doesn't work! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15845) java.lang.LinkageError on remote
olamy created JENKINS-15845 java.lang.LinkageError on remote Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 16/Nov/12 4:45 PM Description: stack trace: Last Built Revision: Revision 11c9bcbacb275a3a7b589a9c104d09f1ec6d93c9 (origin/master) hudson.util.IOException2: remote file operation failed: /home/jenkins/jenkins-slave/workspace/helix at hudson.remoting.Channel@5181fa4:ubuntu5 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:986) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1142) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException: Remote call on ubuntu5 failed at hudson.remoting.Channel.call(Channel.java:673) at hudson.FilePath.act(FilePath.java:831) ... 11 more Caused by: java.lang.LinkageError: loader (instance of hudson/remoting/RemoteClassLoader): attempted duplicate class definition for name: "hudson/model/Run" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:152) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2308) at java.lang.Class.getDeclaredField(Class.java:1897) at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1624) at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:69) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:442) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.init(ObjectStreamClass.java:430) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:327) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:564) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1600) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1749) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at
[JIRA] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
Vincent Latombe created JENKINS-15846 Deadlock during Maven builds Parsing POM step Issue Type: Bug Assignee: Unassigned Attachments: threaddump_deadlock_commons-logging.txt Components: maven Created: 16/Nov/12 5:08 PM Description: The following thread dump (from one stuck slave) shows a deadlock between pool-635-thread-1 and pool-635-thread-2 Looks like it is due to commons-logging used by maven wagon. Environment: Jenkins 1.473 Project: Jenkins Priority: Major Reporter: Vincent Latombe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15837) Jenkins takes a lot of time to respond after 2 days
Michael Pailloncy commented on JENKINS-15837 Jenkins takes a lot of time to respond after 2 days I did an experience in running a Groovy script every minute doing : Jenkins.getInstance().reload() Jenkins has crashed after 2:30 with similar symptoms (see loaded-classes-count.png and non-heap-memory.png) Maybe a problem on unloading classes ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15833) exception with latest Conditional buildstep plugin, with jenkins version 1.490
domi updated JENKINS-15833 exception with latest Conditional buildstep plugin, with jenkins version 1.490 this must be fixed in the groovy plugin Change By: domi (16/Nov/12 5:30 PM) Component/s: groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15847) LDAP plus SASL
Patrick Wong created JENKINS-15847 LDAP plus SASL Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: ldap, security Created: 16/Nov/12 5:30 PM Description: Our corporate security requirements have mandated that our ActiveDirectory servers use DIGEST-MD5 (SASL) as the authentication method. I tested the connection with Apache Directory Studio as well as with Jenkins, and confirmed that this is not covered by LDAPS. Project: Jenkins Labels: ldap sasl Priority: Major Reporter: Patrick Wong This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15848) CVS plugin, add support for 'C' parameter
Dave Stevens created JENKINS-15848 CVS plugin, add support for C parameter Issue Type: Improvement Assignee: Unassigned Components: cvs Created: 16/Nov/12 5:44 PM Description: It appears that the default update parms have changed with the update I just did to Jenkins. I updated Jenkins to 1.466.2 and all the plugins. The Jenkins CVS plugin is now at 2.7 At the start of the build, the CVS update used to look like this: /Developer_4.2/usr/bin/cvs -q -z3 update -PdC -D "Friday, November 9, 2012 7:26:40 PM UTC" It now looks like this: cvs update -d -P -r HEAD -D 16 Nov 2012 01:56:11 -0600 workspace So the builds are now failing any time there are any locally modified files. The -PdC used to take care of that. -P Prune directories d create missing directories C Overwrite locally modified files To the best of my knowledge, that isn't configured anywhere on our system and the only updating done was the Jenkins updates. We do modify the .plists during the build, so it is expected that they are locally modified. I can add a postbuild step to every build to delete the .plists, but that isn't ideal. So it appears that something changed in the Jenkins CVS plugin to cause this to start happening or some other plugin that was updated. Environment: os x, jenkins 1.466.2 CVS plugin 2.7 Project: Jenkins Priority: Major Reporter: Dave Stevens This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15848) CVS plugin, add support for 'C' parameter
SCM/JIRA link daemon resolved JENKINS-15848 as Fixed CVS plugin, add support for C parameter Change By: SCM/JIRA link daemon (16/Nov/12 6:23 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15848) CVS plugin, add support for 'C' parameter
SCM/JIRA link daemon commented on JENKINS-15848 CVS plugin, add support for C parameter Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/AbstractCvs.java src/main/java/hudson/scm/CVSSCM.java src/main/java/hudson/scm/CvsProjectset.java src/main/java/hudson/scm/ICvs.java src/main/resources/hudson/scm/CVSSCM/config.jelly src/main/resources/hudson/scm/CVSSCM/help-forceCleanCopy.html http://jenkins-ci.org/commit/cvs-plugin/79bc7e9ffe49e8edb5f4ead194757a96c510b289 Log: FIXED JENKINS-15848 Add configurable 'C' option for CVS update This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15848) CVS plugin, add support for 'C' parameter
SCM/JIRA link daemon commented on JENKINS-15848 CVS plugin, add support for C parameter Code changed in jenkins User: Michael Clarke Path: src/test/java/hudson/scm/CVSSCMTest.java http://jenkins-ci.org/commit/cvs-plugin/7366c494f97363aa06d425f63a1db0ab5eeb3fbb Log: FIXED JENKINS-15848 Add configurable 'C' option for CVS update This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Jeremy Moore commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Getting a similar error here with similar stack trace. It is always the same "failing to load #195 EXACT: lo=1466,hi=68,size=1466,size2=1466" for us. Could it be an issue with a specific job's data? It seems to be calling "getPreviousBuild" or "getLastBuild". I assume "#195" is the build number? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Jeremy Moore edited a comment on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Getting a similar error here with similar stack trace. It is always the same "failing to load #195 EXACT: lo=1466,hi=68,size=1466,size2=1466" for us. Could it be an issue with a specific job's data? It seems to be calling "getPreviousBuild" or "getLastBuild". I assume "#195" is the build number? We are on build 1.489. We had finally updated from the last "hudson" build before the fork. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13202) Artifact archiving from an ssh slave fails if symlinks are present
dogfood commented on JENKINS-13202 Artifact archiving from an ssh slave fails if symlinks are present Integrated in jenkins_main_trunk #2079 JENKINS-13202 646154f refinement: resolveSymlink is documented to return null, not throw an exception, when called on a regular file. (Revision 0552f5ad75da1468050f8aa3ffb533bd3c5d4ca8) Result = SUCCESS Jesse Glick : 0552f5ad75da1468050f8aa3ffb533bd3c5d4ca8 Files : core/src/test/java/hudson/UtilTest.java core/src/main/java/hudson/Util.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10569) When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times
Alex Lehmann commented on JENKINS-10569 When installing plugins with overlapping dependencies, Jenkins downloads the duplicate plugins multiple times i believe this is not 100% fixed in 1.490, I got one duplicated dependency (though the static analysis plugin is not downloaded for each plugin) http://imgur.com/5EdnY (not quite sure how to attach in image to a comment) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Richard Mortimer assigned JENKINS-15499 to Richard Mortimer HistoryWidget/entry.jelly throws NullPointerException Change By: Richard Mortimer (16/Nov/12 9:42 PM) Assignee: KohsukeKawaguchi RichardMortimer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views
MeTAlMollY commented on JENKINS-11898 Create view if view doesnt exist doesnt work for dynamic views Changeset: 97ddb1298fbc0493bcc243e2345b987d13fa4d81 Author:Mark Date: 2012-11-16 22:34 Message: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) + in the Page name not supported
Joe Hansche resolved JENKINS-15308 as Cannot Reproduce + in the Page name not supported Change By: Joe Hansche (16/Nov/12 10:10 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15308) + in the Page name not supported
Joe Hansche closed JENKINS-15308 as Cannot Reproduce + in the Page name not supported Change By: Joe Hansche (16/Nov/12 10:10 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views
MeTAlMollY edited a comment on JENKINS-11898 Create view if view doesnt exist doesnt work for dynamic views Hi Vincent, Commit 35996f3090bc1eb019f4a46a918231b75c217c51 made to fix this problem is not correct. As the -vws argument is not available for dynamic views. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11898) Create view if view doesn't exist doesn't work for dynamic views
MeTAlMollY edited a comment on JENKINS-11898 Create view if view doesnt exist doesnt work for dynamic views - This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14976) Deserializing parameter 'in2': could not find deserializer for type {http://beans.soap.rpc.confluence.atlassian.com}RemotePageUpdateOptions
Joe Hansche
commented on JENKINS-14976
Deserializing parameter in2: could not find deserializer for type {http://beans.soap.rpc.confluence.atlassian.com}RemotePageUpdateOptions
Looks like this is because Confluence 2.5 does not support the updatePage() method, according to https://confluence.atlassian.com/display/CONF25/Remote+API+Specification#RemoteAPISpecification-methodsRemoteMethods and instead uses storePage() to update a page. That means that 2.5 also does not support the ability to add a comment for the page edit (e.g., to explain what you're changing/why, etc). That is the primary purpose of the RemotePageUpdateOptions encapsulation class.
I'll consider adding a fallback for Confluence 2.5 support, but have you considered upgrading Confluence? The current version is 4.3, with 5.0 already available for developer early access. IMO, this is poor SOAP implementation, because both 2.5 and 3.x have a "v1" WSDL file that is supposed to describe the SOAP API, yet Confluence 2.5 does not support the actual v1 APIs mentioned above.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15472) Option to create a new page
SCM/JIRA link daemon commented on JENKINS-15472 Option to create a new page Code changed in jenkins User: Joe Hansche Path: src/main/java/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher.java http://jenkins-ci.org/commit/confluence-publisher-plugin/35f10018a15df1c228b4c6a4c1233db14a8851a9 Log: FIXED JENKINS-15472 Create the page at build time if it did not exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15472) Option to create a new page
SCM/JIRA link daemon resolved JENKINS-15472 as Fixed Option to create a new page Change By: SCM/JIRA link daemon (16/Nov/12 10:30 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15472) Option to create a new page
Joe Hansche commented on JENKINS-15472 Option to create a new page This has been implemented in an upcoming 1.8 release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10593) Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL
Joe Hansche commented on JENKINS-10593 Project-based Matrix Authorization Strategy: allow a job to not inherit from global ACL Pull request has been created at https://github.com/jenkinsci/jenkins/pull/622 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15847) LDAP plus SASL
Patrick Wong resolved JENKINS-15847 as Not A Defect LDAP plus SASL It turns out that my LDAP settings were wrong. Change By: Patrick Wong (17/Nov/12 1:06 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Ray Cuadra updated JENKINS-15842 Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Change By: Ray Cuadra (17/Nov/12 2:36 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Ray Cuadra commented on JENKINS-15842 Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Is there any other setting I need to make sure the TFS plugin will poll successfully? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15842) Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Ray Cuadra started work on JENKINS-15842 Jenkins V1.489 ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@17a7476[ProjName] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Change By: Ray Cuadra (17/Nov/12 2:46 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11592) NPE: Failed to record SCM polling
Ken Egozi reopened JENKINS-11592 NPE: Failed to record SCM polling Still happening, with 1.490 and tfs plugin 1.20 (the latest) not the NPE, but java.lang.StringIndexOutOfBoundsException: String index out of range: -1 instead Change By: Ken Egozi (17/Nov/12 6:05 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
Farzad Valad commented on JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs When I restart the error begins reporting when I click on any of my job views. All of them have the condition you said, old job histories. But I don't have to open a particular one. Is there any way to get more details of which job it is complaining about? I do have the option to reinstall and port over the job definitions, but I'd rather not do that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
