美眉带着一个小孩美腿是亮点
美眉带着一个小孩美腿是亮点 删除字 --浅谈如何选择网站设计服务商 nzfj.hioe浅谈如何选择网站设计服务商m.ce浅谈如何选择网站设计服务商om?op6ii4dq6 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24272) jnlp slaves fail to reconnect when master is restarted
Daniel Beck
updated JENKINS-24272
jnlp slaves fail to reconnect when master is restarted
Change By:
Daniel Beck
(14/Aug/14 6:00 PM)
Description:
IhavenoticedthatwheneverIrestartmyJenkinsmastermyjnlpslavesarenotreconnectingandrequireamanualslaverestarttobringthembackonline.IvetracedthisbacktothechangestofixJENKINS-19055.SpecificallythosechangescausetheslaveJVMtoberestartedwhenthemasterdisconnects.Priortothischangetheremotingenginewouldwaitfortheservertorestartbeforeattemptingtoreconnecttothemaster.Withthechangeitimmediatelytriestoconnecttothemasterandgetaconnectionerrorbecausethemasterisrestarting.Thiscausestheslavetoimmediatelyterminate.Jenkins1.575givesthefollowingslavelogoutputwhenrestartingthemaster{noformat}Aug12,20143:55:15PMhudson.remoting.jnlp.Main$CuiListenerstatusINFO:TerminatedAug12,20143:55:15PMjenkins.slaves.restarter.JnlpSlaveRestarterInstaller$2$1onDisconnectINFO:Restartingslaveviajenkins.slaves.restarter.UnixSlaveRestarter@32a9f661Aug12,20143:55:17PMhudson.remoting.jnlp.MaincreateEngineINFO:Settingupslave:bishopAug12,20143:55:17PMhudson.remoting.jnlp.Main$CuiListenerinitINFO:Jenkinsagentisrunninginheadlessmode.Aug12,20143:55:17PMhudson.remoting.jnlp.Main$CuiListenerstatusINFO:Locatingserveramong[http://jenkins.example/]Aug12,20143:55:18PMhudson.remoting.jnlp.Main$CuiListenererrorSEVERE:http://jenkins.example/tcpSlaveAgentListener/isinvalid:503ServiceTemporarilyUnavailablejava.lang.Exception:http://jenkins.example/tcpSlaveAgentListener/isinvalid:503ServiceTemporarilyUnavailableathudson.remoting.Engine.run(Engine.java:213){noformat}Noticethejenkins.slaves.restarter.JnlpSlaveRestarterInstalleronDisconnectlogmessagethatperformsaslaverestart.PriortoJENKINS-19055beingintegratedtheslavecalledwaitForServerToBack()repeatedlyuntilthemastercamebackonline.Forexample{noformat}25-Mar-201410:52:16hudson.remoting.jnlp.Main$CuiListenerstatusINFO:Terminated25-Mar-201410:52:26hudson.remoting.EnginewaitForServerToBackINFO:Failedtoconnecttothemaster.Willretryagainjava.net.ConnectException:Connectionrefusedatjava.net.PlainSocketImpl.socketConnect(NativeMethod)atjava.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)atjava.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)atjava.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)atjava.net.SocksSocketImpl.connect(SocksSocketImpl.java:385)atjava.net.Socket.connect(Socket.java:546)atsun.net.NetworkClient.doConnect(NetworkClient.java:173)atsun.net.www.http.HttpClient.openServer(HttpClient.java:409)atsun.net.www.http.HttpClient.openServer(HttpClient.java:530)atsun.net.www.http.HttpClient.init(HttpClient.java:240)atsun.net.www.http.HttpClient.New(HttpClient.java:321)atsun.net.www.http.HttpClient.New(HttpClient.java:338)atsun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:935)atsun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:876)atsun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:801)athudson.remoting.Engine.waitForServerToBack(Engine.java:371)athudson.remoting.Engine.run(Engine.java:278)...25-Mar-201410:54:11hudson.remoting.EnginewaitForServerToBackINFO:Masterisntreadytotalktous.Willretryagain:responsecode=50325-Mar-201410:54:21hudson.remoting.EnginewaitForServerToBackINFO:Masterisntreadytotalktous.Willretryagain:responsecode=50325-Mar-201410:54:31hudson.remoting.jnlp.Main$CuiListenerstatusINFO:Locatingserveramong[http://jenkins.example/]25-Mar-201410:54:31hudson.remoting.jnlp.Main$CuiListenerstatusINFO:Connectingtojenkins.example:4271525-Mar-201410:54:31hudson.remoting.jnlp.Main$CuiListenerstatusINFO:Handshaking25-Mar-201410:54:32hudson.remoting.jnlp.Main$CuiListenerstatusINFO:Connected
{noformat}
[JIRA] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys break SSH credentials plugin
stephenconnolly commented on JENKINS-24273 Presence of ECDSA SSH keys break SSH credentials plugin The support for ECDSA keys is in MINA's SSH 0.12.0 and works with the ssh-agent plugin IIRC my testing of it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe edited a comment on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: Manage Jenkins Configure System Scroll to JDK installations Add JDK Installation Provide JAVA_HOME path to the JDK folder on the client/slave such as C:\Progra~2\Java\jdk1.7.0_67 where Proga~2 resolves to Program Files (x86) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23905) Jenkins Slaves launched with the incorrect environment variables
Sam Xiao commented on JENKINS-23905 Jenkins Slaves launched with the incorrect environment variables +1 We had the same issue on 1.89. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Daniel Christophis edited a comment on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
Tom FENNELLY created JENKINS-24282 Use noun phrases for new items Issue Type: Improvement Assignee: Tom FENNELLY Attachments: current.png, target.png Components: core Created: 15/Aug/14 8:02 AM Description: Freestyle project rather than Build a free-style software project, and so on. Should make Folder, Workflow, etc. look less out of place. Look for impls of TopLevelItemDescriptor.getDisplayName. Most will be out in non-core repos (plugins etc). Project: Jenkins Labels: user-experience Priority: Minor Reporter: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer] (JENKINS-24140) ArtifactDeployer migration breaks lazy-load on Jenkins initialization
Gregory Boissinot resolved JENKINS-24140 as Fixed ArtifactDeployer migration breaks lazy-load on Jenkins initialization I don't know how to make migration with lazy-loading capabilities. Maybe it is not possible. I choose an alternative with few limitations for the new solution. Please test the new version 0.32. Change By: Gregory Boissinot (14/Aug/14 8:29 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] [active-directory] (JENKINS-24248) Cannot configure Active Directory Bind DN or Bind Password
Paul Landolt commented on JENKINS-24248 Cannot configure Active Directory Bind DN or Bind Password Ah! well that makes sense, as I just recall that the person who gave me that attached image is running Jenkins "ver. 1.554.2.2 (Jenkins Enterprise by CloudBees 14.05)" on a Linux machine. I grabbed an eval license to run on my windows machine, and do not see those fields. I'm wondering if JENKINS-22346 is related to these missing fields. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
Hendrik Halkow commented on JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin Yes, I do have the unrestricted JCA policy in the master's JVM. I am running the latest LTS version 1.565.1 on Java 8 update 11. Same happens with the latest Jenkins version, 1.575. Below is my slave connection log. Have a look at the exception and the link I posted above. ERROR: Failed to authenticate as build-tcc with credential=872d37c9-0500-4097-ad35-9fbbdb50edbd java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:106) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:408) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:428) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1138) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:224) ... 11 more 08/14/14 21:14:16 SSH Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 08/14/14 21:14:16 SSH Connection closed. 08/14/14 21:14:16 Launch failed - cleaning up connection This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24278) Node monitor for free inodes
Daniel Beck created JENKINS-24278 Node monitor for free inodes Issue Type: New Feature Assignee: Daniel Beck Components: core, plugin Created: 15/Aug/14 3:55 AM Description: Cor or plugin feature: Add a node monitor (similar to free disk space) for free inodes on Linux systems. Background: All those GBs of free disk space won't help you if you can't create another file. Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe commented on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: 1. Manage Jenkins 1. Configure System 1. Scroll to JDK installations 1. Add JDK Installation 1. Provide JAVA_HOME path to the JDK folder on the client/slave such as `C:\Progra~2\Java\jdk1.7.0_67` *where Proga~2 is Program Files (x86) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
Maurice W. commented on JENKINS-24145 latest ghprb plugin broken for gihub enterprise users There are a number of folks on GitHub that have reported the same issue: https://github.com/janinko/ghprb/issues/178 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [msbuild] (JENKINS-24276) MSBuild targeting both Debug and Release configurations fails
James Talton created JENKINS-24276 MSBuild targeting both Debug and Release configurations fails Issue Type: Bug Affects Versions: current Assignee: kdsweeney Components: msbuild Created: 14/Aug/14 6:38 PM Description: Running MSBuild.exe and targeting both Debug and Release with /p:Configuration="Debug;Release" fails as the quotes are stripped out of the final command line used by Jenkins. There are several other fixes and bugs around the removing of the quotes which should be reviewed and taken into account when considering a fix for this issue. Environment: Windows 8 x64 Project: Jenkins Labels: msbuild Priority: Major Reporter: James Talton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys break SSH credentials plugin
stephenconnolly commented on JENKINS-24273 Presence of ECDSA SSH keys break SSH credentials plugin do you have the unrestricted JCA policy in your master's JVM? Most ECDSA keys are too long to run without unrestricted This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-17096) Differences in config spec detected when config spec is read from file
Vincent Latombe resolved JENKINS-17096 as Fixed Differences in config spec detected when config spec is read from file Change By: Vincent Latombe (14/Aug/14 5:26 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Mike Dubman commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Alex We can have a screen-sharing session to show you what is meant here. Please drop me a line if interested. 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] [managed-scripts] (JENKINS-20963) Allow managed scripts to be called from a post build task
Asko Soukka commented on JENKINS-20963 Allow managed scripts to be called from a post build task @domruf Any success? This would be a really nice 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] [build-name-setter] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.
Damien Nozay
created JENKINS-24277
BUILD_USER_ID not available for build-name-setter plugin.
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
build-name-setter, build-user-vars
Created:
14/Aug/14 11:13 PM
Description:
Hi,
i am trying to use the build-name-setter plugin to change the name of each build to also include the user id (e.g. job has parameters and is user-triggered); for that, i am trying to leverage the user build variables provided by the build-user-vars plugin.
a test job that i created with those 2 plugin has this configuration:
Build name: #${BUILD_NUMBER} - by ${BUILD_USER_ID}
but at runtime, I get:
Unrecognized macro 'BUILD_USER_ID' in '#${BUILD_NUMBER} - by ${BUILD_USER_ID}'
Unrecognized macro 'BUILD_USER_ID' in '#${BUILD_NUMBER} - by ${BUILD_USER_ID}'
Environment:
jenkins LTS, build-name-setter plugin 1.3, build-user-vars-plugin 1.3
Project:
Jenkins
Priority:
Major
Reporter:
Damien Nozay
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-23645) Archiving artifacts does not preserve timestamps if archived on master
Daniel Beck commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if archived on master FWIW some citation needed consider running no builds on the master node a Jenkins best practice, so that may be worth implementing even beyond this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [www] (JENKINS-8694) make all links work with https
Daniel Beck resolved JENKINS-8694 as Cannot Reproduce make all links work with https No response in months to comment asking for updated information, so resolving as Cannot Reproduce. Due to the age of this, please file a new issue if this occurs (still or again) in recent Jenkins versions. Change By: Daniel Beck (15/Aug/14 3:53 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
SCM/JIRA link daemon commented on JENKINS-24258 Broken Build Timeout Plugin implementation Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/TimeoutContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f6ab91cb7488ee4f10410c79a42b37d0a2706295 Log: JENKINS-24258 Broken Build Timeout Plugin implementation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer] (JENKINS-24140) ArtifactDeployer migration breaks lazy-load on Jenkins initialization
SCM/JIRA link daemon commented on JENKINS-24140 ArtifactDeployer migration breaks lazy-load on Jenkins initialization Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/artifactdeployer/DeployedArtifacts.java src/main/java/org/jenkinsci/plugins/artifactdeployer/migration/DeployedArtifactsMigrationItemListener.java src/main/resources/org/jenkinsci/plugins/artifactdeployer/DeployedArtifactsResult/index.jelly http://jenkins-ci.org/commit/artifactdeployer-plugin/f11b368abd0b70339782b4e41e731ae3b7efd237 Log: Fix JENKINS-24140 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactdeployer] (JENKINS-24140) ArtifactDeployer migration breaks lazy-load on Jenkins initialization
Antoine Musso commented on JENKINS-24140 ArtifactDeployer migration breaks lazy-load on Jenkins initialization Gregory, on the first upgrade, I have let the migration complete which took several hours. On the next restart, it started over again which prompted me to downgrade the plugin. It seems the migration is triggered very early in Jenkins startup process. Maybe it can be triggered asynchronously after Jenkins has booted (and at least the web gui is made available).If a job hasn't been migrated yet, the build could trigger the migration. Aka lazy migration :-] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed
Daniel Beck commented on JENKINS-23442 Jenkins 1.568 can not start when monitoring plugin is installed Can this be reproduced with Jenkins out of the box, only installing this plugin? I can't on CentOS, but maybe you can? If not, would be interesting if anyone experiencing this could provide a full list of plugins installed. (Go to /systemInfo and scroll down.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
Hendrik Halkow edited a comment on JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin Yes, I do have the unrestricted JCA policy in the master's JVM. I am running the latest LTS version 1.565.1 on Java 8 update 11. Same happens with the latest Jenkins version, 1.575. On the command line, my ECDSA keys work fine. Below is my slave connection log. Have a look at the exception and the link I posted above. ERROR: Failed to authenticate as build-tcc with credential=872d37c9-0500-4097-ad35-9fbbdb50edbd java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:315) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:467) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:106) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:408) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:428) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1138) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Invalid PEM structure, '-BEGIN...' missing at com.trilead.ssh2.crypto.PEMDecoder.parsePEM(PEMDecoder.java:138) at com.trilead.ssh2.crypto.PEMDecoder.decode(PEMDecoder.java:313) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:224) ... 11 more 08/14/14 21:14:16 SSH Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1143) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:648) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) 08/14/14 21:14:16 SSH Connection closed. 08/14/14 21:14:16 Launch failed - cleaning up connection This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nested-view] (JENKINS-23283) nested view plugin get list of jobs in a sub view ?
Michael Payne
commented on JENKINS-23283
nested view plugin get list of jobs in a sub view ?
Not sure if I understand your use of subview and nested view here. Is this what you want?
def parent = Hudson.instance.getView("Parent_View")
def views = parent.getViews()
def view = views.find {it.getDisplayName() == 'Child_View'}
for(item in view.getItems()) {
println(item.name)
}
}
Perhaps you can elaborate on the requirement here.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-20307) Job status page shows Build has been executing for null on master
jlongman commented on JENKINS-20307 Job status page shows Build has been executing for null on master Also seeing this on 1.571 hosted on a FreeBSD 9.1 machine. Started 3 hr 21 min ago Build has been executing for null on xlicenses May be related to null time refereces in the build progress column plugin, which shows Started null ago Estimated time remaining null (May because the actual parent job has a non-null time for Started ago.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy] (JENKINS-24275) The deploy plugin does not support build parameters
Laimonas S commented on JENKINS-24275 The deploy plugin does not support build parameters Created a pull request with possible solution to the described problem: https://github.com/jenkinsci/deploy-plugin/pull/16 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: tfennelly Path: src/main/resources/org/cloudbees/literate/jenkins/Messages.properties http://jenkins-ci.org/commit/literate-plugin/a0925f1824ca2dae8cdcd03a42df3ac32dffa5ca Log: Use noun phrases for new items JENKINS-24282 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-18935) Make Subversion plugin support Subversion 1.8
Ben Daniels commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 @Jeff @Saad - I've just run into this issue as well since we have a planned upgrade from SVN 1.6 to the latest (1.8) and now I'm finding that our Jenkins server could potentially derail that and force us to only move up to 1.7 We rely heavily on SCM polling among other features, and it's quite frustrating that there is no compatibility with 1.8. There are still plenty of folks using Subversion that need this functionality. I really don't want to introduce pre-build steps of running SVN_UPGRADE and doing full checkouts. If everyone here is onboard, do we know who is developing the Subversion plugin to ask them if 1.8 support is on the roadmap for their particular version of SVNKit? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck updated JENKINS-24287 EnvInject exposes password hashes Change By: Daniel Beck (15/Aug/14 3:16 PM) Labels: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-23946) Artifact Resolver failed to expand tokens for [Artifact...
Stephen B commented on JENKINS-23946 Artifact Resolver failed to expand tokens for [Artifact... I'm having the same issue. I have a parameterized build, but the Artifact Resolver Build step isn't taking in any of those parameters. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-24288) Noclassdef found in openID plugin
junaid shaikh commented on JENKINS-24288 Noclassdef found in openID plugin To be noted that I am behind a proxy. But I dont think it should cause this error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-20307) Job status page shows Build has been executing for null on master
Daniel Beck commented on JENKINS-20307 Job status page shows Build has been executing for null on master See above linked PR 1348 for an explanation and proposed solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24261) Assembla browser breaks config page
Mark Waite assigned JENKINS-24261 to Mark Waite Assembla browser breaks config page Change By: Mark Waite (15/Aug/14 12:00 PM) Assignee: NicolasDeLoof MarkWaite This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert stopped work on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (15/Aug/14 3:51 PM) Status: InProgress 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] [plugin-usage] (JENKINS-24288) Noclassdef found in openID plugin
junaid shaikh created JENKINS-24288 Noclassdef found in openID plugin Issue Type: Bug Assignee: Unassigned Components: plugin-usage Created: 15/Aug/14 2:38 PM Description: was trying to get CAS to work as openID provider and use that openID provider url to login to jenkins. On my CAS side I have a server url as "http://myserver/cas-openid-server/login". However, everytime I try to user this url in jenkins using your plugin, I get this error page which says "javax.servlet.ServletException: java.lang.NoClassDefFoundError: org/openid4java/util/OpenID4JavaDOMParser". The error log doesn't say much Project: Jenkins Labels: plugin jenkins openid error Priority: Major Reporter: junaid shaikh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: tfennelly Path: src/main/resources/hudson/matrix/Messages.properties http://jenkins-ci.org/commit/matrix-project-plugin/611d4b1d167fdf2bf92b9a2f1ae4fa54dc08d9a0 Log: Use noun phrases for new items JENKINS-24282 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-24289) FindBugs Plugin does not honor setting Only use stable builds as reference being off
Markus Schlegel created JENKINS-24289 FindBugs Plugin does not honor setting Only use stable builds as reference being off Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Attachments: Trunk_BuildInstaller Config [Jenkins]_2014-08-15_16-54-12.jpg Components: findbugs Created: 15/Aug/14 2:56 PM Description: It seems to make no difference if "Only use stable builds as reference" is checked or not. The calculation of "new" warnigns always references the last stable build. Attached a screenshot which shows my config. Project: Jenkins Priority: Minor Reporter: Markus Schlegel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cygpath] (JENKINS-20364) Failed to locate cygwin installation
Greg Warner
edited a comment on JENKINS-20364
Failed to locate cygwin installation
I'm seeing this bug too. I ran the failing line using the jython console. I tried both
SOFTWARE\\Cygwin
and
SOFTWARE\\Wow6432Node\\Cygwin
and they both failed. It does, however, find plain ol' "SOFTWARE". Also, I try other keys such as
SOFTWARE\\[Motorola,Intel,TrendMicro]
and it finds all of them. So this seems to be a cygwin-specific problem.
RegistryKey.LOCAL_MACHINE.openReadonly("SOFTWARE\\Cygwin")
Traceback (most recent call last):
File "stdin", line 1, in module
at hudson.util.jna.RegistryKey.check(RegistryKey.java:124)
at hudson.util.jna.RegistryKey.open(RegistryKey.java:223)
at hudson.util.jna.RegistryKey.openReadonly(RegistryKey.java:218)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
hudson.util.jna.JnaException: hudson.util.jna.JnaException: Win32 error: 2 - The
system cannot find the file specified
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: tfennelly Path: src/main/resources/hudson/maven/Messages.properties http://jenkins-ci.org/commit/maven-plugin/354a762b3250c8a92edc640151fb1f48083c14a1 Log: Use noun phrases for new items JENKINS-24282 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-23245) Performance improvement, use catcs to create loadrules (case 11385)
Mads Nielsen resolved JENKINS-23245 as Fixed Performance improvement, use catcs to create loadrules (case 11385) Change By: Mads Nielsen (15/Aug/14 11:39 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman updated JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Change By: Mike Dubman (15/Aug/14 5:53 AM) Description: Hi,Isthatpossibletoallowrunningshellscript /inline commandbeforetakingactionwhentimeoutoccures(actionlikefail/abort).Theuse-caseforthisrequestistoextractstacktraceswithgstackorgdbfromhangingjobbeforebuild-timeoutabortsit?Also,asadditionpre-ontimeoutaction,plugincansendemailtospecificaddressandwaitforsomesentinelfiletoberemovedbyuser.Thiswillallowdevelopertoconnecttothehangingjob,examine/debughang,removesentinelfileandjobwillresumeabort/failroutine.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] [ssh-slaves] (JENKINS-20108) SSH slaves can block for a long time in NativePRNG
Jesse Glick assigned JENKINS-20108 to Unassigned SSH slaves can block for a long time in NativePRNG Change By: Jesse Glick (15/Aug/14 2:22 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
Tom FENNELLY
commented on JENKINS-24282
Use noun phrases for new items
The following are trimmed down greps of what I think might need to be looked at (across all repos in the jenkinsci github org).
TopLevelItemDescriptor:
./repos/strawboss-plugin/src/main/java/captmorgan/ExternalProject.java: public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/views/AbstractWrapper.java: public TopLevelItemDescriptor getDescriptor() {
./repos/jenkins.py/python-wrapper/src/main/java/jenkins/python/descriptor/TopLevelItemDescriptorPW.java:public abstract class TopLevelItemDescriptorPW extends TopLevelItemDescriptor {
./repos/jenkow-plugin/jenkow-plugin/src/main/java/com/cisco/step/jenkins/plugins/jenkow/JenkowWorkflowJob.java://public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/drools-plugin/drools/src/main/java/hudson/drools/DroolsProject.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:import hudson.model.TopLevelItemDescriptor;
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/organizationcontainer/OrganizationContainer.java: public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/item-forwarder-plugin/src/main/java/org/jenkinsci/plugins/item_forwarding/ForwardingItem.java:public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/jprt-plugin/src/main/java/hudson/plugins/jprt/JPRTJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/external-monitor-job-plugin/src/main/java/hudson/model/ExternalJob.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public TopLevelItemDescriptor getDescriptor() {
./repos/branch-api-plugin/src/main/java/jenkins/branch/MultiBranchProjectDescriptor.java:public abstract class MultiBranchProjectDescriptor extends TopLevelItemDescriptor {
./repos/categorized-view-plugin/src/main/java/org/jenkinsci/plugins/categorizedview/GroupTopLevelItem.java: public TopLevelItemDescriptor getDescriptor() {
AbstractProjectDescriptor:
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/jobgenerator-plugin/src/main/java/org/jenkinsci/plugins/jobgenerator/JobGenerator.java: extends AbstractProjectDescriptor {
./repos/matrix-project-plugin/src/main/java/hudson/matrix/MatrixProject.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/build/DynamicProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-plugin/src/main/java/hudson/maven/MavenModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-release-cascade-plugin/src/main/java/com/barchart/jenkins/cascade/CascadeProject.java: public static class TheDescriptor extends AbstractProjectDescriptor {
./repos/build-flow-plugin/src/main/java/com/cloudbees/plugins/flow/BuildFlow.java:public static class BuildFlowDescriptor extends AbstractProjectDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public static class DescriptorImpl extends AbstractProjectDescriptor {
./repos/ivy-plugin/src/main/java/hudson/ivy/IvyModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
What else should I search for?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA
[JIRA] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
SCM/JIRA link daemon commented on JENKINS-24258 Broken Build Timeout Plugin implementation Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/TimeoutContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/wrapper/WrapperHelperSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c34da4dbe36a1417964c8a19126436df3fc0e305 Log: Merge pull request #262 from CoreMedia/JENKINS-24258 JENKINS-24258 Fixed broken build timeout plugin implementation Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/27c21aa1037e...c34da4dbe36a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-22706) git fetching fails after switching from HTTPS to SSH
Emil Styrke commented on JENKINS-22706 git fetching fails after switching from HTTPS to SSH As per this comment, the problem may be that java.io.tmpdir contains spaces. Setting this variable to "C:\temp" fixed this problem for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-17096) Differences in config spec detected when config spec is read from file
Vincent Latombe commented on JENKINS-17096 Differences in config spec detected when config spec is read from file According to the commit information, this has been included since release 1.4 but I forgot to update the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Daniel Christophis commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-24265) Wrong auto-detected editor.log PATH on system user on Windows
lacostej commented on JENKINS-24265 Wrong auto-detected editor.log PATH on system user on Windows I reported issue #626407 @ unity This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-timeout] (JENKINS-24279) run custom shell script on Build timeout as pre-on-timeout hook
Mike Dubman created JENKINS-24279 run custom shell script on Build timeout as pre-on-timeout hook Issue Type: Improvement Affects Versions: current Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 15/Aug/14 5:52 AM Description: Hi, Is that possible to allow running shell script command before taking action when timeout occures (action like fail/abort). The use-case for this request is to extract stacktraces with "gstack" or "gdb" from hanging job before build-timeout aborts it? Also, as addition pre-ontimeout action, plugin can send email to specific address and wait for some sentinel file to be removed by user. This will allow developer to connect to the hanging job, examine/debug hang, remove sentinel file and job will resume abort/fail routine. Thanks Environment: linux Project: Jenkins Labels: build-tmeout Priority: Major Reporter: Mike Dubman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14583) Improve validation of 'builds dir' global setting
Daniel Beck commented on JENKINS-14583 Improve validation of builds dir global setting Maitrey Mishra: Please direct any questions not directly related to wrong builds dir settings to #jenkins on Freenode or the jenkinsci-users mailing list. Unrelated discussion has no place in Jira. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-23901) Job SCM changes are not valid after running plugin
Mads Nielsen assigned JENKINS-23901 to Praqma Support Job SCM changes are not valid after running plugin Change By: Mads Nielsen (15/Aug/14 12:20 PM) Assignee: PraqmaSupport This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [recipe] (JENKINS-22241) Recipe export does not properly quote non-ASCII characters in the job description field
Steven Christou assigned JENKINS-22241 to Steven Christou Recipe export does not properly quote non-ASCII characters in the job description field Change By: Steven Christou (15/Aug/14 10:02 AM) Assignee: StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-14191) Load Statistics: Exponential Moving Average artifacts make interpretation difficult
Daniel Beck commented on JENKINS-14191 Load Statistics: Exponential Moving Average artifacts make interpretation difficult Martina Oefelein Do you think you'll have time to test these soon? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert resolved JENKINS-24259 as Not A Defect Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (15/Aug/14 3:51 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap] (JENKINS-24245) Broken links on Tap Extended test results
Laurent Mazuel commented on JENKINS-24245 Broken links on Tap Extended test results Jenkins version 1.559 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
Tom FENNELLY
edited a comment on JENKINS-24282
Use noun phrases for new items
The following are trimmed down greps of what I think might need to be looked at (across all repos in the jenkinsci github org).
TopLevelItemDescriptor:
./repos/strawboss-plugin/src/main/java/captmorgan/ExternalProject.java: public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/views/AbstractWrapper.java: public TopLevelItemDescriptor getDescriptor() {
./repos/jenkins.py/python-wrapper/src/main/java/jenkins/python/descriptor/TopLevelItemDescriptorPW.java:public abstract class TopLevelItemDescriptorPW extends TopLevelItemDescriptor {
./repos/jenkow-plugin/jenkow-plugin/src/main/java/com/cisco/step/jenkins/plugins/jenkow/JenkowWorkflowJob.java://public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/drools-plugin/drools/src/main/java/hudson/drools/DroolsProject.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/organizationcontainer/OrganizationContainer.java: public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/item-forwarder-plugin/src/main/java/org/jenkinsci/plugins/item_forwarding/ForwardingItem.java:public static class DescriptorImpl extends TopLevelItemDescriptor {
./repos/jprt-plugin/src/main/java/hudson/plugins/jprt/JPRTJob.java:public TopLevelItemDescriptor getDescriptor() {
./repos/external-monitor-job-plugin/src/main/java/hudson/model/ExternalJob.java:public static final class DescriptorImpl extends TopLevelItemDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public TopLevelItemDescriptor getDescriptor() {
./repos/branch-api-plugin/src/main/java/jenkins/branch/MultiBranchProjectDescriptor.java:public abstract class MultiBranchProjectDescriptor extends TopLevelItemDescriptor {
./repos/categorized-view-plugin/src/main/java/org/jenkinsci/plugins/categorizedview/GroupTopLevelItem.java: public TopLevelItemDescriptor getDescriptor() {
AbstractProjectDescriptor:
./repos/tikal-multijob-plugin/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/jobgenerator-plugin/src/main/java/org/jenkinsci/plugins/jobgenerator/JobGenerator.java: extends AbstractProjectDescriptor {
./repos/matrix-project-plugin/src/main/java/hudson/matrix/MatrixProject.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/template-workflows-plugin/src/main/java/org/jenkins/plugin/templateWorkflows/TemplatesWorkflowJob.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/DotCi/src/main/java/com/groupon/jenkins/dynamic/build/DynamicProject.java: public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-plugin/src/main/java/hudson/maven/MavenModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
./repos/maven-release-cascade-plugin/src/main/java/com/barchart/jenkins/cascade/CascadeProject.java: public static class TheDescriptor extends AbstractProjectDescriptor {
./repos/build-flow-plugin/src/main/java/com/cloudbees/plugins/flow/BuildFlow.java:public static class BuildFlowDescriptor extends AbstractProjectDescriptor {
./repos/literate-plugin/src/main/java/org/cloudbees/literate/jenkins/LiterateBranchProject.java:public static class DescriptorImpl extends AbstractProjectDescriptor {
./repos/ivy-plugin/src/main/java/hudson/ivy/IvyModuleSet.java:public static final class DescriptorImpl extends AbstractProjectDescriptor {
What else should I search for?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because
[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Lukas Goormann reopened JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Hmmm progress made... can now find the "Publish CppCheck" step in the job-generator Postbuild menu, but clicking it does not have any visible effect... Change By: Lukas Goormann (15/Aug/14 12:47 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: tfennelly Path: src/main/resources/hudson/ivy/Messages.properties http://jenkins-ci.org/commit/ivy-plugin/abd5fa78025032823040431afb229c872bed3719 Log: Use noun phrases for new items JENKINS-24282 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson created JENKINS-24283 Empty environment variables are deleted Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 15/Aug/14 10:01 AM Description: Empty environment variables are deleted. Three methods tried: 1. Parameter 2. Generate environment variables from script 3. Inject environment variables to the build process As can be seen from the log below, the non-empty variables MYVAR1, MYVAR3 MYVAR5 works as expected, but the empty variables MYVAR2, MYVAR4 MYVAR6 are not present in the environment when the job executes. When looking at the enviroment through the left hand menu "Environment Variables" on the build page all variables are present. You can actually also see that an implicit environment varable TEST_NODE are also deleted. I'm not that the problem is in EnvInject. Feel free to move it to some other component. Looks similar to JENKINS-15146. log: Started by user magjac EnvInject - Loading node environment variables. Building on master in workspace /srv/lhome/jenkins/jobs/empty_env_var_test/workspace workspace $ /bin/sh -xe /tmp/empty_env_var_test6599764777552559363.sh + echo MYVAR3=world + echo MYVAR4= environment-script Adding variable 'MYVAR4' with value '' environment-script Adding variable 'MYVAR3' with value 'world' EnvInject - Executing scripts and injecting environment variables after the SCM step. EnvInject - Injecting as environment variables the properties content MYVAR5=foo MYVAR6= EnvInject - Variables injected successfully. workspace $ /bin/sh -xe /tmp/hudson101371634758484537.sh + env JENKINS_HOME=/srv/lhome/jenkins MAIL=/var/mail/smoker USER=smoker LC_TIME=en_DK.UTF-8 MYVAR1=hello SHLVL=1 NODE_LABELS=master master_label null HUDSON_URL=http://smoketest.netinsight.se/jenkins/ LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64 MYVAR3=world HOME=/home/smoker BUILD_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/6/ MYVAR5=foo JENKINS_SERVER_COOKIE=dad1862e4df27e29 HUDSON_COOKIE=0cebdd7b-7b7f-4962-a07c-c1dc9a842ca6 LC_CTYPE=sv_SE.UTF-8 WORKSPACE=/srv/lhome/jenkins/jobs/empty_env_var_test/workspace LOGNAME=smoker BUILD_CAUSE=MANUALTRIGGER _=/usr/bin/daemon EXECUTOR_NUMBER=380 TERM=rxvt BUILD_DISPLAY_NAME=#6 LC_COLLATE=sv_SE.UTF-8 HUDSON_HOME=/srv/lhome/jenkins PATH=/home/smoker/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games BUILD_ID=2014-08-15_11-35-11 BUILD_TAG=jenkins-empty_env_var_test-6 DISPLAY=worabu.netinsight.se:0.0 JENKINS_URL=http://smoketest.netinsight.se/jenkins/ PYTHONUSERBASE=/home/smoker/.local LANG=C JOB_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/ BUILD_NUMBER=6 NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_ SHELL=/bin/bash HUDSON_SERVER_COOKIE=dad1862e4df27e29 LC_MEASUREMENT=sv_SE.UTF-8 JOB_NAME=empty_env_var_test PWD=/srv/lhome/jenkins/jobs/empty_env_var_test/workspace LC_NUMERIC=sv_SE.UTF-8 LC_PAPER=sv_SE.UTF-8 BUILD_CAUSE_MANUALTRIGGER=true Finished: SUCCESS menu "Environment Variables": - _ /usr/bin/daemon BUILD_CAUSE MANUALTRIGGER BUILD_CAUSE_MANUALTRIGGER true BUILD_DISPLAY_NAME #4 BUILD_ID 2014-08-15_10-40-44 BUILD_NUMBER 4 BUILD_TAG jenkins-magjac-999-dev-smoke-fw025-nosa3-4 BUILD_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/4/ BUILD_USER magjac BUILD_USER_FIRST_NAME magjac BUILD_USER_ID magjac CONFIG_FILE fw025.rc DISPLAY worabu.netinsight.se:0.0 DO_COPY true DO_INSTALL false DO_PUBLISH false DO_TEST true EXECUTOR_NUMBER 324 EXIT_ON_FAILURE false GIT_ROOT /home/magjac/git_repos2 HOME /home/smoker HUDSON_HOME /srv/lhome/jenkins HUDSON_SERVER_COOKIE dad1862e4df27e29 HUDSON_URL http://smoketest.netinsight.se/jenkins/ JENKINS_HOME /srv/lhome/jenkins JENKINS_SERVER_COOKIE dad1862e4df27e29 JENKINS_URL http://smoketest.netinsight.se/jenkins/ JOB_NAME magjac-999-dev-smoke-fw025-nosa3 JOB_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/ LANG
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
Walter Kacynski closed JENKINS-20965 as Fixed SSH CLI -v (console output) option causes high master CPU utilization Change By: Walter Kacynski (15/Aug/14 3:02 PM) Status: Resolved Closed Assignee: StevenChristou WalterKacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-name-setter] (JENKINS-24277) BUILD_USER_ID not available for build-name-setter plugin.
Daniel Beck commented on JENKINS-24277 BUILD_USER_ID not available for build-name-setter plugin. Does the variable exist when you run env (in a Shell build step) or set (in a Batch build step)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator] (JENKINS-23653) Improve performance while establishing view (case 11425)
Mads Nielsen resolved JENKINS-23653 as Fixed Improve performance while establishing view (case 11425) Change By: Mads Nielsen (15/Aug/14 12:09 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-24282) Use noun phrases for new items
SCM/JIRA link daemon commented on JENKINS-24282 Use noun phrases for new items Code changed in jenkins User: Kevin Formsma Path: src/main/resources/hudson/ivy/Messages.properties http://jenkins-ci.org/commit/ivy-plugin/a0f6060f61592ae39d667389e22f6f1f4b6693bc Log: Merge pull request #15 from jenkinsci/JENKINS-24282 Use noun phrases for new items JENKINS-24282 Compare: https://github.com/jenkinsci/ivy-plugin/compare/e2394a70c8cd...a0f6060f6159 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
Daniel Spilker commented on JENKINS-24258 Broken Build Timeout Plugin implementation D'oh! Actually the fix was quite trivial. The plugin stores the value in milliseconds and we were generating the XML with seconds. https://github.com/jenkinsci/job-dsl-plugin/pull/262 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24284) In the commit message - don't write origin
Andrius Ordojan created JENKINS-24284 In the commit message - dont write origin Issue Type: New Feature Assignee: Alexander Uldall Components: pretested-integration Created: 15/Aug/14 10:40 AM Description: The branch name should exclude the name of the remote. Example: git commit -m "Integrated origin/ready/layout" Should be git commit -m "Integrated ready/layout" Project: Jenkins Priority: Major Reporter: Andrius Ordojan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Daniel Christophis edited a comment on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course related with this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Daniel Beck commented on JENKINS-24287 EnvInject exposes password hashes they can use this password hash to expose the password and take control of the account Could you provide steps to reproduce this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24283) Empty environment variables are deleted
Magnus Jacobsson updated JENKINS-24283 Empty environment variables are deleted Change By: Magnus Jacobsson (15/Aug/14 10:04 AM) Description: Emptyenvironmentvariablesaredeleted.Threemethodstried:1.Parameter2.Generateenvironmentvariablesfromscript3.InjectenvironmentvariablestothebuildprocessAscanbeseenfromthelogbelow,thenon-emptyvariablesMYVAR1,MYVAR3MYVAR5worksasexpected,buttheemptyvariablesMYVAR2,MYVAR4MYVAR6arenotpresentintheenvironmentwhenthejobexecutes.WhenlookingattheenviromentthroughthelefthandmenuEnvironmentVariablesonthebuildpage , allvariablesarepresent.Youcanactuallyalsoseethatanimplicitenvironment varable variable TEST_NODE are is alsodeleted.Imnot sure thattheproblemisinEnvInject.Feelfreetomoveittosomeothercomponent.LookssimilartoJENKINS-15146.log:Startedbyusermagjac[EnvInject]-Loadingnodeenvironmentvariables.Buildingonmasterinworkspace/srv/lhome/jenkins/jobs/empty_env_var_test/workspace[workspace]$/bin/sh-xe/tmp/empty_env_var_test6599764777552559363.sh+echoMYVAR3=world+echoMYVAR4=[environment-script]AddingvariableMYVAR4withvalue[environment-script]AddingvariableMYVAR3withvalueworld[EnvInject]-ExecutingscriptsandinjectingenvironmentvariablesaftertheSCMstep.[EnvInject]-InjectingasenvironmentvariablesthepropertiescontentMYVAR5=fooMYVAR6=[EnvInject]-Variablesinjectedsuccessfully.[workspace]$/bin/sh-xe/tmp/hudson101371634758484537.sh+envJENKINS_HOME=/srv/lhome/jenkinsMAIL=/var/mail/smokerUSER=smokerLC_TIME=en_DK.UTF-8MYVAR1=helloSHLVL=1NODE_LABELS=mastermaster_labelnullHUDSON_URL=http://smoketest.netinsight.se/jenkins/LD_LIBRARY_PATH=/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64MYVAR3=worldHOME=/home/smokerBUILD_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/6/MYVAR5=fooJENKINS_SERVER_COOKIE=dad1862e4df27e29HUDSON_COOKIE=0cebdd7b-7b7f-4962-a07c-c1dc9a842ca6LC_CTYPE=sv_SE.UTF-8WORKSPACE=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLOGNAME=smokerBUILD_CAUSE=MANUALTRIGGER_=/usr/bin/daemonEXECUTOR_NUMBER=380TERM=rxvtBUILD_DISPLAY_NAME=#6LC_COLLATE=sv_SE.UTF-8HUDSON_HOME=/srv/lhome/jenkinsPATH=/home/smoker/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/gamesBUILD_ID=2014-08-15_11-35-11BUILD_TAG=jenkins-empty_env_var_test-6DISPLAY=worabu.netinsight.se:0.0JENKINS_URL=http://smoketest.netinsight.se/jenkins/PYTHONUSERBASE=/home/smoker/.localLANG=CJOB_URL=http://smoketest.netinsight.se/jenkins/job/empty_env_var_test/BUILD_NUMBER=6NODE_PATH=/usr/lib/nodejs:/usr/lib/node_modules:/usr/share/_javascript_SHELL=/bin/bashHUDSON_SERVER_COOKIE=dad1862e4df27e29LC_MEASUREMENT=sv_SE.UTF-8JOB_NAME=empty_env_var_testPWD=/srv/lhome/jenkins/jobs/empty_env_var_test/workspaceLC_NUMERIC=sv_SE.UTF-8LC_PAPER=sv_SE.UTF-8BUILD_CAUSE_MANUALTRIGGER=trueFinished:SUCCESSmenuEnvironmentVariables:-_ /usr/bin/daemonBUILD_CAUSE MANUALTRIGGERBUILD_CAUSE_MANUALTRIGGER trueBUILD_DISPLAY_NAME #4BUILD_ID 2014-08-15_10-40-44BUILD_NUMBER 4BUILD_TAG jenkins-magjac-999-dev-smoke-fw025-nosa3-4BUILD_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/4/BUILD_USER magjacBUILD_USER_FIRST_NAME magjacBUILD_USER_ID magjacCONFIG_FILE fw025.rcDISPLAY worabu.netinsight.se:0.0DO_COPY trueDO_INSTALL falseDO_PUBLISH falseDO_TEST trueEXECUTOR_NUMBER 324EXIT_ON_FAILURE falseGIT_ROOT /home/magjac/git_repos2HOME /home/smokerHUDSON_HOME /srv/lhome/jenkinsHUDSON_SERVER_COOKIE dad1862e4df27e29HUDSON_URL http://smoketest.netinsight.se/jenkins/JENKINS_HOME /srv/lhome/jenkinsJENKINS_SERVER_COOKIE dad1862e4df27e29JENKINS_URL http://smoketest.netinsight.se/jenkins/JOB_NAME magjac-999-dev-smoke-fw025-nosa3JOB_URL http://smoketest.netinsight.se/jenkins/job/magjac-999-dev-smoke-fw025-nosa3/LANG CLC_COLLATE sv_SE.UTF-8LC_CTYPE sv_SE.UTF-8LC_MEASUREMENT sv_SE.UTF-8LC_NUMERIC sv_SE.UTF-8LC_PAPER sv_SE.UTF-8LC_TIME en_DK.UTF-8LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64LOGNAME smokerMAIL /var/mail/smokerNETI_BUILDID testingNODE_LABELS mastermaster_labelnullNODE_PATH
[JIRA] [clearcase-ucm] (JENKINS-23246) Performance improvement, use generated load rule to swipe workspace (case 11387)
Mads Nielsen resolved JENKINS-23246 as Fixed Performance improvement, use generated load rule to swipe workspace (case 11387) Change By: Mads Nielsen (15/Aug/14 11:38 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24253) Add JOB_LABELS environment variable
David Ruhmann commented on JENKINS-24253 Add JOB_LABELS environment variable @Daniel, Thanks for your input. I will look into creating a plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Rich Schumacher commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Just wanted to throw my name into the ring as someone who is also hung up on this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs
Johannes Ohlemacher commented on JENKINS-24256 Fail build for missing / erroneous valgrind publisher XMLs Sounds reasonable and should be easy to integrate. I am pretty busy right now, but i will try to look into it within the next couple of days. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24261) Assembla browser breaks config page
Mark Waite commented on JENKINS-24261 Assembla browser breaks config page Thanks for the report. The pull request that introduced Assembla (this commit and this commit) missed a few files. I obviously didn't test it well enough (shame on me). The author corrected the mistake, but it was after the release of the 2.2.4 version of the plugin. It will be fixed in the 2.2.5 version of the plugin. The commit which fixed it has been on github for almost two weeks (on both the master branch and the 2.2.x branch). I'll release 2.2.5 within the next few days to fix that problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22346) jenkins cli command with key fails with - java.io.EOFException
Daniel Christophis commented on JENKINS-22346 jenkins cli command with key fails with - java.io.EOFException Also broken in LTS Version 1.565.1. I get the following LDAP error when trying to use CLI commands: Exception in thread "Thread-XX" org.acegisecurity.userdetails.UsernameNotFoundException: User X not found in directory. at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:126) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:787) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:738) at jenkins.security.ImpersonatingUserDetailsService.loadUserByUsername(ImpersonatingUserDetailsService.java:32) at hudson.model.User.impersonate(User.java:266) at org.jenkinsci.main.modules.cli.auth.ssh.SshCliAuthenticator.authenticate(SshCliAuthenticator.java:44) at hudson.cli.CliManagerImpl$2.run(CliManagerImpl.java:109) And of course related with this: Exception in thread "main" java.io.EOFException at java.io.DataInputStream.readBoolean(DataInputStream.java:244) at hudson.cli.Connection.readBoolean(Connection.java:95) at hudson.cli.CLI.authenticate(CLI.java:634) at hudson.cli.CLI._main(CLI.java:474) at hudson.cli.CLI.main(CLI.java:384) Any suggestions for temporary workarounds? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
Tom FENNELLY commented on JENKINS-24282 Use noun phrases for new items Freestyle Projects (english only): https://github.com/jenkinsci/jenkins/pull/1369 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert edited a comment on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdateSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: ?xml version='1.0' encoding='UTF-8'? sites site idcompany-default/id urlhttps://update-center.company.com/update-center.json/url /site site iddefault/id urlhttp://updates.jenkins-ci.org/stable/update-center.json/url /site Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-24019) Absolute URLs in delivery pipeline break reverse proxy setups
Patrik Boström reopened JENKINS-24019 Absolute URLs in delivery pipeline break reverse proxy setups Will reopen this since the previous fix help in some cases and in some cases not. Need to fix it by removing the absolute URL:s. Change By: Patrik Boström (15/Aug/14 1:17 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24261) Assembla browser breaks config page
Mark Waite started work on JENKINS-24261 Assembla browser breaks config page Change By: Mark Waite (15/Aug/14 11:07 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-6763) Hudson does not set JAVA_HOME for Maven Builds
Damon Overboe edited a comment on JENKINS-6763 Hudson does not set JAVA_HOME for Maven Builds On Jenkins 1.575, working against Windows Server 2012, setting the JDK in Jenkins provides the option to input the JAVA_HOME variable, and that worked around the issue for me. This might be what you were referring to as having it set twice, but given that it seems to completely ignore JAVA_HOME on the clients (even though it reports that correctly with the script console) it doesn't seem to cause any issues. Here were my steps: Manage Jenkins Configure System Scroll to JDK installations Add JDK Installation Provide JAVA_HOME path to the JDK folder on the client/slave such as `C:\Progra~2\Java\jdk1.7.0_67` where Proga~2 is Program Files (x86) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap] (JENKINS-24245) Broken links on Tap Extended test results
Laurent Mazuel commented on JENKINS-24245 Broken links on Tap Extended test results In http://10.128.4.199:8180/jenkins/configure The "Jenkins Location" tab, the "Jenkins URL" is: http://10.128.4.199:8180/jenkins/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter] (JENKINS-24280) Environment variables get corrupted when using Node parameter
Andreas Kleber created JENKINS-24280 Environment variables get corrupted when using Node parameter Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 15/Aug/14 6:45 AM Description: When I use a Node parameter at my jobs, it is not possible for jenkins anymore to start a windows batch script on a windows slave, because cmd.exe can not be found anymore. If I use the Label parameter with that nodes name, everything works as expected. I do not kno if it is relevant but I also use the Environment Injector Plugin. Running Jenkins: 1.554.3, Node and Label parameter plugin: 1.5.1, Environment Injector Plugin 1.89 Started by user Andreas Kleber [EnvInject] - Loading node environment variables. Building remotely on basstu01 (puppet vdp vdk windows) in workspace c:\j\workspace\test-env [test-env] $ cmd /c call C:\Users\XXX\AppData\Local\Temp\hudson4333783914616487877.bat The parameter is incorrect FATAL: command execution failed java.io.IOException: Cannot run program "cmd" (in directory "c:\j\workspace\test-env"): CreateProcess error=87, The parameter is incorrect at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1023) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:990) 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.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: CreateProcess error=87, The parameter is incorrect at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE Project: Jenkins Priority: Major Reporter: Andreas Kleber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials] (JENKINS-24273) Presence of ECDSA SSH keys breaks SSH credentials plugin
Hendrik Halkow updated JENKINS-24273 Presence of ECDSA SSH keys breaks SSH credentials plugin Change By: Hendrik Halkow (14/Aug/14 6:52 PM) Summary: PresenceofECDSASSHkeys break breaks SSHcredentialsplugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cygpath] (JENKINS-20364) Failed to locate cygwin installation
Greg Warner
commented on JENKINS-20364
Failed to locate cygwin installation
I'm seeing this bug too. I ran the failing line using the jython console. I tried both "SOFTWARECygwin" and "SOFTWARE\\Wow6432NodeCygwin" and they both failed. It does, however, find plain ol' "SOFTWARE". Also, I try other keys such as "SOFTWARE[Motorola,Intel,TrendMicro" and it finds all of them. So this seems to be a cygwin-specific problem.
RegistryKey.LOCAL_MACHINE.openReadonly("SOFTWARECygwin")
Traceback (most recent call last):
File "stdin", line 1, in module
at hudson.util.jna.RegistryKey.check(RegistryKey.java:124)
at hudson.util.jna.RegistryKey.open(RegistryKey.java:223)
at hudson.util.jna.RegistryKey.openReadonly(RegistryKey.java:218)
at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
hudson.util.jna.JnaException: hudson.util.jna.JnaException: Win32 error: 2 - The
system cannot find the file specified
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-14583) Improve validation of 'builds dir' global setting
Maitrey Mishra commented on JENKINS-14583 Improve validation of builds dir global setting Hi Bruce, I face the same issue of dead executors with jenkins-1.532.3. Coudl you please provide insights: Here is the log: Exception in thread "Executor #0 for master" java.lang.ClassCastException: hudson.model.FreeStyleBuild cannot be cast to hudson.model.Action at hudson.model.Run.onLoad(Run.java:331) at hudson.model.RunMap.retrieve(RunMap.java:223) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:671) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:470) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:219) at hudson.tasks.Fingerprinter$FingerprintAction.compact(Fingerprinter.java:361) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:350) at hudson.model.Run.onLoad(Run.java:333) at hudson.model.RunMap.retrieve(RunMap.java:223) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:547) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:393) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:335) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1089) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:152) at hudson.model.Job.isLogUpdated(Job.java:293) at hudson.model.AbstractProject.getCauseOfBlockage(AbstractProject.java:1285) at hudson.model.AbstractProject.isBuildBlocked(AbstractProject.java:1222) at hudson.model.Queue.isBuildBlocked(Queue.java:1021) at hudson.model.Queue.maintain(Queue.java:1080) at hudson.model.Queue.pop(Queue.java:935) at hudson.model.Executor.grabJob(Executor.java:297) at hudson.model.Executor.run(Executor.java:211) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase-ucm] (JENKINS-23920) The '' Special character not handled with describe (case 11500)
Mads Nielsen resolved JENKINS-23920 as Fixed The Special character not handled with describe (case 11500) Change By: Mads Nielsen (15/Aug/14 11:36 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-18824) Build Causer doesn't resolve CLI based usernames
dogfood commented on JENKINS-18824 Build Causer doesnt resolve CLI based usernames Integrated in jenkins_main_trunk #3620 JENKINS-18824 prevent failure when startedBy is ‘unknown’ (Revision 3efe07f563d30a38cf405a20c9145c3ea88e5051) Result = SUCCESS Nicolas De Loof : 3efe07f563d30a38cf405a20c9145c3ea88e5051 Files : core/src/main/java/hudson/cli/BuildCommand.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken Note I've posted on the dev list for a bit of help: https://groups.google.com/d/msg/jenkinsci-dev/LjHaBd6yUW8/LstWtVCaOHwJ "Troubleshooting remoting related input/output stream piping issues" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert commented on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdatSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: ?xml version='1.0' encoding='UTF-8'? sites site idcompany-default/id urlhttps://update-center.company.com/update-center.json/url /site site iddefault/id urlhttp://updates.jenkins-ci.org/stable/update-center.json/url /site Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-24288) Noclassdef found in openID plugin
Daniel Beck updated JENKINS-24288 Noclassdef found in openID plugin Seems unrelated to Plugin Usage Plugin (components, with few exceptions, are plugin names). Change By: Daniel Beck (15/Aug/14 3:18 PM) Component/s: openid Component/s: plugin-usage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
James Talton commented on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs I pulled the latest code and merged in the changes from https://github.com/jenkinsci/cobertura-plugin/pull/26. The code coverage is indeed aggregated up and looks good on the matrix job. What is not working for us is that the code coverage thresholds are still being applied at each matrix run and not on the aggregated results. This causes a matrix run to fail even though the aggregated coverage is 100%. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-24287) EnvInject exposes password hashes
Walter Kacynski created JENKINS-24287 EnvInject exposes password hashes Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 15/Aug/14 1:36 PM Description: Currently, if a user without configuration access to a job can read the job they have access to the link "Environment variables". This allows the non-privileged user to see the password hashes. If they have Config access to a difference folder on the same master, they can use this password hash to expose the password and take control of the account. I propose that this link or at least the password hashes be restricted to only users with job config access. Project: Jenkins Priority: Critical Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24284) In the commit message - don't write origin
Mads Nielsen assigned JENKINS-24284 to Praqma Support In the commit message - dont write origin Change By: Mads Nielsen (15/Aug/14 10:48 AM) Assignee: AlexanderUldall PraqmaSupport This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-24282) Use noun phrases for new items
Tom FENNELLY updated JENKINS-24282 Use noun phrases for new items Change By: Tom FENNELLY (15/Aug/14 8:11 AM) Attachment: target.png Attachment: current.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rqm] (JENKINS-24264) Better logging when execute fails (case 11732)
Mads Nielsen resolved JENKINS-24264 as Fixed Better logging when execute fails (case 11732) Change By: Mads Nielsen (15/Aug/14 6:40 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24258) Broken Build Timeout Plugin implementation
Daniel Spilker resolved JENKINS-24258 as Fixed Broken Build Timeout Plugin implementation 1.25 will contain the fix. Change By: Daniel Spilker (15/Aug/14 9:18 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration] (JENKINS-24285) Improve commit message
Andrius Ordojan created JENKINS-24285 Improve commit message Issue Type: New Feature Assignee: Praqma Support Components: pretested-integration Created: 15/Aug/14 10:56 AM Description: The commit messages from the most recent commit in the accumulated change set should be reused - concatenated with the name of the branch that has been integrated. Project: Jenkins Priority: Major Reporter: Andrius Ordojan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit] (JENKINS-23564) PHPUnit test results from dataProvider tests are not parsed by xUnit
Gregory Boissinot commented on JENKINS-23564 PHPUnit test results from dataProvider tests are not parsed by xUnit By giving your test result file to xUnit it is OK. Could you attach a complete reproductible sample with the problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
