[JIRA] [copyartifact] (JENKINS-23444) Copy Artifact doesn't fail when only some of the defined artifacts are successfully copied
ikedam commented on JENKINS-23444 Copy Artifact doesn't fail when only some of the defined artifacts are successfully copied https://github.com/jenkinsci/copyartifact-plugin/pull/42 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18662) Add a exclude file(s) field to CopyArtifact plugin
ikedam commented on JENKINS-18662 Add a exclude file(s) field to CopyArtifact plugin https://github.com/jenkinsci/copyartifact-plugin/pull/42 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23745) Create links to the running/executed remote job
Maurice W. commented on JENKINS-23745 Create links to the running/executed remote job Outputting to the log the URL of the remote server may not be desirable for publicly accessible Jenkins servers due to security concerns. Once typically does not want to over-expose "internal workings" of your job to the public. As for adding a new UI bit similar to "downstream projects"... that sounds interesting. I have no clue how to implement that at the moment, but I'll leave this feature request open. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23770) populateJenkinsHome does not work for all Jenkins TYPEs
Ulli Hafner
created JENKINS-23770
populateJenkinsHome does not work for all Jenkins TYPEs
Issue Type:
Bug
Affects Versions:
current
Assignee:
Oliver Gondža
Components:
acceptance-test-harness
Created:
13/Jul/14 9:12 AM
Description:
Oliver, seems that the new implementation of JenkinsController#start does work only for a small subset of controllers:
try {
populateJenkinsHome(new File(JenkinsController.class.getResource("jenkins_updates").toURI()), false);
} catch (URISyntaxException ex) {
throw new AssertionError(ex);
}
Most controllers throw an exception in populateJenkinsHome. Moreover, if using the jutServer.sh command, then the resource "jenkins_updates" is within a jar and the conversion to a URI fails with an exception.
I already removed the exception for the TYPE=existing implementation: de8d094
Project:
Jenkins
Priority:
Major
Reporter:
Ulli Hafner
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-23560) Slave hung in startup phase with missing logging in the GUI
Daniel Beck commented on JENKINS-23560 Slave hung in startup phase with missing logging in the GUI What about local logging on the slave machine? Anything interesting there? How was the slave being started (SSH, …)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22826) use wildcard syntax to get direct link to artifact
Daniel Beck updated JENKINS-22826 use wildcard syntax to get direct link to artifact Change By: Daniel Beck (13/Jul/14 12:51 PM) Issue Type: Improvement New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-14900) Copying from workspace drops files matching Ant's default excludes
ikedam commented on JENKINS-14900 Copying from workspace drops files matching Ant's default excludes https://github.com/jenkinsci/copyartifact-plugin/pull/42 Fix for this issue should be introduced with fix for JENKINS-18662. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22927) Build fails if remote jenkins is offline or job is missing
Maurice W. commented on JENKINS-22927 Build fails if remote jenkins is offline or job is missing I'm closing this issues. If you updated to to v2.1.3 and still have the same problem, please re-open. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14636) Create Artifacts From an Wrong Build
ikedam resolved JENKINS-14636 as Duplicate Create Artifacts >From an Wrong Build Duplicates JENKINS-11655 (and it is in progress now). Change By: ikedam (13/Jul/14 4:07 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23763) Cannot use jsonp with buildWithParameters
Daniel Beck resolved JENKINS-23763 as Not A Defect Cannot use jsonp with buildWithParameters This is an issue tracker, not a support site. Please try IRC or the jenkinsci-users mailing list to get help. Change By: Daniel Beck (13/Jul/14 12:42 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20663) file name encoding broken in zip archives
Lauri Taaleš commented on JENKINS-20663 file name encoding broken in zip archives I'm not really a Java dev, but I took some time to test the output of both java.util.zip.ZipOutputStream and org.apache.commons.compress.archivers.zip.ZipArchiveOutputStream. I used both to zip a file named 'õäöü.txt' and then tried to unzip it with the default application, i.e. whatever runs from context menu, on Windows 7 and Manjaro 0.8.10 Archive created with ZipOutputStream had a mangled file name when unzipped on both Windows and Linux. The same was true for ZipArchiveOutputStream when using only the default options. But by setting additional flags as described at http://info.michael-simons.eu/2010/01/05/create-zip-archives-containing-unicode-filenames-with-java/ the archive produced became readable on Linux. Even though it does not help me with my Windows problem, I consider this preferrable to current behavior. Usage of ZipArchiveOutputStream would also allow to add a (maybe job specific) configuration option for setting zip archive encoding for those poor souls stuck on Windows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-22927) Build fails if remote jenkins is offline or job is missing
Maurice W. closed JENKINS-22927 as Fixed Build fails if remote jenkins is offline or job is missing Change By: Maurice W. (13/Jul/14 7:36 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22855) SSH Credential's username isn't used.
Mark Waite commented on JENKINS-22855 SSH Credential's username isn't used. Confirmed also from a newly launched Amazon EC2 instance. I added a private key with the username "mwaite" but the log files on the machine receiving the request report the user "jenkins" was attempted, rather than the user "mwaite": Jul 12 19:50:29 wheezy64b sshd[10486]: Failed password for jenkins from 54.205.194.178 port 36176 ssh2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-2673) Invalid CRON Warnings
Daniel Beck commented on JENKINS-2673 Invalid CRON Warnings Often there are better alternatives to polling, and polling in Jenkins doesn't scale. So the warning makes sense for patterns that indicate the user wants to poll every minute, i.e. as frequently as possible during a given time frame. It's just that, a warning to make sure the user does not accidentally configure it this way. Recent Jenkins versions also show the projected previous and next polling times, so misunderstandings of the kind mentioned in the issue comments are almost impossible now. Will add clarification to the warning to indicate the suggested pattern only polls once per hour. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-8045) Weird log display behavior for too fast workerThread in TaskAction
Daniel Beck resolved JENKINS-8045 as Incomplete Weird log display behavior for too fast workerThread in TaskAction Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 1:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23534) Unable to set number of executors on slave through Groovy system script
Daniel Beck commented on JENKINS-23534 Unable to set number of executors on slave through Groovy system script Might be sufficient to make Computer.setNumExecutors(int) public, but I have no idea what the side effects of that would be. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22927) Build fails if remote jenkins is offline or job is missing
Maurice W. resolved JENKINS-22927 as Fixed Build fails if remote jenkins is offline or job is missing Change By: Maurice W. (13/Jul/14 7:36 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extra-columns] (JENKINS-23756) Column suggestion for Extra Column plugin
Rupen Anjaria commented on JENKINS-23756 Column suggestion for Extra Column plugin Thank you Fred. I have created another issue https://issues.jenkins-ci.org/browse/JENKINS-23771 Should I close this one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Don Ross
edited a comment on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I am seeing this same behavior after upgrading from 1.1.21 to 2.2.2.
I noticed that the default is now to always use 'Fast remote polling'; in my production environment I have this option turned off. So, I enabled 'Force polling using workspace', and I am now seeing a different message (but the same behavior of false changes being found), as follows:
Started on Jul 14, 2014 1:16:38 PM
Polling SCM changes on slave-host-name
Using strategy: Default
[poll] Last Built Revision: Revision 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f (origin/release_branch)
> git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repositories
> git config remote.origin.url ssh://build@gitserver/git/product.git
Fetching upstream changes from ssh://build@gitserver/git/product.git
> git --version
> git fetch --tags --progress ssh://build@gitserver/git/product.git +refs/heads/*:refs/remotes/origin/*
Polling for changes in
> git rev-parse "origin/release_branch^{commit}"
> git rev-parse "release_branch^{commit}"
> git log --full-history --no-abbrev --format=raw -M -m --raw 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f..9f74e3057c7fb30d2c001f886e394d5bea0271a
Done. Took 1.8 sec
Changes found
It is interesting to me that the '9f74e3' commit ID in that git log command is the commit immediately before the '44bfcc7' commit.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-19393) global search should not jump to exact result if more than one result is found
Daniel Beck commented on JENKINS-19393 global search should not jump to exact result if more than one result is found Probably more of a terminology issue leading to expectations that don't match reality: The "search" in Jenkins seems to be set up to be some kind of "quick navigation" (similar to desktop tools like Quicksilver, LaunchBar, Enso Launcher, …) rather than a plain "search". Supporting indicators: If an exact match can be found, it navigates to the result It supports queries like projectname #2 console which have nothing to do with actual keyword search (if there's a build #2, it will have a console output page, so search is pointless) Searching for inexact 'launcher' type queries like projectname console will fail If no exact match can be found, the resulting web page is a 404 error page with suggestions (i.e. showing this is definitely not the default operation) I'm not saying this shouldn't be changed – I've never even used search as "launcher" except to try it – but this should give you an idea that it's not just "get rid of the exact match resolution and done". In fact, I tried it, and the problem is that even the suggested results on the "error page" only link to the search page, assuming their exact match will result in jumping to the referenced item – so the search API needs to be changed to support a list of name/URL pairs instead of just names as currently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
George Bloggs created JENKINS-23779 Layout in 1.572 is broken in IE9 Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Attachments: jenkins-1572.png Components: dashboard-view, ui-changes Created: 14/Jul/14 3:56 PM Description: The new layout introduced in 1.572 is broken in IE9, Version 9.0.28 (9.0.8112.16421). The CSS does no appear to be laying out the page correctly. Page draw ok in FireFox 30. Environment: Windows 7, IE9, Version 9.0.28 (9.0.8112.16421) Project: Jenkins Priority: Major Reporter: George Bloggs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11002) Windows DCOM slave fails to connect
Jeebitesh Kalantri commented on JENKINS-11002 Windows DCOM slave fails to connect We need this feature very badly, As Everything related to Windows 7 (Resolution) worked perfectly and we were able to create template out of the same, so that we never face the issue. But for Windows 2008 R3 (64 bit) Server we have not been able to come to a get this resolved. I am looking into this if we can get the workaround as issue is with NTLMv2 Authentication. As we are moving towards VMWare vSphere Cloud & Lab management features of Jenkins, this becomes more and more important for dynamic deployment. I am looking into this and will try assign it as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23780) ActiveDirectoryTest should support to selection of Group Lookup Strategy
Scott Hebert started work on JENKINS-23780 ActiveDirectoryTest should support to selection of Group Lookup Strategy Change By: Scott Hebert (14/Jul/14 5:59 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23732) HP Analyses - no results file found for - can't find results when run via hp-application-automation-tools-plugin
Juraj Kutes commented on JENKINS-23732 HP Analyses - no results file found for - can't find results when run via hp-application-automation-tools-plugin Some progress. By changing Jenkins slave Windows service account to different admin account, this ran successfully. Unfortunately, I can't use this particular account permanently, so I still need a help with this. I guess now we at least know, that this privileges related. Is there any more specific requirement for privileges, because both of the accounts I used are admins? Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [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 Hello Stephen. i am trying to use this plugin and i encounter some problems. i am getting error [ssh-agent] Using credentials emxtest (emxtest-agodlin-key) [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 java.io.IOException: Remote call on sdel64-04.iil.intel.com failed i tried to downgrade to 1.3. got still same problem. i even tried to downgrade to 1.1 and didn't have any luck. could you please help ? i was not able to find any more ideas on how to solve this problem full error: [ssh-agent] Using credentials emxtest (emxtest-agodlin-key) [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 java.io.IOException: Remote call on sdel64-04 failed at hudson.remoting.Channel.call(Channel.java:748) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:203) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:119) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:89) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:76) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1732) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: java.lang.ExceptionInInitializerError at jnr.ffi.FFIProvider.getSystemProvider(FFIProvider.java:33) at jnr.ffi.Runtime$SingletonHolder.(Runtime.java:37) at jnr.ffi.Runtime.getSystemRuntime(Runtime.java:32) at jnr.unixsocket.SockAddrUnix.(SockAddrUnix.java:34) at jnr.unixsocket.SockAddrUnix$DefaultSockAddrUnix.(SockAddrUnix.java:128) at jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:99) at jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:32) at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:66) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.RuntimeException: Could not load FFI provider jnr.ffi.provider.jffi.Provider at jnr.ffi.FFIProvider$SystemProviderSingletonHolder.getInstance(FFIProvider.java:78) at jnr.ffi.FFIProvider$SystemProviderSingletonHolder.(FFIProvider.java:64) ... 20 more Caused by: java.lang.UnsatisfiedLinkError: could not get native definition for type: POINTER at com.kenai.jffi.Type$InvalidLookupTable.find(Type.java:284) at com.kenai.jffi.Type$BuiltinTypeInfo.find(Type.java:319) at com.kenai.jffi.Type$Builtin.size(Type.java:216) at jnr.ffi.provider.jffi.NativeRuntime$TypeDelegate.size(NativeRuntime.java:153) at jnr.ffi.provider.AbstractRuntime.(AbstractRuntime.java:48) at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:55) at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:39) at jnr.ffi.provider.jffi.NativeRuntime$SingletonHolder.(NativeRuntime.java:51) at jnr.ffi.provider.jffi.NativeRuntime.getInstance(NativeRuntime.java:47) at jnr.ffi.provider.jffi.Provider.(Provider.java:31) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Met
[JIRA] [core] (JENKINS-18435) Navigating back, then forward, from a job configuration causes loss of config data
Daniel Beck updated JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data Similar issues affect multiple browsers, so removing Chrome from title. Given the number of issues that appear to be duplicates, raising priority. Change By: Daniel Beck (13/Jul/14 2:20 PM) Summary: Navigating back, then forward, from a job configuration causes loss of config data in Chrome Priority: Major 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] [email-ext] (JENKINS-23458) NullPointerException if Before Build reciepients is empty
Jan Hoppe resolved JENKINS-23458 as Cannot Reproduce NullPointerException if Before Build reciepients is empty Yes, but currently the problem has gone... Change By: Jan Hoppe (14/Jul/14 5:36 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-19316) Build with Params screen is not rendering lists and choices properly.
SCM/JIRA link daemon commented on JENKINS-19316 Build with Params screen is not rendering lists and choices properly. Code changed in jenkins User: mcupak Path: src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameter.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction.java src/main/resources/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction/index.jelly http://jenkins-ci.org/commit/build-with-parameters-plugin/1388c4440affe67e49c9a42c49ffb4e114554fbf Log: JENKINS-19316 added support for text parameters rendered via textareas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23492) UI improvements / refreshing
Tom FENNELLY commented on JENKINS-23492 UI improvements / refreshing We'll look into that Ulli. Thanks for letting us know. I agree with you re creating multiple JIRAs. I was flipping and flopping between doing it on one JIRA (as we currently are doing) and multiple JIRAs. I think if we do as you say and introduce a new "user experience" component, then we can use multiple JIRAs 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] [github] (JENKINS-23661) github webhook failing
SCM/JIRA link daemon resolved JENKINS-23661 as Fixed github webhook failing Change By: SCM/JIRA link daemon (14/Jul/14 3:10 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] [credentials] (JENKINS-20276) Native Library Error after upgrading ssh-agent from 1.3 to 1.4
arkady godlin edited a comment on JENKINS-20276 Native Library Error after upgrading ssh-agent from 1.3 to 1.4 Hello Stephen. i am trying to use this plugin and i encounter some problems. i am getting error [ssh-agent] Using credentials emxtest (emxtest-agodlin-key) [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 java.io.IOException: Remote call on sdel64-04 failed i tried to downgrade to 1.3. got still same problem. i even tried to downgrade to 1.1 and didn't have any luck. could you please help ? i was not able to find any more ideas on how to solve this problem full error: [ssh-agent] Using credentials emxtest (emxtest-agodlin-key) [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 java.io.IOException: Remote call on sdel64-04 failed at hudson.remoting.Channel.call(Channel.java:748) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentFactory.start(JNRRemoteAgentFactory.java:61) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$SSHAgentEnvironment.(SSHAgentBuildWrapper.java:203) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.createSSHAgentEnvironment(SSHAgentBuildWrapper.java:119) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper.preCheckout(SSHAgentBuildWrapper.java:89) at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:76) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529) at hudson.model.Run.execute(Run.java:1732) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Caused by: java.lang.ExceptionInInitializerError at jnr.ffi.FFIProvider.getSystemProvider(FFIProvider.java:33) at jnr.ffi.Runtime$SingletonHolder.(Runtime.java:37) at jnr.ffi.Runtime.getSystemRuntime(Runtime.java:32) at jnr.unixsocket.SockAddrUnix.(SockAddrUnix.java:34) at jnr.unixsocket.SockAddrUnix$DefaultSockAddrUnix.(SockAddrUnix.java:128) at jnr.unixsocket.SockAddrUnix.create(SockAddrUnix.java:99) at jnr.unixsocket.UnixSocketAddress.(UnixSocketAddress.java:32) at com.cloudbees.jenkins.plugins.sshagent.jna.AgentServer.start(AgentServer.java:66) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgent.(JNRRemoteAgent.java:64) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:54) at com.cloudbees.jenkins.plugins.sshagent.jna.JNRRemoteAgentStarter.call(JNRRemoteAgentStarter.java:35) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.RuntimeException: Could not load FFI provider jnr.ffi.provider.jffi.Provider at jnr.ffi.FFIProvider$SystemProviderSingletonHolder.getInstance(FFIProvider.java:78) at jnr.ffi.FFIProvider$SystemProviderSingletonHolder.(FFIProvider.java:64) ... 20 more Caused by: java.lang.UnsatisfiedLinkError: could not get native definition for type: POINTER at com.kenai.jffi.Type$InvalidLookupTable.find(Type.java:284) at com.kenai.jffi.Type$BuiltinTypeInfo.find(Type.java:319) at com.kenai.jffi.Type$Builtin.size(Type.java:216) at jnr.ffi.provider.jffi.NativeRuntime$TypeDelegate.size(NativeRuntime.java:153) at jnr.ffi.provider.AbstractRuntime.(AbstractRuntime.java:48) at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:55) at jnr.ffi.provider.jffi.NativeRuntime.(NativeRuntime.java:39) at jnr.ffi.provider.jffi.NativeRuntime$SingletonHolder.(NativeRuntime.java:51) at jnr.ffi.provider.jffi.NativeRuntime.getInstance(NativeRuntime.java:47) at jnr.ffi.provider.jffi.Provider.(Provider.java:31) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at
[JIRA] [git] (JENKINS-10131) Git polling shouldn't need a workspace on a slave.
Don Ross commented on JENKINS-10131 Git polling shouldn't need a workspace on a slave. Now that the default behavior of the plug-in is to use remote polling, does this mean we need to not use exclusion filters? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-19316) Build with Params screen is not rendering lists and choices properly.
SCM/JIRA link daemon commented on JENKINS-19316 Build with Params screen is not rendering lists and choices properly. Code changed in jenkins User: mcupak Path: src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameter.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction.java src/main/resources/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction/index.jelly http://jenkins-ci.org/commit/build-with-parameters-plugin/315101efb33c7c7792d1df9d47a5624f06f7caa0 Log: [FIXED JENKINS-19316] added support for choice parameters rendered via selects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-19316) Build with Params screen is not rendering lists and choices properly.
SCM/JIRA link daemon commented on JENKINS-19316 Build with Params screen is not rendering lists and choices properly. Code changed in jenkins User: mcupak Path: src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameter.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameterType.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction.java src/main/resources/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction/index.jelly src/test/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersActionTest.java http://jenkins-ci.org/commit/build-with-parameters-plugin/0349984bc7fe66f8a9ad4360157f1b9792dd976d Log: JENKINS-19316 added support for boolean parameters rendered via checkboxes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23771) Repository URL in Dashboard
Rupen Anjaria created JENKINS-23771 Repository URL in Dashboard Issue Type: Bug Assignee: Unassigned Components: subversion Created: 14/Jul/14 7:08 AM Description: Please refer https://issues.jenkins-ci.org/browse/JENKINS-23756 We need small modification to have facility to show Repository URL in Jenkin dashboard. This will help to identify in dashboard where the perticular Jenkin job is pointing to. Otherwise we have to see the configuration for the same. Project: Jenkins Priority: Major Reporter: Rupen Anjaria This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13551) Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set
ikedam commented on JENKINS-13551 Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set Or maybe same to JENKINS-13515. It is fixed in copyartifact 1.24. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23492) UI improvements / refreshing
SCM/JIRA link daemon commented on JENKINS-23492 UI improvements / refreshing Code changed in jenkins User: tfennelly Path: core/src/main/resources/lib/layout/breadcrumbs.css core/src/main/resources/lib/layout/breadcrumbs.js core/src/main/resources/lib/layout/layout.jelly core/src/main/resources/lib/layout/menu_down_arrow2.png war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/a277b73497edf8a0068a41b5a100d0c856782ce4 Log: JENKINS-23492 Fixed auth/login links in top navbar Compare: https://github.com/jenkinsci/jenkins/compare/b598301ec313...a277b73497ed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [build-with-parameters] (JENKINS-19316) Build with Params screen is not rendering lists and choices properly.
SCM/JIRA link daemon resolved JENKINS-19316 as Fixed Build with Params screen is not rendering lists and choices properly. Change By: SCM/JIRA link daemon (14/Jul/14 2:49 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] [drmemory] (JENKINS-23769) gen drmemory report fail ( dir not exist problem)
Praqma Support commented on JENKINS-23769 gen drmemory report fail ( dir not exist problem) Please provide your drmemory specific job configuration details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23492) UI improvements / refreshing
Tom FENNELLY commented on JENKINS-23492 UI improvements / refreshing New general layout using s f277502a83 Switch underline/non underline on sidebar in c438a5f2ab Line up elements in the left side 8057217f1f Fixed issue where empty welcome page callout block was appearing in 65d3799 Fixed auth/login links in top navbar in a277b73 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [configurationslicing] (JENKINS-23776) Matrix axes are sometimes treated as jobs
Andy Bigos created JENKINS-23776 Matrix axes are sometimes treated as jobs Issue Type: Bug Affects Versions: current Assignee: mdonohue Attachments: matrix-axes.PNG, matrix-jobs.PNG Components: configurationslicing Created: 14/Jul/14 2:05 PM Description: I'm seeing some odd behaviour for matrix jobs. In some cases I'm seeing each axis of the matrix being treated as a job. When I look at all my jobs in the 'Configuration by View->All' view I see a list of jobs, as expected. I have two views that contain jobs, each of these jobs is a matrix type. In one of the views I see the jobs I expect. In another view I see a list of all axes in the matrix job. I'm attaching 2 files to clarify. Matrix-Jobs.png shows a view containing a list of jobs - the expected behaviour. Matrix-Axes.ping shows a view that is displayed as a list of all the matrix configurations. As the matrix axes view consists of several hundred combinations it's impossible to use. Environment: Jenkins ver. 1.554.3 - stable. Project: Jenkins Priority: Major Reporter: Andy Bigos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Don Ross
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I ran these two commands on my slave and got the same results:
> git rev-parse "origin/release_branch^{commit}"
44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f
> git rev-parse "release_branch^{commit}"
9f74e3057c7fb30d2c001f886e394d5bea0271a
It looks like the local branch is not being updated to match the remote.
Which is not a surprise to me, since behavior in 1.1 was to check out detached, and never even create a local branch.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [memory-map] (JENKINS-23734) Memory map plugin does not allow to enter absolute or relative path
Praqma Support edited a comment on JENKINS-23734 Memory map plugin does not allow to enter absolute or relative path Would you please attach the memory map specific job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-14035) Responsive design
Daniel Beck resolved JENKINS-14035 as Fixed Responsive design Implemented in 1.572. Change By: Daniel Beck (14/Jul/14 4:45 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] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Don Ross
commented on JENKINS-20427
Build Parameter variable in branch name causes polling to detect false changes in GIT
I am seeing this same behavior after upgrading from 1.1.21 to 2.2.2.
I noticed that the default is now to always use Fast Remote Polling; in my production environment I have this option turned off. So, I enabled 'Force polling using workspace', and I am now seeing a different message (but the same behavior of false changes being found), as follows:
Started on Jul 14, 2014 1:16:38 PM
Polling SCM changes on slave-host-name
Using strategy: Default
[poll] Last Built Revision: Revision 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f (origin/release_branch)
> git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repositories
> git config remote.origin.url ssh://build@gitserver/git/product.git
Fetching upstream changes from ssh://build@gitserver/git/product.git
> git --version
> git fetch --tags --progress ssh://build@gitserver/git/product.git +refs/heads/*:refs/remotes/origin/*
Polling for changes in
> git rev-parse "origin/release_branch^{commit}"
> git rev-parse "release_branch^{commit}"
> git log --full-history --no-abbrev --format=raw -M -m --raw 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f..9f74e3057c7fb30d2c001f886e394d5bea0271a
Done. Took 1.8 sec
Changes found
It is interesting to me that the '9f74e3' commit ID in that git log command is the commit immediately before the '44bfcc7' commit.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Don Ross commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name We use a parameter because it is the only way to have other parts of the build job know what the branch is. IE, we set a parameter for the branch name, and use it when polling, and when pushing our results to Coverity, and when sending email notifications. Otherwise, every time I create a new job I need to manually edit all of these settings and you know I am going to miss one. Or three. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23774) Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
feng yu updated JENKINS-23774 Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor. Change By: feng yu (14/Jul/14 12:05 PM) Summary: Jenkins ver. 1.572 has a an exception in hudson.diagnosis.ReverseProxySetupMonitor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit] (JENKINS-9110) Add Build Date to Junit Test Result (History and Case View)
Chris Arnott commented on JENKINS-9110 Add Build Date to Junit Test Result (History and Case View) This page was updated with a missing localisation. @lukasfunk, has this resolved the problem you were seeing? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16338) Jenkins fails to keep connection alive on Windows 8
Daniel Beck resolved JENKINS-16338 as Incomplete Jenkins fails to keep connection alive on Windows 8 Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 1:59 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [fstrigger] (JENKINS-23211) Unable to updated or modify the project
Daniel Beck updated JENKINS-23211 Unable to updated or modify the project Change By: Daniel Beck (14/Jul/14 4:44 PM) Component/s: fstrigger Component/s: ui-changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck commented on JENKINS-21335 Forward slashes in a File Parameter's file location cause parameter download links to break Eric Anker: Ping! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
George Bloggs updated JENKINS-23779 Layout in 1.572 is broken in IE9 Change By: George Bloggs (14/Jul/14 3:57 PM) Description: The new layout introduced in 1.572 is broken in IE9, Version 9.0.28 (9.0.8112.16421). The CSS does no not appear to be laying out the page correctly. Page draw draws ok in FireFox 30. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16017) Workspace will not create in Jenkins from script
Daniel Beck resolved JENKINS-16017 as Incomplete Workspace will not create in Jenkins from script Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 2:04 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18866) Symlink prevens backup from ThinBackup
Bart Bialek edited a comment on JENKINS-18866 Symlink prevens backup from ThinBackup I have the same problem with Jenkins 1.550 and thinBackup 1.7 on CentOS 6.3: Jul 11, 2014 4:22:43 PM org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork backupNow SEVERE: Cannot perform a backup. Please be sure jenkins/hudson has write privileges in the configured backup path '/var/lib/jenkins/backups'. java.io.FileNotFoundException: Source '/var/lib/jenkins/jobs/Cron_AWD_Sitemap_Generation/builds/lastFailedBuild' does not exist at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:866) at org.apache.commons.io.FileUtils.copyDirectory(FileUtils.java:814) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildFiles(HudsonBackup.java:280) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupBuildsFor(HudsonBackup.java:263) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJob(HudsonBackup.java:202) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobsDirectory(HudsonBackup.java:190) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backupJobs(HudsonBackup.java:169) at org.jvnet.hudson.plugins.thinbackup.backup.HudsonBackup.backup(HudsonBackup.java:136) at org.jvnet.hudson.plugins.thinbackup.ThinBackupPeriodicWork.backupNow(ThinBackupPeriodicWork.java:87) at org.jvnet.hudson.plugins.thinbackup.ThinBackupMgmtLink$1.execute(ThinBackupMgmtLink.java:76) at org.jvnet.hudson.plugins.thinbackup.hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:54) at java.lang.Thread.run(Thread.java:722) The lastFailed build link points to a non existant file: /var/lib/jenkins/jobs/Cron_AWD_Sitemap_Generation/builds/lastFailedBuild -> -1 There are many other jobs that have these broken symlinks. I will manually remove them, but it would be nice for thinBackup to ignore them instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
ikedam resolved JENKINS-12732 as Not A Defect Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs The reporter seems no longer here. As I commented, this is not related to fingerprinting, and seems a file permission issue. Anyway, this issue is no linger valid, and I close it. Change By: ikedam (14/Jul/14 12:24 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ui-changes] (JENKINS-18514) Who is in the queue?
Daniel Beck resolved JENKINS-18514 as Duplicate Who is in the queue? Duplicates your other issue which I've fixed. Change By: Daniel Beck (14/Jul/14 4:46 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] [core] (JENKINS-18497) zipped files generated from userContent have their permissions removed/flattened
Daniel Beck resolved JENKINS-18497 as Incomplete zipped files generated from userContent have their permissions removed/flattened Resolving as Incomplete after no response for 2+ weeks to comment asking for updated information. Change By: Daniel Beck (13/Jul/14 1:58 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13551) Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set
ikedam commented on JENKINS-13551 Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set I cannot get what you mean with "instance of Jenkins". Anyway, it looks caused by a file permission problem. Please check followings: On whose authorization Jenkins slave runs. Who owes zzzBuild and BY_NAR_SOP8_Front.zip And it may be resolved by deleting zzzBuild at the beginning of a build. Please try that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [memory-map] (JENKINS-23734) Memory map plugin does not allow to enter absolute or relative path
Praqma Support commented on JENKINS-23734 Memory map plugin does not allow to enter absolute or relative path Would you please attach the job configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-23777) Support clear/set for all the boolean selection
Andy Bigos created JENKINS-23777 Support clear/set for all the boolean selection Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 14/Jul/14 2:12 PM Description: First thanks for this excellent plugin - nice job. I have a minor suggestion that I think would work quite nicely for handling large numbers of jobs with boolean options. For booleans it would be nice to have a select/clear all items in a view. We have a large number of jobs and often need to disable a group at a time. For example when we go into a release phase we enable a bunch of jobs that don't typically run. Being able to enable/disable all of these jobs in one go would be very useful. Thanks Andy Project: Jenkins Priority: Minor Reporter: Andy Bigos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21749) builds seem to hang forever and can't be canceled, but actually complete
Daniel Beck resolved JENKINS-21749 as Incomplete builds seem to hang forever and can't be canceled, but actually complete Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information, and the original issue report started out incomplete as well. Change By: Daniel Beck (13/Jul/14 2:05 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17948) Downstream projects section is not visibile and downstream projects are not triggered
Daniel Beck resolved JENKINS-17948 as Incomplete Downstream projects section is not visibile and downstream projects are not triggered Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 2:01 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23661) github webhook failing
SCM/JIRA link daemon commented on JENKINS-23661 github webhook failing Code changed in jenkins User: Nukul Bhasin Path: src/main/java/com/cloudbees/jenkins/GitHubWebHook.java http://jenkins-ci.org/commit/github-plugin/18e9de49c44ae56045945616e488f3cb9966f3c9 Log: Merge pull request #43 from hubba/master [FIXED JENKINS-23661] Compare: https://github.com/jenkinsci/github-plugin/compare/bf6ed268d626...18e9de49c44a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20038) saving Configure System page intermittently causes JDK install settings to change
Daniel Beck resolved JENKINS-20038 as Duplicate saving Configure System page intermittently causes JDK install settings to change Without response to comment in 2+ weeks, assuming this is a duplicate of JENKINS-18435. Change By: Daniel Beck (13/Jul/14 2: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] [ui-changes] (JENKINS-23773) Layout is broken in Version 1.572
Daniel Beck resolved JENKINS-23773 as Fixed Layout is broken in Version 1.572 Resolved in this commit: https://github.com/jenkinsci/jenkins/commit/a277b73497edf8a0068a41b5a100d0c856782ce4 Will probably be fixed in 1.574. Change By: Daniel Beck (14/Jul/14 4: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] [core] (JENKINS-5620) Hudson can't detect UTF-16 encoding for HTML files in workspace.
Daniel Beck resolved JENKINS-5620 as Incomplete Hudson can't detect UTF-16 encoding for HTML files in workspace. Resolving as Incomplete after no response for 2+ weeks to comment asking for updated information. Change By: Daniel Beck (13/Jul/14 1:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-23775) Shutdown of VM after Inactivity Failed
Florian Hug created JENKINS-23775 Shutdown of VM after Inactivity Failed Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 14/Jul/14 1:53 PM Description: After upgrading from 1.1.10 to 1.1.11 our VM Slaves (configured as "Take this note on-line when in demand and off-line when idle) will no longer shut down. To be more precise the idle counter is correctly triggered and the slave is disconnected. But afterwards the VM is not shut down (no command is send to the vSphere Server) and the Build slave reconnects and becomes online again. Reverting back to 1.1.10 solves the problem. Environment: Jenkins LTS 1.554.3, vSphere 5.5 Project: Jenkins Priority: Major Reporter: Florian Hug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-12618) Copy Artifact plugin - Access is denied to copy content
ikedam commented on JENKINS-12618 Copy Artifact plugin - Access is denied to copy content It looks caused by - file permission problem. Please check followings: On whose authorization Jenkins runs. Who owes ¥[downstream_dir]\Generated_Code\XX.XX.g.cs or ¥[downstream_dir]\Generated_Code And it may be resolved by deleting Generated_Code at the beginning of a build. Please try that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-23780) ActiveDirectoryTest should support to selection of Group Lookup Strategy
Scott Hebert created JENKINS-23780 ActiveDirectoryTest should support to selection of Group Lookup Strategy Issue Type: New Feature Assignee: Scott Hebert Components: acceptance-test-harness Created: 14/Jul/14 5:59 PM Description: The Acceptance Test Harness test case for Active Directory should support the selection of the Group Lookup Strategy that was introduced in version 1.38 of the AD plugin. Project: Jenkins Priority: Minor Reporter: Scott Hebert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11002) Windows DCOM slave fails to connect
Jeebitesh Kalantri reopened JENKINS-11002 Windows DCOM slave fails to connect Issue still persists on Windows 2008 R2 server and was never resolved for the same. Only windows 7 (all version) works with the provided fixes Change By: Jeebitesh Kalantri (14/Jul/14 10:09 AM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11002) Windows DCOM slave fails to connect
Jeebitesh Kalantri edited a comment on JENKINS-11002 Windows DCOM slave fails to connect We need this feature very badly, As Everything related to Windows 7 (Resolution) worked perfectly and we were able to create template out of the same, so that we never face the issue. But for Windows 2008 R2 (64 bit) Server, Issue still exists. I will try and work on getting the exact root cause, if we cannot get it working as issue is with NTLMv2 Authentication. As we are moving towards VMWare vSphere Cloud & Lab management features of Jenkins, this becomes more and more important for dynamic deployment. I am looking into this and will try assign it as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-with-parameters] (JENKINS-19316) Build with Params screen is not rendering lists and choices properly.
SCM/JIRA link daemon commented on JENKINS-19316 Build with Params screen is not rendering lists and choices properly. Code changed in jenkins User: Miroslav Cupak Path: src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameter.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildParameterType.java src/main/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction.java src/main/resources/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersAction/index.jelly src/test/java/org/jenkinsci/plugins/buildwithparameters/BuildWithParametersActionTest.java http://jenkins-ci.org/commit/build-with-parameters-plugin/829deeadf1198e72c7a912c9f694d0c22871a2d0 Log: Merge pull request #8 from mcupak/parameter-display [FIXED JENKINS-19316] improved handling of boolean, choice and text parameters Compare: https://github.com/jenkinsci/build-with-parameters-plugin/compare/545936db7cb4...829deeadf119 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23661) github webhook failing
SCM/JIRA link daemon commented on JENKINS-23661 github webhook failing Code changed in jenkins User: Nukul Bhasin Path: src/main/java/com/cloudbees/jenkins/GitHubWebHook.java http://jenkins-ci.org/commit/github-plugin/4cfd5efdc6665e768a2c114c3ccc3cd85d78fd33 Log: [FIXED JENKINS-23661] Github webhook specifies a "X-Github-Event" header but github services do not. This adds back the support github services that don't specify a header to just fallback on the old 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Weird. What about other web browsers? Could you provide a screenshot (with sensitive data removed) what the view (e.g. List View, Dashboard, ...) looks like? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [console-tail] (JENKINS-23778) Console output shown for unstable builds
Jan Wittig created JENKINS-23778 Console output shown for unstable builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: console-tail Created: 14/Jul/14 2:43 PM Description: The console output is also shown for unstable builds, i.e. "Finished: UNSTABLE" is shown in console. Environment: Windows Project: Jenkins Priority: Major Reporter: Jan Wittig This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14774) Failed to copy artifacts from another build job with timestamp exception
ikedam resolved JENKINS-14774 as Duplicate Failed to copy artifacts from another build job with timestamp exception Looks a duplicate of JENKINS-13515. It is fixed in 1.24. Change By: ikedam (14/Jul/14 10:39 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-23773) Layout is broken in Version 1.572
R. H. created JENKINS-23773 Layout is broken in Version 1.572 Issue Type: Bug Assignee: Unassigned Attachments: problem.PNG Components: ui-changes Created: 14/Jul/14 9:35 AM Description: Hello, the new layout is cool. But i have some wired problems in the Layout. Is that a common problem? Or comes this problem from an extension? Best Regards, Stony Environment: Jenkins 1.572 / Chrome Last Version Project: Jenkins Priority: Major Reporter: R. H. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22617) Can't delete crash report
R. H. closed JENKINS-22617 as Fixed Can't delete crash report Problem is solved. Change By: R. H. (14/Jul/14 9:25 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23492) UI improvements / refreshing
SCM/JIRA link daemon commented on JENKINS-23492 UI improvements / refreshing Code changed in jenkins User: tfennelly Path: core/src/main/resources/hudson/model/AllView/noJob.jelly http://jenkins-ci.org/commit/jenkins/65d3799f155fe11fe2c86e8be14a929707e9bd9e Log: JENKINS-23492 Fixed issue where empty welcome page callout block was appearing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [image-gallery] (JENKINS-23772) Percent for image width attribute
Balint Kovacs created JENKINS-23772 Percent for image width attribute Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: image-gallery Created: 14/Jul/14 9:12 AM Description: Allow responsive value for "Image width" attribute. Eg.: "80%". Plugin now allow only number in this filed. Project: Jenkins Priority: Major Reporter: Balint Kovacs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ui-samples] (JENKINS-21471) My jenkins crashed for once and now some options have gone missing
Daniel Beck resolved JENKINS-21471 as Not A Defect My jenkins crashed for once and now some options have gone missing Not a defect. After enabling security and setting 'logged in users can do anything', you need to log in to get full permissions back. Change By: Daniel Beck (14/Jul/14 4:48 PM) Status: In Progress Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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
Daniel Beck commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Alright, noticed one issue that still exists: If the folder you check out is changed (e.g. properties), results in StringIndexOutOfBoundsException. Will amend my PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-4390) Hudson hangs on archiving
Daniel Beck resolved JENKINS-4390 as Incomplete Hudson hangs on archiving Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 2:00 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14774) Failed to copy artifacts from another build job with timestamp exception
ikedam commented on JENKINS-14774 Failed to copy artifacts from another build job with timestamp exception It looks caused by a file permission problem. Please check followings: On whose authorization Jenkins runs. Who owes deploy and some_file.txt And it may be resolved by deleting the deploy directory at the beginning of a build. Please try that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23774) Jenkins ver. 1.572 has a exception in hudson.diagnosis.ReverseProxySetupMonitor.
feng yu
created JENKINS-23774
Jenkins ver. 1.572 has a exception in hudson.diagnosis.ReverseProxySetupMonitor.
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
14/Jul/14 12:04 PM
Description:
Jenkins told me reverse proxy setup is broken, but the older version is OK.
So I use this command from wiki: curl -iL http://your.reverse.proxy/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
Here is what I say:
HTTP/1.1 500 Server Error
Date: Mon, 14 Jul 2014 11:52:52 GMT
Server: Server: Jetty(7.x.x)
Cache-Control: no-cache,must-revalidate
X-Hudson-Theme: default
X-Frame-Options: sameorigin
Content-Type: text/html;charset=UTF-8
Set-Cookie: JSESSIONID.ed28295c=xdj0afbo9qxg1nc2ha0fnj8r6;Path=/jenkins
Expires: Thu, 01 Jan 1970 00:00:00 GMT
X-Hudson: 1.395
X-Jenkins: 1.572
X-Jenkins-Session: d1d89bb0
X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsOFirN6go5UvL/Ve6c+7uNF47wPrAis9aAZWSEYGWYHBOGp+AHzVhebh3cP814+KrdDrQp1HoP9l6+GG4IkPukeadtVg6iKIwhajRJHZiK+UzS0kaBJUt49rpDTqx31HkoKdERWOefKxOmMsU4d9ja+ou+n+GhCHE8FLzO7eFH7LMaqiI7n7MY5i+K0nLY3/mIQE1SIZIwsDlUHlI1iEWP9oSAHm6+cOXfIf2dyMkY+PZqJ3pVUATAirLL1dKLAQlNYNJLEJU9WQTi43BysPxVCimZXAl4wryAH+cnstStA1qvtlgmSUfH4ydW5dDMFcjMjMrE/3LtfoBByJSpgX5wIDAQAB
Connection: close
Transfer-Encoding: chunked
Jenkins [Jenkins]var isRunAsTest=false; var rootURL="/jenkins"; var resURL="/jenkins/static/d1d89bb0";crumb.init("", "");var Q=jQuery.noConflict()Skip to content 登录
注册 createSearchBox("/jenkins/search/");Jenkins
Jenkins project
Bug tracker
Mailing Lists
Twitter: @jenkinsci Oops!A problem occurred while processing the request.
Please check our bug tracker to see if a similar problem has already been reported.
If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.
If you think this is a new issue, please file a new issue.
When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.
The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: java.lang.NullPointerException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.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.a
[JIRA] [copyartifact] (JENKINS-13551) Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set
ikedam commented on JENKINS-13551 Copy Artifact fails if selector class="hudson.plugins.copyartifact.StatusBuildSelector" is set This may be the same issue to /ENKINS-11073 . It should be fixed with Jenkins 1.447. Please report your Jenkins and copyartifact versions if the problem still remains. I'll close this issue if no more reports in a month. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
SCM/JIRA link daemon commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration Code changed in jenkins User: rym002 Path: src/main/resources/hudson/plugins/accurev/AccurevSCM/global.jelly http://jenkins-ci.org/commit/accurev-plugin/13b88b5ab0251f48b0fc9f281a0bcfd6b150b9d2 Log: Merge pull request #16 from rym002/JENKINS-21496 Jenkins 21496 Compare: https://github.com/jenkinsci/accurev-plugin/compare/a2729a6abf67...13b88b5ab025 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23718) Unable to use ${NODE_NAME} as a Workspace name
Paul Allen
commented on JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
I'm still looking into the best implementation for this issue.
Currently I only support ${...} formatters for template and streams workspaces, but I can understand why you need them for static workspaces.
That part of change is fairly simple, but I am trying to understand how to access environment vars. I have been experimenting with Parameters builds vars and environment vars, but not sure about their visibility outside of a build (e.g. SCM polling).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-21748) Cloud slaves do not take work when master executor has 0 for the number of executors
Daniel Beck resolved JENKINS-21748 as Incomplete Cloud slaves do not take work when master executor has 0 for the number of executors Resolving as Incomplete after no response for 2+ weeks to comment asking for additional information. Change By: Daniel Beck (13/Jul/14 2:09 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23774) Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
feng yu
updated JENKINS-23774
Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
Change By:
feng yu
(14/Jul/14 12:09 PM)
Description:
Jenkins told me reverse proxy setup is broken, but the older version is OK.So I use this command from wiki: curl -iL http://your.reverse.proxy/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testHere is
my apache configure:ServerAdmin webmaster@localhostDocumentRoot /var/www/htmlErrorLog ${APACHE_LOG_DIR}/error.logCustomLog ${APACHE_LOG_DIR}/access.log combinedServerName localhostProxyRequests offProxyPreserveHost OnSetEnv proxy-nokeepalive 1ProxyPass /jenkins ajp://127.0.0.1:8009/jenkins nocanonAllowEncodedSlashes NoDecodeAnd here is
what I
say
saw
:HTTP/1.1 500 Server ErrorDate: Mon, 14 Jul 2014 11:52:52 GMTServer: Server: Jetty(7.x.x)Cache-Control: no-cache,must-revalidateX-Hudson-Theme: defaultX-Frame-Options: sameoriginContent-Type: text/html;charset=UTF-8Set-Cookie: JSESSIONID.ed28295c=xdj0afbo9qxg1nc2ha0fnj8r6;Path=/jenkinsExpires: Thu, 01 Jan 1970 00:00:00 GMTX-Hudson: 1.395X-Jenkins: 1.572X-Jenkins-Session: d1d89bb0X-Instance-Identity: MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsOFirN6go5UvL/Ve6c+7uNF47wPrAis9aAZWSEYGWYHBOGp+AHzVhebh3cP814+KrdDrQp1HoP9l6+GG4IkPukeadtVg6iKIwhajRJHZiK+UzS0kaBJUt49rpDTqx31HkoKdERWOefKxOmMsU4d9ja+ou+n+GhCHE8FLzO7eFH7LMaqiI7n7MY5i+K0nLY3/mIQE1SIZIwsDlUHlI1iEWP9oSAHm6+cOXfIf2dyMkY+PZqJ3pVUATAirLL1dKLAQlNYNJLEJU9WQTi43BysPxVCimZXAl4wryAH+cnstStA1qvtlgmSUfH4ydW5dDMFcjMjMrE/3LtfoBByJSpgX5wIDAQABConnection: closeTransfer-Encoding: chunkedJenkins [Jenkins]|Please check If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.If you think this is a new issue, please file a new issue.When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.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:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurit
[JIRA] [core] (JENKINS-11265) rssFailed feed should not report "not built" modules in a Maven 3 multi-module project with incremental build enabled.
Daniel Beck resolved JENKINS-11265 as Incomplete rssFailed feed should not report "not built" modules in a Maven 3 multi-module project with incremental build enabled. Resolving as Incomplete after no response for 2+ weeks to comment asking for updated and additional information. Change By: Daniel Beck (13/Jul/14 2:02 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13753) plink call in build.bat file doesn't execute remote shell script
Daniel Beck resolved JENKINS-13753 as Incomplete plink call in build.bat file doesn't execute remote shell script Resolving as Incomplete after no response for 3+ months to comment asking for updated information. Change By: Daniel Beck (13/Jul/14 2:03 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23774) Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
Daniel Beck commented on JENKINS-23774 Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor. The request's referer does not seem to be set. Are you using some kind of "privacy protection" software? Anti-Malware with web-related features? What web browser and OS (in which versions?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-5125) "Block build when upstream is building" option is not working with multiple executors
Daniel Beck commented on JENKINS-5125 "Block build when upstream is building" option is not working with multiple executors Is anyone still experiencing this problem on recent Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23492) UI improvements / refreshing
dogfood commented on JENKINS-23492 UI improvements / refreshing Integrated in jenkins_main_trunk #3521 JENKINS-23492 Fixed issue where empty welcome page callout block was appearing. (Revision 65d3799f155fe11fe2c86e8be14a929707e9bd9e) JENKINS-23492 Fixed auth/login links in top navbar (Revision a277b73497edf8a0068a41b5a100d0c856782ce4) Result = SUCCESS tom.fennelly : 65d3799f155fe11fe2c86e8be14a929707e9bd9e Files : core/src/main/resources/hudson/model/AllView/noJob.jelly tom.fennelly : a277b73497edf8a0068a41b5a100d0c856782ce4 Files : war/src/main/webapp/css/style.css core/src/main/resources/lib/layout/breadcrumbs.css core/src/main/resources/lib/layout/menu_down_arrow2.png core/src/main/resources/lib/layout/breadcrumbs.js core/src/main/resources/lib/layout/layout.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
