[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. I upgraded to 227 with no improvement. Chrome is still working fine but it would be nice to understand what's going on with FF. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205157.1584115782000.11271.1584977280045%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. Some further info... All of the above is true of Firefox 73, I think. I restarted and upgraded to 74.0 but nothing has changed there. I also tried Chrome and the problem is not happening there, so far. I have not used Chrome to manage this server before so there would be no cached data, etc. I have been using Jenkins logged out and with 'anyone can do anything' set over the last few hours, to avoid having to log in. It still doesn't work properly in FF at all. Menus don't work and the inability to remain logged in remains. When I view a running job's console it displays and then aborts with HTTP ERROR 403 No valid crumb was included in the request URI: /view/JobDSL%20Pipeline%20Test/job/x/140/logText/progressiveHtml STATUS: 403 MESSAGE: No valid crumb was included in the request SERVLET: Stapler Powered by Jetty:// 9.4.27.v20200227 Refreshing the page causes the new console data to display and then this message re-appears. I have now tried reverting to 2.223 and 2.222. Neither of them work at all, reporting hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /opt/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:244) ... when the UI tries to display, so it looks like the recent UI changes or something else have made the config incompatible. I verified this in Chrome, as well. I am now back on 225 and using Chrome for the moment as that has at least provided some relief from the problem in FF. Add Comment
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. OK, I didn't expect the latest plugin to work with versions of core prior to 220 because of the change that occurred in 220 and broke the plugin. Are you sure that that's the case? We are and always have been using LDAP Please read before asking. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205157.1584115782000.7807.1584355980131%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title
g hs1 edited a comment on JENKINS-61476
Re: Can't stay logged in with latest versions.
We seem to be speaking different languages here, somehow. I don't know why this isn't clear... \{quote}To clarify, is the following correct:\{quote}Neither. I went 217 -> 224 -> 225. At least the swarm plugin was updated on the way to 224. I said I'd revert if a fix wasn't found and, that being the case, I can't revert further than 221 because of Jenkins-61029. I haven't reverted anything yet. If we can't find a solution quickly I'll have to because things are currently painful. As general information, anything interesting in the Jenkins log?\{quote} Today I found this, which may be relevant except that no-one was around yesterday to try and login, as far as I know, so it's a little odd in that respect. I don't know what these reports refer to, as yet.{code:java}Mar 15, 2020 5:48:01 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTriggerNew Stapler routing rules result in the URL "/authentication/login/" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getAuthentication". Learn more: https://jenkins.io/redirect/stapler-routingMar 15, 2020 5:48:28 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTriggerNew Stapler routing rules result in the URL "/version" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getVersion". Learn more: https://jenkins.io/redirect/stapler-routingMar 15, 2020 5:48:37 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleExceptionCaught unhandled exception with ID d8fa20da-b17a-4988-8a26-81718dd12060 java.lang.IllegalArgumentException: /..\pixfir~1\how_to_login.html at org.kohsuke.stapler.TokenList.(TokenList.java:66) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:667) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title
g hs1 commented on JENKINS-61476
Re: Can't stay logged in with latest versions.
We seem to be speaking different languages here, somehow. I don't know why this isn't clear... {quote}To clarify, is the following correct:{quote} Neither. I went 217 -> 224 -> 225. At least the swarm plugin was updated on the way to 224. I said I'd revert if a fix wasn't found and, that being the case, I can't revert further than 221 because of Jenkins-61029. I haven't reverted anything yet. If we can't find a solution quickly I'll have to because things are currently painful. As general information, anything interesting in the Jenkins log?{quote} Today I found this, which may be relevant except that no-one was around yesterday to try and login, as far as I know, so it's a little odd in that respect. I don't know what these reports refer to, as yet.
Mar 15, 2020 5:48:01 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger
New Stapler routing rules result in the URL "/authentication/login/" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getAuthentication". Learn more: https://jenkins.io/redirect/stapler-routing
Mar 15, 2020 5:48:28 PM WARNING jenkins.security.stapler.StaplerFilteredActionListener onGetterTrigger
New Stapler routing rules result in the URL "/version" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "staticMethod jenkins.model.Jenkins getVersion". Learn more: https://jenkins.io/redirect/stapler-routing
Mar 15, 2020 5:48:37 PM WARNING hudson.init.impl.InstallUncaughtExceptionHandler handleException
Caught unhandled exception with ID d8fa20da-b17a-4988-8a26-81718dd12060 java.lang.IllegalArgumentException: /..\pixfir~1\how_to_login.html at org.kohsuke.stapler.TokenList.(TokenList.java:66) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:667) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. What issue is that? JENKINS-61029 Yep, your session will have expired by then, then the menu cannot load. Nope, I'm referring to when logged in, as well. Further, menus must be able to load regardless of session since users can be allowed to perform actions without logging in. Which is the latest known good version wrt being logged in? 2.221? Which is the first known bad one? 2.224? 217, as mentioned. 224, as also mentioned. I haven't tried anything in between, yet. Between the last known good, and first broken release, do you change plugin versions too? Or is the Jenkins (core) version the only thing that's changed to break/repair it? I updated the swarm plugin, which went from 217 to 218 due to the aforementioned critical issue. I can't remember if there were other updates. It's possible there were a couple but it wasn't a long list if so. They'd been updated fairly recently. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 commented on JENKINS-61476 Re: Can't stay logged in with latest versions. One more thing. Of course 'keep me logged in' is always selected. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205157.1584115782000.6851.1584115860174%40Atlassian.JIRA.
[JIRA] (JENKINS-61476) Can't stay logged in with latest versions.
Title: Message Title g hs1 created an issue Jenkins / JENKINS-61476 Can't stay logged in with latest versions. Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-13 16:09 Environment: RHEL7 Jenkins 2.224, 2.225 Priority: Major Reporter: g hs1 Jenkins has become basically unusable for us since updating to 224 two days ago. I also tried 225 today with no change. We now can't stay logged into the UI for any length of time. 9 times out of 10 we are either logged out again once the page has refreshed or the first page change will result in being logged out. On occasion we can manage to navigate a couple of times and are then logged out. We were previously using 217 pending a fix for the swarm plugin issue and that was fine, as have been all prior versions. There has been no change on the host server. We are and always have been using LDAP on this Jenkins instance. That has always worked fine, too. I did try turning off the new UI via the system jenkins.ui.refresh property but didn't know if that was still valid and could find no help as to how to do it correctly, so may have got it wrong. In a possibly related issue, the drop-down menus on links, which have always been slow and somewhat unreliable, are now useless as they almost always refuse to display. That also makes nav painful. The only other factor I can offer is that I cleared out all local browser storage after upgrading, seeing this issue and poking around for a while and that seemed to help a little i.e. I could stay logged in for longer before being kicked out again but trying that again today hasn't helped. Let me know if I can supply any more info. If I can't get this fixed quickly I will try rolling back but I can't go beyond 221 as the swarm issue will break our builds. Thanks.
[JIRA] (JENKINS-59026) Snippet generator broken for GitLab triggers
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-59026
Snippet generator broken for GitLab triggers
Issue Type:
Bug
Assignee:
Owen Mehegan
Attachments:
image-2019-08-21-12-59-45-849.png
Components:
gitlab-plugin
Created:
2019-08-21 12:00
Environment:
Jenkins 2.121.2 GitLab plugin 1.5.12
Priority:
Minor
Reporter:
g hs1
The snippet generator produces nonsense when trying to generate a snippets for GitLab triggers.
properties([gitLabConnection(''), [$class: 'GitlabLogoProperty', repositoryName: ''], pipelineTriggers([])])
I have no idea why the GitLab Logo plugin is referenced there. Thanks.
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title g hs1 commented on JENKINS-58468 Re: Unable to checkout git repo from agents Firstly, as stated, I have taken most of those actions and I don't actually know if there is a bug here. It's hard to imagine what else is going wrong, given the situation described. I did try and look at your mailing lists but they require logins to Google, which I don't want to deal with, before I can even see the archive. Thanks for the suggestions, though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200602.1562935438000.8800.156294241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58468) Unable to checkout git repo from agents
Title: Message Title g hs1 created an issue Jenkins / JENKINS-58468 Unable to checkout git repo from agents Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-07-12 12:43 Environment: Jenkins ver. 2.162 Git plugin 3/10.0 RHEL7 git versions 1.8 and 2.16 tried Priority: Minor Reporter: g hs1 We are unable to get any agent to check out a repo from git (GitLab in our case). We have configured the certs and verified that both the jenkins user and the user in the credential we use to access GitLab can check out locally on the agent. When we run a build which checks out using that same credential on the same agent, the fetch fails with Peer's Certificate issuer is not recognized. We have also configured the Jenkins master with the certs and that can check out from a build run on the master without problems. As soon as we attempt to run on an agent, we hit the same issue. We have sslVerify=false set for all users. The cert is self-signed. It seems somehow that the authentication isn't crossing the master-agent boundary. Since git is the default RCS for Jenkins and so widely used we might be missing something but we're at a loss to know how to proceed. Thanks.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title g hs1 closed an issue as Fixed Jenkins / JENKINS-56779 yamllint never finds issues Change By: g hs1 Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198423.1553698214000.4216.1562591520242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title g hs1 commented on JENKINS-56779 Re: yamllint never finds issues Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56779) yamllint never finds issues
Title: Message Title g hs1 updated JENKINS-56779 Jenkins / JENKINS-56779 yamllint never finds issues Change By: g hs1 Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56779) yamllint never finds issues
Title: Message Title g hs1 commented on JENKINS-56779 Re: yamllint never finds issues I'm not sure what your first question is asking but I tried -f parsable. That didn't change anything with files or scanning the console before. Fair question. It was 1.11.1. I updated. No change. Still no detection of any kind. -sh-4.2$ yamllint -v yamllint 1.15.0 However, after the update I tried -f parsable again and that was what was missing. The need for the parsable output isn't mentioned on the wiki, either. I now get: [Pipeline] sh 09:39:48 + yamllint -v 09:39:48 yamllint 1.15.0 [Pipeline] sh 09:39:50 + yamllint -f parsable ./ 09:39:51 ./windows-utilities.yml:6:1: [error] too many blank lines (2 > 1) (empty-lines) 09:39:51 ./windows-utilities.yml:7:1: [warning] comment not indented like content (comments-indentation) 09:39:51 ./windows-utilities.yml:7:2: [warning] missing starting space in comment (comments) 09:39:51 ./windows-utilities.yml:9:1: [error] too many blank lines (2 > 1) (empty-lines) 09:39:51 ./windows-utilities.yml:11:22: [error] no new line character at the end of file (new-line-at-end-of-file) [Pipeline] echo 09:39:51 hudson.AbortException: script returned exit code 1 [Pipeline] recordIssues 09:39:51 Skipping issues blame since Git is the only supported SCM up to now. 09:39:51 [YamlLint] Sleeping for 5 seconds due to JENKINS-32191... 09:39:56 [YamlLint] Parsing console log (workspace: '/var/lib/jenkins/workspace/CC3') 09:39:58 [YamlLint] [-ERROR-] Can't resolve absolute paths for some files: 09:39:58 [YamlLint] [-ERROR-] - 51.203Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] - 51.204Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] Can't create fingerprints for some files: 09:39:58 [YamlLint] [-ERROR-] - '51.203Z] ./windows-utilities.yml', IO exception has been thrown: java.nio.file.NoSuchFileException: 51.203Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] - '51.204Z] ./windows-utilities.yml', IO exception has been thrown: java.nio.file.NoSuchFileException: 51.204Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] - '51.204Z] ./windows-utilities.yml', IO exception has been thrown: java.nio.file.NoSuchFileException: 51.204Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] - '51.204Z] ./windows-utilities.yml', IO exception has been thrown: java.nio.file.NoSuchFileException: 51.204Z] ./windows-utilities.yml 09:39:58 [YamlLint] [-ERROR-] - '51.204Z] ./windows-utilities.yml', IO exception has been thrown: java.nio.file.NoSuchFileException: 51.204Z] ./windows-utilities.yml 09:39:58 [YamlLint] Post processing issues on 'uwreg014' with source code encoding 'windows-1252' 09:39:58 [YamlLint] Resolving absolute file names for all issues in workspace '/var/lib/jenkins/workspace/CC3' 09:39:58 [YamlLint] -> 0 resolved, 2 unresolved, 0 already resolved 09:39:58 [YamlLint] Copying affected files to Jenkins' build folder 'C:\Jenkins\jobs\CC3\builds\33\files-with-issues' 09:39:58 [YamlLint] -> 0 copied, 0 not in workspace, 2 not-found, 0 with I/O error 09:39:58 [YamlLint] Resolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files) 09:39:58 [YamlLint] ->
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-56779 yamllint never finds issues Change By: g hs1 Attachment: yamllint.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-56779) yamllint never finds issues
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-56779
yamllint never finds issues
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-03-27 14:50
Environment:
Various linux and Windows servers Jenkins 2.160+
Priority:
Major
Reporter:
g hs1
I have managed to get ansible-lint to report failures but the yamllint parser never works. It doesn't matter if I write to a log amd parse that, parse the console, separate scanning and publishng. The result is always no issues found.
[Pipeline] { (Run yamllint)
[Pipeline] sh
14:41:07 + yamllint ./
14:41:08 ./windows-utilities.yml
14:41:086:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:087:1 warning comment not indented like content (comments-indentation)
14:41:087:2 warning missing starting space in comment (comments)
14:41:089:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:0811:22 errorno new line character at the end of file (new-line-at-end-of-file)
14:41:08
[Pipeline] echo
14:41:08 hudson.AbortException: script returned exit code 1
[Pipeline] recordIssues
14:41:08 Skipping issues blame since Git is the only supported SCM up to now.
14:41:08 [YamlLint] Sleeping for 5 seconds due to JENKINS-32191...
14:41:13 [YamlLint] Parsing console log (workspace: '/var/lib/jenkins/workspace/CC3')
14:41:13 [YamlLint] Attaching ResultAction with ID 'yamllint' to run 'CC3 #21'.
14:41:13 [YamlLint] Using reference build 'CC3 #20' to compute new, fixed, and outstanding issues
14:41:13 [YamlLint] Issues delta (vs. reference
[JIRA] (JENKINS-56779) yamllint never finds issues
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-56779
yamllint never finds issues
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-03-27 14:50
Environment:
Various linux and Windows servers Jenkins 2.160+
Priority:
Major
Reporter:
g hs1
I have managed to get ansible-lint to report failures but the yamllint parser never works. It doesn't matter if I write to a log amd parse that, parse the console, separate scanning and publishng. The result is always no issues found.
[Pipeline] { (Run yamllint)
[Pipeline] sh
14:41:07 + yamllint ./
14:41:08 ./windows-utilities.yml
14:41:086:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:087:1 warning comment not indented like content (comments-indentation)
14:41:087:2 warning missing starting space in comment (comments)
14:41:089:1 errortoo many blank lines (2 > 1) (empty-lines)
14:41:0811:22 errorno new line character at the end of file (new-line-at-end-of-file)
14:41:08
[Pipeline] echo
14:41:08 hudson.AbortException: script returned exit code 1
[Pipeline] recordIssues
14:41:08 Skipping issues blame since Git is the only supported SCM up to now.
14:41:08 [YamlLint] Sleeping for 5 seconds due to JENKINS-32191...
14:41:13 [YamlLint] Parsing console log (workspace: '/var/lib/jenkins/workspace/CC3')
14:41:13 [YamlLint] Attaching ResultAction with ID 'yamllint' to run 'CC3 #21'.
14:41:13 [YamlLint] Using reference build 'CC3 #20' to compute new, fixed, and outstanding issues
14:41:13 [YamlLint] Issues delta (vs. reference
[JIRA] (JENKINS-54582) How to get a list of all Freestyle jobs from a Pipeline job?
Title: Message Title g hs1 commented on JENKINS-54582 Re: How to get a list of all Freestyle jobs from a Pipeline job? N.B. I never post requests like this without having spent many hours trying to solve problems myself. I have found nothing that works anywhere. I'm not even convinced that it's possible, which is why I asked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54582) How to get a list of all Freestyle jobs from a Pipeline job?
Title: Message Title g hs1 commented on JENKINS-54582 Re: How to get a list of all Freestyle jobs from a Pipeline job? Jenkins 2.151 Pipeline 2.6 and numerous dependencies. I'm not going to list them all. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54582) How to get a list of all Freestyle jobs from a Pipeline job?
Title: Message Title g hs1 commented on JENKINS-54582 Re: How to get a list of all Freestyle jobs from a Pipeline job? Can anyone suggest how to approach this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54582) How to get a list of all Freestyle jobs from a Pipeline job?
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-54582
How to get a list of all Freestyle jobs from a Pipeline job?
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-11-12 15:12
Priority:
Minor
Reporter:
g hs1
I'm trying to use the API to get to Freestyle jobs from a Pipeline job. There are various things I need to do but, as a first step, I've just been trying to retrieve a job or list of jobs. Nothing works. I've tried everything suggested here: https://stackoverflow.com/questions/47940699/get-all-pipeline-jobs-in-jenkins-groovy-script and elsewhere. The code runs from the system console but nothing will run from a Pipeline job e.g.
for(job in Jenkins.instance.getAllItems(hudson.model.Job)) {
println job.fullName
}
No problem in the console but...
[Pipeline] node
Running on master in /var/lib/jenkins/workspace/ghs1test@9
[Pipeline] End of Pipeline
java.lang.NoClassDefFoundError: Could not initialize class sun.nio.fs.UnixCopyFile
at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
at java.nio.file.Files.move(Files.java:1395)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:463)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgram(CpsThreadGroup.java:434)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.saveProgramIfPossible(CpsThreadGroup.java:422)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:362)
at
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title g hs1 commented on JENKINS-41818 Re: Performance Plugin - Compare Reports with Build number not working So what is this telling us? Is it expecting to find the jtl file from the previous build on the filesystem and using that to do the comparison? If so, how's that supposed to work when previous build artifacts are removed and archived? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53386) Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from the Artifactory repo.
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-53386 Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from the Artifactory repo. Change By: g hs1 Summary: Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from teh the Artifactory repo. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-53386) Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from teh Artifactory repo.
Title: Message Title g hs1 created an issue Jenkins / JENKINS-53386 Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from teh Artifactory repo. Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-09-03 10:10 Priority: Critical Reporter: g hs1 Neither [RELEASE] nor [INTEGRATION] are working when downloading packages from the Artifactory repo. E.g. http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/swarm-client/[RELEASE]/swarm-client-[RELEASE].jar fails. Using specific version numbers works: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/swarm-client/3.13/swarm-client-3.13.jar It stopped working on or about 24/8 according to my build logs. I returned from holiday to find things broken. I verifed that the calls fail on several packages using Postman. Thanks.
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title g hs1 closed an issue as Fixed Jenkins / JENKINS-50840 Powershell script execution broken in powershellHelper.ps1 Change By: g hs1 Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52650) Using @RequiresPlugin in wrapper classes
Title: Message Title
g hs1 updated JENKINS-52650
Thanks, Daniel. I actually went further than that and made use of JenkinsJobManagement, which opens the door to things like:
new JenkinsJobManagement(out, [:], new File('')).requirePlugin(name, this.failOnMissingPlugin)
and
new JenkinsJobManagement(out, [:], new File('')).requireMinimumPluginVersion(name, version, this.failOnMissingPlugin)
which give the full experience. Cheers.
Jenkins / JENKINS-52650
Using @RequiresPlugin in wrapper classes
Change By:
g hs1
Status:
Open Fixed but Unreleased
Resolution:
Fixed
Add Comment
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title g hs1 resolved as Fixed Thank you for your help and for investigating the problem. I'm not set up for Maven so I have applied your workaround and the script is now working. Jenkins / JENKINS-50840 Powershell script execution broken in powershellHelper.ps1 Change By: g hs1 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
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title
g hs1 commented on JENKINS-50840
Re: Powershell script execution broken in powershellHelper.ps1
Thank you. It doesn't appear so. Here's the script:
Param (
[Alias("Host")]
[string]$VIServer = "***",
[string]$vmname = "***",
[string]$admin = "***",
[string]$pathToCredentials
)
#You must change these values to securely save your credential files
$key = ***
Function Get-Credentials {
Param (
[String]$authUser = $env:USERNAME,
[string]$pathToCred
)
#Build the path to the credential file
$credFile = $authUser.Replace("\","~")
If (-not $pathToCred){
$pathToCred = Split-Path $MyInvocation.MyCommand.Path
}
$file = Join-Path -Path $pathToCred -ChildPath "\Credentials-$credFile.crd"
#And find out if it's there, if not create it
If(-not (Test-Path $file)){
(Get-Credential $authUser).Password | ConvertFrom-SecureString -Key $key | Set-Content $file
}
#Load the credential file
$password = Get-Content $file | ConvertTo-SecureString -Key $key
$authUser = (Split-Path $file -Leaf).Substring(12).Replace("~","\")
$authUser = $authUser.Substring(0,$authUser.Length - 4)
$credential = New-Object System.Management.Automation.PsCredential($authUser,$password)
Return $credential
}
If(-not $pathToCredentials){
$pathToCredentials = Split-Path $MyInvocation.MyCommand.Path
}
Clear-Host
$svr = "***"
$snapshot = "***"
$cred = Get-Credentials $admin $pathToCredentials
Try{
Write-Output "Connecting to vSphere server..."
$vc = Connect-VIServer $VIServer -Credential $cred -ErrorAction Stop 3>$null
Get-VM -Server $vc -Name $svr | Get-Snapshot | Select VM, Created, Name, SizeMB | FT
Write-Output "Restoring snapshot..."
$vm = Get-VM -Server $vc -Name $vmname
$snapshot = Get-Snapshot -VM $vm -Name $snapshot
Set-VM -VM $vm -Snapshot $snapshot -Confirm:$false
}
Catch{
Throw "Error connecting to $VIServer because ""$($Error[1])"""
}
# Exit with 0 unless an exception is thrown.
# Prevents returned values greater than 1 failing the build unnecessarily.
exit 0
It uses VMware's PowerCLI to restore a VM from a snapshot. Is there any way I can test your fix without waiting weeks or months for a release? Thanks.
Add Comment
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title g hs1 edited a comment on JENKINS-50840 Re: Powershell script execution broken in powershellHelper.ps1 Note that the PowerShell script itself still runs correctly outside of Jenkins. There are no spaces in the job name (JENKINS-48415) 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-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title g hs1 commented on JENKINS-50840 Re: Powershell script execution broken in powershellHelper.ps1 Note that the script itself still runs correctly outside of Jenkins. 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-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title
g hs1 updated an issue
Jenkins / JENKINS-50840
Powershell script execution broken in powershellHelper.ps1
Change By:
g hs1
Powershell script execution is broken, possibly after upgrading to durable task pluin plugin 1.22.{code:java}11:15:08 out-lineoutput : Object reference not set to an instance of an object.11:15:08 At C:\Builds\home\workspace\INTG_Lab_Installation_Script_Test\workspace@tmp\durable-19f0c27a\powershellHelper.ps1:25 char:711:15:08 + $Input | Out-String -Stream -Width 192 | ForEach-Object { $Writer.WriteLin ...11:15:08 + 11:15:08 + CategoryInfo : NotSpecified: (:) [out-lineoutput], NullReferenceException11:15:08 + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.OutLineOutputCommand11:15:08 {code}Reverting to 1.17 broke everything{code}Running in Durability level: MAX_SURVIVABILITY[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'node' found among steps [addBadge, addErrorBadge, addHtmlBadge, addInfoBadge, addShortText, addWarningBadge, ansiColor, archive, build, catchError, checkout, createSummary, deleteDir, dir, echo, error, fileExists, getContext, git, input, isUnix, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, mail, milestone, p4, p4approve, p4publish, p4sync, p4tag, p4unshelve, parallel, properties, publishHTML, pwd, readFile, readTrusted, removeBadges, removeHtmlBadges, removeSummaries, resolveScm, retry, sleep, stage, stash, step, svn, timeout, timestamps, tm, tool, unarchive, unstash, waitUntil, withContext, withCredentials, withEnv, wrap, writeFile] or symbols [absolute, agent, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, approve, architecture, archiveArtifacts, artifactManager, authorizationMatrix, autoClean, batchFile, bitbucket, booleanParam, buildButton, buildDiscarder, bzt, caseInsensitive, caseSensitive, certificate, checkstyle, choice, choiceParam, ciGame, cleanup, clientSpec, clock, cloud, command, credentials, cron, crumb, defaultView, demand, depotSource, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, envVars, file, fileCopyOperation, fileCreateOperation, fileDeleteOperation, fileDownloadOperation, fileJoinOperation, fileOperations, fileParam, filePath, filePropertiesToJsonOperation, fileRenameOperation, fileTransformOperation, fileUnTarOperation, fileUnZipOperation, fileZipOperation, fingerprint, fishEye, flushOnly, folderCopyOperation, folderCreateOperation, folderDeleteOperation, folderRenameOperation, forceClean, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, github, githubPush, globalLib, gradle, graphClean, graphSource, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, incremental, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, label, lastDuration, lastFailure,
[JIRA] (JENKINS-50840) Powershell script execution broken in powershellHelper.ps1
Title: Message Title
g hs1 created an issue
Jenkins / JENKINS-50840
Powershell script execution broken in powershellHelper.ps1
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2018-04-17 10:30
Environment:
Win2008R2 master, Win2016 agent. Jenkins 2.117 and earlier.
Priority:
Major
Reporter:
g hs1
Powershell script execution is broken, possibly after upgrading to durable task pluin 1.22.
11:15:08 out-lineoutput : Object reference not set to an instance of an object.
11:15:08 At C:\Builds\home\workspace\INTG_Lab_Installation_Script_Test\workspace@tmp\durable-19f0c27a\powershellHelper.ps1:25 char:7
11:15:08 + $Input | Out-String -Stream -Width 192 | ForEach-Object { $Writer.WriteLin ...
11:15:08 +
11:15:08 + CategoryInfo : NotSpecified: (:) [out-lineoutput], NullReferenceException
11:15:08 + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.PowerShell.Commands.OutLineOutputCommand
11:15:08
Reverting to 1.17 broke everything
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] End of Pipeline
java.lang.NoSuchMethodError: No such DSL method 'node' found among steps [addBadge, addErrorBadge, addHtmlBadge, addInfoBadge, addShortText,
[JIRA] (JENKINS-48325) Powershell step hangs indefinitely.
Title: Message Title g hs1 closed an issue as Duplicate Jenkins / JENKINS-48325 Powershell step hangs indefinitely. Change By: g hs1 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-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Change By: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this| [ https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/] ] .There's no apparent way around the exceptions and it's not clear how to make it work in other ways. 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-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 updated an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Change By: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this|[https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/] . ] . There's no apparent way around the exceptions and it's not clear how to make it work in other ways. 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-42801) Can't access "include" or "list" in parallel test executor. Security exceptions thrown.
Title: Message Title g hs1 created an issue Jenkins / JENKINS-42801 Can't access "include" or "list" in parallel test executor. Security exceptions thrown. Issue Type: Bug Assignee: Unassigned Components: parallel-test-executor-plugin Created: 2017/Mar/15 10:41 AM Environment: Win2008 R2. Jenkins 2.49. Latest plugins. Priority: Critical Reporter: g hs1 Jenkins throws security exceptions when trying to access "split.includes" or "split.list", as described in examples such as [this|https://jenkins.io/blog/2016/06/16/parallel-test-executor-plugin/.] There's no apparent way around the exceptions and it's not clear how to make it work in other ways. Add Comment
