[JIRA] [batch-task] (JENKINS-18507) some command can't exit in the execute windows batch command (praqma case 9630)
dzy dzy commented on JENKINS-18507 some command cant exit in the execute windows batch command (praqma case 9630) when it taked 30minutes,the job can't stop so i canceld, you can see "Build was aborted" ,but it taked less than 3 seconds in cmd model. 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/groups/opt_out.
[JIRA] [gui] (JENKINS-18614) Config screen loading dialog permanently blocks config
Matthew Riley created JENKINS-18614 Config screen loading dialog permanently blocks config Issue Type: Bug Assignee: Unassigned Attachments: config_screen_blocked.png Components: gui Created: 04/Jul/13 6:23 AM Project: Jenkins Priority: Major Reporter: Matthew Riley 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/groups/opt_out.
[JIRA] [gui] (JENKINS-18614) Config screen loading dialog permanently blocks config
podskalsky commented on JENKINS-18614 Config screen loading dialog permanently blocks config I have the same blocking point with the new 1.521 !!! 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
podskalsky updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: podskalsky (04/Jul/13 6:39 AM) Priority: Major Blocker Component/s: core 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
podskalsky updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: podskalsky (04/Jul/13 6:39 AM) Affects Version/s: current Environment: 1.521-solaris10 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/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
Geoff Cummings created JENKINS-18616 Build with paramters using wrong url Issue Type: Bug Affects Versions: current Assignee: takeshi ito Components: call-remote-job Created: 04/Jul/13 6:59 AM Description: When calling a build with paramters you need to use the following url: http://server/job/myjob/buildWithParameters?PARAMETER=Value currently it is using http://server/job/myjob/build?PARAMETER=Value Project: Jenkins Priority: Major Reporter: Geoff Cummings 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18609) Triggers two mails: UNSTABLE and REGRESSION
Stéphane Bruckert started work on JENKINS-18609 Triggers two mails: UNSTABLE and REGRESSION Change By: Stéphane Bruckert (04/Jul/13 6:58 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
Geoff Cummings commented on JENKINS-18616 Build with paramters using wrong url Information from jenkins wiki: https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+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/groups/opt_out.
[JIRA] [core] (JENKINS-18528) ruby plugins cannot work on Jenkins 1.519+
Yuu Yamashita edited a comment on JENKINS-18528 ruby plugins cannot work on Jenkins 1.519+ #88 has been merged to fix this problem. It is a simple workaround that explodes WEB-INF/lib/classes.jar into WEB-INF/classes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18578) Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable
Andréas Berg updated JENKINS-18578 Default jar cache location is hardcoded to ~/.jenkins/cache/jars and not configurable Change By: Andréas Berg (04/Jul/13 7:10 AM) Description: Thedefaultjarcachelocationisnowhardcodedto~/.jenkins/cache/jarswhichisareallybadideaforabigproductionenvironmentwithnetworkedhomedirectoriesandmultipleaccountsrunningslaves.Thisbehaviourwasintroducedwiththiscommit:https://github.com/jenkinsci/remoting/commit/b5145a06876f4390ef3229d70fa5a7edf0739daeThiscachelocationneedstobeconfigurable.Abonuswouldbeifpermissionswithinitwerehandledinawaythatsupports multi multiple accountsusingit.Thatmightbethecasealreadythough. Wevetriedtoputaworkaroundinplacebydefining-Duser.hometojavabutthataffectsotherthingstooandevenwhendoneformasterandeveryslaveseperatelyIamnotsureifitsolvestheproblementirely. 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/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18528) ruby plugins cannot work on Jenkins 1.519+
Yuu Yamashita updated JENKINS-18528 ruby plugins cannot work on Jenkins 1.519+ Change By: Yuu Yamashita (04/Jul/13 7:12 AM) Component/s: core 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/groups/opt_out.
[JIRA] [ruby-runtime] (JENKINS-18528) ruby plugins cannot work on Jenkins 1.519+
Yuu Yamashita closed JENKINS-18528 as Fixed ruby plugins cannot work on Jenkins 1.519+ Change By: Yuu Yamashita (04/Jul/13 7:13 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
Andréas Berg commented on JENKINS-18614 Config screen loading dialog permanently blocks config I encountered this as well and narrowed it down a bit. Disabling the envinject plugin fixes the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
Andréas Berg updated JENKINS-18614 Config screen loading dialog permanently blocks config Change By: Andréas Berg (04/Jul/13 7:23 AM) Component/s: envinject 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
Björn Pedersen commented on JENKINS-18614 Config screen loading dialog permanently blocks config Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-18595? 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
Andréas Berg commented on JENKINS-18614 Config screen loading dialog permanently blocks config In my case, yes, its a duplicate of that 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/groups/opt_out.
[JIRA] [testlink] (JENKINS-18188) When connecting to TestLink, finding error ClassCastException
stephane Buisson commented on JENKINS-18188 When connecting to TestLink, finding error ClassCastException The same for me Jenkins - 1.5.0 Testlink - 1.9.5 Plugin testlink - 3.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
stanislav bashkirtsev commented on JENKINS-18614 Config screen loading dialog permanently blocks config Guys, do you run system tests before doing a new release? Again the very basic feature works badly.. 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/groups/opt_out.
[JIRA] [testlink] (JENKINS-15937) TestLink Plugin prevents Jenkins from parsing Jobs
stephane Buisson commented on JENKINS-15937 TestLink Plugin prevents Jenkins from parsing Jobs Bug confirmed with Jenkins 1.5.0 and Testlink plugin 3.1.2 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances
Oleg Nenashev commented on JENKINS-18583 [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances Hello, issue is being reproduced for one Perforce SCM as well 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-18617) When checkout depth is files, changes in un checked out files deeper in the tree still trigger a build
Timor Raiman created JENKINS-18617 When checkout depth is files, changes in un checked out files deeper in the tree still trigger a build Issue Type: Bug Assignee: Unassigned Components: subversion Created: 04/Jul/13 9:48 AM Description: A build step needs to monitor a repository for changes at root level only (depth=files). Contrary to what is expected, the svn plugin does not distinguish modifications to files deeper in the tree from local changes at depth=files, and a build is triggered for every change in the entire repository (almost every poll, as this is a large project with many teams) The expected behaviour could be achieved by parsing the output of "svn status --show-updates --depth=files", excluding the entry for "." (I realize that polling might be running from the master, where no workspace is available and it could be not easy to implement this kind of action...) Project: Jenkins Priority: Major Reporter: Timor Raiman 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/groups/opt_out.
[JIRA] [core] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
Guy Sheffer commented on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring Getting this with Jenkins on Debian ver 1.521 . Is there any workaround? 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/groups/opt_out.
[JIRA] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse resolved JENKINS-18456 as Wont Fix Jenkins Job Current Log Status ( our case 9603) I'm resolving this issue with reference to robjohncox's answer on stackoverflow. It turns our the the big-unsplitable build is run by FinalBuilder, which basically makes it the responsibility of FinalBuilder to give you the insight you need. To use Jenkins, you should let Jenkins execute the jobs rather than FinalBuilder, then you would be able to see what your looking for in the console output - as the job executes. Change By: Lars Kruse (04/Jul/13 11:04 AM) Status: Open Resolved Resolution: WontFix 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/groups/opt_out.
[JIRA] [nested-view] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Hannes Kogler commented on JENKINS-14546 Regular users (others than admin) cant see any nested-views (other than the default one) with role-based authorization strategy activated We have the same problems when using both of the plugins. Jenkins v1.518 Role-based Authorization Strategy Plugin v1.1.2 Nested View Plugin v1.10 regardless if the jobs of the nested views have jobs or not. Users with standard permissions cannot access the nested Views and only see those jobs through the All view. Would be great if anybody fixes this, because I don't want to grant every user the admin permissions to see all views.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Avi Rosenfeld reopened JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Resolving it by saying its a Final Builder responsibility isn't a solution ... It doesn't have to be Final Builder job. Think its a job that's builing a Solution with lots of projects. I want to know which project is being currently compiled. How to do that? I wrote two ideas above. why not trying to implement one of them? Change By: Avi Rosenfeld (04/Jul/13 11:09 AM) Resolution: WontFix 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/groups/opt_out.
[JIRA] [build-timeout] (JENKINS-18618) Build Timeout Plugin configuration interface shows all sub options
Thomas P
created JENKINS-18618
Build Timeout Plugin configuration interface shows all sub options
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Attachments:
Presse-papiers-1.png
Components:
build-timeout
Created:
04/Jul/13 11:15 AM
Description:
When displaying configuration interface of this plugin, all sub options are displayed.
For example sub options of "Likely Stuck" ("Fail the build" and "Writing the build description") should only be displayed when this option is selected.
Instead, when they are all displayed.
Note that if you change the option from ("Likely stuck" to "absolute") the sub options disappear.
I suppose that the JS code is OK while the server code is not doing it's job
This has been broken since we installed this plugin (January?)
Environment:
Firefox
Project:
Jenkins
Priority:
Minor
Reporter:
Thomas P
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/groups/opt_out.
[JIRA] [core] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
Julian Dreissig commented on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring Same over here. Works fine again after downgrading to 1.520. 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/groups/opt_out.
[JIRA] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Lars Kruse commented on JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Sorry for shutting you down too soon. It looks like you are trying to implement a divide-and-conquer strategy for a huge job that's controlled by FinalBuilder. The easiest way to have Jenkins break it down, is to hand the responsibility of the execution over to Jenkins. Your first suggestion, to add a prefix to each line in the console output based on the current project being compiled makes me think that in order to do that Jenkins would have to know what project is being compiled - but since your using FinalBuilder - which is then creating the output for that particular compilation, makes me think that it's really FinalBuilder that should do the pre-fix. Where does the Project name you want in the pre-fix come from? You second suggestion, to update the job description during runtime with the project being build would require a plugin, that knew the name of the project - But isn't it FinalBuilder who knows what is currently being build? The way I see it, wrapping it all up in one-big-FinalBuilder job is really what needs to be broken down. Maybe I'm missing your points. If you thing I am, then please throw some examples (screen shorts, logs, configurations) to clarify, what you are trying to achieve. 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/groups/opt_out.
[JIRA] [core] (JENKINS-12051) Latest jenkins running on tomcat prevents me from configuring
sogabe commented on JENKINS-12051 Latest jenkins running on tomcat prevents me from configuring @Guy, @Julian See JENKINS-18595 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/groups/opt_out.
[JIRA] [core] (JENKINS-18614) Config screen loading dialog permanently blocks config
sogabe resolved JENKINS-18614 as Duplicate Config screen loading dialog permanently blocks config Change By: sogabe (04/Jul/13 11:45 AM) Status: Open 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/groups/opt_out.
[JIRA] [ruby] (JENKINS-18619) readlink not provided by default on Solaris
Laurent Sauvage created JENKINS-18619 readlink not provided by default on Solaris Issue Type: Bug Affects Versions: current Assignee: vivekp Components: ruby Created: 04/Jul/13 11:58 AM Description: readlink is not provided by default on Solaris. Notice java 7 now provides an API to deal with symbolic links. Here is the stack trace obtained on solaris: java.io.IOException: Cannot run program "readlink" (in directory "/opt/instance/SUNWappserver/domains/dom-hudson/config/."): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) at java.lang.Runtime.exec(Runtime.java:593) at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:61) at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51) at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196) at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160) at hudson.Util.resolveSymlink(Util.java:1236) at hudson.Util.resolveSymlinkToFile(Util.java:1166) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:346) at hudson.model.Run.init(Run.java:294) at hudson.model.AbstractBuild.init(AbstractBuild.java:182) at hudson.model.Build.init(Build.java:103) at hudson.model.FreeStyleBuild.init(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor313.newInstance(Unknown Sourc e) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC onstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1120) at hudson.model.AbstractProject$1.create(AbstractProject.java:317) at hudson.model.AbstractProject$1.create(AbstractProject.java:315) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap .java:667) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap .java:629) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunM ap.java:368) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:1020) at hudson.model.Job.getBuildHealthReports(Job.java:980) at hudson.model.Job.getBuildHealth(Job.java:945) Environment: Solaris 10 x86 Project: Jenkins Priority: Minor Reporter: Laurent Sauvage 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
[JIRA] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3
Bakkiaraj Murugesan commented on JENKINS-18559 Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3 @ChrisWoZny, Thanks for the update. I did update from Jenkins , I overlook the release notes. 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/groups/opt_out.
[JIRA] [logging] (JENKINS-18456) Jenkins Job Current Log Status ( our case 9603)
Avi Rosenfeld commented on JENKINS-18456 Jenkins Job Current Log Status ( our case 9603) Let's say it's not FinalBuilder Let's say its just a VS compilation of a Solution that containcs lots of projects. You asked where the PROJECT NAME comes from. Well, DURING the compilation and the log generation, if Jenkins finds the string (for example): - Rebuild All started: Project: PROJ1 , Configuration: Release x64 -- Now Jenkins knows that PROJ1 is being compiled now. and the PROJECT NAME will be PROJ1 Now you can update the job desription with a flashing PROJECT NAME. 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/groups/opt_out.
[JIRA] [coverity] (JENKINS-18559) Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3
Bakkiaraj Murugesan closed JENKINS-18559 as Fixed Coverity plugin 1.2.5 is not working with Coverity IM 5.5.3 Since the latest version of the coverity plugin only works with Coverity Connect and this behaviour is documented. So This is not a bug really. This ticket can be closed. Change By: Bakkiaraj Murugesan (04/Jul/13 12:05 PM) Status: Open Closed 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/groups/opt_out.
[JIRA] [core] (JENKINS-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
Bakkiaraj Murugesan commented on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start I have updated to latest ruby-runtime (via jenkins plugin management page) but still jenkins is not starting. 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/groups/opt_out.
[JIRA] [ci-game] (JENKINS-5710) Publish game points in email
aaditya sood commented on JENKINS-5710 Publish game points in email This would be lovely. If the plugin could publish to the global variables, then I could use it in the email-ext jelly plugin. Any hopes? 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/groups/opt_out.
[JIRA] [core] (JENKINS-18620) Configure tag freezes with Firefox and Chrome
Jens Hausherr created JENKINS-18620 Configure tag freezes with Firefox and Chrome Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 04/Jul/13 12:18 PM Description: The job configuration dialog freezes at the grey "loading" overlay with Firefox and Chrome. It works (at least) with Opera, so I guess it is unlikely to be related to a plugin (like in one older ticket). Environment: Mac OS X 10.7.5 Firefox 22.0 Chrome 27.0.1453.116 Opera 12.15 (Build 1748) Project: Jenkins Priority: Critical Reporter: Jens Hausherr 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
pancake
commented on JENKINS-13835
E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Greg, the problem is indeed on the Jenkins side. Not necessarily on Jenkins server itself. Basically speaking this glitch occurs when svn client (Jenkins server or slave) stops communicating to svn server for unexpectedly long time (KeepAlive). In our Jenkins deployment we saw that svn checkout on slave consumed 100% of one CPU core, i.e. checkout speed was limited by per-core performance of Jenkins node. So, to workaround the alleviate the situation you can:
See if CPU/disk performance is a bottleneck for svn checkout and upgrade the hardware of relevant Jenkins node.
Tune Jenkins GC options. We didn't check, but it's very likely that delays are due to GC.
Increase KeepAlive on svn server. You'll probably want to setup a dedicated svn mirror for Jenkins and set KeepAlive on that mirror only. That's not good to have insanely big KeepAlive on a publicly available servers.
Note that we're using 1.6 WC format on Jenkins ("Manage Jenkins" "Configure System" "Subversion"). I don't quite remember what exactly bug made us downgrade 1.7 - 1.6 and not even sure if it's still there. But you can try it if the above doesn't help.
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/groups/opt_out.
[JIRA] [plugin] (JENKINS-16792) Debian package build plugin : Unknown option: distributor
andy aspell-clark commented on JENKINS-16792 Debian package build plugin : Unknown option: distributor Does anyone have a ETA for this fix?? I'm getting the "Unknown option: distributor" error on jenkins 1.521 or is this plugin dead? 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/groups/opt_out.
[JIRA] [core] (JENKINS-18620) Configure tag freezes with Firefox and Chrome
Sylvain Benner commented on JENKINS-18620 Configure tag freezes with Firefox and Chrome I've got the same issue while upgrading from 1.519. 1.519 - OK 1.520 - OK 1.521 - KO We have a bunch of plugins installed, do we have to list all of them to track the issue ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18620) Configure tab freezes with Firefox and Chrome
Jens Hausherr updated JENKINS-18620 Configure tab freezes with Firefox and Chrome Change By: Jens Hausherr (04/Jul/13 1:18 PM) Summary: Configure tag tab freezeswithFirefoxandChrome 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/groups/opt_out.
[JIRA] [core] (JENKINS-18621) Weird IllegalArgumentException prevents SVN polling from working
Pawel Gronkiewicz created JENKINS-18621 Weird IllegalArgumentException prevents SVN polling from working Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Attachments: ERROR.txt Components: core, maven, pollscm Created: 04/Jul/13 1:25 PM Description: My job stopped to poll changes from SVN some time ago - it all runs properly when started manually or by timer, but it won't poll when a change occurs in repository. I have tried tweaking with Maven installations, cloning the job etc. Other jobs using Git do not have this problem. SVN polling shows: ERROR: Failed to record SCM polling for hudson.maven.MavenModuleSet@eafaabescmTest java.lang.IllegalArgumentException: Null value not allowed as an environment variable: M2_HOME at hudson.EnvVars.put(EnvVars.java:172) at hudson.tasks.Maven$MavenInstallation.buildEnvVars(Maven.java:492) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:173) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1523) at hudson.model.AbstractProject.poll(AbstractProject.java:1448) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) When I get into job configuration in Maven build section I get "ERROR" below Root POM line. I am attaching the exact ERROR message as a separate file. Environment: Jenkins 1.517 Project: Jenkins Priority: Major Reporter: Pawel Gronkiewicz 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/groups/opt_out.
[JIRA] [core] (JENKINS-18620) Configure tab freezes with Firefox and Chrome
sogabe resolved JENKINS-18620 as Duplicate Configure tab freezes with Firefox and Chrome Change By: sogabe (04/Jul/13 1:24 PM) Status: Open 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/groups/opt_out.
[JIRA] [compact-columns] (JENKINS-18622) Broken description tool-tip display in Job Name w/ Options
Andréas Berg created JENKINS-18622 Broken description tool-tip display in Job Name w/ Options Issue Type: Bug Affects Versions: current Assignee: Jacob Robertson Components: compact-columns Created: 04/Jul/13 2:22 PM Description: When description is not set for a job and Job Name w/ Options is used with a description tool-tip, the description of previously moused over job is re-used. Environment: Windows 7 with Chrome browser Project: Jenkins Priority: Minor Reporter: Andréas Berg 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/groups/opt_out.
[JIRA] [read-only-configurations] (JENKINS-18623) Viewing the Read Only for Global configuration or any Job results in a NPE
Andrei Ababei created JENKINS-18623 Viewing the Read Only for Global configuration or any Job results in a NPE Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: read-only-configurations Created: 04/Jul/13 2:34 PM Description: Viewing the Read Only for Global configuration or any Job fails with the following exception java.lang.NullPointerException at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.jenkinsci.plugins.readonly.JenkinsConfiguration.transformToReadOnly(JenkinsConfiguration.java:106) at org.jenkinsci.plugins.readonly.JenkinsConfiguration.doIndex(JenkinsConfiguration.java:90) 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:297) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:155) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:381) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:684) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
takeshi ito started work on JENKINS-18616 Build with paramters using wrong url Change By: takeshi ito (04/Jul/13 2:36 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/groups/opt_out.
[JIRA] [call-remote-job] (JENKINS-18616) Build with paramters using wrong url
takeshi ito resolved JENKINS-18616 as Fixed Build with paramters using wrong url fixed https://github.com/jenkinsci/call-remote-job-plugin/commit/022760621fe8dac28ba1c51f43fff3eff90bed83#src/main/java/org/ukiuni/callOtherJenkins/CallOtherJenkins/JenkinsRemoteIF.java Change By: takeshi ito (04/Jul/13 2:38 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [read-only-configurations] (JENKINS-18623) Viewing the Read Only for Global configuration or any Job results in a NPE
Alex Earl assigned JENKINS-18623 to Unassigned Viewing the Read Only for Global configuration or any Job results in a NPE Change By: Alex Earl (04/Jul/13 2:54 PM) Assignee: AlexEarl 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-18607) Xvfb plugin doesn't work on matrix jobs with slaves on the same machine
SCM/JIRA link daemon commented on JENKINS-18607 Xvfb plugin doesnt work on matrix jobs with slaves on the same machine Code changed in jenkins User: takeuchi Path: pom.xml src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java http://jenkins-ci.org/commit/xvfb-plugin/2f536ed7432d270b9726dd3a3b1c6905cc92b3d6 Log: JENKINS-18607 Fixed problems with concurrent when launching Xvfb 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/groups/opt_out.
[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Ryan Smith commented on JENKINS-12983 Redundat syncs when using matrix jobs This feature causes my builds to fail sporadically. Most of my jobs are set up to use the same custom workspace. So when this second sync occurs on top of a running job, it starts modifying the workspace while building. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18624) Partial Workspace Wipe
wim jongman created JENKINS-18624 Partial Workspace Wipe Issue Type: Improvement Assignee: Unassigned Components: core Created: 04/Jul/13 3:56 PM Description: It would be nice if parts of the workspace could be wiped. Sometimes I only want to wipe some target directories and keep the sources. There are other uses cases where this could be handy. Environment: All Project: Jenkins Priority: Major Reporter: wim jongman 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/groups/opt_out.
[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Chris Withers commented on JENKINS-12983 Redundat syncs when using matrix jobs Ryan: yep, that was my experience too. The workaround is to use the Tie Parent plugin, and tie all matrix parent jobs to a "sacrificial node", that node should do nothing else other than run matrix parent jobs. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances
Oleg Nenashev assigned JENKINS-18583 to Oleg Nenashev [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances Change By: Oleg Nenashev (04/Jul/13 6:21 PM) Assignee: RobPetti OlegNenashev 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-18607) Xvfb plugin doesn't work on matrix jobs with slaves on the same machine
SCM/JIRA link daemon commented on JENKINS-18607 Xvfb plugin doesnt work on matrix jobs with slaves on the same machine Code changed in jenkins User: takeuchi Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java src/main/java/org/jenkinsci/plugins/xvfb/XvfbDisplayAllocator.java src/main/resources/org/jenkinsci/plugins/xvfb/Messages.properties src/main/resources/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper/config.jelly http://jenkins-ci.org/commit/xvfb-plugin/b67a13e71f768a06da573f6ff82662e009d1bdf5 Log: JENKINS-18607 Fixed problems with concurrent when launching Xvfb 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances
Oleg Nenashev started work on JENKINS-18583 [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances Change By: Oleg Nenashev (04/Jul/13 6:21 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/groups/opt_out.
[JIRA] [core] (JENKINS-18621) Weird IllegalArgumentException prevents SVN polling from working
kutzi commented on JENKINS-18621 Weird IllegalArgumentException prevents SVN polling from working The error says that you have somehow managed to have a 'null' value for M2_HOME. Have you checked the environment variable definitions in 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/groups/opt_out.
[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Thomas Fields commented on JENKINS-12983 Redundat syncs when using matrix jobs So any ideas when this improvement might be implemented? Seems like its something jenkins users want to see fixed. Tom 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances
SCM/JIRA link daemon commented on JENKINS-18583 [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkinsci/plugins/perforce/DepotType.java src/main/java/hudson/plugins/perforce/PerforceSCM.java src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly http://jenkins-ci.org/commit/perforce-plugin/21f91d6ae68ea120985876e8a6116a0c1dd5ce62 Log: PerforceSCM.DataBoundConstructor - Added "proof-of-concept" implementation of the bugfix. Related issue: https://issues.jenkins-ci.org/browse/JENKINS-18583 Signed-off-by: Oleg Nenashev nenas...@synopsys.com 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances
Oleg Nenashev commented on JENKINS-18583 [MultipleSCM integration] - View Map is empty in case of multiple Perforce SCM instances Hello Robert, Just for review… Pull request: https://github.com/jenkinsci/perforce-plugin/pull/33 Proposed fix resolves issue with instantiation of Perforce plugin in the MultipleSCM’s hetero list. Issue was in the incomplete handling of data in the DataBoundConstructor. If fix is applicable, I’ll modify unit tests and remove temporary stuff from the *.pom. Then, we will be able to merge pull request. 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/groups/opt_out.
[JIRA] [core] (JENKINS-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
SCM/JIRA link daemon commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/lib/form/textarea/textarea.js http://jenkins-ci.org/commit/jenkins/059e6081d0be21a3a92d705c43c9e1f658347797 Log: FIXED JENKINS-18585 The earlier fix by @ssogabe broke the test. This fix corrects the problem properly. The reason this error happens with some plugins is that if there's an input field whose name is "on", then even after prototype.js extends an element object, "form.on" will refer to the input element, not the prototype.js function to add an event handler. 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/groups/opt_out.
[JIRA] [core] (JENKINS-8881) After Log Rolling, Pervious, Uncompressed Log File is Deleted But _Not_ Closed and its Disk Space Not Freed
evernat resolved JENKINS-8881 as Duplicate After Log Rolling, Pervious, Uncompressed Log File is Deleted But _Not_ Closed and its Disk Space Not Freed No response, so resolving as supposed duplicate of JENKINS-5784 Change By: evernat (04/Jul/13 8:20 PM) Status: Open 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-18215) [M2 Release Plugin] lock builds lack of inline documentation
teilo resolved JENKINS-18215 as Fixed [M2 Release Plugin] lock builds lack of inline documentation fixed in https://github.com/jenkinsci/m2release-plugin/commit/f5b043a105405948f564f887565bc5dae44a3b67 will be in 0.11.0 Change By: teilo (04/Jul/13 8:26 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18590) When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list
Steve Moyer updated JENKINS-18590 When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list Attaching the plugin config and the job config. In this example I would expect an email sent to defa...@example.com but instead jenkins will try and send an email to notenab...@example.com Change By: Steve Moyer (04/Jul/13 9:56 PM) Attachment: config.xml Attachment: hudson.plugins.emailext.ExtendedEmailPublishercopy.txt 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-18590) When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list
Alex Earl commented on JENKINS-18590 When you populate recipients on failure but disable failure emails, the address is used for first failure rather than the default list Please attach a build log as well. 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/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-18000) Sauce on Demand setting incorrect pass/fail status
Ross Rowe started work on JENKINS-18000 Sauce on Demand setting incorrect pass/fail status Change By: Ross Rowe (05/Jul/13 3:39 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-18000) Sauce on Demand setting incorrect pass/fail status
Ross Rowe commented on JENKINS-18000 Sauce on Demand setting incorrect pass/fail status Hi Scott, apologies for the delay in addressing this issue. I'm looking into it now, and should have a fix ready within the next day or so. 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/groups/opt_out.
[JIRA] [core] (JENKINS-17858) f:dropdownDescriptorSelector does not allow defaulting to specifig instance
irfan sayed updated JENKINS-17858 f:dropdownDescriptorSelector does not allow defaulting to specifig instance Change By: irfan sayed (05/Jul/13 4:02 AM) 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/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-18000) Sauce on Demand setting incorrect pass/fail status
SCM/JIRA link daemon commented on JENKINS-18000 Sauce on Demand setting incorrect pass/fail status Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandReportPublisher.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/dc3db0e64680354c9220e761d176a1e4bf938beb Log: JENKINS-18000 Ensure that pass/fail status is not set if the value already 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/groups/opt_out.
[JIRA] [core] (JENKINS-17695) error 500 after Delete Project
epikur2412 resolved JENKINS-17695 as Wont Fix error 500 after Delete Project After removing the Build Pipeline Plugin, the error disappeared. Change By: epikur2412 (05/Jul/13 5:43 AM) Status: Open Resolved Resolution: WontFix 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/groups/opt_out.
[JIRA] [artifactory] (JENKINS-18625) Artifactory Release: Mercurial SCM support
Dmitriy Shakhovkin created JENKINS-18625 Artifactory Release: Mercurial SCM support Issue Type: New Feature Assignee: yossis Components: artifactory Created: 05/Jul/13 5:53 AM Project: Jenkins Priority: Minor Reporter: Dmitriy Shakhovkin 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/groups/opt_out.
