[JIRA] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor
Tim Brown commented on JENKINS-22427 Parameterized Remote Trigger Plugin fails when remote job waits for available executor Are you using 'wait to trigger remote builds until no other builds are running'? If not does it fix your issue? I found I needed both working together for it to be reliable. If so is the problem that the build gets triggered but is waiting in the queue (as it's waiting for and executor)? I will see if I can have a look tomorrow. Had a lot on the last week. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22464) Exception when auto-compliting existing jobs during new job creation
Alexander Obuhovich reopened JENKINS-22464 Exception when auto-compliting existing jobs during new job creation You forgot to indicate the issue which this one maybe duplicates. Without it I can't really know if original issue is fixed at all. Change By: Alexander Obuhovich (10/Apr/14 7:06 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22464) Exception when auto-compliting existing jobs during new job creation
Daniel Beck resolved JENKINS-22464 as Duplicate Exception when auto-compliting existing jobs during new job creation The link to the original issue is in the Issue Links section that's between Description and Activity. I see no point in posting redundant information. Change By: Daniel Beck (10/Apr/14 7:17 AM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Alexander Obuhovich commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job It doesn't affect building process, but when you're about to create a job based on another one, then you need to open 2 browser windows: 1. one to copy-paste original job name from 2. another to paste that in and create a job, since auto-complete doesn't work Definitely a usability issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22464) Exception when auto-compliting existing jobs during new job creation
Alexander Obuhovich commented on JENKINS-22464 Exception when auto-compliting existing jobs during new job creation Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-22559) Add openGrok as SCM browser to clearcase plugin
Gosha Frost created JENKINS-22559 Add openGrok as SCM browser to clearcase plugin Issue Type: New Feature Assignee: Vincent Latombe Components: clearcase Created: 10/Apr/14 7:33 AM Description: It would be nice if clearcase plugin would support OpenGrok as SCM browser as was already done for Bazaar and CVS. It will allow to see the diffs in the changed files through web. 10x, Gosha Project: Jenkins Priority: Major Reporter: Gosha Frost 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Daniel Beck updated JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job While it's unfortunate that autocomplete doesn't work, it's not a critical issue. Reclassifying based on Jira issue priority descriptions; an easy workaround is described by Alexander Obuhovich (note that a single tab suffices, the clip board isn't cleared when navigating to a different web page): Critical Crashes, loss of data, severe memory leak. Major Major loss of function. Minor Minor loss of function, or other problem where easy workaround is present. And I've already provided a possible fix, so there's no need to set a high priority just to get someone to look at this Change By: Daniel Beck (10/Apr/14 7:40 AM) Priority: Critical Minor 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Alexander Obuhovich commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job And I've already provided a possible fix Am I missing something? I see you've mentioned a GitHub Pull Request, but how this is a fix? I'm still getting that exception. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
Daniel Beck commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job The fix exists, it just hasn't been released (or even merged). With some luck it'll be in 1.560 and 1.554.2. If this is a real problem for you, you can always branch off the Jenkins release you're using and cherry-pick the commit in the PR to create your own fixed build. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-13234) Option to specify the view storage location - our case 8516
Jens Brejner commented on JENKINS-13234 Option to specify the view storage location - our case 8516 Ok, now I think I understand, I will get back to you. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on lslaves since 1.556
Dirk Kuypers created JENKINS-22560 Deadlocked executors on lslaves since 1.556 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Apr/14 8:39 AM Description: Could it be that the change in JENKINS-22131 is causing deadlocks? If I downgrade to 1.555, there is no problem, all versions from 1.556 show the same behaviour: More and more executors are deadlocked. To me it looks if two concurrent jobs do something which locks each other. Warning, the following threads are deadlocked : Executor #0 for 1sp-slave12 : executing CONTEST_Technologies_Tests #1568, Executor #13 for 1sp-slave1 : executing CONTEST_Technologies_Tests #1569 The threads are blocked in: hudson.model.Run.save(Run.java:1856) (#1568) hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178) (#1569) em Executor#13for1sp-slave1:executingCONTEST_Technologies_Tests#1569br hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178)br jenkins.model.lazy.LazyBuildMixIn$RunMixIn.dropLinks(LazyBuildMixIn.java:336)br hudson.model.AbstractBuild.dropLinks(AbstractBuild.java:193)br hudson.model.RunMap.removeValue(RunMap.java:120)br hudson.model.RunMap.remove(RunMap.java:86)br jenkins.model.lazy.LazyBuildMixIn.removeRun(LazyBuildMixIn.java:216)br hudson.model.AbstractProject.removeRun(AbstractProject.java:1002)br hudson.model.AbstractProject.removeRun(AbstractProject.java:145)br hudson.model.Run.removeRunFromParent(Run.java:1478)br hudson.model.Run.delete(Run.java:1473)br hudson.tasks.LogRotator.perform(LogRotator.java:124)br hudson.model.Job.logRotate(Job.java:441)br hudson.model.Run.execute(Run.java:1751)br hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)br hudson.model.ResourceController.execute(ResourceController.java:88)br hudson.model.Executor.run(Executor.java:231)br /em em Executor#0for1sp-slave12:executingCONTEST_Technologies_Tests#1568br hudson.model.Run.save(Run.java:1856)br hudson.plugins.changelog_history.ChangeLogHistoryRunListener.copyChangeLogs(ChangeLogHistoryRunListener.java:82)br hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:50)br hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:40)br hudson.model.listeners.RunListener.fireDeleted(RunListener.java:244)br hudson.model.Run.delete(Run.java:1447)br hudson.tasks.LogRotator.perform(LogRotator.java:124)br hudson.model.Job.logRotate(Job.java:441)br hudson.model.Run.execute(Run.java:1751)br hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)br hudson.model.ResourceController.execute(ResourceController.java:88)br hudson.model.Executor.run(Executor.java:231)br /em Environment: Windows 2008 R2 Master, Windows 7 Slaves Project: Jenkins Priority: Blocker Reporter: Dirk Kuypers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Dirk Kuypers updated JENKINS-22560 Deadlocked executors on slaves since 1.556 Change By: Dirk Kuypers (10/Apr/14 8:44 AM) Summary: Deadlockedexecutorson lslaves slaves since1.556 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-ssh] (JENKINS-16240) Problem with NOT_BUILT build result
Isaac Cruz commented on JENKINS-16240 Problem with NOT_BUILT build result It's happening to me too. I have a multimodule project where I'm only building one module and its dependencies (using -am), so some modules are not built... and I'm getting the "SSH: Current build result is NOT_BUILT, not going to run." 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-22561) publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used
Sam Liddicott created JENKINS-22561 publish-over-cifs should be able to use Jenkins session credentials - including domain when Jenkins Active Directory authentication is used Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: active-directory, publish-over-cifs Created: 10/Apr/14 9:26 AM Description: If a user has logged in to Jenkins with active directory username and password, with a domain configured or discovered via the active directory plugin, then publish-over-cifs ought to be able to use these values to authenticate when connecting to the remote cifs server to publish files. Project: Jenkins Labels: active_directory, credentials cifs Priority: Major Reporter: Sam Liddicott 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test2] (TEST-39) testing
navaneethan k created TEST-39 testing Issue Type: Bug Assignee: navaneethan k Components: test2 Created: 10/Apr/14 9:53 AM Project: test Priority: Major Reporter: navaneethan k 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix] (JENKINS-22562) Cannot restrict matrix *children* to a label
Phil Rutherford created JENKINS-22562 Cannot restrict matrix *children* to a label Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: matrix Created: 10/Apr/14 9:57 AM Description: It is possible to restrict the matrix parent to a label (see https://issues.jenkins-ci.org/browse/JENKINS-7825), but it is not possible to restrict the matrix child jobs to a label. This would be very useful. Environment: Windows Project: Jenkins Priority: Major Reporter: Phil Rutherford 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [javanet] (JENKINS-15288) JAVA_HOME env variable not populating path to JDK installation
Stephane Odul commented on JENKINS-15288 JAVA_HOME env variable not populating path to JDK installation I'm getting this quite often on maven builds but not consistently. Eventually the Slave will gets its brain back together and get the jvm that it auto install, but it cause a bit of confusion and complaints from our developers. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21903) Not all maven downstream jobs get triggered
Stephane Odul commented on JENKINS-21903 Not all maven downstream jobs get triggered Also present in 1.558 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Sampo Niskanen commented on JENKINS-18687 Intermittent failure whilst recording test results caused by java.util.MissingResourceException The problem disappeared when I updated all my Jenkins plugins. No idea which one fixed the problem. And no idea why my other slave was working without problems. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-22563) Option to show status of individual matrix children
Phil Rutherford created JENKINS-22563 Option to show status of individual matrix children Issue Type: Improvement Assignee: Peter Hayes Components: dashboard-view Created: 10/Apr/14 10:17 AM Description: It would be very useful to have an option to show the status of the children of a matrix configuration build on the dashboard itself - just as you get if you go to the status page of a matrix configuration build. Project: Jenkins Priority: Minor Reporter: Phil Rutherford 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22564) Env variables not passed to job
Onno van der Straaten created JENKINS-22564 Env variables not passed to job Issue Type: Bug Assignee: Unassigned Components: jenkins-tracker Created: 10/Apr/14 10:28 AM Description: I think there is a bug. Or documentation is not correct. Regarding env variables. When using the "Trigger/Call builds on another project" item. If the trigger is configured with the "Block until the triggered projects finish their builds" enabled, the following Environment variables are made available for further build steps https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin Above statement is not true in 2.22. I have this setup but also no environment variables. Project: Jenkins Priority: Major Reporter: Onno van der Straaten 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-22565) Promoting a build based on release condition is not working
delbert d created JENKINS-22565 Promoting a build based on release condition is not working Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 10/Apr/14 10:38 AM Description: The problem is described here: https://groups.google.com/d/msg/jenkinsci-users/Yz05SVWXcSw/lFVw6qz53EoJ The job X is not promoted when its released (Condition) using the maven-release-plugin and hence the following action (trigger another project) is not executed. Jenkins ver. 1.558 org.jenkins-ci.plugins:promoted-builds:2.17 Project: Jenkins Priority: Major Reporter: delbert d 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22566) XML API does not escape/filter invalid characters
Michael Keppler created JENKINS-22566 XML API does not escape/filter invalid characters Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Apr/14 10:42 AM Description: In some of our jobs, the build result page gets some text appended using a Groovy postbuild step. The appended text can contain arbitrary characters, even an escape character (character code 27). Everything works fine. On accessing such a build via XML api, there is an exception because the XML output contains invalid characters: error on line 1 at column 9913: PCDATA invalid Char value 27 I'm aware that I can avoid this issue by filtering the appended text in the groovy step, but generally the XML API should filter or escape such invalid characters from the output. Project: Jenkins Priority: Minor Reporter: Michael Keppler 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl resolved JENKINS-20078 as Fixed email-ext plugin takes a huge amount of time to send out final status emails (30min) Change By: Alex Earl (10/Apr/14 10:54 AM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22567) Build history: ability to add columns of jobs' parameters
dor cohen created JENKINS-22567 Build history: ability to add columns of jobs parameters Issue Type: New Feature Assignee: Unassigned Components: core Created: 10/Apr/14 11:01 AM Description: In the page of the build history: please add the ability to show jobs' parameters (either all of them or specific parameter) Project: Jenkins Priority: Minor Reporter: dor cohen 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite reopened JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) The change which is now on the tip of the git-plugin also breaks the URL for githubweb. It is important that the githubweb URL (and other URLs) work before the next release of the git-plugin. Change By: Mark Waite (10/Apr/14 11:15 AM) Resolution: Fixed Status: Resolved Reopened Assignee: NicolasDeLoof MarkWaite 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21509) Create new item fails: NumberFormatException: for InputString
banoss commented on JENKINS-21509 Create new item fails: NumberFormatException: for InputString I'm just going through issues and I have no problems creating new jobs on version 1.557 running under Tomcat6 on Linux (RHEL6.5) with ~500 jobs and many muiltple slave config. Is this still an issue for you? Very few people watching and voting this one. Might be specific to your setup? It's a fundemental operation that I'd expect we'd see more feedback on. Have you tried uninstalling or disabling your green balls 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Maciej Matys
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
It still doesn't work if you specify ** or leave blank job ${branch} job parameter
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Maciej Matys
edited a comment on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
It still doesn't work if you specify ** or leave blank job ${branch} parameter
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Denis Ilyin
created JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL ${SVN_REPO_VARIABLE}
Issue Type:
Bug
Affects Versions:
current
Assignee:
stephenconnolly
Components:
credentials, subversion
Created:
10/Apr/14 11:36 AM
Description:
While the build itself woks fine, with subversion polling, I got E200015 error, even with correct Additional Credentials configured. This happens only for projects with variables in repo URL (but they are substituted correctly) or for repos with externals.
variables testcase:
Started on Apr 9, 2014 9:32:59 AM
Received SCM poll call on windows7 for DUMMY on 9.4.2014 9:32:54
ERROR: Failed to check repository revision for svn+ssh://jenk...@xxx.com/svn/XXX/trunk
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185)
at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:77)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461)
at hudson.scm.SubversionSCM.parseSvnInfo(SubversionSCM.java:1267)
at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:78)
at hudson.scm.CompareAgainstBaselineCallable.call(CompareAgainstBaselineCallable.java:26)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
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.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at hudson.remoting.Engine$1$1.run(Engine.java:63)
at java.lang.Thread.run(Unknown Source)
Done. Took 56 ms
No changes
For externals, the error seems the same:
Started on Apr 9, 2014 9:34:59 AM
Received SCM poll call on windows7 for DUMMY2 on 9.4.2014 9:34:54
ERROR: Failed to check repository revision for svn+ssh://XXX.com/svn/XXX/trunk/EXT_REF
org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32)
at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185)
at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:77)
at
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Maciej Matys commented on JENKINS-14276 Git SCM-polling doesnt work when using a parametrized branch-name @Tomasz did You managed to configure jenkins this way? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Denis Ilyin
updated JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL ${SVN_REPO_VARIABLE}
Change By:
Denis Ilyin
(10/Apr/14 11:43 AM)
Assignee:
stephenconnolly
Attachment:
ScreenShot2014-04-10at15.41.35.png
Environment:
CentOS664bitmaster,Win764bit,CentOS564bitslaves.Jenkinsver.1.558subversionplugin:2.
3-SNAPSHOT(private-04/07/201406:29-jenkins)
2
credentialsplugin:1.10
(otherpluginsviascreenshot)
Description:
Whilethebuilditselfwoksfine,withsubversionpolling,
When
I
gotE200015error,evenwithcorrectAdditionalCredentialsconfigured.Thishappensonlyforprojectswithvariablesinrepo
setRepository
URL
asvariableinsteadofdirecturl
(
buttheyaresubstitutedcorrectly
pleaseseeattachment
)
orforreposwithexternals
,pollingisnowworking
.
Checkoutandupdateareworkingfine.
variablestestcase:Startedon
Apr
9
10
,2014
9
10
:
32
03
:
59
17
AM
ReceivedSCMpollcallonwindows7forDUMMYon9
hudson
.
4
scm
.
20149:32:54
SubversionSCM$DescriptorImpldoCheckRevisionPropertiesSupported
ERROR
INFO
:Failedto
check
accesssubversion
repository
revisionforsvn+ssh://jenk...@xxx.com/svn/XXX/trunk
${SVN_REPO}
org.tmatesoft.svn.core.
SVNCancelException
SVNException
:svn:
E200015
E125002
:
Nocredentialtotry.Authenticationfailed
MalformedURL${SVN_REPO}
atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.
cancel
error
(SVNErrorManager.java:
37
64
) atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.
cancel
error
(SVNErrorManager.java:
32
51
) atorg.tmatesoft.svn.core.
internal
SVNURL
.
wc.DefaultSVNAuthenticationManager.getFirstAuthentication
init
(
DefaultSVNAuthenticationManager
SVNURL
.java:
185
233
) atorg.tmatesoft.svn.core.
internal
SVNURL
.
io.svn.SVNSSHConnector.open
parseURIDecoded
(
SVNSSHConnector
SVNURL
.java:
77
115
) at
org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) atorg.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) atorg.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) atorg.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:46) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteGetInfo.run(SvnRemoteGetInfo.java:31) atorg.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) atorg.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) atorg.tmatesoft.svn.core.wc.SVNWCClient.doInfo(SVNWCClient.java:2461) at
hudson.scm.SubversionSCM
$DescriptorImpl
.
parseSvnInfo
doCheckRevisionPropertiesSupported
(SubversionSCM.java:
1267
2185
) at
hudson
sun
.
scm
reflect
.
CompareAgainstBaselineCallable
NativeMethodAccessorImpl
.
call
invoke0
(
CompareAgainstBaselineCallable.java:78
NativeMethod
) at
hudson
sun
.
scm
reflect
.
CompareAgainstBaselineCallable
NativeMethodAccessorImpl
.
call
invoke
(
CompareAgainstBaselineCallable
NativeMethodAccessorImpl
.java:
26
57
) at
hudson
sun
.
remoting
reflect
.
UserRequest
DelegatingMethodAccessorImpl
.
perform
invoke
(
UserRequest
DelegatingMethodAccessorImpl
.java:
118
43
) at
hudson.remoting.UserRequest.perform(UserRequest.
java
:48) athudson
.
remoting
lang
.
Request$2
reflect
.
run(Request
Method
.
java:326) athudson.remoting.InterceptingExecutorService$1.call
invoke
(
InterceptingExecutorService
Method
.java:
72
606
) at
java
org
.
util
kohsuke
.
concurrent
stapler
.
FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource)
[JIRA] [credentials] (JENKINS-22568) Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
Denis Ilyin
updated JENKINS-22568
Subversion polling not work when Repository URL value is variable - E125002: Malformed URL ${SVN_REPO_VARIABLE}
Change By:
Denis Ilyin
(10/Apr/14 11:45 AM)
Environment:
CentOS664bitmaster
,Win764bit,CentOS564bitslaves.
Jenkinsver.1.558subversionplugin:2.2credentialsplugin:1.10
Description:
WhenIsetRepositoryURLasvariableinsteadofdirecturl(pleaseseeattachment),pollingis
now
not
working.Checkoutandupdateareworkingfine.Apr10,201410:03:17AMhudson.scm.SubversionSCM$DescriptorImpldoCheckRevisionPropertiesSupportedINFO:Failedtoaccesssubversionrepository${SVN_REPO}org.tmatesoft.svn.core.SVNException:svn:E125002:MalformedURL${SVN_REPO} atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) atorg.tmatesoft.svn.core.SVNURL.init(SVNURL.java:233) atorg.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:115) athudson.scm.SubversionSCM$DescriptorImpl.doCheckRevisionPropertiesSupported(SubversionSCM.java:2185) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:606) atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)-- atorg.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) atorg.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) atorg.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) atorg.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) atorg.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:668) atorg.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) atwinstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:724)Causedby:svn:E125002:MalformedURL${SVN_REPO} atorg.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171) atorg.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126) atorg.tmatesoft.svn.core.SVNURL.init(SVNURL.java:232) ...94more
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) What kind of URLs does it break - do you have any examples? It's passing the test cases, so I'm not sure what needs fixing. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-22569) git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
Steven Aerts created JENKINS-22569 git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers Issue Type: Bug Assignee: jyrkiput Components: gerrit, gerrit-trigger, git-client Created: 10/Apr/14 11:54 AM Description: As described in the documentation, Gerrit allows you to start a git job manually by specifying the GERRIT_REFSPEC parameter. In my setup the value of this parameter is ignored and gerrit checks out the remote HEAD instead of the specified refspec. I tried to trace down the issue and found out that the Gerrit merge strategy will select the FETCH_HEAD to start the build from. The problem is however that the git-client not only fetches the $GERRIT_REFSPEC but also fetches an empty refspec, so on the command line, it executes: git fetch --tags --progress url of repo "" $GERRIT_REFSPEC The empty parameter will be translated on the remote site to the HEAD and this is where the FETCH_HEAD will be put on. So the build will start from the wrong git version. Environment: ubuntu 12.04 Project: Jenkins Priority: Major Reporter: Steven Aerts 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
stephenconnolly created JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Apr/14 11:55 AM Description: buildFormTree changes the DOM while parsing the radio button sections, mutating the name field of each element. Since the DOM model is that there can only be at most one selected element for each distinct name, the last radio button selected for each base name will be the only one selected. The fix is not to mutate the DOM while building the JSON form data. Project: Jenkins Priority: Major Reporter: stephenconnolly 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-22569) git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
Steven Aerts
commented on JENKINS-22569
git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
I tried to find out with the debugger where this empty refspec is coming from (gerrit-trigger, git-client-plugin, git-plugin or jgit). But I was unable to do so.
To unblock myself, I altered the git-client-plugin to ignore empty refspecs with the following hack:
--- a/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ b/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -244,8 +244,12 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
if (refspecs != null)
for (RefSpec rs: refspecs)
-if (rs != null)
+if (rs != null) {
+ String refString = rs.toString();
+ if(!StringUtils.isBlank(refString)) {
args.add(rs.toString());
+ }
+}
if (prune) args.add("--prune");
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
SCM/JIRA link daemon resolved JENKINS-22570 as Fixed On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Change By: SCM/JIRA link daemon (10/Apr/14 11:59 AM) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite edited a comment on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) It appears this change breaks the previously working githubweb links until the next time the job is saved. We can't release the plugin with that behavior because we can't force our users to save the job definition in order to restore something that was working previously. The steps I took to show the problem were: Define a job using GitHub URL https://github.com/jenkinsci/git-plugin and GitHub repository browser URL https://github.com/jenkinsci/git-plugin Save that job Let the job run when changes arrive on that GitHub project Upgrade the git plugin to the latest unreleased version Open the job and click one of the recent changes links to githubweb. A slash will be missing from the githubweb URL. Instead of https://github.com/jenkinsci/git-plugin/commit/fb12fed4c1c8af11db68ec236961401d3d11eb7b it will be https://github.com/jenkinsci/git-plugincommit/fb12fed4c1c8af11db68ec236961401d3d11eb7b Configure the job Save that configuration without making any changes Click one of the recent change links to githubweb. A slash will be inserted correctly into the githubweb URL. The link fb12fed works Can you propose a change which will fix that case? If you don't have time for that, I'll reopen the bug and revert this change so that plugin releases of other fixes and improvements are not blocked. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit] (JENKINS-22569) git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
Steven Aerts commented on JENKINS-22569 git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers It might by possible that JENKINS-15313 is a duplicate of this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite edited a comment on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) It appears this change breaks the previously working githubweb links until the next time the job is saved. We can't release the plugin with that behavior because we can't force our users to save the job definition in order to restore something that was working previously. The steps I took to show the problem were: Define a job using GitHub URL https://github.com/jenkinsci/git-plugin and GitHub repository browser URL https://github.com/jenkinsci/git-plugin Save that job Let the job run when changes arrive on that GitHub project Upgrade the git plugin to the latest unreleased version Open the job and click one of the recent changes links to githubweb. A slash will be missing from the githubweb URL. Instead of fb12fed it will be https://github.com/jenkinsci/git-plugincommit/fb12fed4c1c8af11db68ec236961401d3d11eb7b Configure the job Save that configuration without making any changes Click one of the recent change links to githubweb. A slash will be inserted correctly into the githubweb URL. The link fb12fed works Can you propose a change which will fix that case? If you don't have time for that, I'll reopen the bug and revert this change so that plugin releases of other fixes and improvements are not blocked. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) It appears this change breaks the previously working githubweb links until the next time the job is saved. We can't release the plugin with that behavior because we can't force our users to save the job definition in order to restore something that was working previously. The steps I took to show the problem were: Define a job using GitHub URL https://github.com/jenkinsci/git-plugin and GitHub repository browser URL https://github.com/jenkinsci/git-plugin Save that job Let the job run when changes arrive on that GitHub project Upgrade the git plugin to the latest unreleased version Open the job and click one of the recent changes links to githubweb. A slash will be missing from the githubweb URL. Instead of fb12fed it will be https://github.com/jenkinsci/git-plugincommit/fb12fed4c1c8af11db68ec236961401d3d11eb7b Configure the job Save that configuration without making any changes Click one of the recent change links to githubweb. A slash will be inserted correctly into the githubweb URL. The link fb12fed works We can't release a version of the plugin which requires every job to be visited. Some Jenkins servers have hundreds of jobs configured. Can you propose a change which will fix that case? If you don't have time for that, I'll reopen the bug and revert this change so that plugin releases of other fixes and improvements are not blocked. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
SCM/JIRA link daemon commented on JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Code changed in jenkins User: Stephen Connolly Path: war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/88d84f6e9b2f05366bc8e6f4bc62ac61e7211926 Log: FIXED JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Changed from mutating the e.name value to maintaining an index and using that index to get the required substring Risk of unintended consequences is low. The Submit flow moves off the page before the consequences of the effect could be seen... though a careful attention to the page submit can identify the change... and the page is now left as before clicking f:apply instead of mutated. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22569) git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
Steven Aerts updated JENKINS-22569 git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers Change By: Steven Aerts (10/Apr/14 12:00 PM) Component/s: gerrit 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Mark Waite commented on JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT I'll need more information about your configuration (upload a copy of the job definition) and a copy of the git polling log in order to understand why it doesn't work in your case and does work in other cases. Can you upload that information? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22569) git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers
Steven Aerts assigned JENKINS-22569 to rsandell git plugin checks out HEAD instead of $GERRIT_REFSPEC for manual triggers Change By: Steven Aerts (10/Apr/14 12:01 PM) Assignee: jyrkiput rsandell 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
stephenconnolly updated JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Change By: stephenconnolly (10/Apr/14 12:06 PM) Labels: lts-candidate 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) When I compare the job definitions, one point that may be relevant is that the jobs with the failing URL's do not have any normalizeUrl tag inserted into the job definition, while those jobs which have been edited get a normalizeUrl tag with the value "true". 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
clausfod commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap We experience exactly the some problem when running maven jobs with Maven 3.2.1 on Jenkins 1.558 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-22571) Groovyscript executed on master even of parent build is tied to a slave
Anton Lundin created JENKINS-22571 Groovyscript executed on master even of parent build is tied to a slave Issue Type: Bug Assignee: emanuelez Components: groovyaxis Created: 10/Apr/14 12:15 PM Description: I have a groovy-script that discovers connected devices and then generates axis for each device to test on. All the devices are connected to a specific slave, but the groovy script gets run on the master, and not on the slave where the parent build is tied to. Environment: jenkins 1.558 , Linux Project: Jenkins Priority: Minor Reporter: Anton Lundin 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on slaves since 1.556
kutzi assigned JENKINS-22560 to Jesse Glick Deadlocked executors on slaves since 1.556 Quite possible that this was caused by JENKINS-22131 Change By: kutzi (10/Apr/14 12:17 PM) Assignee: JesseGlick 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
clausfod commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap It's also a problem with the maven-checkstyle-plugin:2.11, maven-pmd-plugin:3.0.1 and the findbugs-maven-plugin:2.5.2 plugins: java.io.IOException: Remote call on channel failed 14:13:15 at hudson.remoting.Channel.call(Channel.java:731) 14:13:15 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) 14:13:15 at $Proxy7.execute(Unknown Source) 14:13:15 at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:201) 14:13:15 at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:326) 14:13:15 at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:317) 14:13:15 at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) 14:13:15 at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) 14:13:15 at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) 14:13:15 at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) 14:13:15 at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) 14:13:15 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) 14:13:15 at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) 14:13:15 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) 14:13:15 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) 14:13:15 at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) 14:13:15 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) 14:13:15 at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) 14:13:15 at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) 14:13:15 at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) 14:13:15 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) 14:13:15 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) 14:13:15 at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) 14:13:15 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 14:13:15 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 14:13:15 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 14:13:15 at java.lang.reflect.Method.invoke(Method.java:597) 14:13:15 at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) 14:13:15 at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) 14:13:15 at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) 14:13:15 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 14:13:15 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 14:13:15 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 14:13:15 at java.lang.reflect.Method.invoke(Method.java:597) 14:13:15 at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) 14:13:15 at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) 14:13:15 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 14:13:15 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 14:13:15 at hudson.remoting.Request$2.run(Request.java:328) 14:13:15 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 14:13:15 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 14:13:15 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 14:13:15 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 14:13:15 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 14:13:15 at java.lang.Thread.run(Thread.java:662) 14:13:15 Caused by: java.lang.LinkageError: Failed to load com.google.common.collect.AbstractMapBasedMultimap 14:13:15 at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:326) 14:13:15 at
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Alan Clucas commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) Ok, that's me not understanding how all this stuff works. I can confirm that I'm sure my change breaks it. I'll have a look at fixing it today 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) Thanks very much. I've alerted Nicolas to not release a new version of the plugin until we either have a fix or we have reverted the change. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
dogfood commented on JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Integrated in jenkins_main_trunk #3289 FIXED JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection (Revision 88d84f6e9b2f05366bc8e6f4bc62ac61e7211926) Result = UNSTABLE Stephen Connolly : 88d84f6e9b2f05366bc8e6f4bc62ac61e7211926 Files : war/src/main/webapp/scripts/hudson-behavior.js 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
SCM/JIRA link daemon commented on JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Code changed in jenkins User: Stephen Connolly Path: war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/6f6dce4bef25846d6efcbf75e1a3aa50bbe77d77 Log: FIXED JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Always run git status before and after you commit, just in case there are changes you made since your last call to git add At least the integration test cases caught this one though 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
SCM/JIRA link daemon commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/ViewDescriptor.java http://jenkins-ci.org/commit/jenkins/b35f834b665178b52cbcb1b77600a8060509bbc6 Log: JENKINS-22142 Noting merge of #1179. Compare: https://github.com/jenkinsci/jenkins/compare/6f6dce4bef25...b35f834b6651 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
SCM/JIRA link daemon resolved JENKINS-22142 as Fixed No autocompletion and NullPointerException when using Copy Existing Job Change By: SCM/JIRA link daemon (10/Apr/14 1:44 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
SCM/JIRA link daemon commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ViewDescriptor.java http://jenkins-ci.org/commit/jenkins/c07301142961f3dc904161a52fc06fd20f6b4142 Log: Merge branch 'JENKINS-22142' of github.com:daniel-beck/jenkins 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
SCM/JIRA link daemon commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/ViewDescriptor.java http://jenkins-ci.org/commit/jenkins/b264fa6e6af6df94db8d9eef86a2a650af125079 Log: FIXED JENKINS-22142 Removed obsolete method. Hoping nobody uses it programmatically. Also, added @Restricted to the new one. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick
updated JENKINS-22560
Deadlocked executors on slaves since 1.556
Change By:
Jesse Glick
(10/Apr/14 1:47 PM)
Labels:
deadlockregression
Description:
CoulditbethatthechangeinJENKINS-22131iscausingdeadlocks?IfIdowngradeto1.555,thereisnoproblem,allversionsfrom1.556showthesamebehaviour:Moreandmoreexecutorsaredeadlocked.Tomeitlooksiftwoconcurrentjobsdosomethingwhichlockseachother.Warning,thefollowingthreadsaredeadlocked:Executor#0for1sp-slave12:executingCONTEST_Technologies_Tests#1568,Executor#13for1sp-slave1:executingCONTEST_Technologies_Tests#1569Thethreadsareblockedin:
{code:none}
hudson.model.Run.save(Run.java:1856)(#1568)hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178)(#1569)
{code}
em
{code:none}
Executor
nbsp;
#13
nbsp;
for
nbsp;
1sp-slave1
nbsp;
:
nbsp;
executing
nbsp;
CONTEST_Technologies_Tests
nbsp;
#1569
br
hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178)
br
jenkins.model.lazy.LazyBuildMixIn$RunMixIn.dropLinks(LazyBuildMixIn.java:336)
br
hudson.model.AbstractBuild.dropLinks(AbstractBuild.java:193)
br
hudson.model.RunMap.removeValue(RunMap.java:120)
br
hudson.model.RunMap.remove(RunMap.java:86)
br
jenkins.model.lazy.LazyBuildMixIn.removeRun(LazyBuildMixIn.java:216)
br
hudson.model.AbstractProject.removeRun(AbstractProject.java:1002)
br
hudson.model.AbstractProject.removeRun(AbstractProject.java:145)
br
hudson.model.Run.removeRunFromParent(Run.java:1478)
br
hudson.model.Run.delete(Run.java:1473)
br
hudson.tasks.LogRotator.perform(LogRotator.java:124)
br
hudson.model.Job.logRotate(Job.java:441)
br
hudson.model.Run.execute(Run.java:1751)
br
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
br
hudson.model.ResourceController.execute(ResourceController.java:88)
br
hudson.model.Executor.run(Executor.java:231)
br
/em
em
Executor
nbsp;
#0
nbsp;
for
nbsp;
1sp-slave12
nbsp;
:
nbsp;
executing
nbsp;
CONTEST_Technologies_Tests
nbsp;
#1568
br
hudson.model.Run.save(Run.java:1856)
br
hudson.plugins.changelog_history.ChangeLogHistoryRunListener.copyChangeLogs(ChangeLogHistoryRunListener.java:82)
br
hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:50)
br
hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:40)
br
hudson.model.listeners.RunListener.fireDeleted(RunListener.java:244)
br
hudson.model.Run.delete(Run.java:1447)
br
hudson.tasks.LogRotator.perform(LogRotator.java:124)
br
hudson.model.Job.logRotate(Job.java:441)
br
hudson.model.Run.execute(Run.java:1751)
br
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
br
hudson.model.ResourceController.execute(ResourceController.java:88)
br
hudson.model.Executor.run(Executor.java:231)
br
/em
{code}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick
updated JENKINS-22560
Deadlocked executors on slaves since 1.556
In the future please attach an actual thread dump (preferably as produced by jstack) as that would indicate the proximate cause of the deadlock, specifically which locks are being held.
Change By:
Jesse Glick
(10/Apr/14 1:55 PM)
Description:
CoulditbethatthechangeinJENKINS-22131iscausingdeadlocks?IfIdowngradeto1.555,thereisnoproblem,allversionsfrom1.556showthesamebehaviour:Moreandmoreexecutorsaredeadlocked.Tomeitlooksiftwoconcurrentjobsdosomethingwhichlockseachother.
{code:none}
Warning,thefollowingthreadsaredeadlocked:Executor#0for1sp-slave12:executingCONTEST_Technologies_Tests#1568,Executor#13for1sp-slave1:executingCONTEST_Technologies_Tests#1569Thethreadsareblockedin:
{code:none}
hudson.model.Run.save(Run.java:1856)(#1568)hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178)(#1569)
{code}
{code:none}
Executor#13for1sp-slave1:executingCONTEST_Technologies_Tests#1569hudson.model.AbstractBuild.getRunMixIn(AbstractBuild.java:178)jenkins.model.lazy.LazyBuildMixIn$RunMixIn.dropLinks(LazyBuildMixIn.java:336)hudson.model.AbstractBuild.dropLinks(AbstractBuild.java:193)hudson.model.RunMap.removeValue(RunMap.java:120)hudson.model.RunMap.remove(RunMap.java:86)jenkins.model.lazy.LazyBuildMixIn.removeRun(LazyBuildMixIn.java:216)hudson.model.AbstractProject.removeRun(AbstractProject.java:1002)hudson.model.AbstractProject.removeRun(AbstractProject.java:145)hudson.model.Run.removeRunFromParent(Run.java:1478)hudson.model.Run.delete(Run.java:1473)hudson.tasks.LogRotator.perform(LogRotator.java:124)hudson.model.Job.logRotate(Job.java:441)hudson.model.Run.execute(Run.java:1751)hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)hudson.model.ResourceController.execute(ResourceController.java:88)hudson.model.Executor.run(Executor.java:231)Executor#0for1sp-slave12:executingCONTEST_Technologies_Tests#1568hudson.model.Run.save(Run.java:1856)hudson.plugins.changelog_history.ChangeLogHistoryRunListener.copyChangeLogs(ChangeLogHistoryRunListener.java:82)hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:50)hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:40)hudson.model.listeners.RunListener.fireDeleted(RunListener.java:244)hudson.model.Run.delete(Run.java:1447)hudson.tasks.LogRotator.perform(LogRotator.java:124)hudson.model.Job.logRotate(Job.java:441)hudson.model.Run.execute(Run.java:1751)hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)hudson.model.ResourceController.execute(ResourceController.java:88)hudson.model.Executor.run(Executor.java:231){code}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Stefan Hirche commented on JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked We just moved to 1.558 and the issue still exists 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Dirk Kuypers commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 We are a .NET shop. I need more details how I could debug Java applications. I even asked on the user mailing list how to get a thread dump but got no answer. I was really glad when I could extract it from the bubble help of monitoring plugin's html page. So if I can provide more info just tell me what I should do. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick updated JENKINS-22560 Deadlocked executors on slaves since 1.556 Looks like Run.execute always acquired a lock on an older build via LogRotator and Run.delete. And using the Change Log History plugin means that when deleting an older build Jenkins also acquires a lock on a newer build, which is a bug in that plugin. And the change in 1.556 means that Run.delete could also (via dropLinks) acquire locks on both older and newer builds, which in combination with the bug in CLH means that deadlocks are possible. Change By: Jesse Glick (10/Apr/14 2:07 PM) Labels: deadlockregression threads Component/s: changelog-history 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 @bruce the Monitoring plugin can give some information but that is not in a great format for our purposes. jstack (a tool from the JDK) is ideal for diagnosing thread dumps. You can also navigate to /threadDump in a browser; or install the Support Core plugin and use the Support link to generate a complete diagnostic bundle. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick started work on JENKINS-22560 Deadlocked executors on slaves since 1.556 Change By: Jesse Glick (10/Apr/14 2:07 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22572) Master consumes excessive native memory if slave is taken on-line on demand
Raphaël UNIQUE created JENKINS-22572 Master consumes excessive native memory if slave is taken on-line on demand Issue Type: Bug Assignee: Unassigned Components: master-slave Created: 10/Apr/14 2:28 PM Description: we use jenkins Jenkins ver. 1.558 on a RHEL 6.4 platform (x86_64) 2 vcpu 6 Go RAM jdk 1.7.0_51 x64 JAVA OPTIONS: -Xmx1g -Xms1g -XX:MaxPermSize=256m we have 150 jobs and 20 slaves. all the slave are taken online on demand (and offline when not used). each time a build is lauched, the memory (of the master) used grow (and is not released). after many hours, the machine swap. the heap space and permegen space are correctly used. The native memory use increase Project: Jenkins Priority: Major Reporter: Raphaël UNIQUE 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 Also looks like this deadlock would only happen if the job were marked as being capable of concurrent builds. Not clear to me whether it requires the presence of CLH; looks like it might be possible (if less likely) without it. Note that the behavior of LogRotator for concurrent-capable jobs is not well defined: it might wind up deleting the wrong number of builds, since it does not hold a lock on a Run for the duration of its loop, but just does a one-off calculation of old build candidates. Probably harmless normally. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22570) On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection
dogfood commented on JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection Integrated in jenkins_main_trunk #3290 FIXED JENKINS-22570 On a configure screen that has multiple groups of radio buttons, clicking the apply button clears all but the last radio group selection (Revision 6f6dce4bef25846d6efcbf75e1a3aa50bbe77d77) Result = SUCCESS Stephen Connolly : 6f6dce4bef25846d6efcbf75e1a3aa50bbe77d77 Files : war/src/main/webapp/scripts/hudson-behavior.js 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22572) Master consumes excessive native memory if slave is taken on-line on demand
Raphaël UNIQUE updated JENKINS-22572 Master consumes excessive native memory if slave is taken on-line on demand Change By: Raphaël UNIQUE (10/Apr/14 2:29 PM) Description: weusejenkinsJenkinsver.1.558onaRHEL6.4platform(x86_64)2vcpu6GoRAMjdk1.7.0_51x64JAVAOPTIONS:-Xmx1g-Xms1g-XX:MaxPermSize=256mwehave150jobsand20slaves.alltheslavearetakenonlineondemand(andofflinewhennotused).eachtimeabuildis lauched launched ,thememory(ofthemaster)usedgrow(andisnotreleased).aftermanyhours,themachineswap.theheapspaceandpermegenspacearecorrectlyused.Thenativememoryuseincrease 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22572) Master consumes excessive native memory if slave is taken on-line on demand
Raphaël UNIQUE updated JENKINS-22572 Master consumes excessive native memory if slave is taken on-line on demand Change By: Raphaël UNIQUE (10/Apr/14 2:33 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22572) Master consumes excessive native memory if slave is taken on-line on demand
Raphaël UNIQUE updated JENKINS-22572 Master consumes excessive native memory if slave is taken on-line on demand Change By: Raphaël UNIQUE (10/Apr/14 2:41 PM) Description: weusejenkinsJenkinsver.1.558onaRHEL6.4platform(x86_64)2vcpu6GoRAMjdk1.7.0_51x64JAVAOPTIONS:-Xmx1g-Xms1g-XX:MaxPermSize=256mwehave150jobsand20slaves.alltheslavearetakenonlineondemand(andofflinewhennotused).eachtimeabuildislaunched,thememory(ofthemaster)usedgrow(andisnotreleased).aftermanyhours,themachineswap.theheapspaceandpermegenspacearecorrectlyused.Thenativememory use usedneverstopto increase 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-12234) Gradle Plugin incorrectly adds warning text to name of executed Javadoc task on console view
Jarek Bochniak
edited a comment on JENKINS-12234
Gradle Plugin incorrectly adds warning text to name of executed Javadoc task on console view
As a workaround you can install Jenkins Simple Theme Plugin https://wiki.jenkins-ci.org/display/JENKINS/Simple+Theme+Plugin and use following CSS snippet:
#console-outline-body a {
display: block;
padding: 5px 0;
width: 157px;
word-wrap: break-word;
}
it will reduce the width of the left column.
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-12234) Gradle Plugin incorrectly adds warning text to name of executed Javadoc task on console view
Jarek Bochniak
commented on JENKINS-12234
Gradle Plugin incorrectly adds warning text to name of executed Javadoc task on console view
As a workaround you can install Jenkins Simple Theme Plugin https://wiki.jenkins-ci.org/display/JENKINS/Simple+Theme+Plugin and use following CSS snippet:
#console-outline-body a {
display: block;
padding: 5px 0;
width: 157px;
word-wrap: break-word;
}
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
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-22571) Groovyscript executed on master even of parent build is tied to a slave
emanuelez commented on JENKINS-22571 Groovyscript executed on master even of parent build is tied to a slave Yes, the script runs on the master, but that's the way it's meant to be by design. One think that you could do is to expand your groovy script to connect to each node and discover devices. Another options would be to be inspired by Kohsuke's plugin (https://wiki.jenkins-ci.org/display/JENKINS/iOS+Device+Connector+Plugin) and adapt it to whatever device you are planning to test. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Dirk Kuypers commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 I generate the jobs via JOB-DSL plugin from template. So if it helps to start them non-concurrent I can give it a try after upgrading again. But I think concurrency is the key here and if it goes away after removing it from the jobs it wouldn't help much. Removing the CLH plugin is another option, but I would loose quite useful changelog history... Seems to be out of maintainance either. H. I think I will give the removal a try. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Jesse Glick commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 Or just go back to 1.555 (or whatever) temporarily; I hope the fix will be in 1.560. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-21009) Allow manual trigger
Ivan Boyko commented on JENKINS-21009 Allow manual trigger It's very good news. My boss is waiting for this feature! )) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
Dirk Kuypers commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 I am back to 1.555. But I was not sure if it is fixable in short time. Then I will change nothing and will be happy to run the ultimative test for you. I think this issue is not easily reproducible. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-18782) slave connection failed starting with 1.519
Andrew Kesterson commented on JENKINS-18782 slave connection failed starting with 1.519 I had the same issue, and I was able to get around it by upgrading my CentOS slave's Java to java-1.7.0-openjdk. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22142) No autocompletion and NullPointerException when using 'Copy Existing Job'
dogfood commented on JENKINS-22142 No autocompletion and NullPointerException when using Copy Existing Job Integrated in jenkins_main_trunk #3291 FIXED JENKINS-22142 Removed obsolete method. (Revision b264fa6e6af6df94db8d9eef86a2a650af125079) JENKINS-22142 Noting merge of #1179. (Revision b35f834b665178b52cbcb1b77600a8060509bbc6) Result = SUCCESS daniel-beck : b264fa6e6af6df94db8d9eef86a2a650af125079 Files : core/src/main/java/hudson/model/ViewDescriptor.java Jesse Glick : b35f834b665178b52cbcb1b77600a8060509bbc6 Files : core/src/main/java/hudson/model/ViewDescriptor.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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
SCM/JIRA link daemon commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/hudson/model/Run.java core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java http://jenkins-ci.org/commit/jenkins/a5d848bcec45100ca4f12303a8c619664f2eb945 Log: FIXED JENKINS-22560 Avoid deadlock by making AbstractBuild.runMixIn final. (Forgot that Run’s are unmarshalled in place after a special constructor is called, so there is no need for readResolve or other tricks.) Also calling RunListener.onDeleted outside of the Run lock to avoid problems with things like ChangeLogHistoryRunListener. Compare: https://github.com/jenkinsci/jenkins/compare/b35f834b6651...a5d848bcec45 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
SCM/JIRA link daemon resolved JENKINS-22560 as Fixed Deadlocked executors on slaves since 1.556 Change By: SCM/JIRA link daemon (10/Apr/14 3:40 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [monitoring] (JENKINS-21967) Node monitoring links are broken -- they don't use the proper root URL
Christian Höltje commented on JENKINS-21967 Node monitoring links are broken -- they dont use the proper root URL Yay! Pretty icons! It works! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Christian Höltje commented on JENKINS-21933 PermGen leaks No. Unfortunately. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Christian Höltje commented on JENKINS-21933 PermGen leaks Heather: We're using winstone. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Mark Waite commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder I think it should have been present in the repository reflog, unless the repository was wiped from one job to the next. At a minimum, that SHA1 should be somewhere in the Jenkins jobs directory, since the value needs to be remembered on disc somewhere. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-22571) Groovyscript executed on master even of parent build is tied to a slave
Anton Lundin commented on JENKINS-22571 Groovyscript executed on master even of parent build is tied to a slave It would feel more logical if the groovy script was executed as a part of the parent build, or at least on the same node as the parent build. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovyaxis] (JENKINS-22571) Groovyscript executed on master even of parent build is tied to a slave
emanuelez commented on JENKINS-22571 Groovyscript executed on master even of parent build is tied to a slave Well, it's a design choice in Jenkins, not in the plugin.There's not much I can do about it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-22427) Parameterized Remote Trigger Plugin fails when remote job waits for available executor
Tim Brown commented on JENKINS-22427 Parameterized Remote Trigger Plugin fails when remote job waits for available executor It looks like the root issue is that we are not getting a response from the REST API. This is because until the build get's an executor it won't have a REST API page. whenw e try and call the page we get a null or response. There is an update coming for the JSON issue you're seeing, thanks to @scotthains, which will likely fix your issue. I think this should work because getBuildStatus method takes a null response (from sendHTTPCall) to mean the build has not yet started - the problem with this though is that this means if someone cancels the job before it gets an executor the Remote trigger plugsdsdin will wait indefinitely. The best way I can see to solve this is to try and get Jenkins Core to give jobs an API page before they get an executor. I'm not sure how easy that would be as, if I remember correctly, the job is a different class of object after it gets and executor and before. Did you check with the link Maurice posted? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history] (JENKINS-22560) Deadlocked executors on slaves since 1.556
dogfood commented on JENKINS-22560 Deadlocked executors on slaves since 1.556 Integrated in jenkins_main_trunk #3292 FIXED JENKINS-22560 Avoid deadlock by making AbstractBuild.runMixIn final. (Revision a5d848bcec45100ca4f12303a8c619664f2eb945) Result = SUCCESS Jesse Glick : a5d848bcec45100ca4f12303a8c619664f2eb945 Files : core/src/main/java/hudson/model/AbstractBuild.java core/src/main/java/jenkins/model/lazy/LazyBuildMixIn.java changelog.html core/src/main/java/hudson/model/Run.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Mihails Strasuns commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Ok, we have done more detailed investigation and here are new findings: faulty hash is hash of merge commit created by GitHub automatically from one of older builds (before force push) problem manifests when using build configurations: in global build instance description correct hashes are used, but configuration-specific consoles still try to checkout the old one it is still unclear how to get PR in that state but once it gets there, it is stuck always trying to checkout same hash in configuration 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22573) SCM Sync Stops working
Jay Beeckman created JENKINS-22573 SCM Sync Stops working Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 10/Apr/14 5:21 PM Description: I think it's related to JENKINS-22199, but the SCM Sync stopped working. Says ERROR and when you click details, it gives the following stack trace: Passing user name builder and password you entered FAILED: svn: E175002: OPTIONS x failed org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/QA/Jenkins failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:2285) at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:2230) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.marvelution.hudson.plugins.apiv2.servlet.filter.HudsonAPIV2ServletFilter.doFilter(HudsonAPIV2ServletFilter.java:115) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at
[JIRA] [github] (JENKINS-22537) Seemingly random failures of GitHub plugin PR builder
Mihails Strasuns commented on JENKINS-22537 Seemingly random failures of GitHub plugin PR builder Is there any way to check parameters / env vars for configuration job? Using `export` in job script itself does not help because failed checkout happens before it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-20248) OpenID Plugin redirects REST API requests also
Yar n commented on JENKINS-20248 OpenID Plugin redirects REST API requests also so old bug and no activity? sucks((( 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [view-job-filters] (JENKINS-22574) Hide/Disable the built-in filters
Christian Höltje created JENKINS-22574 Hide/Disable the built-in filters Issue Type: Bug Assignee: Jacob Robertson Components: view-job-filters Created: 10/Apr/14 6:09 PM Description: The default view/job filters are useless compared to your awesome plugin. Can you disable the default filters in any way? Or give them an id attribute so CSS can be used to disable them? Ciao! Project: Jenkins Priority: Major Reporter: Christian Höltje 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22436) IsPossible to get IP address of newly created vms as environment variable/build variable
steverdavidson commented on JENKINS-22436 IsPossible to get IP address of newly created vms as environment variable/build variable Hi, thanks. I had created a short script to get this, but environment variable will be nicer. thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-22575) Plot loses data points for expired jobs
Kevin German created JENKINS-22575 Plot loses data points for expired jobs Issue Type: Bug Affects Versions: current Assignee: Kevin German Components: plot Created: 10/Apr/14 6:21 PM Description: When a job is configured to Discard Old Builds and the Plot "Number of builds to include" is greater than "Max # of builds to keep." The plot will drop data points for expired builds. This functionality that existed in previous versions of the plugin was lost in the fix for JENKINS-4934. Project: Jenkins Priority: Minor Reporter: Kevin German 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-21319) Provide retry option to Android-emulator plugin when the emulator fails to boot
Sam Xiao commented on JENKINS-21319 Provide retry option to Android-emulator plugin when the emulator fails to boot +1 for this feature 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
