[JIRA] [build-environment] (JENKINS-24239) latest RC-Download available is still 1.565 from 20. May 2014. Latest release candidate is not available.
Markus Schlegel created JENKINS-24239 latest RC-Download available is still 1.565 from 20. May 2014. Latest release candidate is not available. Issue Type: Bug Assignee: Peter Hayes Components: build-environment, release Created: 13/Aug/14 6:10 AM Description: When I am on the RC download page (http://jenkins-ci.org/rc) and clicking a download link there (for example the windows download), I get the URL http://mirrors.jenkins-ci.org/war-rc/latest/jenkins.war The war currently provided by this link is V 1.565 from 20-May-2014 14:33 ! According to the Website, we should have 1.576 now. I tried various mirrors but could not find one which provides the actual RC release. Project: Jenkins Priority: Major Reporter: Markus Schlegel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-24227) Test Results Analyzer plugin doesn't produce anything
Varun Menon assigned JENKINS-24227 to Varun Menon Test Results Analyzer plugin doesnt produce anything Change By: Varun Menon (13/Aug/14 6:54 AM) Assignee: VarunMenon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-17702) CopyArtifact with parameter selection fails when parameters changed
Tom Ghyselinck updated JENKINS-17702 CopyArtifact with parameter selection fails when parameters changed Change By: Tom Ghyselinck (13/Aug/14 7:14 AM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-17702) CopyArtifact with parameter selection fails when parameters changed
Tom Ghyselinck
commented on JENKINS-17702
CopyArtifact with parameter selection fails when parameters changed
Hi,
Thank you for the reply!
The procedure is correct as you tested it, but maybe two important differences with our setup:
We use List Subversion tags (and more) parameter in ProjectX:
Name : MY_X_PARAM
Repository URL : svn+ssh://subversion.company.com/repo/branches
Tags filter :
Default value : test
Maximum tags to display :
Sort newest first : enabled
Sort Z to A : disabled
In step 3, we also changed the artifacts: artifact.txt - artifact2.txt
The ProjectY Copy artifacts from another project configuration:
Project name : ProjectX
Which build : Specified by a build parameter
Parameter Name : PROJECT_X_BUILD
Artifacts to copy : artifact2.txt
Target directory : packages
Parameter filters : MY_X_PARAM=${USE_X_PARAM}
where
PROJECT_X_BUILD: Build selector for Copy Artifact, defaulting to Last successful build
USE_X_PARAM: Choice parameter with choices test, ...
I hope this update helps to reproduce the issue!
Thank you very much in advance!
With best regards,
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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24231) Broken implementation for Workspace Cleanup Plugin
SCM/JIRA link daemon commented on JENKINS-24231 Broken implementation for Workspace Cleanup Plugin Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/2f6850c6fbfd608168623bd3875adac398b27b56 Log: Merge pull request #260 from CoreMedia/JENKINS-24231 JENKINS-24231 fixed workspace cleanup external delete command Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/9feecda554c1...2f6850c6fbfd This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24231) Broken implementation for Workspace Cleanup Plugin
SCM/JIRA link daemon commented on JENKINS-24231 Broken implementation for Workspace Cleanup Plugin Code changed in jenkins User: Daniel Spilker Path: docs/Home.md docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/2bab0d865a009a1bddcb7dec65dcf73520505e77 Log: JENKINS-24231 fixed workspace cleanup external delete command This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner
commented on JENKINS-23442
Jenkins 1.568 can not start when monitoring plugin is installed
Hi magnayn.
Try stopping the Jenkins service, then cd into ${JENKINS_HOME}/plugins and remove the file monitoring.jpi as well as monitoring directory.
Then start Jenkins, and reinstall monitoring plugin.
Report back your findings, then evernat get's something to work with. If you can send him your Jenkins log, it may be usefull too.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24231) Broken implementation for Workspace Cleanup Plugin
Daniel Spilker resolved JENKINS-24231 as Fixed Broken implementation for Workspace Cleanup Plugin Change By: Daniel Spilker (13/Aug/14 7:39 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Success! Thank you very much. The certificate on Subversion was issued by our CA so I don't think that applies, however I did get one slave to build just now by adding the -Djsse.enableSNIExtension=false argument in to the slave.xml file. arguments-Xrs -Djsse.enableSNIExtension=false -jar "%BASE%\slave.jar"... That looks like it'll get the jobs running again to me, I'll apply it to the other slaves but when I go to configure the job in Jenkins it still gives me E175002 as shown above, despite it then working on the slave. Do you know how I can apply the same fix to my Jenkins server? I don't see a java.exe process so I'm thinking that's different? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher] (JENKINS-11689) HTMLPublisher does not publish latest report to project page if build fails
Michael Niestegge commented on JENKINS-11689 HTMLPublisher does not publish latest report to project page if build fails I am also facing this "misbehavior". A fix would be nice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24219) Jenkins keeps forgetting my password
Matthias Viehweger updated JENKINS-24219 Jenkins keeps forgetting my password Change By: Matthias Viehweger (13/Aug/14 8:06 AM) Summary: Jenkins keep keeps forgettingmypassword This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24219) Jenkins keeps forgetting my password
Matthias Viehweger commented on JENKINS-24219 Jenkins keeps forgetting my password Okay, I tried this without the password-auto fill (I used the chrome-builtin feature, btw). Sadly, after todays update to 1.575, I got logged out and my previous password did not work anymore. After resetting the password, I could log in with that temporary password, change it, log out, and finally log in with my usual password again. Funnily, this only seems to affect me. I am now "the one that jenkins does not like". Which information could help to narrow this error down? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21487) Frozen UI
magnayn reopened JENKINS-21487 Frozen UI Change By: magnayn (13/Aug/14 8:17 AM) Resolution: CannotReproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis] (JENKINS-24209) Dynamic axis ignores matrix option Execute touchstone builds first
Tetiana Tvardovska updated JENKINS-24209 Dynamic axis ignores matrix option Execute touchstone builds first Change By: Tetiana Tvardovska (13/Aug/14 8:21 AM) Labels: matrix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-axis] (JENKINS-24209) Dynamic axis ignores matrix option Execute touchstone builds first
Tetiana Tvardovska updated JENKINS-24209 Dynamic axis ignores matrix option Execute touchstone builds first Change By: Tetiana Tvardovska (13/Aug/14 8:22 AM) Labels: dynamic-axis matrix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21487) Frozen UI
magnayn commented on JENKINS-21487 Frozen UI So, I'm re-opening this as I can re-create the "white screen of death" regularly on our Jenkins instance, on the latest LTS (1.565.1). I think this is strongly influenced by slow(ish) disk (we are ZFS on Linux), because it's often sitting relatively low levels of CPU. We have a reasonable number of jobs, but nothing to write home about. Running the groovy script from above seems to show it spending extreme amounts of time in what looks like parsing XML files. To get the size, it's triggering the following bit of trace: at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:234) at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) at java.io.BufferedInputStream.read(BufferedInputStream.java:265) locked 0xf9b461f0 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(FilterInputStream.java:83) at java.io.PushbackInputStream.read(PushbackInputStream.java:139) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.getHeader(XmlHeaderAwareReader.java:79) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.init(XmlHeaderAwareReader.java:61) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65) at hudson.XmlFile.unmarshal(XmlFile.java:163) at hudson.model.Run.reload(Run.java:321) at hudson.model.Run.init(Run.java:309) at hudson.model.AbstractBuild.init(AbstractBuild.java:173) at hudson.maven.AbstractMavenBuild.init(AbstractMavenBuild.java:54) at hudson.maven.MavenModuleSetBuild.init(MavenModuleSetBuild.java:146) at sun.reflect.GeneratedConstructorAccessor58.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at jenkins.model.lazy.LazyBuildMixIn.loadBuild(LazyBuildMixIn.java:153) at jenkins.model.lazy.LazyBuildMixIn$1.create(LazyBuildMixIn.java:134) at hudson.model.RunMap.retrieve(RunMap.java:218) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:687) locked 0x82951908 (a hudson.model.RunMap) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:670) at jenkins.model.lazy.AbstractLazyLoadRunMap.getById(AbstractLazyLoadRunMap.java:542) at jenkins.model.lazy.BuildReferenceMapAdapter.unwrap(BuildReferenceMapAdapter.java:42) at jenkins.model.lazy.BuildReferenceMapAdapter.access$200(BuildReferenceMapAdapter.java:27) at jenkins.model.lazy.BuildReferenceMapAdapter$SetAdapter._unwrap(BuildReferenceMapAdapter.java:356) at jenkins.model.lazy.BuildReferenceMapAdapter$SetAdapter.access$400(BuildReferenceMapAdapter.java:248) at jenkins.model.lazy.BuildReferenceMapAdapter$SetAdapter$1.adapt(BuildReferenceMapAdapter.java:271) at jenkins.model.lazy.BuildReferenceMapAdapter$SetAdapter$1.adapt(BuildReferenceMapAdapter.java:269) at hudson.util.AdaptedIterator.next(AdaptedIterator.java:54) at com.google.common.collect.Iterators$7.computeNext(Iterators.java:648) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1101) at java.util.AbstractMap$2$1.hasNext(AbstractMap.java:392) at hudson.util.RunList.size(RunList.java:108) That seems really, really expensive to perform when all the caller cares about is the size of the runlist. Regardless of anything else, that looks like an easy optimisation. Similarly, the home page lockups seem to be because it spends a long time figuring out "what was the last successful / last failed" build, which looks to be similar in nature. I wonder if that could be cached to speed it up without having to load the entire dataset. It's possible that it's memory pressure causing the system to dump this stuff and it having to reload. I'm going to try increasing Xmx and maybe getting some dumps to figure out what's happening. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more
[JIRA] [core] (JENKINS-9142) Add Build Step button broken in job configure page
clamonsch commented on JENKINS-9142 Add Build Step button broken in job configure page I'm still able to reproduce this issue. Adding post build steps is not possible. However this problem only occurs when accessing Jenkins over a proxy. Direct access to the same instance is working fine. Jenkins ver. 1.554.2 Jenkins is started "standalone" - not within a Tomcat. (java -jar jenkins.war) Jenkins access_log: ci@myhost jenkins$ less access_log | grep "$stapler/bound" 172.17.2.152 - - 13/Aug/2014:08:47:17 +0200 "POST /ci/$stapler/bound/14d7256f-189c-4f7d-bc25-badacbc9e2b6/render HTTP/1.1" 404 1426 "https://ci.company.com/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" 172.17.2.152 - - 13/Aug/2014:08:47:17 +0200 "POST /ci/$stapler/bound/877daf46-3cda-4dee-93dc-f0138e0d6b58/render HTTP/1.1" 404 1426 "https://ci.company.com/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" 172.17.2.152 - - 13/Aug/2014:08:47:51 +0200 "POST /ci/$stapler/bound/3b0ac66b-e538-4db5-8e38-8d9234bd96c6/render HTTP/1.1" 404 1426 "https://ci.company.com/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" 172.17.2.152 - - 13/Aug/2014:08:49:45 +0200 "POST /ci/$stapler/bound/64ca65fd-d021-4d0a-9e50-f4d3184a02aa/render HTTP/1.1" 200 177 "http://myhost:8080/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" 172.17.2.152 - - 13/Aug/2014:08:49:45 +0200 "POST /ci/$stapler/bound/ee2f370a-6125-41e4-9061-9f110521fa05/render HTTP/1.1" 200 26 "http://myhost:8080/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" 172.17.2.152 - - 13/Aug/2014:08:49:58 +0200 "POST /ci/$stapler/bound/d7847927-9b59-497b-a19c-7186a4ddc653/render HTTP/1.1" 200 982 "http://myhost:8080/ci/job/abc-004-7/configure" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0" There is no exception or error logged in jenkins.log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Jens Brejner commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Reproduced on Ubuntu 14.04, Jenkins 1.574 + latest monitoring plugin After installing the monitoring plugin, Jenkins does not complete startup as described above. Removing the plugin fixes. I use Oracle java version 1.7.0_65-b17 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24226) use credentials-plugin to define SCM credentials
Frédéric Camblor closed JENKINS-24226 as Duplicate use credentials-plugin to define SCM credentials dup for JENKINS-21640 Change By: Frédéric Camblor (13/Aug/14 8:48 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-24240) Add support for folders plugin
Dirk Kuypers created JENKINS-24240 Add support for folders plugin Issue Type: Improvement Affects Versions: current Assignee: Maurice W. Components: parameterized-remote-trigger Created: 13/Aug/14 9:15 AM Description: I want to trigger a job on a remote server using the folders plugin. I tried various combinations of "path/to/jobname" without success, so I guess this is not supported and needs some programmatic enhancement to the plugin. Project: Jenkins Priority: Major Reporter: Dirk Kuypers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24241) StackOverflow in build queue section with jelly after upgrade to 1.575
Kirill Merkushev created JENKINS-24241 StackOverflow in build queue section with jelly after upgrade to 1.575 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Aug/14 9:35 AM Description: After upgrade to 1.575 i got in UI: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.575.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.575.jar!/lib/hudson/queue.jelly:70:48: j:forEach java.lang.StackOverflowError at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) 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 jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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:79) 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) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at
[JIRA] [other] (JENKINS-24227) Test Results Analyzer plugin doesn't produce anything
Varun Menon resolved JENKINS-24227 as Fixed Test Results Analyzer plugin doesnt produce anything Change By: Varun Menon (13/Aug/14 9:51 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-24242) On evaluation failure is not being honored
Luis Bosque created JENKINS-24242 On evaluation failure is not being honored Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep Created: 13/Aug/14 10:01 AM Description: I'm testing this plugin and the string comparisson I'm doing seems to work fine. However I would like to cancel the build if the comparisson doesn't match. It actually cancels the build but it always ends as Success. I've tried the "on evaluation failure" options "falid the build" and "mark the build unstable" but it always ends as success. Although the build is actually cancelled I would really need it to be marked as failed so it doesn't cause confussion to the person executing the build. This is the text it appears in the output: Run condition Strings match preventing perform for step BuilderChain Finished: SUCCESS Thanks Environment: Ubuntu 12.04 Jenkins official debian package 1.575 Project: Jenkins Priority: Major Reporter: Luis Bosque This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-24242) On evaluation failure is not being honored
Luis Bosque updated JENKINS-24242 On evaluation failure is not being honored Change By: Luis Bosque (13/Aug/14 10:04 AM) Environment: Ubuntu12.04Jenkinsofficialdebianpackage1.575 Conditionalbuildstepplugin1.3.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-24227) Test Results Analyzer plugin doesn't produce anything
Varun Menon commented on JENKINS-24227 Test Results Analyzer plugin doesnt produce anything Fixed the issue in 0.1.1 release which was done today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
Daniel Beck commented on JENKINS-24200 All builds fail with E175002 Jenkins.xml in Jenkins home, or in /etc/defaults or /etc/sysconfig depending on OS. For future requests for assistance, please try the mailing lists or IRC first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken I will set up a full testbed for master/slave scenarios. I will also set up a long running build (maybe one that builds multiple architecture in a row, for let's say 1h). Just to make sure I got you: you have a distributed environment with masterslave on the same server the pipe failure happens in the middle of the build (i.e. not just a few seconds before the completion). I am also working on new features (like auto-install of unity). Feel free to take contact to discuss this further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Success! Thank you very much. The certificate on Subversion was issued by our CA so I don't think that applies, however I did get one slave to build just now by adding the -Djsse.enableSNIExtension=false argument in to the slave.xml file in C:\Jenkins_Slave_Home. arguments-Xrs -Djsse.enableSNIExtension=false -jar "%BASE%\slave.jar"... That looks like it'll get the jobs running again to me, I'll apply it to the other slaves but when I go to configure the job in Jenkins it still gives me E175002 as shown above, despite it then working on the slave. Do you know how I can apply the same fix to my Jenkins server? I don't see a java.exe process so I'm thinking that's different? (Edit: all jobs now work so I'm down to Jenkins reporting an error in the job configuration page.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21487) Frozen UI
Daniel Beck commented on JENKINS-21487 Frozen UI magnayn: Remember that in the case of Maven, the number of projects is (1 + number of modules that ever existed) and the number of builds likewise. Also, reopening with much different versions of everything isn't a good idea. So far it superficially doesn't even look like the same problem. Also, you forgot to mention the versions of everything else, like Maven Plugin. In general, with the information you currently provide, this would be more suited to a request for assistance on the lists or IRC than a Jira issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24219) Jenkins keeps forgetting my password
Daniel Beck commented on JENKINS-24219 Jenkins keeps forgetting my password Is your password basic printable ASCII so we can exclude charset issues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21487) Frozen UI
magnayn resolved JENKINS-21487 as Fixed Frozen UI Change By: magnayn (13/Aug/14 11:24 AM) 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/d/optout.
[JIRA] [core] (JENKINS-21487) Frozen UI
magnayn commented on JENKINS-21487 Frozen UI I think it is still an issue, but the issue is much bigger (I.E: it's dumb parsing thousands of files to render a simple UI homepage). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-24243) Add ability to disable using the global configured proxy
Jan Vansteenkiste created JENKINS-24243 Add ability to disable using the global configured proxy Issue Type: Bug Assignee: Unassigned Components: repository-connector Created: 13/Aug/14 11:32 AM Description: After upgrading to 1.0.0, the artifact resolver stopped working for us since we have a global proxy configured but it should not be used for resolving artifacts (these servers run internally). Please add the ability to disable the use of a proxy for all (or certain) repositories. Project: Jenkins Priority: Blocker Reporter: Jan Vansteenkiste This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22539) Getting Bad AJP13 rcv packet Warnings
S Stack commented on JENKINS-22539 Getting Bad AJP13 rcv packet Warnings Jenkins 1.554.3_LTS We're seeing similar log warnings, although not sure this actually causing any problems. Aug 13, 2014 7:16:13 AM org.eclipse.jetty.util.log.JavaUtilLog warn WARNING: handle failed? java.io.IOException: Bad AJP13 rcv packet: 0x7b22 expected 0x1234 org.eclipse.jetty.ajp.Ajp13Parser@aaf0040 at org.eclipse.jetty.ajp.Ajp13Parser.parseNext(Ajp13Parser.java:276) at org.eclipse.jetty.ajp.Ajp13Parser.parseAvailable(Ajp13Parser.java:158) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) 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:724) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on tr IDs
Dominique Brice commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs Thanks! That's interesting. If they keyboard plugin only needs each tr to have an id, without paying attention to the value/meaning of the id, we could simply put a value somewhat unique like the hashKey of the Job object. No non-HTML characters in there. Or if there's a unique id for each job already in the data model we could use it too. I'll have a look. I'll also install the plugin to play with it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stop working
Rick Oosterholt created JENKINS-24244 Polling of Mercurial scm stop working Issue Type: Bug Assignee: Jesse Glick Components: mercurial, pollscm Created: 13/Aug/14 11:58 AM Description: Mercurial scm polling stops after running once after restart. config.xml scm: scm class="hudson.plugins.mercurial.MercurialSCM" plugin="mercurial@1.50" installation(Default)/installation sourcehttp://host/path/project/source modules/ revisionTypeBRANCH/revisionType revisionstable/revision cleantrue/clean browser class="hudson.plugins.mercurial.browser.HgWeb" urlhttp://host/path/project//url /browser credentialsId/ disableChangeLogfalse/disableChangeLog /scm triggers: triggers hudson.triggers.SCMTrigger specH 3 * * 1-6/spec ignorePostCommitHooksfalse/ignorePostCommitHooks /hudson.triggers.SCMTrigger /triggers Project: Jenkins Priority: Major Reporter: Rick Oosterholt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:06 PM)
Summary:
PollingofMercurialscm
stop
stoped
working
Description:
Mercurialscmpollingstopsafterrunningonceafterrestart.config.xmlscm:{code:xml}scmclass=hudson.plugins.mercurial.MercurialSCMplugin=mercurial@1.50installation(Default)/installationsourcehttp://host/path/project/sourcemodules/revisionTypeBRANCH/revisionTyperevisionstable/revisioncleantrue/cleanbrowserclass=hudson.plugins.mercurial.browser.HgWeburlhttp://host/path/project//url/browsercredentialsId/disableChangeLogfalse/disableChangeLog/scm{code}
config.xml
triggers:{code:xml}triggershudson.triggers.SCMTriggerspecH3**1-6/specignorePostCommitHooksfalse/ignorePostCommitHooks/hudson.triggers.SCMTrigger/triggers{code}
scm-polling.log:{code}Startedon9-aug-20143:27:01PollingSCMchangesonmaster[workspace]$hgpull--revstablepullingfromhttp://host/path/projectnochangesfound[workspace]$hglog--revstable--template{node}[workspace]$hglog--revstable--template{rev}Done.Took1,3secondenNochanges{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle 8GB and doesn't error out.
Akihiro KAYAMA commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. This is critical for my project. 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/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:08 PM)
Description:
Mercurialscmpollingstopsafterrunningonceafterrestart.config.xmlscm:{code:xml}scmclass=hudson.plugins.mercurial.MercurialSCMplugin=mercurial@1.50installation(Default)/installationsourcehttp://host/path/project/sourcemodules/revisionTypeBRANCH/revisionTyperevisionstable/revisioncleantrue/cleanbrowserclass=hudson.plugins.mercurial.browser.HgWeburlhttp://host/path/project//url/browsercredentialsId/disableChangeLogfalse/disableChangeLog/scm{code}config.xmltriggers:{code:xml}triggershudson.triggers.SCMTriggerspecH3**1-6/specignorePostCommitHooksfalse/ignorePostCommitHooks/hudson.triggers.SCMTrigger/triggers{code}scm-polling.log
(todayis14-aug-2014,soitdidnotrunforacoupleofdaysalready)
:{code}Startedon9-aug-20143:27:01PollingSCMchangesonmaster[workspace]$hgpull--revstablepullingfromhttp://host/path/projectnochangesfound[workspace]$hglog--revstable--template{node}[workspace]$hglog--revstable--template{rev}Done.Took1,3secondenNochanges{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt
updated JENKINS-24244
Polling of Mercurial scm stoped working
Change By:
Rick Oosterholt
(13/Aug/14 12:09 PM)
Description:
Mercurialscmpollingstopsafterrunningonceafterrestart.
Jenkinsversion:1.570(canonlychoosecurrentinJira)
config.xmlscm:{code:xml}scmclass=hudson.plugins.mercurial.MercurialSCMplugin=mercurial@1.50installation(Default)/installationsourcehttp://host/path/project/sourcemodules/revisionTypeBRANCH/revisionTyperevisionstable/revisioncleantrue/cleanbrowserclass=hudson.plugins.mercurial.browser.HgWeburlhttp://host/path/project//url/browsercredentialsId/disableChangeLogfalse/disableChangeLog/scm{code}config.xmltriggers:{code:xml}triggershudson.triggers.SCMTriggerspecH3**1-6/specignorePostCommitHooksfalse/ignorePostCommitHooks/hudson.triggers.SCMTrigger/triggers{code}scm-polling.log(todayis14-aug-2014,soitdidnotrunforacoupleofdaysalready):{code}Startedon9-aug-20143:27:01PollingSCMchangesonmaster[workspace]$hgpull--revstablepullingfromhttp://host/path/projectnochangesfound[workspace]$hglog--revstable--template{node}[workspace]$hglog--revstable--template{rev}Done.Took1,3secondenNochanges{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24241) StackOverflow in build queue section with jelly after upgrade to 1.575
evernat resolved JENKINS-24241 as Duplicate StackOverflow in build queue section with jelly after upgrade to 1.575 Change By: evernat (13/Aug/14 12:15 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/d/optout.
[JIRA] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows loading jobs..
Lars Hagström commented on JENKINS-23620 The periodic refresh shows loading jobs.. No, that doesnt do it for me For example I set the update interval to 30 and the paint interval to 60, and that still causes occasional flashes (not quite as frequent, though). My best workaround is still commenting out the "Loading jobs..." line in walldisplay.js... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle 8GB and doesn't error out.
Daniel Beck commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. Akihiro KAYAMA: Create smaller files (e.g. splitting them up for archiving every 7GB, or packaging them using a tool that can split archives. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-24245) Broken links on Tap Extended test results
Laurent Mazuel created JENKINS-24245 Broken links on Tap Extended test results Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: plugin, tap Created: 13/Aug/14 12:47 PM Description: The website site address of my Jenkins is http://10.128.4.199:8180/jenkins/ and not directly a hostname:port as http://10.128.4.199:8180/ Then the link exposed in Tap extended result is: http://10.128.4.199:8180/job/MyJob/ws/myfile.xml and not http://10.128.4.199:8180/jenkins/job/MyJob/ws/myfile.xml Seems like the plugin uses server root, maybe the Jenkins API provide a access to Workspace dir and not root dir? Project: Jenkins Labels: plugin Priority: Major Reporter: Laurent Mazuel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23330) Spaces in project names are not encoded on tr IDs
Daniel Beck commented on JENKINS-23330 Spaces in project names are not encoded on tr IDs Asked jieryn on Github for his opinion on how to proceed. It's clear that the current approach is broken. My favorite solution would be to extend the KS plugin to not require these (shouldn't be too difficult to add them in a _javascript_ by the plugin) and remove from core, but haven't tried whether it's feasible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)
Vivekanand SV commented on JENKINS-22758 Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin) @koshuke, I am using jenkins version 1.574 and I get this error after upgrade to 1.574 for windows slaves (windows 8 and windows 2008 server, I also have windows 7 and windows 2012 server but they are working fine after jenkins upgrade). How should I get the fix that you mentioned above ? Do I just need to download salve.jar from the node page of the current jenkins and use that ? If yes, I tried that and it didn't work. Any ideas ? Vivek. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync Apologies, my testing may have been wrong. As This still appears to be occurring even with version 1.0.11, I rolled back to version 1.0.10 and it was happening there too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24188) p4 credentials does not work for slave
Paul Allen closed JENKINS-24188 as Fixed p4 credentials does not work for slave Fixed 1.0.11 Change By: Paul Allen (13/Aug/14 1:58 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/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Just so it's all writeen down here, a copy of my last note in the IRC chat: Well that was easier to find than I expected. http://docs.appdynamics.com/display/PRO14S/Tomcat+as+a+Windows+Service+Configuration shows how to add Java Options to Tomcat startup. I added -Djsse.enableSNIExtension=false to Java Options in the Configure Tomcat application and restarted the Apache Tomcat service, now it works perfectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Just so it's all written down here, a copy of my last note in the IRC chat: Well that was easier to find than I expected. http://docs.appdynamics.com/display/PRO14S/Tomcat+as+a+Windows+Service+Configuration shows how to add Java Options to Tomcat startup. I added -Djsse.enableSNIExtension=false to Java Options in the Configure Tomcat application and restarted the Apache Tomcat service, now it works perfectly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator resolved JENKINS-24200 as Fixed All builds fail with E175002 With Daniel's help my server and slave nodes are all now behaving exactly as they should do. Change By: System Administrator (13/Aug/14 2:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24246) Jenkins Yum Repository lists older jenkins versions, but the files are not found
Martin Meier created JENKINS-24246 Jenkins Yum Repository lists older jenkins versions, but the files are not found Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 13/Aug/14 2:07 PM Description: The yum repo http://pkg.jenkins-ci.org/redhat/ lists all kind of versions back to 2009 but only newer versions than jenkins-1.522-1.1.noarch.rpm can be obtained here. Example: http://pkg.jenkins-ci.org/redhat/jenkins-1.514-1.1.noarch.rpm You should make the old versions available too or remove them from the repository list. I would prefere that you keep the older versions in case somebody wants to freeze the version of jenkins they are using. Kind Regards, Martin Environment: Yum, Browser Project: Jenkins Priority: Major Reporter: Martin Meier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync Is the log truncated? The node log stops at "... force update false", I would have expected to see "... bypass have false" unless the populate options are different? I don't think it is possible to have different populate options for the nodes, unless there is some corruption. It could be a Windows bug; I need to setup a Windows environment to look at this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync The log in the comments is one that was not failing to sync, but was syning @ the client so nothing was synced since that is effectively have on that machine. With 1.0.11 installed here's logs: Log from the node: 09:06:59 EnvInject - Loading node environment variables. 09:06:59 Building remotely on rsmsnbuild114 in workspace c:\trees 09:07:03 SCM Task: cleanup workspace: RSMSNBUILD114 09:07:03 SCM Task: syncing files at change: 993536 09:07:03 ... sync c:\trees/...@993536 09:07:03 ... force update false 09:07:03 ... bypass have false 09:07:11 Unable to update workspace: com.perforce.p4java.exception.ConnectionException: For input string: "3605760456" 09:07:11 P4: Build failed 09:07:11 ERROR: P4: Build failed 09:07:11 Retrying after 10 seconds 09:07:24 SCM Task: cleanup workspace: RSMSNBUILD114 09:07:24 SCM Task: syncing files at change: 993537 09:07:24 ... sync c:\trees/...@993537 09:07:24 ... force update false 09:07:24 ... bypass have false 09:07:33 Unable to update workspace: com.perforce.p4java.exception.ConnectionException: For input string: "3605760456" 09:07:33 P4: Build failed 09:07:33 ERROR: P4: Build failed 09:07:33 Finished: FAILURE Log from the parent: 09:03:31 EnvInject - Loading node environment variables. 09:03:31 Building remotely on rsmsnbuild118 in workspace c:\trees 09:03:36 SCM Task: cleanup workspace: RSMSNBUILD118 09:03:36 SCM Task: syncing files at change: 993533 09:03:36 ... sync c:\trees/...@993533 09:03:36 ... force update false 09:03:36 ... bypass have false 09:06:24 listing changes: //RSMSNBUILD118/...@993492,993533 09:06:59 Triggering rsmsnbuild114 09:07:36 Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken FYI, I've setup a local master/slave setup, using 1.565.1 (latest stable). I have 0 executors on master, 1 on slave. The slave connects using ssh, as in your setup. I configured the install of Unity 4.5.1f2 in jenkins. I added the EnvInject plugin to tune the config a bit. I created a Unity project to try to reproduce your workload. The git repo is on: https://bitbucket.org/WeWantToKnow/unity3d-sample-project Basically I run the 2D platform sample from Unity3d, and have a jennkins job that builds 8 platforms in a row, multiple times (4 in my case). I.e. 32 builds. I was unable to get the project to fail so far. This takes 10 min on my machine. I run java 1.7.0_21 Mac OS X 10.9.4 I would be great to know if this project fails to run on your machine. You can reproduce the same config by using the following configuration: Prepare an environment for the run - Properties Content BUILD_MANY_TIMES=4 Git - Repository URL g...@bitbucket.org:WeWantToKnow/unity3d-sample-project.git Unity3d Builder: - Unity3d installation name: Unity 4.5.1f2 - Editor command line arguments -quit -batchmode -executeMethod MyEditorScript.PerformAllManyBuild -logFile $WORKSPACE/unity3d_editor.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step] (JENKINS-24205) Cannot COPY or ADD files during create image
Harald Albers commented on JENKINS-24205 Cannot COPY or ADD files during create image This is unexpected, see https://docs.docker.com/reference/builder/#format The Instruction is not case-sensitive, however convention is for them to be UPPERCASE in order to distinguish them from arguments more easily. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Shannon Kerr commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Just to confirm what Daniel already wrote, the Retry count is meaningless here. It only appeared to be that issue was happening during the update because it was so close, but the update went fine. The failure followed the update. I really wish this could be fixed in 2.4.2. Subversion plugin committers, will you please give us a patch for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24247) Subversion Repository URL validation does not support variable substitution
Tim Bradt created JENKINS-24247 Subversion Repository URL validation does not support variable substitution Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 13/Aug/14 3:00 PM Description: Variable substitution is supported for polling SCM and for checkouts, but not for validation of the Repository URL. At best this is extremely misleading - the first time I tried variable substitution I aborted any further attempts since the URL validation told me it was invalid. It was only after I later returned to the concept and did research that I found out it appeared others were using this approach and I tried it successfully. To me, this seems like a defect, or at least a design flaw that should be addressed. If the product supports variable substitution, then so should the on screen validation. Environment: Windows Server 2012, Java 1.8.0_05, Jenkins 1.573 Project: Jenkins Priority: Major Reporter: Tim Bradt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Paul Landolt created JENKINS-24248 Cannot configure Active Directory Bind DN or Bind Password Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: active-directory Created: 13/Aug/14 3:07 PM Description: When configuring the Active Directory Security Realm through the web browser, I can specify the domain Name and (optionally) the Domain controller. There are no fields for Bind DN or Bind Password. Should these be displayed when configuring Global Security? Can they be set somewhere else? Environment: Win XP, Tomcat 7 Project: Jenkins Priority: Major Reporter: Paul Landolt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Paul Landolt
commented on JENKINS-24248
Cannot configure Active Directory Bind DN or Bind Password
Looked at the code from
./src/main/java/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.java
And the magic can indeed happen:
public ActiveDirectorySecurityRealm(String domain, String site, String bindName, String bindPassword, String server, GroupLookupStrategy groupLookupStrategy) {
this.domain = fixEmpty(domain);
this.site = fixEmpty(site);
this.bindName = fixEmpty(bindName);
this.bindPassword = Secret.fromString(fixEmpty(bindPassword));
this.groupLookupStrategy = groupLookupStrategy;
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Paul Landolt updated JENKINS-24248 Cannot configure Active Directory Bind DN or Bind Password Scereen shot from enterprise version of the Active Directory plugin, showing both the Bind DN and Password edit fields Change By: Paul Landolt (13/Aug/14 3:26 PM) Attachment: ActiveDirectorySecurityRealm-BindDNandPassword.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
arkady godlin commented on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 still getting this error on 1 of the machines i have my configuration OS: CentOS-4.8 SSH Agent Plugin: 1.5 SSH Credentials Plugin : 1.8 Credentials Plugin : 1.16 java version "1.6.0_45" EnvInject - Loading node environment variables. Building remotely on sdel64-12 (CentOS-4.8 sde CentOS lin internal-rs amd64-CentOS-4.8 linux 4.8 amd64-CentOS amd64) in workspace /home/emxtest2/emx/internal-rs/workspace/SDE-tmp ssh-agent Using credentials emxtest (emxtest) ssh-agent Looking for ssh-agent implementation... ssh-agent Java/JNR ssh-agent ssh-agent FATAL: Could not find a suitable ssh-agent provider ssh-agent Diagnostic report ssh-agent * Java/JNR ssh-agent ssh-agent java.io.IOException: Remote call on sdel64-12 failed ssh-agent at hudson.remoting.Channel.call(Channel.java:748) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.init(SSHAgentBuildWrapper.java:314) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:224) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:189) ssh-agent at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:76) ssh-agent at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) ssh-agent at hudson.model.Run.execute(Run.java:1740) ssh-agent at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) ssh-agent at hudson.model.ResourceController.execute(ResourceController.java:88) ssh-agent at hudson.model.Executor.run(Executor.java:234) ssh-agent Caused by: java.lang.UnsatisfiedLinkError: could not load FFI provider jnr.ffi.provider.jffi.Provider ssh-agent at jnr.ffi.provider.InvalidRuntime.newLoadError(InvalidRuntime.java:83) ssh-agent at jnr.ffi.provider.InvalidRuntime.findType(InvalidRuntime.java:24) ssh-agent at jnr.ffi.Struct$NumberField.init(Struct.java:649) ssh-agent at jnr.ffi.Struct$Unsigned16.init(Struct.java:1007) ssh-agent at jnr.unixsocket.SockAddrUnix$DefaultSockAddrUnix.init(SockAddrUnix.java:129) ssh-agent at jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:99) ssh-agent at jnr.unixsocket.UnixSocketAddress.init(UnixSocketAddress.java:32) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:66) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.init(JNRRemoteAgent.java:64) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) ssh-agent at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) ssh-agent at hudson.remoting.UserRequest.perform(UserRequest.java:118) ssh-agent at hudson.remoting.UserRequest.perform(UserRequest.java:48) ssh-agent at hudson.remoting.Request$2.run(Request.java:328) ssh-agent at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) ssh-agent at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) ssh-agent at java.util.concurrent.FutureTask.run(Unknown Source) ssh-agent at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) ssh-agent at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ssh-agent at java.lang.Thread.run(Unknown Source) ssh-agent Caused by: java.lang.ExceptionInInitializerError ssh-agent at jnr.ffi.provider.jffi.NativeRuntime.getInstance(NativeRuntime.java:49) ssh-agent at jnr.ffi.provider.jffi.Provider.init(Provider.java:29) ssh-agent at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ssh-agent at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) ssh-agent at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) ssh-agent at java.lang.reflect.Constructor.newInstance(Unknown Source) ssh-agent at java.lang.Class.newInstance0(Unknown Source) ssh-agent at java.lang.Class.newInstance(Unknown Source) ssh-agent at
[JIRA] [security] (JENKINS-24249) Dynamic pop-up menus don't appear when Prevent Cross Site Request Forgery exploits is enabled
Stefan Thurnherr created JENKINS-24249 Dynamic pop-up menus dont appear when Prevent Cross Site Request Forgery exploits is enabled Issue Type: Bug Assignee: Unassigned Components: security Created: 13/Aug/14 3:39 PM Description: When enabling the Global Security option "Prevent Cross Site Request Forgery exploits", the dynamic pop-up menus stop working (they dont appear at all anymore). This applies to the Job menu in a view, to items in the Build Queue and the Build Executor Status, and to the "Jenkins" breadcrumb menu (top-left corner), so seems to apply to all menus. "Crumb Algorithm" = "Default Crumb Issuer", and "Enable proxy compatibility" doesnt seem to make any difference. Environment: Jenkins v1.575, jenkins stand-alone war file * nginx as a proxy server in front of jenkins. Project: Jenkins Priority: Major Reporter: Stefan Thurnherr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24249) Dynamic pop-up menus don't appear when Prevent Cross Site Request Forgery exploits is enabled
Stefan Thurnherr updated JENKINS-24249 Dynamic pop-up menus dont appear when Prevent Cross Site Request Forgery exploits is enabled Change By: Stefan Thurnherr (13/Aug/14 3:41 PM) Component/s: gui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24249) Dynamic pop-up menus don't appear when Prevent Cross Site Request Forgery exploits is enabled
Stefan Thurnherr commented on JENKINS-24249 Dynamic pop-up menus dont appear when Prevent Cross Site Request Forgery exploits is enabled If this is a known down-side of enabling "Prevent Cross Site Request Forgery exploits", then it should be mentioned there, see JENKINS-15252 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-24249) Dynamic pop-up menus don't appear when Prevent Cross Site Request Forgery exploits is enabled
Stefan Thurnherr updated JENKINS-24249 Dynamic pop-up menus dont appear when Prevent Cross Site Request Forgery exploits is enabled Change By: Stefan Thurnherr (13/Aug/14 3:42 PM) Environment: Jenkinsv1.575,jenkinsstand-alonewarfile *nginx ginx asaproxyserverinfrontofjenkins . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap] (JENKINS-24250) TAP plugin truncates testresult.tap file
Wolf Wolfswinkel created JENKINS-24250 TAP plugin truncates testresult.tap file Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 13/Aug/14 4:09 PM Description: I have some long existing Jenkins jobs with TAP tests configured. However at some update of either Jenkins or the tap-plugin the tap plugin stopped functioning correctly. This wasn't noticed earlier because the build jobs did not fail. The plugin run ends with a message "Found matching files but did not find any TAP results"; in the workspace the testresult file is indeed empty. Analyzing this further it turns out that tap-plugin 1.7 works correctly, but any higher version seems to truncate the testresult file to 0 bytes before processing it. Any ideas? Environment: Jenkins 1.575 on Windows 7 32-bit; tap-plugin 1.8-1.20 Project: Jenkins Priority: Major Reporter: Wolf Wolfswinkel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-24227) Test Results Analyzer plugin doesn't produce anything
Jérôme BACHELET commented on JENKINS-24227 Test Results Analyzer plugin doesnt produce anything Thank you for the correction. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24251) No JDK named ‘(Default)’ found
David Ruhmann created JENKINS-24251 No JDK named ‘(Default)’ found Issue Type: Bug Assignee: Jesse Glick Components: core Created: 13/Aug/14 4:41 PM Description: "No JDK named ‘(Default)’ found" is printing out for every job despite whether or not the job even uses Java. It is quite annoying. Cause traced to this Pull Request: https://github.com/jenkinsci/jenkins/commit/9d016f68fd7f4e45b0d933b48bb79f219ab91437 Started by user Ruhmann,David Building remotely on Windows 2008 R2 (JAVA) Jarvis (JARVIS JAVA7 JAVA6 MAVEN2 SKYBOX JAVA8 WINDOWS MAVEN3) in workspace C:\Jenkins\workspace\JenkinsTesting No JDK named ‘(Default)’ found [JenkinsTesting] $ cmd /c call c:\temp\hudson1584677057763580094.bat C:\Jenkins\workspace\JenkinsTestingexit /b 0 Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS Environment: Jenkins = 1.575 Project: Jenkins Priority: Minor Reporter: David Ruhmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync I tried this out using Windows slaves, but have had no success at reproducing the issue. I have added more logging for remote slaves (change 9987 on the main branch). I have a theory that would be great if you could test out for me... My gut feeling here is that this is a serialization issue and old objects are not being read/passed correctly. To prove/disprove this the perfect way would be to setup a clean Jenkins install and see if you still have the bug. However, a quicker alternative would be to create a new Perforce Credentials object (delete the old one if you like) and perhaps try it with a new Jenkins 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/d/optout.
[JIRA] [ldap] (JENKINS-18355) LDAP does not populate Your Name field
Walter Kacynski closed JENKINS-18355 as Fixed LDAP does not populate Your Name field Change By: Walter Kacynski (13/Aug/14 5:02 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)
Oleg Nenashev resolved JENKINS-23597 as Fixed Job restrictions based on folders plugin (job restrictions plugin, folders plugin) Change By: Oleg Nenashev (13/Aug/14 5:33 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Jesse Glick commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Correcting a minor regression in 8423158: User.getAuthorities should not pass on the UsernameNotFoundException. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Sean Abbott updated JENKINS-24228 maven project fails build when log claims with success. A number of reports grabbed during the build. number 6 was grabbed immediately after it finished running maven. Change By: Sean Abbott (13/Aug/14 5:57 PM) Attachment: build-reports.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/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Sean Abbott commented on JENKINS-24228 maven project fails build when log claims with success. Was there a different api call besides just grabbing the json I was supposed to do? I don't really see any new info in that. :-/ Pastebin of the "most likely relevant" reading: http://pastebin.com/H9dLxh9A This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24252) option to run multiple jobs for the same review independently
Peter Eisentraut created JENKINS-24252 option to run multiple jobs for the same review independently Issue Type: New Feature Assignee: rsandell Components: gerrit-trigger Created: 13/Aug/14 6:00 PM Description: When multiple jobs trigger from the same gerrit review, the result is not reported until all jobs have finished. I would like to have an option to do this differently. I would like to have, say, one job that does a quick test, and a second job that runs a longer test, and they would each report back to gerrit as soon as possible. They would either use different review categories (it's possible to configure this now, but it doesn't work and results in a bit of a mess), or the later job could overwrite the earlier job's verdict. Project: Jenkins Priority: Major Reporter: Peter Eisentraut This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24253) Add JOB_LABELS environment variable
David Ruhmann created JENKINS-24253 Add JOB_LABELS environment variable Issue Type: New Feature Assignee: David Ruhmann Components: core Created: 13/Aug/14 6:34 PM Description: Add the environment variable JOB_LABELS containing the labels specified for the job in the configuration. Environment: Jenkins = 1.575 Project: Jenkins Priority: Minor Reporter: David Ruhmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24254) New slaves fails to execute jobs on first connection
Mattias Appelgren created JENKINS-24254 New slaves fails to execute jobs on first connection Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 13/Aug/14 6:41 PM Description: I'm getting this error in the console output of jobs executed on a recently created slave. Started by user anonymous ERROR: Issue with creating launcher for slave slave_name. Building remotely on slave_nameFATAL: null java.lang.NullPointerException at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) at hudson.model.Run.execute(Run.java:1732) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) After the job fails the slave reconnects and there's no problems for it to build jobs in the future. Project: Jenkins Labels: slave Priority: Major Reporter: Mattias Appelgren This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-24254) New slaves fails to execute jobs on first connection
Mattias Appelgren
updated JENKINS-24254
New slaves fails to execute jobs on first connection
Change By:
Mattias Appelgren
(13/Aug/14 6:42 PM)
Description:
Imgettingthiserrorintheconsoleoutputofjobsexecutedonarecentlycreatedslave.{code}StartedbyuseranonymousERROR:Issuewithcreatinglauncherforslaveslave_name.Buildingremotelyonslave_nameFATAL:nulljava.lang.NullPointerException athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:521) athudson.model.Run.execute(Run.java:1732) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:234){code}Afterthejobfailstheslavereconnectsandtheresnoproblemsforittobuildjobs
inthefuture
afterthis
.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Daniel Beck commented on JENKINS-24228 maven project fails build when log claims with success. I'm sorry, that was the wrong URL please repeat the API access for /job/jobname/buildnumber/api/json with 'buildnumber' the number of the currently running build at around the time it skips Sonar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Sean Abbott updated JENKINS-24228 maven project fails build when log claims with success. Ok, the second one here was grabbed right after maven finished and reported success, while the CLM can was running. Change By: Sean Abbott (13/Aug/14 6:59 PM) Attachment: build-results-2.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/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Sean Abbott commented on JENKINS-24228 maven project fails build when log claims with success. I would delete the extraneous build-reports.txt file, but it won't let me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
上海美术学院美女交际花
上海美术学院美女交际花 2sl.hi内oem.com 注意：删除字“内” -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
dserodio commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection I've seen this error message when trying to use jenkins-cli pointing to a Jenkins master where the JNLP port is blocked by a firewall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [swarm] (JENKINS-20138) swarm 1.9 can't connect to current LTS as slave.jar too old
SCM/JIRA link daemon commented on JENKINS-20138 swarm 1.9 cant connect to current LTS as slave.jar too old Code changed in jenkins User: Martin Konrad Path: manifests/params.pp http://jenkins-ci.org/commit/puppet-jenkins/2963468b2364c1d8216d952a7c9da4831d40c133 Log: Install swarm-client 1.16 This is necessary to avoid compatibility issues with newer Jenkins versions (e.g. see https://issues.jenkins-ci.org/browse/JENKINS-20138). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24253) Add JOB_LABELS environment variable
David Ruhmann updated JENKINS-24253 Add JOB_LABELS environment variable Change By: David Ruhmann (13/Aug/14 7:28 PM) Description: AddtheenvironmentvariableJOB_LABELScontainingthelabelsspecifiedforthejobintheconfiguration. ThelabelsusedtodeterminetheNodewouldbemoreusefulthanallofthelabelsassignedtoaNodeasinNODE_LABELS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Is it only happening when there isn't a previous build? Confirmed. Once the job has changes, I no longer see this NPE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync I'll give that a shot in the next day or so. Pre-occupied with other tasks right now. But I'll follow up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Nancy Robertson edited a comment on JENKINS-22345 disk-usage-plugin causes jobs to hang at the end for 5min I have encountered this issue on my Jenkins installation with a subset of the jobs. The jobs that have this problem are the ones that have a Custom Workspace defined. After the job finishes, the jenkins process on the master starts using a lot of CPU while the Disk Usage plugin is trying to estimate the size of the workspace on the slave. While this is happening, the build history for the job shows that it has finished, but the job is still shown in the Build Executor Status and the console log for the build does not show the expected last statement of "Finished: SUCCESS". This goes on for 5 minutes, which happens to match the configured value of the timeout for calculating the size of the workspace on slaves. Not sure if this matters, but our jobs are of type: "free-style software project" and the version of Jenkins we use is 1.566 We had version 0.23 of the disk usage plugin, the problem went away by uninstalling the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Nancy Robertson commented on JENKINS-22345 disk-usage-plugin causes jobs to hang at the end for 5min I have encountered this issue on my Jenkins installation with a subset of the jobs. The jobs that have this problem are the ones that have a Custom Workspace defined. After the job finishes, the jenkins process on the master starts using a lot of CPU while the Disk Usage plugin is trying to estimate the size of the workspace on the slave. While this is happening, the build history for the job shows that it has finished, but the job is still shown in the Build Executor Status and the console log for the build does not show the expected last statement of "Finished: SUCCESS". This goes on for 5 minutes, which happens to match the configured value of the timeout for calculating the size of the workspace on slaves. Not sure if this matters, but our jobs are of type: "free-style software project" and the version of Jenkins we use is 1.566 We had version 0.23 of the disk usage plugin, the problem went away by uninstalling the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24219) Jenkins keeps forgetting my password
Matthias Viehweger
commented on JENKINS-24219
Jenkins keeps forgetting my password
yes. the one I use for our internal jenkins instance matches /a-zA-Z0-9{6,20}/.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-24255) HockeyApp plugin doesn't upload multiple IPAs as documented
Antek Baranski created JENKINS-24255 HockeyApp plugin doesnt upload multiple IPAs as documented Issue Type: Bug Affects Versions: current Assignee: Antek Baranski Components: hockeyapp Created: 13/Aug/14 8:12 PM Description: The current HockeyappRecorder.java code in the perform function is hard coded to only pick the first element from the file array to upload like this: FilePath[] remoteFiles = remoteWorkspace.list(vars.expand(filePath)); File file = getLocalFileFromFilePath(remoteFiles0, tempDir); Project: Jenkins Priority: Major Reporter: Antek Baranski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-24255) HockeyApp plugin doesn't upload multiple IPAs as documented
Antek Baranski started work on JENKINS-24255 HockeyApp plugin doesnt upload multiple IPAs as documented Change By: Antek Baranski (13/Aug/14 8:15 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-24255) HockeyApp plugin doesn't upload multiple IPAs as documented
Antek Baranski resolved JENKINS-24255 as Fixed HockeyApp plugin doesnt upload multiple IPAs as documented GitHub pul request: https://github.com/jenkinsci/hockeyapp-plugin/pull/23 Change By: Antek Baranski (13/Aug/14 8:16 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Christian Fetzer created JENKINS-24256 Fail build for missing / erroneous valgrind publisher XMLs Issue Type: Improvement Assignee: Johannes Ohlemacher Components: valgrind Created: 13/Aug/14 8:19 PM Description: I've been using the valgrind publisher in an environment where valgrind under some circumstances is not executed correctly leading to either missing, or malformed xml files. Under normal conditions, valgrind reports errors for the project rather rarely (and the trend usually is at 0 for several builds). This leads to a situation where errors can be missed, because it's not easily visible if valgrind reported 0 errors, or if the publisher failed to read the valgrind output. Hence, I've got a suggestion to improve the publisher plugin: Would it be possible to add an option which fails the build in case no valgrind xml reports were found, or if one or more reports couldn't be parsed. Project: Jenkins Priority: Minor Reporter: Christian Fetzer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Daniel Beck commented on JENKINS-24228 maven project fails build when log claims with success. I'm out of good ideas. It seems weird that no artifacts are recorded for the build, but that may well be regular behavior, I just don't know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build when log claims with success.
Sean Abbott commented on JENKINS-24228 maven project fails build when log claims with success. Well, and it's also weird because even though it claims failure, all the tests pass and the artifacts are successfully uploaded to the nexus artifact repository. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-23549) HockeyApp Plugin : ArrayIndexOutOfBoundsException
Antek Baranski started work on JENKINS-23549 HockeyApp Plugin : ArrayIndexOutOfBoundsException Change By: Antek Baranski (13/Aug/14 8:41 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24246) Jenkins Yum Repository lists older jenkins versions, but the files are not found
Daniel Beck resolved JENKINS-24246 as Fixed Jenkins Yum Repository lists older jenkins versions, but the files are not found Temporary issue that is being worked on, see linked INFRA issue. Change By: Daniel Beck (13/Aug/14 8:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Jesse Glick updated JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Does sound like it must have been caused by my https://github.com/jenkinsci/mailer-plugin/commit/667b82e05e41b6f603c405dc31fdef6d7e47b83f though I am not sure how. Try the script console (/script): hudson.tasks.Mailer.descriptor().getSmtpAuthPassword() Does this still show your password? Does $JENKINS_HOME/hudson.tasks.Mailer.xml change depending on whether you are using pre-1.10 or 1.10? Change By: Jesse Glick (13/Aug/14 8:45 PM) Summary: Testemailfailswithjavax.mail.AuthenticationFailedExceptioninmailerv1. 1.0 10 Labels: regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
