[JIRA] (JENKINS-41086) Performance plugin support in dsl plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-41086 Performance plugin support in dsl plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-43210 Windows Agent can't connect to Master through JNLP Change By: Oleg Nenashev Component/s: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-43210 Windows Agent can't connect to Master through JNLP Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck edited a comment on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? kubectl get po -l jenkins=slave shows 0 pods. https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesCloud.java#L743So that code should not give 20? Its worth noting that i have 2 jenkins masters deploying creating slaves. And my old one have also started complaining about total cap reached. So i created a new namespace and configured my second master to use that and now the problem is gone. But the code seems to only count labels jenkins:slave so it should not be a problem? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41885) Build log is scrolled down unconditionally on update
Title: Message Title Daniel Beck commented on JENKINS-41885 Re: Build log is scrolled down unconditionally on update FWIW 1.0.0-rc1 stops updating the build log when you scroll up. There's one more update, then it stops. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43238) Ambiguous warning: TLS is not correctly configured on Active Directory plugin
Title: Message Title Félix Belzunce Arcos resolved as Fixed I just resolved this on the wiki under the section SECURITY-251 Active Directory Plugin did not verify certificate of AD server See: https://wiki.jenkins-ci.org/display/JENKINS/Active+Directory+plugin Jenkins / JENKINS-43238 Ambiguous warning: TLS is not correctly configured on Active Directory plugin Change By: Félix Belzunce Arcos Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-41402) Corner case in job deletion without history?
Title: Message Title Jochen A. Fürbacher resolved as Done Jenkins / JENKINS-41402 Corner case in job deletion without history? Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Stefan Brausch Jochen A. Fürbacher Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43261) withMaven parses emtpy EventSpy logfiles
Title: Message Title Jannis Oeltjen updated an issue Jenkins / JENKINS-43261 withMaven parses emtpy EventSpy logfiles Change By: Jannis Oeltjen Attachment: screenshot.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36612) Java Pipeline job instances duplicated on each job modification
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-36612 Java Pipeline job instances duplicated on each job modification Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43085) Downstream promotion is getting auto approved on approving upstream promotion
Title: Message Title Saga P edited a comment on JENKINS-43085 Re: Downstream promotion is getting auto approved on approving upstream promotion 1.Approve A2.Then Approve C(No action ll be carried out as promotion B is pending)3.Approve BThen check Promtion C..it will be re executed by SYSTEM. But ideally it should not be re executed by SYSTEM. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18949) Renaming Project causes content encoding error
Title: Message Title Jochen A. Fürbacher resolved as Cannot Reproduce No response. Jenkins / JENKINS-18949 Renaming Project causes content encoding error Change By: Jochen A. Fürbacher Status: Open Resolved Assignee: Mirko Friedenhagen Jochen A. Fürbacher Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because
[JIRA] (JENKINS-43263) Credentials usage tracking completely redacts secrets causing false duplicate tracking
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-43263 Credentials usage tracking completely redacts secrets causing false duplicate tracking Issue Type: Improvement Assignee: Stephen Connolly Components: credentials-plugin Created: 2017/Mar/31 10:27 AM Priority: Minor Reporter: Stephen Connolly If you are using folder scoped credentials with the same ID and same description (only differing based on the secret) then the usage tracking will track incorrectly as the secrets are completely redacted instead of being replaced with a hash (either of the secret and the store or of just the store). This can also show up when the secret is updated as the tracking of usage will continue against the original secret value (though this could be considered useful too) Add Comment
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Adrian Bridgett commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Steven Loomis's fix solved it for me as well. I purged the other lines from ~/.ssh/known_hosts just in case. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41958) Append node not working when adding TFS to MultiScm node
Title: Message Title Daniel Spilker closed an issue as Won't Fix Jenkins / JENKINS-41958 Append node not working when adding TFS to MultiScm node Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41979) `multibranchPipelineJob/branchSources/git` should support `browser`
Title: Message Title Daniel Spilker closed an issue as Won't Fix Jenkins / JENKINS-41979 `multibranchPipelineJob/branchSources/git` should support `browser` Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41741) wrong parameters order with Jenkins Parameterized Trigger plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-41741 wrong parameters order with Jenkins Parameterized Trigger plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43218) Discard Unreadable Data leads to NPE in TreeMap.putAll
Title: Message Title Felix Neumann commented on JENKINS-43218 Re: Discard Unreadable Data leads to NPE in TreeMap.putAll Oleg Nenashev: Okay, at first I didn't find the file, as the file name isn't mentioned in the UI. Now I found it and it contains invalid XML. I searched for the string 7562 mentioned in the error message above and it contains the following (I anonymized the project names): example/com.example:example-common-documents 7562 < example-it/org.example:example-wos-war 3094,3097 I suggest that I could simply delete this file, which should allow Jenkins to complete the discard unreadable data action? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43262) It's difficult to tell whether the build is still running
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-43262 It's difficult to tell whether the build is still running Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/31 10:13 AM Environment: BO 1.0.0-rc1 Priority: Minor Reporter: Daniel Beck Especially in the case of freestyle jobs, it's difficult to tell from the default position at the bottom of the build log whether the current build is still running. The "spinner" or an equivalent from classic Jenkins is missing. Add Comment
[JIRA] (JENKINS-16496) latest version of jobConfigHistory fails on the first run when using a matrix job
Title: Message Title Jochen A. Fürbacher commented on JENKINS-16496 Re: latest version of jobConfigHistory fails on the first run when using a matrix job Can't reproduce with JCH 2.15 and core 2.52. Brian Murrell: Does your problem still occur? If so, what kind ob jobs fail? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43261) withMaven parses emtpy EventSpy logfiles
Title: Message Title Jannis Oeltjen updated an issue Jenkins / JENKINS-43261 withMaven parses emtpy EventSpy logfiles Change By: Jannis Oeltjen The maven pipeline plugin in version 2.0 tries to parse an empty event spy logfile and logs error messages because of that (that is fine).Calling withMaven() should not even try to parse any log files from the event spy if the event spy has been disabled via one of the two options available for that.In my case I disabled the event spy via setting the environment variable JENKINS_MAVEN_AGENT_DISABLED to "true". In this case no valid log file is created and the MavenSpyLogProcessor can't process it so it should not even try it . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42211) Issue a warning when default jdk is used - advise to use jdk(...)
Title: Message Title Daniel Spilker closed an issue as Won't Do Jenkins / JENKINS-42211 Issue a warning when default jdk is used - advise to use jdk(...) Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42887) job-dsl-plugin Still Uses Mattermost showCommitList
Title: Message Title Daniel Spilker closed an issue as Won't Fix Jenkins / JENKINS-42887 job-dsl-plugin Still Uses Mattermost showCommitList Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42741) Option "Prepare SonarQube Scanner Environment" missing in Job DSL Plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-42741 Option "Prepare SonarQube Scanner Environment" missing in Job DSL Plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42691) Job DSL stacktrace in log
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-42691 Job DSL stacktrace in log Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42697) Add Job DSL Support
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-42697 Add Job DSL Support Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42508) Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public"
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-42508 Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public" Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43210) Windows Agent can't connect to Master through JNLP
Title: Message Title
Oleg Nenashev commented on JENKINS-43210
Re: Windows Agent can't connect to Master through JNLP
So I am mostly aware about the JNLP4 protocol failure
Caused by: java.security.cert.CertificateException: Public key of the first certificate in chain (subject: C=US, OU=jenkins.io, O=instances, CN=74df086770b5c378864b03273a8576ae) is
{{ not in the list of trusted keys}}
{{ at org.jenkinsci.remoting.protocol.cert.PublicKeyMatchingX509ExtendedTrustManager.checkPublicKey(PublicKeyMatchingX509ExtendedTrustManager.java:216)}}
{{ at org.jenkinsci.remoting.protocol.cert.PublicKeyMatchingX509ExtendedTrustManager.checkServerTrusted(PublicKeyMatchingX509ExtendedTrustManager.java:263)}}
{{ at org.jenkinsci.remoting.protocol.cert.DelegatingX509ExtendedTrustManager.checkServerTrusted(DelegatingX509ExtendedTrustManager.java:148)}}
{{ ... 17 more}}Mõr 30, 2017 9:29:36 AM hudson.remoting.jnlp.Main$CuiListener status
INFORMATION: Protocol JNLP4-connect encountered an unexpected exception
java.util.concurrent.ExecutionException: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
Due to whatever reason the agent does not consider master's certificate as a trusted one. It should never happen for auto-generated certificates AFAIK, so I would assume your master is available over HTTPS and has untrusted certificate. Please provide more information about your master settings. Jenkins System logs would be also useful.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Sasha Miroshnich edited a comment on JENKINS-42678 Re: hudson.remoting.ChannelClosedException: channel is already closed https://github.com/jenkinsci/jenkins/commit/6d95e3680c8edf49c2353633dd9c1a7072440989 Looks like it was fixed with trivial _try ... catch_ block at some forked version.Could it be ported to some of the official builds? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Sasha Miroshnich commented on JENKINS-42678 Re: hudson.remoting.ChannelClosedException: channel is already closed Looks like it was fixed with trivial try ... catch block at some forked version. Could it be ported to some of the official builds? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Sasha Miroshnich updated an issue Jenkins / JENKINS-42678 hudson.remoting.ChannelClosedException: channel is already closed Change By: Sasha Miroshnich Comment: https://github.com/jenkinsci/jenkins/commit/6d95e3680c8edf49c2353633dd9c1a7072440989Looks like it was fixed with trivial _try ... catch_ block at some forked version. Could it be ported to some of the official builds? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43235) Total container cap of 10 reached when NO slaves are running?
Title: Message Title Jonas Falck commented on JENKINS-43235 Re: Total container cap of 10 reached when NO slaves are running? Here is a senario. I have cap conf at 20.. it does not start.. i increase to 100 and then is says Waiting for Pod to be scheduled (0/100). If there was 20 running it should say 20/100? Mar 31, 2017 11:38:50 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 20 reached, not provisioning: 20 running in namespace default Mar 31, 2017 11:39:00 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 31, 2017 11:39:00 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud addProvisionedSlave INFO: Total container cap of 20 reached, not provisioning: 20 running in namespace default Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Mar 31, 2017 11:39:10 AM io.fabric8.kubernetes.client.Config tryServiceAccount WARNING: Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring. Mar 31, 2017 11:39:10 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes-dev with 1 executors. Remaining excess workload: 0 Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Created Pod: deploy-kubernetes-4df2b007ba2f Mar 31, 2017 11:39:10 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud$ProvisioningCallback call INFO: Waiting for Pod to be scheduled (0/100): deploy-kubernetes-4df2b007ba2f Mar 31, 2017 11:39:13 AM hudson.TcpSlaveAgentListener$ConnectionHandler run Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title David van Laatum commented on JENKINS-43178 Re: Can't send email to unknown email address Basically we just need make the check that complains about unregistered users a bit smarter so it understands the difference between explicitly configured email addresses vs user email addresses. Havn't looked into how hard this is yet but it might require the reworking of how it builds the list of addresses up I have been thinking about. (ie pass around a list of objects rather than strings containing email addresses so its possible to tell where they came from). Unfortunately my health is not up for it at the moment so not going to happen quick unless someone else picks it up Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43261) withMaven parses emtpy EventSpy logfiles
Title: Message Title Jannis Oeltjen created an issue Jenkins / JENKINS-43261 withMaven parses emtpy EventSpy logfiles Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2017/Mar/31 7:55 AM Environment: Jenkins ver. 2.32.3 Pipeline Maven Plugin 2.0 Labels: pipeline maven maven-plugin-support Priority: Minor Reporter: Jannis Oeltjen The maven pipeline plugin in version 2.0 tries to parse an empty event spy logfile and logs error messages because of that (that is fine). Calling withMaven() should not even try to parse any log files from the event spy if the event spy has been disabled via one of the two options available for that. In my case I disabled the event spy via setting the environment variable JENKINS_MAVEN_AGENT_DISABLED to "true". In this case no valid log file is created and the MavenSpyLogProcessor can't process it.
[JIRA] (JENKINS-42894) Job-dsl-plugin support for envInject plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-42894 Job-dsl-plugin support for envInject plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42893) Job-dsl-plugin support for parameterized scheduler plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-42893 Job-dsl-plugin support for parameterized scheduler plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42710) Update Active Choices DSL to support new secureScript tag (script-security-plugin)
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-42710 Update Active Choices DSL to support new secureScript tag (script-security-plugin) Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42859) categorizedJobsView default "recurse" value is not honored
Title: Message Title Daniel Spilker closed an issue as Not A Defect Jenkins / JENKINS-42859 categorizedJobsView default "recurse" value is not honored Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43218) Discard Unreadable Data leads to NPE in TreeMap.putAll
Title: Message Title Oleg Nenashev edited a comment on JENKINS-43218 Re: Discard Unreadable Data leads to NPE in TreeMap.putAll The issue is here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Fingerprint.java#L1412Usages variable is supposed to be deserialized from the disk, but according to the ticket reading fails, because there is no "entry" field. I suppose the root cause of this issue is the whatever XStream issue, which causes improper reading of maps.[~fxnn] would it be possible to retrieve the XML file for the fingerprint from the disk? It would be useful for diagnostics Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43218) Discard Unreadable Data leads to NPE in TreeMap.putAll
Title: Message Title Oleg Nenashev commented on JENKINS-43218 Re: Discard Unreadable Data leads to NPE in TreeMap.putAll The issue is here: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Fingerprint.java#L1412 Usages variable is supposed to be deserialized from the disk, but according to the ticket reading fails, because there is no "entry" field. I suppose the root cause of this issue is the whatever XStream issue, which causes improper reading of maps. Felix Neumann would it be possible to retrieve the XML file for the fingerprint from the disk? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38105) Fail to set reference parameters with different type of drop down list
Title: Message Title Sergej Kleva commented on JENKINS-38105 Re: Fail to set reference parameters with different type of drop down list Any news on this? I am having the exact problem! Thanks guys! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43218) Discard Unreadable Data leads to NPE in TreeMap.putAll
Title: Message Title
Felix Neumann edited a comment on JENKINS-43218
Re: Discard Unreadable Data leads to NPE in TreeMap.putAll
[~oleg_nenashev]:Okay, at first I didn't find the file, as the file name isn't mentioned in the UI. Now I found it and it contains invalid XML. I searched for the string {{7562}} mentioned in the error message above and it contains the following (I anonymized the project names):{code:xml |title=d:\\jenkins\\fingerprints\\53\\22\\792f9f6480dde9de2d2bcc0fda18.xml } example/com.example:example-common-documents 7562< example-it/ org com .example:example-wos-war 3094,3097{code}I suggest that I could simply delete this file, which should allow Jenkins to complete the discard unreadable data action?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43238) Ambiguous warning: TLS is not correctly configured on Active Directory plugin
Title: Message Title davida2009 commented on JENKINS-43238 Re: Ambiguous warning: TLS is not correctly configured on Active Directory plugin Thank you. The 'Save' cleared the warning as you described. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13288) Config history does not appear for certain jobs
Title: Message Title Jochen A. Fürbacher resolved as Postponed No response, so postponed. Jenkins / JENKINS-13288 Config history does not appear for certain jobs Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Postponed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43260) Nuget plugin reports a circular dependency issue on startup
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-43260 Nuget plugin reports a circular dependency issue on startup Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/nuget-plugin/pull/11 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43275) Support for BlueOcean plugin
Title: Message Title Martin Reinhardt created an issue Jenkins / JENKINS-43275 Support for BlueOcean plugin Issue Type: New Feature Assignee: Martin Reinhardt Components: rocket-chat-notifier-plugin Created: 2017/Mar/31 2:53 PM Priority: Minor Reporter: Martin Reinhardt Would be cool to link to BlueOcean views Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-support-plugin/b4c0da271dbff56b46eb0603bbcf4be174db25f4 Log: JENKINS-26137 Pass pickleFactories directly into the RiverWriter constructor. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26137) Mysterious serialization errors
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26137 Re: Mysterious serialization errors Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/support/pickles/serialization/RiverWriter.java http://jenkins-ci.org/commit/workflow-support-plugin/a3389777f39dcbae5c7758980f1c6a0d02b65c62 Log: Merge pull request #35 from jglick/no-PickleFactory-JENKINS-26137 JENKINS-26137 Pass pickleFactories directly into the RiverWriter constructor Compare: https://github.com/jenkinsci/workflow-support-plugin/compare/467dd0dca178...a3389777f39d Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title micheljung edited a comment on JENKINS-39667 Re: PIpeline job ignores custom workspace location I don't understand how "this is intentional" is a justification for this unexpected and very problematic behavior. Unfortunately , I'm not able to find anything any explanation in the release notes either.Our project can't even be cloned because of this, making it impossible to use pipeline builds. And even if it wasn't problematic because of the path length:"As builds tend to be disk I/O intensive, changing this value enables you to put build workspaces on faster storage hardware, such as SSDs or even RAM disks."We don't get this with pipeline builds? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41272) Pipeline "currentBuild" should expose build causes
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-41272 Pipeline "currentBuild" should expose build causes Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42374) While extracting war file getting error as failed to launch IOHub
Title: Message Title Oleg Nenashev resolved as Duplicate No response from the requester. Closing as a duplicate of JENKINS-34405 Jenkins / JENKINS-42374 While extracting war file getting error as failed to launch IOHub Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-41972) Slow page loading and page unresponsive in version 2.44
Title: Message Title Oleg Nenashev commented on JENKINS-41972 Re: Slow page loading and page unresponsive in version 2.44 Still needs investigation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30782) Failed to read environment variable table error
Title: Message Title Oleg Nenashev commented on JENKINS-30782 Re: Failed to read environment variable table error Partial fix in WinP, which reduces the issue frequency: https://github.com/kohsuke/winp/pull/34 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43277) best practice to backup config files Jenkins
Title: Message Title m ali created an issue Jenkins / JENKINS-43277 best practice to backup config files Jenkins Issue Type: Story Assignee: Unassigned Components: jenkins-tracker Created: 2017/Mar/31 4:41 PM Environment: 1.636 Priority: Minor Reporter: m ali I am using Jenkins on remote Debian 7.8 . I want to update Debian 7.8 to 8.7. I tried to update and it went fine however Jenkins was broken and could not start the service. I tried everything but could find any solution. Finally I used purged command and it deleted previous configurations and builds like fresh install Now I restore the server and want to update again but I want a complete Jenkins backup of config and builds so restore it from last running instance. same login connected to window credential and built config. What's the best practice to backup the configs as simple as possible (with less effort and problems) and configure and then merge the backuped files. Which data / config files I have to backup? Regards, Add Comment
[JIRA] (JENKINS-42778) Unable to run project in firefox browser through Jenkins
Title: Message Title Oleg Nenashev resolved as Not A Defect Not a defect from what I see. No response from the requester Jenkins / JENKINS-42778 Unable to run project in firefox browser through Jenkins Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Brian Wilson commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I also used the "Manually trusted key Verification Strategy" and the Agent came back online with no further issues. I then switched back to the "Known hosts file Verification Strategy", took the Agent offline and brought it back online with no issues. Its almost as if the known_hosts file being checked isn't the file for the user id executing the Jenkins war file. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42678 hudson.remoting.ChannelClosedException: channel is already closed Change By: Oleg Nenashev Labels: remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42678) hudson.remoting.ChannelClosedException: channel is already closed
Title: Message Title Oleg Nenashev resolved as Incomplete No response from the submitter. There is not enough information to decide if it is a bug. Jenkins / JENKINS-42678 hudson.remoting.ChannelClosedException: channel is already closed Change By: Oleg Nenashev Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36933) Name or alias Shell Script Step (sh)
Title: Message Title Christian Saide commented on JENKINS-36933 Re: Name or alias Shell Script Step (sh) So I really need this functionality as I have some stages with 10+ `Shell Script`'s and its a pain to have to click through each one to figure out what it is/was doing. I am using the `Stage View Plugin` and the `Blueocean Plugin`, but looking at the code they both use the same call to get the name of the step. Which currently is hard coded to output "Shell Script" which is less than useful. Also having one stage turn into 10 is not an option as that would mean certain builds could end up having close to 50 stages which is even less digestible than the current setup. Why was this closed? Is there a technical reason why this can't be done? I ask because I couldn't find one in the comments here or in the code. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Steve Prentice edited a comment on JENKINS-35140
Re: JsonSlurper does not work after updating to Jenkins 2.x
Posting this here as I recently had to work around this issue: {code:java}@NonCPSdef paseJson parseJson (jsonString) {// Would like to use readJSON step, but it requires a context, even for parsing just text.def lazyMap = new JsonSlurper().parseText(jsonString)// JsonSlurper returns a non-serializable LazyMap, so copy it into a regular map before returningdef m = [:]m.putAll(lazyMap)return m}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35140) JsonSlurper does not work after updating to Jenkins 2.x
Title: Message Title
Steve Prentice commented on JENKINS-35140
Re: JsonSlurper does not work after updating to Jenkins 2.x
Posting this here as I recently had to work around this issue:
@NonCPS
def paseJson(jsonString) {
// Would like to use readJSON step, but it requires a context, even for parsing just text.
def lazyMap = new JsonSlurper().parseText(jsonString)
// JsonSlurper returns a non-serializable LazyMap, so copy it into a regular map before returning
def m = [:]
m.putAll(lazyMap)
return m
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title David van Laatum commented on JENKINS-43178 Re: Can't send email to unknown email address jpschewe I think your problem might be a different problem if the email address its complaining about is attached to a jenkins user it should allow it. This bug is for the case where you manually enter a email address directly into a job that doesn't exist on any current users Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43178) Can't send email to unknown email address
Title: Message Title
jpschewe commented on JENKINS-43178
Re: Can't send email to unknown email address
For this particular problem, before the changes I used the following pre-send script. recipients = msg.getRecipients(javax.mail.Message.RecipientType.TO) {{filtered = recipients.findAll { addr -> addr.toString().contains('@domain1.com') || addr.toString().contains('@domain2.com') }}} msg.setRecipients(javax.mail.Message.RecipientType.TO, filtered as javax.mail.Address[])cancel = build.result.toString().equals("ABORTED"); That worked quite well. With this new change I can't send email to people that aren't explicit users.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Alexey Bychko created an issue Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Issue Type: Bug Assignee: Oliver Gondža Components: ws-cleanup-plugin Created: 2017/Mar/31 12:03 PM Environment: Jenkins ver. 2.32.3, workspace cleanup plugin 1.0.5 Priority: Critical Reporter: Alexey Bychko if we run a lot of copies of the same job with workspace cleanup enabled - every next job will clean up workspaces on slaves with already running jobs. jobs are executed in parallel, so perhaps it's better to check if workspace is used currently and belongs to running job before the cleanup. it's important for us because we have ENOSPACE with cleanup disabled and many failed jobs with cleanup enabled. running job copies one-by-one is not an option for us, because it will take a lot of time. thanks in advance Add Comment
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-43171 Correct Pom for build-monitor-plugin Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-43171 Correct Pom for build-monitor-plugin Change By: Daniel Spilker Component/s: job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42508) Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public"
Title: Message Title Simon van der Veldt edited a comment on JENKINS-42508 Re: Class org.apache.commons.jexl.util.PropertyExecutor can not access a member of class javaposse.jobdsl.plugin.actions.GeneratedObjectsRunAction with modifiers "public" Sorry for the silence, whilst I can easily trigger this issue with out our live seedjob, it's been hard pinpointing what exactly causes it, so I haven't been able to come up with a simple reproducible test case I can share. It might have something to do with the amount of jobs created (we have over 2500).I Will try the new version with our live seedjob though and see if it still happens. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43264) NullPointerException when credentialid is not found
Title: Message Title
Cyril Jouve created an issue
Jenkins / JENKINS-43264
NullPointerException when credentialid is not found
Issue Type:
Bug
Assignee:
Stephen Connolly
Attachments:
about.html
Components:
credentials-plugin
Created:
2017/Mar/31 10:31 AM
Environment:
see attached about.html
Priority:
Minor
Reporter:
Cyril Jouve
with the following: steps { withCredentials([ string(credentialsId: params.GITHUB_PASSWORD, variable: 'GITHUB_PASSWORD'), string(credentialsId: params.GITHUB_APP_SECRET, variable: 'GITHUB_APP_SECRET') ]) { {{ ansiblePlaybook(}} . {{ )}} {{ }}} if param.GITHUB_PASSWORD is null (not defined), a NullPointerException is raised. The code in com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById should check for null value of id and provide a more useful message than a stacktrace.
[JIRA] (JENKINS-43267) JaCoCo plugin2.2.0 shows 100% coverage for 0 classes
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-43267 JaCoCo plugin2.2.0 shows 100% coverage for 0 classes Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco-plugin Created: 2017/Mar/31 11:49 AM Environment: Jenkins ver. 2.46.1 on SLES 11.4 Priority: Blocker Reporter: Torsten Kleiber Rolling back to plugin 2.1.0 and rerunning my job shows again the real coverage and find all of my classes. Have not changed any plugin properties. Path to exec files: */*.exec Path to class directories: **/artefakte/build/lib/ikb (there are a lot of *.jars, no direct *.class files) Path to source directories: **/src Add Comment
[JIRA] (JENKINS-43237) Can't login without clearing cookies
Title: Message Title Félix Belzunce Arcos commented on JENKINS-43237 Re: Can't login without clearing cookies This is very strange... In order to replicate this, I will need that you create a logger for hudson.plugins.active_directory = ALL and then you reproduce the issue again. Then , you will need to generate a support bundle (with the support-core plugin) before reverting the instance to 2.0. I know there are already a lot of companies on 2.4 without any issue and since you don't provide exactly steps to reproduce, neither any diagnostic information, I am lowering the priority to low for the moment https://support.cloudbees.com/hc/en-us/articles/204880580-How-do-I-create-a-logger-in-Jenkins-for-troubleshooting-and-diagnostic-information https://support.cloudbees.com/hc/en-us/articles/218625237-How-to-diagnose-AD-integration-problems Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43237) Can't login without clearing cookies
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-43237 Can't login without clearing cookies Change By: Félix Belzunce Arcos Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Daniel Spilker commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin This is not a Job DSL issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Oliver Gondža commented on JENKINS-43269 Re: workspace cleanup removes workspaces for running job This certainly should not happen. Please provide more information about the situation (reproducer ideally) as well as plugin version (ws-cleanup was never released in version 1.0.5 as stated). Do you use custom workspace on these jobs? Are you running parallel build on the same machine? Do you share the drive with workspaces between machines? Any erorrs/logs somewhere? Are the workspaces cleaned asynchronously? How do you know it is ws-cleanup that is deleting those directories? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37570) Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project
Title: Message Title Alexandre Aubert updated an issue Jenkins / JENKINS-37570 Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project i increase the criticity because our Jenkins is unusable when too many branch indexing operations are triggered, and this is not configurable so it directly depends on multibranch jobs count. It would be really nice to find a solution for this. Change By: Alexandre Aubert Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-43265) REGRESSION Dashboard showPipelineList prevents extension point rendering
Title: Message Title
Thorsten Scherler created an issue
Jenkins / JENKINS-43265
REGRESSION Dashboard showPipelineList prevents extension point rendering
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2017/Mar/31 11:07 AM
Priority:
Blocker
Reporter:
Thorsten Scherler
https://github.com/jenkinsci/blueocean-plugin/blob/master/blueocean-dashboard/src/main/js/components/Pipelines.jsx#L76
const showPipelineList = !this.pager.pending && pipelines && pipelines.length > 0;
const showEmptyState = !this.pager.pending && (!pipelines || !pipelines.length);
{ showEmptyState && }
{ showPipelineList &&
{ /* TODO: need to adjust Extensions to make store available */ }
"jenkins.pipeline.list.top"
store={ this.context.store }
router={ this.context.router }
/>
The above prevents that the extension point "jenkins.pipeline.list.top" is rendered when no pipelines are there. However in my use case I want to render a navigation box but it has nothing to do with pipelines (not directly) so it should always show. In case the point is that this extension point is thought to be only there in case pipeline exists, then IMO we need another extension renderer call outside. REGRESSION because before we always rendered the extension point.
[JIRA] (JENKINS-43266) credentialsId doesn't appear to work with github enterprise
Title: Message Title simon Wall created an issue Jenkins / JENKINS-43266 credentialsId doesn't appear to work with github enterprise Issue Type: Bug Assignee: Raul Arabaolaza Components: pipeline-githubnotify-step-plugin Created: 2017/Mar/31 11:37 AM Priority: Minor Reporter: simon Wall I have been trying out the Pipeline Githubnotify Step Plugin as part of notifying pull requests to a repo in a GitHub Enterprise environment. If I do not specify the credentialsId then the plugin reports back to GitHub Enterprise fine. But the following is reported at the end of the pipeline job processing: java.lang.IllegalArgumentException: The suplied credentials are invalid to login at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getGitHubIfValid(GitHubStatusNotificationStep.java:234) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.getRepoIfValid(GitHubStatusNotificationStep.java:239) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep.access$100(GitHubStatusNotificationStep.java:75) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:344) at org.jenkinsci.plugins.pipeline.githubstatusnotification.GitHubStatusNotificationStep$Execution.run(GitHubStatusNotificationStep.java:326) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:213) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[JIRA] (JENKINS-43267) JaCoCo plugin2.2.0 shows 100% coverage for 0 classes
Title: Message Title Torsten Kleiber updated an issue Jenkins / JENKINS-43267 JaCoCo plugin2.2.0 shows 100% coverage for 0 classes Change By: Torsten Kleiber Attachment: 2.2.0.png Attachment: 2.1.0.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43218) Discard Unreadable Data leads to NPE in TreeMap.putAll
Title: Message Title
Felix Neumann edited a comment on JENKINS-43218
Re: Discard Unreadable Data leads to NPE in TreeMap.putAll
[~oleg_nenashev]:Okay, at first I didn't find the file, as the file name isn't mentioned in the UI. Now I found it and it contains invalid XML. I searched for the string {{7562}} mentioned in the error message above and it contains the following (I anonymized the project names):{code:xml|title=d:\\jenkins\\fingerprints\\53\\22\\792f9f6480dde9de2d2bcc0fda18.xml} example/com.example:example-common-documents 7562< example-it/com.example:example-wos-war 3094,3097{code} This explains the error message {{ConversionException: : unexpected character in markup (position: END_TAG seen ...7562\r\n < ... @738:7)}}. I suggest that I could simply delete this file the five affected files and restart Jenkins , which should allow Jenkins to complete the discard unreadable data action . What do you think ?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36724) Branch indexing hangs
Title: Message Title Alexandre Aubert reopened an issue Hi, i'm sorry to re-open this but it seems there is a real problem with multiple branch indexing causing Jenkins to hang and be unusable. if we have a lot of multibranch pipeline jobs, it triggers 'branch indexing' operations and it regularly hangs when there are too many of those. I commented on ticket 37570 already but i think the problem is also related to this one. Could you please have a look on that? I of course available for any additional test or information in order to investigate to find out a solution. Thanks. Jenkins / JENKINS-36724 Branch indexing hangs Change By: Alexandre Aubert Resolution: Incomplete Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43264) NullPointerException when credentialid is not found
Title: Message Title
Cyril Jouve updated an issue
Jenkins / JENKINS-43264
NullPointerException when credentialid is not found
Change By:
Cyril Jouve
{{with the following:}}{{ steps \{}}{{ withCredentials([}}{{ string(credentialsId: params.GITHUB_PASSWORD, variable: 'GITHUB_PASSWORD'),}}{{ string(credentialsId: params.GITHUB_APP_SECRET, variable: 'GITHUB_APP_SECRET')}}{{ ]) \{}}{{ ansiblePlaybook( }}{{ }}{{ ... .. }}{{ )}}{{ }}} {{ }}} if param.GITHUB_PASSWORD is null (not defined), a NullPointerException is raised.The code in com.cloudbees.plugins.credentials.CredentialsProvider.findCredentialById should check for null value of id and provide a more useful message than a stacktrace.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-43081) Quality-gates plugin do not work with SonarQube 6.3
Title: Message Title pablo perez commented on JENKINS-43081 Re: Quality-gates plugin do not work with SonarQube 6.3 Any idea when this bug will be solved? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43268) Can't send email to registered users
Title: Message Title jpschewe created an issue Jenkins / JENKINS-43268 Can't send email to registered users Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2017/Mar/31 11:55 AM Environment: Jenkins Version 2.32.3 Email extension plugin 2.57.1 Priority: Major Reporter: jpschewe I see that some security was added so that emails don't get sent to people that shouldn't get emails. I had fixed this by using a pre-send script that filtered out email addresses. However now with the new change, emails are not getting sent at all. I use the unix database backend for my Jenkins system. If I goto the People page I see 2 entries for myself, one as "Jon Schewe" with an email address "j...@domain1.com". I see a second one as "user1" (which is my unix username) with email address "j...@domain2.com". If I setup a job to send email to "j...@domain1.com" I get the error that the email will not be sent to unregistered users. If I send an email to "j...@domain2.com", then it works. Note that I've set "domain2.com" as my default email suffix. So the first question here is what is a registered user when using the unix database backend? Second, what is considered the email address for a registered user when using the unix database backend?
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Alexey Bychko updated an issue Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: Alexey Bychko Attachment: Screen Shot 2017-03-31 at 15.27.28.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Brian Wilson edited a comment on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I logged in to the Master server in a command line shell and sudo 'd (sudo -su ) to the user running the Jenkins war file. I ran the ssh command to connect to each of the Jenkins Agent machines and had no issue connecting. I did this with both the machine name and the fully qualified domain name (e.g. machine1, and machine1.company-name.com). From what I could see the ssh ~/.ssh/known_hosts file contained valid information on the Agent machines and had correct permissions of 644. On the Jenkins Master web page , I went to the Nodes, Agent, Configure page (http://:8080/computer//) and switched from the "Known hosts file Verification Strategy" to the "Manually trusted key Verification Strategy" then brought the Agents online with no issues. I then switched the Agent configuration back to the "Known hosts file Verification Strategy", took the Agents offline and brought them back online again with no issues. I looked at the time stamp on the ~/.ssh/known_hosts file and verified its contents hadn't changed. Its almost as if the known_hosts file being checked isn't the file for the user id executing the Jenkins war file. Either way, this is an issue that needs to be addressed sooner rather than later. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title apotek commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I'll try to summarize what we already know here from reading the original post, and the first few comments. Jenkins uses a Java ssh library. It does not use the same ssh as is used on the command line. The exception found in the original issue description makes this clear The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) 2. As stated by Steven Loomis above: I needed this workaround from the mailing list: > ssh -o HostKeyAlgorithms=ssh-rsa slave2.example.com The implication below is that Jenkins is using weaker encryption. https://groups.google.com/d/msgid/jenkinsci-users/7006ab93-7ca4-4063-baf6-7c844be60165%40googlegroups.com 3. The workaround (not fix) seems to be to switch the node over to "Manually trusted key Verification Strategy". The actual fix, then, seems to be for the com.trilead.ssh2 library to be updated to handle advances in which kinds of ssh keys are considered secure at this point. But a search on the internet makes it clear it is no longer being worked on by the original developers, though someone appears to be maintaining it somewhat here: https://github.com/jenkinsci/trilead-ssh2 If that Java library is not going to be updated, then perhaps there needs to be a push to find another Java library for managing ssh connections. sshj seems to be the best option at the moment: https://github.com/hierynomus/sshj every thing else I am finding seems pretty dormant. Add Comment
[JIRA] (JENKINS-16496) latest version of jobConfigHistory fails on the first run when using a matrix job
Title: Message Title Brian J Murrell commented on JENKINS-16496 Re: latest version of jobConfigHistory fails on the first run when using a matrix job Jochen A. Fürbacher: I'm afraid with my comment on this issue being over 3 years old now, I have no recollection. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Brian Wilson edited a comment on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I also used logged in to the Master server and sudo (sudo -su ) to the user running the Jenkins war file. I ran the ssh command to connect to each of the Jenkins Agent machines and had no issue connecting. I did this with both the machine name and the fully qualified domain name (e.g. machine1, and machine1.company-name.com). From what I could see the ssh ~/.ssh/known_hosts file contained valid information on the Agent machines and had correct permissions of 644. On the Jenkins Master, I went to the Nodes, Agent, Configure page and switched from the " Known hosts file Verification Strategy" to the " Manually trusted key Verification Strategy" and then brought the Agent came back Agents online with no further issues. I then switched the Agent configuration back to the "Known hosts file Verification Strategy", took the Agent Agents offline and brought it them back online again with no issues. I looked at the time stamp on the ~/.ssh/known_hosts file and verified its contents hadn't changed. Its almost as if the known_hosts file being checked isn't the file for the user id executing the Jenkins war file. Either way, this is an issue that needs to be addressed sooner rather than later. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-43278) Pressing "Show More" button on Activity tab for Multibranch yields unpredictable results
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-43278
Pressing "Show More" button on Activity tab for Multibranch yields unpredictable results
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2017/Mar/31 6:22 PM
Priority:
Minor
Reporter:
Cliff Meyers
Preconditions:
Set up a multibranch pipeline with 5 branches and 10 runs for each branch.
Repro Steps 1. Navigate to the Activity branch for the MBP 2. Note there are 25 runs displayed 3. Press "Show More" Expected Result
A total of 50 runs should be displayed
Actual Results
No addition runs are displayed and the "Show More" button disappears
Analysis: When the second request is made, it hits the /activities endpoint sending parameters of start=25 and limit=26. This request returns an empty array. The bug appears to be in MultiBranchPipelineImpl.getRuns() which is called from getActivities(). Inside of the anonymous BlueRunContainer.iterator(int start, int limit) method there is a bug around line 281:
for(final BluePipeline b: branches) {
Iterator it = b.getRuns().iterator(0,MAX_MBP_RUNS_ROWS);
int count = 0;
Iterators.skip(it, start);
while(it.hasNext() && count++ < limit){
c.add(it.next());
}
}
[JIRA] (JENKINS-43243) Verification of password containing [ or ] fails
Title: Message Title Claudiu Guiman started work on JENKINS-43243 Change By: Claudiu Guiman Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title
apotek edited a comment on JENKINS-42959
Re: Failed known_hosts verification for SSH agent
I'll try to summarize what we already know here from reading the original post, and the first few comments. # Jenkins uses a Java ssh library. It does not use the same ssh as is used on the command line. The exception found in the original issue description makes this clear {code:java}The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) {code} 2. As stated by [~srl295] above: {quote}I needed this workaround from the mailing list:> ssh -o HostKeyAlgorithms=ssh-rsa [slave2.example.com|http://slave2.example.com/] {quote}{quote}The implication below is that Jenkins is using weaker encryption.[https://groups.google.com/d/msgid/jenkinsci-users/7006ab93-7ca4-4063-baf6-7c844be60165%40googlegroups.com|https://groups.google.com/d/msgid/jenkinsci-users/7006ab93-7ca4-4063-baf6-7c844be60165%40googlegroups.com?utm_medium=email_source=footer]{quote}3. The workaround (not fix) seems to be to switch the node over to "Manually trusted key Verification Strategy".The actual fix, then, seems to be for the com.trilead.ssh2 library to be updated to handle advances in which kinds of ssh keys are considered secure at this point. But a search on the internet makes it clear it is no longer being worked on by the original developers, though someone appears to be maintaining it somewhat here: [ https://github.com/jenkinsci/trilead-ssh2 ] If that Java library is not going to be updated, then perhaps there needs to be a push to find another Java library for managing ssh connections.sshj seems to be the best option at the moment: [https://github.com/hierynomus/sshj] every thing else I am finding seems pretty dormant. Apache Mina SSHD might also be an option: http://mina.apache.org/sshd-project/
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title
Alexey Bychko commented on JENKINS-43269
Re: workspace cleanup removes workspaces for running job
we don't have any custom workspaces
no. we have a lot of slaves, every slave is able to build the job
no
yes, from failed jobs. we have cleanup disabled at the moment, so no fresh logs. usually it looks like {code}+ mv /mnt/workspace/percona-server-5.6-param/BUILD_TYPE/debug/Host/centos5-64/mysql-test/test_results.subunit /mnt/workspace/percona-server-5.6-param/BUILD_TYPE/debug/Host/centos5-64 mv: cannot stat `/mnt/workspace/percona-server-5.6-param/BUILD_TYPE/debug/Host/centos5-64/mysql-test/test_results.subunit': No such file or directory{code} suddenly workspace disappears.
workspaces set to be cleaned up at the start of build. so, it looks like next started copy will destroy already running jobs
because such a failures disappeared after disabling the cleanup
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: Oliver Gondža Component/s: hudson-wsclean-plugin Component/s: hudson-pview Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: Oliver Gondža Component/s: hudson-pview Component/s: ws-cleanup-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Oliver Gondža assigned an issue to tspengler Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: Oliver Gondža Assignee: Oliver Gondža tspengler Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43270) Unable to switch between running parallel nodes in pipeline view
Title: Message Title Emil Styrke created an issue Jenkins / JENKINS-43270 Unable to switch between running parallel nodes in pipeline view Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/31 12:59 PM Environment: blueocean 1.0.0-rc3 Jenkins 2.52 Priority: Major Reporter: Emil Styrke When I click on a parallel step "circle" to switch to it, I get the following _javascript_ error. It seems to work for completed parallel steps (green checkbox) but not ones currently running (blue circle). [ERROR - io.jenkins.blueocean.dashboard.harmonizeTimes] not found any startTime, seems that a component should not have called this me error @ blueocean.js:18681 2blueocean.js:18681 [ERROR - io.jenkins.blueocean.dashboard.harmonizeTimes] not found any startTime, seems that a component should not have called this me error @ blueocean.js:18681 harmonizeTimes @ blueocean.js:7944 convertJenkinsNodeDetails @ jenkins-js-extension.js:49241 (anonymous) @ jenkins-js-extension.js:49312 convertJenkinsNodeGraph @ jenkins-js-extension.js:49311 processData @ jenkins-js-extension.js:49387 componentWillReceiveProps @ jenkins-js-extension.js:49378 updateComponent @ blueocean.js:84564 receiveComponent @ blueocean.js:84497 receiveComponent @ blueocean.js:91302 _updateRenderedComponent @ blueocean.js:84704 _performComponentUpdate @ blueocean.js:84674 updateComponent @ blueocean.js:84595 receiveComponent @ blueocean.js:84497 receiveComponent @ blueocean.js:91302 _updateRenderedComponent @ blueocean.js:84704 _performComponentUpdate @ blueocean.js:84674 updateComponent @ blueocean.js:84595 receiveComponent @ blueocean.js:84497 receiveComponent @ blueocean.js:91302 performUpdateIfNecessary @ blueocean.js:84509 performUpdateIfNecessary @ blueocean.js:91334 runBatchedUpdates
[JIRA] (JENKINS-43271) withDockerContainer build failure while there is no error
Title: Message Title asyd created an issue Jenkins / JENKINS-43271 withDockerContainer build failure while there is no error Issue Type: Bug Assignee: Nicolas De Loof Components: docker Created: 2017/Mar/31 1:16 PM Environment: awt.toolkit sun.awt.X11.XToolkit executable-war /srv/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_121-b13 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_121 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.121-b13 jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna8187628283815269746.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-327.10.1.el7.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.121-0.b13.el7_3.x86_64/jre/classes sun.boot.library.path
[JIRA] (JENKINS-24806) Scoverage: iFrames blocked by many server setups
Title: Message Title david perez commented on JENKINS-24806 Re: Scoverage: iFrames blocked by many server setups It doesn't work for me, I've changed the /etc/init.d/jenkins service. Using CentOS 7. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Oliver Gondža commented on JENKINS-43269 Re: workspace cleanup removes workspaces for running job Uh, that is for https://wiki.jenkins-ci.org/display/JENKINS/Distributed+Workspace+Clean+plugin. I have fixed the component name and the wiki page so users can find what the component name is. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title Alexey Bychko updated an issue Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: Alexey Bychko Attachment: Screen Shot 2017-03-31 at 15.42.40.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41246) Branch scanning fails when PR refer to a deleted fork
Title: Message Title Vladislav Ivanov commented on JENKINS-41246 Re: Branch scanning fails when PR refer to a deleted fork Can confirm this problem, happened to my repo on github. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42465) LDAP lockout when using Gerrit HTTP password
Title: Message Title Tatiana Didik resolved as Fixed Fixed 1.0.8 Jenkins / JENKINS-42465 LDAP lockout when using Gerrit HTTP password Change By: Tatiana Didik Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
