[JIRA] [jobgenerator] (JENKINS-17730) Support for Custom Workspace
Marko Macek commented on JENKINS-17730 Support for Custom Workspace This seems to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [jobgenerator] (JENKINS-17895) job enabled status should be preserved
Marko Macek created JENKINS-17895 job enabled status should be preserved Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 08/May/13 7:48 AM Description: IMO, job status should be preserved when regenerating (at least for main job, if not all) Project: Jenkins Priority: Minor Reporter: Marko Macek This message is automatically generated by JIRA. 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] [jobgenerator] (JENKINS-17895) job enabled status should be preserved
Marko Macek commented on JENKINS-17895 job enabled status should be preserved Probably, main job should also start disabled, so things can be verified and maybe adjusted (schedule, nodes, ...) This message is automatically generated by JIRA. 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-17861) Providing Java-based SVN SCM provider
teilo resolved JENKINS-17861 as Won't Fix Providing Java-based SVN SCM provider The absolute last thing any plugin should do is change the behaviour of the build from what would be performed on the command line. If you want to use the pure Java provider you will need to configure it in your pom. Change By: teilo (08/May/13 7:56 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. 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] [concurrent-build] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov commented on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Do anybody know how to solve this problem? Any patch, 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] [concurrent-build] (JENKINS-9913) Concurrent builds getting batched/nodes not getting released when jobs are completed
Sergey Smirnov edited a comment on JENKINS-9913 Concurrent builds getting batched/nodes not getting released when jobs are completed Do anybody know how to solve this problem? Any patch, workaround...? I can't remove post build steps for the job This message is automatically generated by JIRA. 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] [clearcase] (JENKINS-17896) View gets deleted although view tag was not changed
Dirk Kuypers created JENKINS-17896 View gets deleted although view tag was not changed Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 08/May/13 8:24 AM Description: I faced a strange error yesterday evening when a project should produce its nightly setup. The CC plugin says: Removing view because the view tag of the job SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x doesn't match the current view tag SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x I just copy both view tags here again for clarity: SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x They look absolutely the same to me?!? I also have seen this error after rebooting the master due to Windows updates. This only happens with views on my master, rebooting a slave with snapshots does not affect jobs running there. If could help with some command line investigations – no problem. Running one of the command like the log suggests causes an error when issued by hand: C:\Users\sa_mu_1sp1cm-build>cleartool lsview -cview -s SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x cleartool: Error: Extra arguments: "SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x" Usage: lsview [-short | -long] [-host hostname [-quick]] [-properties [-full | -text_mode] | -age] [-region 'network-region-pattern'] [-cview | 'view-tag-pattern' ... -storage view-storage-pname ... -uuid view-uuid] Full Log of the job: 19:44:18 [EnvInject] - Loading node environment variables. 19:44:18 Building on master in workspace C:\Snapshots 19:44:18 [RS-PQA-3.2x] $ cleartool lsview -cview -s 19:44:18 SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:18 [Snapshots] $ cleartool lsview SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:18 SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x \\CONTEST-MASTER\ccstg_c\views\SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x.vws 19:44:18 [INFO] computeChangeLogBeforeCheckout = false 19:44:18 [INFO] computeChangeLogAfterCheckout = true 19:44:18 [Snapshots] $ cleartool lsview SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:18 SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x \\CONTEST-MASTER\ccstg_c\views\SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x.vws 19:44:18 [RS-PQA-3.2x] $ cleartool lsview -cview -s 19:44:18 SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:28 Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information 19:44:28 Removing view because the view tag of the job SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x doesn't match the current view tag SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:28 Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information 19:44:28 [Snapshots] $ cleartool rmview -force RS-PQA-3.2x 19:44:28 Removing references from VOB "\ts89xy_cm" ... 19:44:28 Removed references to view "C:\Snapshots\RS-PQA-3.2x" from VOB "\ts89xy_cm". 19:44:28 Removing references from VOB "\contest_sw" ... 19:44:29 Removed references to view "C:\Snapshots\RS-PQA-3.2x" from VOB "\contest_sw". 19:44:29 Removing references from VOB "\contest_bin" ... 19:44:29 Removed references to view "C:\Snapshots\RS-PQA-3.2x" from VOB "\contest_bin". 19:44:29 Removing references from VOB "\contest_sw_cmwperf" ... 19:44:29 Removed references to view "C:\Snapshots\RS-PQA-3.2x" from VOB "\contest_sw_cmwperf". 19:44:49 Removing the job view tag because we detected that it already exists. 19:44:49 [Snapshots] $ cleartool rmview -force -tag SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:49 cleartool: Error: View tag not found: "SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x". 19:44:49 cleartool: Error: Unable to remove view "SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x". 19:44:49 FATAL: Base ClearCase failed. exit code=1 19:44:49 [Snapshots] $ cleartool rmtag -view SA_MU_1SP1CM-BUILD_CONTEST-MASTER_RS-PQA-3.2x 19:44:49 cleartool: Err
[JIRA] [update-center] (JENKINS-13153) "Upgrade Automatically" does not seem to work on Windows
Dirk Heinrichs commented on JENKINS-13153 "Upgrade Automatically" does not seem to work on Windows Maybe this functionality should generaly be disabled on Windows? This message is automatically generated by JIRA. 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] [xunit] (JENKINS-6200) xunit/cppunit causes exception when trying to scan a non-accessible directory
Wojciech Rynczuk reopened JENKINS-6200 xunit/cppunit causes exception when trying to scan a non-accessible directory The plugin (v.1.54) fails and returns: [xUnit] [ERROR] - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read C:\XXX\workspace\generatedJUnitFiles\JUnit\TEST-507924303.xml When it's trying to parse unrecognized xml format or the xml file is incomplete (which might happen in our case sometimes). E.g. one of the xml files that caused the problem was: It would be great if it wouldn't assert on broken xml files and generated some nice output showing this misbehavior. Change By: Wojciech Rynczuk (08/May/13 9:47 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xunit] (JENKINS-17884) Support CTest XML format
Gregory Boissinot commented on JENKINS-17884 Support CTest XML format Thanks for your suggestion. If you provide some result files and an XSLT for a JUnit output, I'll integrate it into the xUnit pluign. This message is automatically generated by JIRA. 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] [concurrent-build] (JENKINS-17897) Subversion checkout fails occasionally when concurrent builds execute
Chris Withers created JENKINS-17897 Subversion checkout fails occasionally when concurrent builds execute Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: concurrent-build, subversion Created: 08/May/13 10:42 AM Description: Nicely summed up here: http://jenkins.361315.n4.nabble.com/subversion-plugin-not-for-concurrent-builds-td4636014.html A race condition or two exist where two concurrent builds both try to delete svnexternals.txt from the project root. Surely this file belongs in the workspace for the particular build? When this happens you get: java.io.IOException: Unable to delete /var/lib/jenkins/jobs//svnexternals.txt at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:178) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:700) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Project: Jenkins Priority: Major Reporter: Chris Withers This message is automatically generated by JIRA. 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] [git] (JENKINS-17898) Git plugin: tags & triggers don't work as expected
Ferry Huberts
created JENKINS-17898
Git plugin: tags & triggers don't work as expected
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
08/May/13 11:06 AM
Description:
I trigger Jenkins from a post-receive hook on my git server:
curl -s "${jenkinsUrl}/git/notifyCommit?url="">
When I push a tag on the latest commit that Jenkins has already built, no new built is started.
Since the commit sha of the branch to build doesn't change that's logical.
However, since I use 'git describe' to provide traceability of my artifacts, this is not what I'd like to happen: the 'git describe' output actually changes because of the new tag.
To fix this, the git plugin must not only look at the commit sha but also check the tags on the latest commit that it has built; if there is a new/changed tag on that commit, a new build has to be started.
Environment:
Fedora 17 64bit
Project:
Jenkins
Priority:
Major
Reporter:
Ferry Huberts
This message is automatically generated by JIRA.
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] [git] (JENKINS-17898) Git plugin: tags & triggers don't work as expected
Ferry Huberts
updated JENKINS-17898
Git plugin: tags & triggers don't work as expected
Change By:
Ferry Huberts
(08/May/13 11:07 AM)
Description:
I trigger Jenkins from a post-receive hook on my git server: curl -s "${jenkinsUrl}/git/notifyCommit?url="">When I push a tag on the latest commit that Jenkins has already built, no new
built
build
is started.Since the commit sha of the branch to build doesn't change that's logical.However, since I use 'git describe' to provide traceability of my artifacts, this is not what I'd like to happen: the 'git describe' output actually changes because of the new tag.To fix this, the git plugin must not only look at the commit sha but also check the tags on the latest commit that it has built; if there is a new/changed tag on that commit, a new build has to be started.
This message is automatically generated by JIRA.
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] [git] (JENKINS-17898) Git plugin: tags & triggers don't work as expected
Ferry Huberts
updated JENKINS-17898
Git plugin: tags & triggers don't work as expected
Change By:
Ferry Huberts
(08/May/13 11:08 AM)
Description:
I trigger Jenkins from a post-receive hook on my git server: curl -s "${jenkinsUrl}/git/notifyCommit?url="">When I push a
(annotated)
tag on the latest commit that Jenkins has already built, no new build is started.Since the commit sha of the branch to build doesn't change that's logical.However, since I use 'git describe' to provide traceability of my artifacts, this is not what I'd like to happen: the 'git describe' output actually changes because of the new tag.To fix this, the git plugin must not only look at the commit sha but also check the tags on the latest commit that it has built; if there is a new/changed tag on that commit, a new build has to be started.
This message is automatically generated by JIRA.
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] [other] (JENKINS-1878) Ability to move job to top of queue
Franz Hirschbeck commented on JENKINS-1878 Ability to move job to top of queue This feature would be very helpful for our scenario. It is really annoying if one has to either wait for other projects to be build first or need to stop them and thus breaking the usual code checking functionality of the build server. There are some situations like developing/debugging the build of the server itself or using the artifacts of the project as an urgent release where this feature would be really nice. Adding more slaves is reducing the problem but not really solving (at least for numSlaves < numProjects). This message is automatically generated by JIRA. 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] [git] (JENKINS-17899) Add support for Token Macro expansion to GIT plugin
stephenconnolly created JENKINS-17899 Add support for Token Macro expansion to GIT plugin Issue Type: New Feature Assignee: Nicolas De Loof Components: git Created: 08/May/13 12:22 PM Description: The GIT plugin currently only supports build parameter expansion and not the other tokens, leading to a dichotomy whereby it provides token-macro supported tokens but it will not resolve them. The most critical sign of this is where either slave local environment variables or folder level environment variables (when using the CloudBees Folders plugin) are not evaluated during SCM polling, and as such the polling never triggers... though there are other edge cases. 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/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-13288) Config history does not appear for certain jobs
Jesse Glick commented on JENKINS-13288 Config history does not appear for certain jobs Are your jobs inside folders by any chance? This message is automatically generated by JIRA. 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-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml
Marco Lenhardt created JENKINS-17900 subversion credentials are not stored in hudson.scm.SubversionSCM.xml Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 08/May/13 1:57 PM Description: We installed jenkins as described here: https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu On a fresh installed Ubuntu 12.04 LTS 64bit system. If I try to configure a job with a svn repository via https, which has no anonymous access, I got the message "unable to access https://svn" for no svn access. After clicking the link "enter credential" ( http://devbuild.bla.at:8080/job/test/descriptorByName/hudson.scm.SubversionSCM/enterCredential?https://svn.bla.at/repos/XYZ/trunk/kkms ) I filled in my username and password and press OK. I got this error: FAILED: svn: E175002: OPTIONS /repos/XYZ/trunk/kkms failed org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/XYZ/trunk/kkms failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1939) at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1884) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$
[JIRA] [subversion] (JENKINS-17900) subversion credentials are not stored in hudson.scm.SubversionSCM.xml
Marco Lenhardt updated JENKINS-17900 subversion credentials are not stored in hudson.scm.SubversionSCM.xml Change By: Marco Lenhardt (08/May/13 1:59 PM) Description: We installed jenkins as described here:https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+UbuntuOn a fresh installed Ubuntu 12.04 LTS 64bit system.If I try to configure a job with a svn repository via https, which has no anonymous access, I got the message "unable to access https://svn" for no svn access.After clicking the link "enter credential" ( http://devbuild.bla.at:8080/job/test/descriptorByName/hudson.scm.SubversionSCM/enterCredential?https://svn.bla.at/repos/XYZ/trunk/kkms )I filled in my username and password and press OK.I got this error:FAILED: svn: E175002: OPTIONS /repos/XYZ/trunk/kkms failedorg.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /repos/XYZ/trunk/kkms failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1939) at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1884) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:
[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers
ikedam commented on JENKINS-17875 Make Jenkins environment variables available to dynamic providers It may be difficult to pass information about the current job to a groovy script. ParameterDefinition, which extensible-choice-parameter is based on, has no interface to retreive information about the job it runs on. http://javadoc.jenkins-ci.org/hudson/model/ParameterDefinition.html Would you tell me why you want to get the job name, not just write it in the script? How about a following feature to meet your requirement? Groovy scripts in a system scope, that is, multiple jobs can share a same script. Just like Global Choice Parameter. Each job can pass its own parameter to the groovy script. In your case, pass the prefix of the name of jobs. You must write the parameter value in the job configuration. It may be annoying when you create many 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] [envinject] (JENKINS-16882) Job-B ${WORKSPACE} has value of Job-A WORKSPACE
Natalia Naumova
commented on JENKINS-16882
Job-B ${WORKSPACE} has value of Job-A WORKSPACE
I see the same issue if job A uses scripttrigger 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/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17901) Add blacklist functionality
Steve Ebersole created JENKINS-17901 Add blacklist functionality Issue Type: Bug Assignee: Honza Brázdil Components: ghprb Created: 08/May/13 2:53 PM Description: The project I work on does not typically use pull requests for code review amongst the development team. Instead pull requests are typically contributions from the community. I'd like to leverage your pull request plugin to valid that each incoming pull request is "buildable". In general I like everything the plugin does now. However, it works explicitly on the whitelist model. So it wants to have the contributor of every pull request added to the whitelist before it tries to build that pull request, and if they are not it continues to add comments to the pull request. Instead, I'd like each pull request to be built by default. Obviously this opens the server up to brute force type attacks via spamming the project with pull requests. So I'd like to see a blacklist for accounts, which is the inverse of the whitelist. Esepcially if the feature could allow automatic blacklisting after a configurable number of failed pull request builds. Project: Jenkins Priority: Major Reporter: Steve Ebersole This message is automatically generated by JIRA. 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] [xtrigger] (JENKINS-17641) Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause
Gregory Boissinot commented on JENKINS-17641 Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause A bit complex because we need to have a sub library 'xtrigger-lib' synchronized between all plugins. Please upgrade to the following versions URLTrigger Plugin 0.31 ScriptTrigger Plugin 0.28 BuildResultTrigger Plugin 0.10 and it should be OK This message is automatically generated by JIRA. 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] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks commented on JENKINS-16863 After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable After applying the uberClassLoader workaround, the Groovy post-build action script succeeds. This message is automatically generated by JIRA. 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] [xtrigger] (JENKINS-17641) Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause
Gregory Boissinot resolved JENKINS-17641 as Fixed Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause Change By: Gregory Boissinot (08/May/13 2:59 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] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner updated JENKINS-17047 Make dependency to bundled ant plugin optional Change By: Ulli Hafner (08/May/13 4:02 PM) Assignee: Ulli Hafner Sebastian Hansbauer This message is automatically generated by JIRA. 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] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner
commented on JENKINS-17047
Make dependency to bundled ant plugin optional
Original code in HealthAwareRecorder:
protected boolean isAntBuild(final AbstractBuild build) {
if (build.getProject() instanceof Project) {
Project project = (Project)build.getProject();
for (Builder builder : project.getBuilders()) {
if (builder instanceof Ant) {
return true;
}
}
}
return false;
}
Needs to be wrapped with:
if (Jenkins.getInstance().getPlugin("ant") != null) {
}
Wrapped code must be moved to a new class with static method isAntBuild
static method isAntBuild should return false if ClassNotFoundException is thrown
dependency in pom.xml should be made optional
This message is automatically generated by JIRA.
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] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner
edited a comment on JENKINS-17047
Make dependency to bundled ant plugin optional
Original code in HealthAwareRecorder:
protected boolean isAntBuild(final AbstractBuild build) {
if (build.getProject() instanceof Project) {
Project project = (Project)build.getProject();
for (Builder builder : project.getBuilders()) {
if (builder instanceof Ant) {
return true;
}
}
}
return false;
}
Needs to be wrapped with:
if (Jenkins.getInstance().getPlugin("ant") != null) {
}
Wrapped code must be moved to a new class with static method isAntBuild
static method isAntBuild should return false if ClassNotFoundException is thrown
ant dependency in pom.xml should be made optional
This message is automatically generated by JIRA.
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] [xunit] (JENKINS-6200) xunit/cppunit causes exception when trying to scan a non-accessible directory
SCM/JIRA link daemon commented on JENKINS-6200 xunit/cppunit causes exception when trying to scan a non-accessible directory Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/5128b7dc41c280a26388ace4ddae64266460e56a Log: Fix JENKINS-6200 This message is automatically generated by JIRA. 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] [urltrigger] (JENKINS-17145) URLTrigger gives severe error message, envinject NPE
Gregory Boissinot resolved JENKINS-17145 as Fixed URLTrigger gives severe error message, envinject NPE Please test urltrigger from 0.31 It should be fixed for now. Thanks Change By: Gregory Boissinot (08/May/13 4:34 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] [xunit] (JENKINS-6200) xunit/cppunit causes exception when trying to scan a non-accessible directory
Gregory Boissinot resolved JENKINS-6200 as Fixed xunit/cppunit causes exception when trying to scan a non-accessible directory Please test from 1.57. Be careful on options for each metrics. Change By: Gregory Boissinot (08/May/13 4:38 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release] (JENKINS-16853) Installation on Windows 7 fails
Kohsuke Kawaguchi resolved JENKINS-16853 as Duplicate Installation on Windows 7 fails Dupliate of JENKINS-12011 Change By: Kohsuke Kawaguchi (08/May/13 5: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] [all-changes] (JENKINS-12011) Windows installer silently fails if it can't add a firewall rule
Kohsuke Kawaguchi resolved JENKINS-12011 as Fixed Windows installer silently fails if it can't add a firewall rule Fixed for 1.515. Change By: Kohsuke Kawaguchi (08/May/13 5:31 PM) Status: Open Resolved Assignee: Kohsuke Kawaguchi 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] [ghprb] (JENKINS-17902) NullPointerException and "pull request doesn't exist" when triggering build via GitHub hooks
Evan Coury created JENKINS-17902 NullPointerException and "pull request doesn't exist" when triggering build via GitHub hooks Issue Type: Bug Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 08/May/13 5:31 PM Description: Just upgraded to v1.8 from 1.5.1. We decided to change from the cron to using the hook/callback. It worked fine when comments were added such as "retest this please" (issue_comment hook), but when a new commit is pushed (pull_request hook, synchronize action), it isn't triggering a new build. Closing and opening the pull request does trigger a new build. I checked the logs and there seems to be a null pointer exception. I haven't had time to really debug it any further yet. May 08, 2013 1:57:36 AM org.jenkinsci.plugins.ghprb.GhprbRootAction doIndex INFO: Got payload event: pull_request May 08, 2013 1:57:36 AM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 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:135) 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 hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServle
[JIRA] [core] (JENKINS-12088) Installation silently installs in default directory if user-specified directory does not exist
Kohsuke Kawaguchi commented on JENKINS-12088 Installation silently installs in default directory if user-specified directory does not exist I actually thought we don't even ask you where to install. Was I wrong? This message is automatically generated by JIRA. 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-17101) Not able to login with chrome, chromium, opera - Only works with firefox
mdunphy reopened JENKINS-17101 Not able to login with chrome, chromium, opera - Only works with firefox I recently upgraded from 1.509 to version 1.514 but have been unable to login with my credentials. Reverted back to 1.509 still no luck. Stumbled across this bug. It seems I can login OK under IE but not chrome (which is my browser of choice) Is there any other diagnostic info I can provide to help? Thanks Mike Change By: mdunphy (08/May/13 5:36 PM) Resolution: Fixed 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot commented on JENKINS-17873 FSTrigger does not accept Parameters Job Parameters are only processed at build tine. They cannot be used by XTrigger plugin as the FSTrigger plugin. Therefore, you have to put the plain value. This message is automatically generated by JIRA. 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot started work on JENKINS-17873 FSTrigger does not accept Parameters Change By: Gregory Boissinot (08/May/13 7:38 PM) Status: Open In Progress This message is automatically generated by JIRA. 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Gregory Boissinot commented on JENKINS-17873 FSTrigger does not accept Parameters Does it suit 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/groups/opt_out.
[JIRA] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles created JENKINS-17903 PeriodicBackup Full-backups not working Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: periodicbackup Created: 08/May/13 8:02 PM Description: I initiated a full backup and it took about 12 hours to complete. The tar.gz it created was only 23 KB in size and only contained 4 job dirs from the Jenkins workspace dir (nothing else). I'm using periodic backup v1.3 and Jenkins v1.514 (problem also occurred using Jenkins 1.510). Note: the config-only backup seems to work OK Due Date: 17/May/13 12:00 AM Environment: RHEL 6.3 Project: Jenkins Priority: Critical Reporter: Nathan Biles This message is automatically generated by JIRA. 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] [fstrigger] (JENKINS-17873) FSTrigger does not accept Parameters
Ken Beal commented on JENKINS-17873 FSTrigger does not accept Parameters Hi Gregory, not exactly. Our scenario is: we want to define the location in one place, and reference it from the other. Right now we have it as a Parameter, and also as an FSTrigger setting. I understand that job Parameters cannot be used here – the question now is: is there any mechanism to avoid having this information hard-coded in two locations? The FSTrigger is to a completion file that the build writes when it is done; we also want to do a directory of that for forensics, so we know time/date and size etc. The location is a complex path with the "branch" as a component of the path. We create new build jobs for new branches, and it would be far preferable to have to update one piece of data with the new branch, rather than needing to update two. Is there any possibility that some other functionality might assist us here? Thanks! Ken This message is automatically generated by JIRA. 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-17838) full build log not in content of email
Alex Gray updated JENKINS-17838 full build log not in content of email Change By: Alex Gray (08/May/13 8:23 PM) Attachment: pom.xml This message is automatically generated by JIRA. 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-17838) full build log not in content of email
Alex Gray updated JENKINS-17838 full build log not in content of email Change By: Alex Gray (08/May/13 8:31 PM) Attachment: mavenConfigure.png Attachment: mavenProject..png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-17838) full build log not in content of email
Alex Gray commented on JENKINS-17838 full build log not in content of email I added a dummy pom.xml to this jar. In Jenkins create a new "Maven project" (I attached a screenshot of creating this type of project). I don't know if you need a plugin to create a Maven project, or if it comes out-of-the-box-Jenkins. In the configuration of the job, point it to the pom.xml and select "test" as the target (I've attached a screenshot of this too). The build will fail, since there are no sources, but it doesn't have to pass to reproduce this problem. When you build it, the text on the console will have something like: == blah blah blah blah <===[JENKINS REMOTING CAPACITY]===> blah blah blah Failure == The message body will only contain stuff above the "Jenkins Remoting Capacity" text. On a side note, I'm also going to try to get rid of one other variable: Cloudbees. I'm going to install Jenkins locally on my machine and try to reproduce this. I'm more and more convinced that it has to do with how Jenkins Cloudbees handles the console text. The reason I say this is because if I just try to echo out the contents of the console text, it works fine. I will let you know my results. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Matt Riedemann assigned JENKINS-17903 to Matt Riedemann PeriodicBackup Full-backups not working Change By: Matt Riedemann (08/May/13 8:50 PM) Assignee: Matt Riedemann This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Matt Riedemann commented on JENKINS-17903 PeriodicBackup Full-backups not working Might want to provide config settings for periodic backup and any information about the jenkins environment, i.e. recursive dump of /var/lib/jenkins in an attached txt file? This message is automatically generated by JIRA. 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] [warnings] (JENKINS-17762) Renaming the Clang parsers silently breaks Jenkins configs
Richard Buckle commented on JENKINS-17762 Renaming the Clang parsers silently breaks Jenkins configs Hi Ulli, I have looked around in GitHub but I'm unclear in which release this fix is deployed. Please forgive my lack of experience with the release process. If you could please point me to the release that includes this fix, I'd be very grateful! This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working Here is 5 minutes of log activity: May 8, 2013 4:49:37 PM hudson.model.AsyncPeriodicWork doRun INFO: PeriodicBackup thread is still running. Execution aborted. May 8, 2013 4:49:33 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/rpmbuild-python-routes/builds/lastUnstableBuild isn't a file. May 8, 2013 4:49:01 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/TEST_e2e_bld_ntfy__bvt-ibm-folsom-proposed-x86_64/builds/lastUnstableBuild isn't a file. May 8, 2013 4:48:37 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/TEST_e2e_bld_ntfy__email-ibm-folsom/builds/lastFailedBuild isn't a file. May 8, 2013 4:48:37 PM hudson.model.AsyncPeriodicWork doRun INFO: PeriodicBackup thread is still running. Execution aborted. May 8, 2013 4:47:37 PM hudson.model.AsyncPeriodicWork doRun INFO: PeriodicBackup thread is still running. Execution aborted. May 8, 2013 4:47:37 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/ibm-ego-osee-grizzly-proposed/builds/lastUnstableBuild isn't a file. May 8, 2013 4:47:36 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/rpmbuild-python-netifaces-ppc64/builds/lastUnsuccessfulBuild isn't a file. May 8, 2013 4:46:37 PM hudson.model.AsyncPeriodicWork doRun INFO: PeriodicBackup thread is still running. Execution aborted. May 8, 2013 4:46:32 PM org.jenkinsci.plugins.periodicbackup.TarGzStorage backupAddFile WARNING: Could not add file to the archive. /var/lib/jenkins/jobs/cinderclient-es-osee-master/builds/lastUnsuccessfulBuild isn't a file. May 8, 2013 4:45:58 PM hudson.model.AsyncPeriodicWork$1 run INFO: Started PeriodicBackup May 8, 2013 4:45:37 PM hudson.mo This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working I attached the config xml above This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles updated JENKINS-17903 PeriodicBackup Full-backups not working Change By: Nathan Biles (08/May/13 9:51 PM) Attachment: periodicBackup.xml This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles updated JENKINS-17903 PeriodicBackup Full-backups not working Directory listing of /var/lib/jenkins Change By: Nathan Biles (08/May/13 9:56 PM) Attachment: dir-list_var-lib-jenkins.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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working Note: the "lastUnsuccessfulBuild isn't a file" warnings are caused by links that do not point to a target, for example 3 are shown below. I doubt this is the problem though. lrwxrwxrwx 1 esbld p/emsol/admin2 Apr 18 08:07 lastFailedBuild -> -1 lrwxrwxrwx 1 esbld p/emsol/admin2 Apr 18 13:07 lastStableBuild -> 45 lrwxrwxrwx 1 esbld p/emsol/admin2 Apr 18 13:07 lastSuccessfulBuild -> 45 lrwxrwxrwx 1 esbld p/emsol/admin2 Apr 9 12:31 lastUnstableBuild -> -1 lrwxrwxrwx 1 esbld p/emsol/admin2 Apr 18 08:07 lastUnsuccessfulBuild -> -1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git] (JENKINS-17894) Can't Clone Git repository over SSH 'Process leaked file descriptors'
Brian Mills commented on JENKINS-17894 Can't Clone Git repository over SSH 'Process leaked file descriptors' I went back to old versions of both Jenkins and the Git Plugin, to no avail. I identified that wish.exe was being executed by gitk.cmd, but not terminated, I had hundreds of open processes over the course of testing. In the end, I added a tool location of Git(default) to use git.exe (instead of gitk.cmd). This resolved the issue. I did this with the latest version of Jenkins, but git plugin versison 1.1.14. I intend to try using the latest git plugin with this override next. Its unclear to me what was wrong with executing using the gitk.cmd as this cmd used to be required to ensure the processing environment of Git was setup correctly on windows. This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles updated JENKINS-17903 PeriodicBackup Full-backups not working Change By: Nathan Biles (08/May/13 11:46 PM) Attachment: dead-links.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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working I searched /var/lib/jenkins for dead links and saved to a list. Interesting it found some loops too. I cleaned up all the dead links / loops (they are just temporary build artifacts that can safely be deleted) and restarted the backup to see if it makes any difference. Attaching list (below). This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles
commented on JENKINS-17903
PeriodicBackup Full-backups not working
Note, the warnings regarding the dead links are probably not a problem, looking in TarGzStorage:
@Override
public void backupAddFile(File fileToStore) throws PeriodicBackupException {
try {
archiver.addFile(fileToStore, Util.getRelativePath(fileToStore, Hudson.getInstance().getRootDir()));
} catch (ArchiverException e) {
LOGGER.warning("Could not add file to the archive. " + e.getMessage());
}
}
This message is automatically generated by JIRA.
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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working that is, assuming org.codehaus.plexus.archiver.tar.TarArchiver doesn't start messing up once it is asked to add one of them This message is automatically generated by JIRA. 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] [xcode] (JENKINS-17457) get a "non-existing directory" problem when making an IPA after building a workspace.
david clark
commented on JENKINS-17457
get a "non-existing directory" problem when making an IPA after building a workspace.
I am having a similar issue. I am not using cocoapods, and I have specified a value for configuration, but I have set it to ${Environment} a variable that I set earlier. The message that I get is:
Cannot remove *.ipa files from a non-existing directory: /Users/Shared/Jenkins/Home/jobs/HotelSearch_iPhone_stage/workspace/build/${Environment}-iphoneos
Environment is set to Stage and the directory /Users/Shared/Jenkins/Home/jobs/HotelSearch_iPhone_stage/workspace/build/Stage-iphoneos does exist.
BTW: for your issue Dan, as a workaround, what happens if you do just specify Release for configuration? Does it break the workspace 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working Disregarding the fact that the .tar.gz was missing all of the files, I'm wondering if one reason it could be so slow is due to using archiver.addFile() instead of using the addArchivedFileSet() method (to add a directory in one step)? This message is automatically generated by JIRA. 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] [periodicbackup] (JENKINS-17903) PeriodicBackup Full-backups not working
Nathan Biles commented on JENKINS-17903 PeriodicBackup Full-backups not working Another obvious reason I missed is because when it scans files it follows links, so it will effectively try to backup everything in our /opt/build/jenkins/workspace/ directory too. /var/lib/jenkins is 6.9 GB, and /opt/build/jenkins/workspace/ is 13G This message is automatically generated by JIRA. 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] [active-directory] (JENKINS-17357) Random Crashes From Active Directory Plugin
Michael Fowler closed JENKINS-17357 as Fixed Random Crashes From Active Directory Plugin Fixed in 1.33 Change By: Michael Fowler (09/May/13 12:57 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] [job-dsl-plugin] (JENKINS-16358) In configuration, control if generated jobs should be deleted or disabled
Justin Ryan resolved JENKINS-16358 as Fixed In configuration, control if generated jobs should be deleted or disabled Change By: Justin Ryan (09/May/13 1:00 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17817) Jenkins crashed when I stopped a job; all jobs running were killed
Lisa Reeber commented on JENKINS-17817 Jenkins crashed when I stopped a job; all jobs running were killed Hi, I've seen this bug a couple more times over the past few days. Below is the log from jenkins when I saw one of these crashes: INFO: fw_xmain_display_sip #83 main build action completed: SUCCESS May 7, 2013 4:18:00 PM winstone.Logger logInternal SEVERE: Error while serving http://peopf317:8181/view/fw_xmain/job/fw_xmain_build/build java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor408.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java: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 hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) a
[JIRA] [core] (JENKINS-17116) gracefull job termination
Martin d'Anjou commented on JENKINS-17116 gracefull job termination After experimenting some more, it seems Jenkins cuts the ties to the child process too soon after sending the TERM signal. Some times, when the job runs on the master, I do see the message from the SIGTERM trap, and a lot of times, I don't see it. This makes it hard to tell what really happens. It looks like Jenkins simply needs to wait for the job process to cut the ties to stdout/stderr before it stops listening to the job itself. On IRC (May 8, 2013), there was a discussion on changing SIGTERM to SIGTERM -> wait 10 sec -> SIGKILL, but I would prefer if this delay was configurable or even optional, as the clean up done by a properly behaving job could take more than 10 seconds (and it does take a few minutes in my case due to a very large amount of small files to clean up on NFS). Here are loosely related but different requests: JENKINS-11995 JENKINS-11996 This message is automatically generated by JIRA. 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-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf commented on JENKINS-16343 Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! This message is automatically generated by JIRA. 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-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Also happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! This message is automatically generated by JIRA. 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-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Also happens with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! This message is automatically generated by JIRA. 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-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.
ily naf edited a comment on JENKINS-16343 Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error. Happens here with Jenkins 1.514, Subversion plugin 1.45, Subversion server 1.6.5 (https + SSLv3). Doesn't happen with SVN server 1.5.5 (https + TLSv1) on the same Jenkins + Subversion plugin. This is quite annoying & the workaround requires manipulation on all nodes (master, slaves). Please consider a fix for this roadblock ASAP. Tks! This message is automatically generated by JIRA. 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-17838) full build log not in content of email
Alex Earl commented on JENKINS-17838 full build log not in content of email I am getting the following: Started by user anonymous Building in workspace /home/user/Projects/email-ext-plugin/work/workspace/JENKINS-17838 No emails were triggered. Parsing POMs JENKINS-17838 $ java -Xdebug -Xrunjdwp:transport=dt_socket,server=n,address=47661 -cp /home/user/Projects/email-ext-plugin/./work/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/user/bin/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /home/user/bin/apache-maven-3.0.5 /home/user/Projects/email-ext-plugin/target/work/webapp/WEB-INF/lib/remoting-2.23.jar /home/user/Projects/email-ext-plugin/./work/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 40854 ERROR: transport error 202: connect failed: Connection refused ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510) JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:741] FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197) Not sure what the issue is... This message is automatically generated by JIRA. 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] [platformlabeler] (JENKINS-17904) Platform labeler should be able to allow exclude some labels
kevincai created JENKINS-17904 Platform labeler should be able to allow exclude some labels Issue Type: Improvement Affects Versions: current Assignee: lifeless Components: platformlabeler Created: 09/May/13 2:42 AM Description: current when platform labeler is installed, platform related labels are automatically added to the slaves. This is awesome. However, there is some cases that some of the labels are not wanted to associated to a specific slave. There is no way to remove the unwanted label. There are two ways to approach the requirement. platform labeler is able to have blacklist, slaves/nodes listed in the blacklist should not be added labels, let user full control of the label, or platform labeler is able to have exclude label list for every slaves, labels listed in the exclude list should not be attached to the slave/node. Project: Jenkins Priority: Major Reporter: kevincai This message is automatically generated by JIRA. 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] [job-dsl-plugin] (JENKINS-16361) @Grab Grape support
Justin Ryan started work on JENKINS-16361 @Grab Grape support Change By: Justin Ryan (09/May/13 4:00 AM) Status: Open In Progress This message is automatically generated by JIRA. 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-17905) how to create a maven projectto download files from maven repository.and also how to use POM.xml.
haritha chundu created JENKINS-17905 how to create a maven projectto download files from maven repository.and also how to use POM.xml. Issue Type: Task Affects Versions: current Assignee: Unassigned Components: artifactory Created: 09/May/13 6:39 AM Fix Versions: current Project: Jenkins Priority: Major Reporter: haritha chundu This message is automatically generated by JIRA. 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.
