[JIRA] (JENKINS-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")
Title: Message Title Boguslaw Klimas commented on JENKINS-55769 Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter") Hi Kevin, Plugin don't use 'git tag' to getting tags from repository, I explain this on wiki . 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-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Torben Knerr commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters Hi Bruno P. Kinoshita and Jenkins team, as a long term user and big fan of active choices, I would really love to see it being supported in blue ocean That's what is currently preventing us to upgrade from Jenkins classic to blue ocean. I can't help much more that than, just providing feedback that this would really be awesome to have Cheers, Torben 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-55071) Slow branch scan when using Bitbucket source
Title: Message Title Łukasz Wojciechowski commented on JENKINS-55071 Re: Slow branch scan when using Bitbucket source Not sure I'll bring anything to the topic but at least I can share my "solution" for the same problem. In my case, we have projects with crazy amount of branches backed by mercurial which results in 3+ minutes delays. In practice, we need Jenkins build kick in, only for a very small subset of branches so at some point I've ended up building my own version of bitbucket-branch-source-plugin. Note, that I have "zero" experience in Java dev world. So, with below change I got rid of that nasty delay before every build and in the end it was all I needed. https://github.com/lukaswoj/bitbucket-branch-source-plugin/commit/549899cf8d8b0229c37a3a155b588f36b98f2c78 This is how I build it, launched from repo root dir docker run -it -v "$(pwd)":/usr/src/mymaven -w /usr/src/mymaven maven:latest mvn -DskipTests package You should end up with HPI file generated under "target" subdirectory. HPI file can be installed under Upload Plugin section on "/pluginManager/advanced" page of your Jenkins installation. Hope this will be useful for someone. 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-55749) Support Rocket.Chat via Incoming Webhook for all Job types
Title: Message Title Martin Reinhardt commented on JENKINS-55749 Re: Support Rocket.Chat via Incoming Webhook for all Job types Give version 1.4.0 of the plugin a try. I added a system config entry for webhooks 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-55749) Support Rocket.Chat via Incoming Webhook for all Job types
Title: Message Title Martin Reinhardt updated an issue Jenkins / JENKINS-55749 Support Rocket.Chat via Incoming Webhook for all Job types Change By: Martin Reinhardt Released As: 1.4.0 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-55749) Support Rocket.Chat via Incoming Webhook for all Job types
Title: Message Title Martin Reinhardt started work on JENKINS-55749 Change By: Martin Reinhardt Status: Open In Progress 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Okay Thanks... I think here the behaviour of changed code is not okay and the tests failed are unrelated to my code. So now how should I approach to solve 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-55791) Mis-cleaned the Simplified Chinese localization files
Title: Message Title Rick updated an issue Jenkins / JENKINS-55791 Mis-cleaned the Simplified Chinese localization files Change By: Rick According to the LTS changelog, there are two LTS version (2.150.2, 2.150.1) missing the Chinese localization for install wizard. 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-44704) specify vault path as a parameter
Title: Message Title Mingzhe Huang commented on JENKINS-44704 Re: specify vault path as a parameter Hi, Is there any progress on this issue? I found it's quite useful. It's a common scenario that a set of properties have different sets of value under different environments. If we can support environment variables in Vault plugin, then people don't need to do the mapping by their own. It would be better if key names can support environment variables too. 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-55791) Mis-cleaned the Simplified Chinese localization files
Title: Message Title Rick created an issue Jenkins / JENKINS-55791 Mis-cleaned the Simplified Chinese localization files Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-26 01:02 Priority: Major Reporter: Rick According to the LTS changelog, there are two LTS version missing the Chinese localization for install wizard. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55790) Enable opt-out of RawHtmlMarkupFormatter processing
Title: Message Title Tom Skrainar created an issue Jenkins / JENKINS-55790 Enable opt-out of RawHtmlMarkupFormatter processing Issue Type: Improvement Assignee: Marc Brugger Components: badge-plugin Created: 2019-01-26 00:56 Environment: badge-plugin 1.5 and newer Priority: Minor Reporter: Tom Skrainar Commit 63a7744cef8e62898576a50bcc521d76ba9f (in support of SECURITY-906) filters text passed to BadgeSummaryAction.appendText() through a RawHtmlMarkupFormatter, which prevents arbitrary URI schemes being rendered as hrefs (only http/mailto seem to be supported). I appreciate the intent behind this change, but for people who rely on being able to provide hyperlinked text to arbitrary URI schemes, it would be really useful to explicitly disable this (resulting in a call to getRawHtml() instead). The current implementation is a (very) reasonable default, but I would like the ability to explicitly select "give me the unsanitized HTML". Add Comment
[JIRA] (JENKINS-55789) Document expected bug 23212 - idle timeout overrides boot
Title: Message Title Josiah Eubank created an issue Jenkins / JENKINS-55789 Document expected bug 23212 - idle timeout overrides boot Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2019-01-26 00:40 Priority: Minor Reporter: Josiah Eubank This 2014 comment is still applicable "Was able to reproduce the described behavior using JNLP connection with a long post-boot delay and a short idle time to disconnect. The two features are colliding. Solutions: decrease post-boot delay to bare minimum needed, use non-JNLP slave agent connection, or increase the idle time to disconnect." However, I cannot find this documented anywhere and it should be on the plugin page – or fixed. Idle timeout should not start counting down until after the connect is complete. Add Comment
[JIRA] (JENKINS-55788) Error when configuring Kubernetes Plugin v1.14.3
Title: Message Title Michael Douglas Pacheco Gonçalves Dias created an issue Jenkins / JENKINS-55788 Error when configuring Kubernetes Plugin v1.14.3 Issue Type: Bug Assignee: Michael Douglas Pacheco Gonçalves Dias Attachments: 1.png Components: kubernetes-plugin Created: 2019-01-25 22:52 Environment: Jenkins version: 2.161 Kubernetes-plugin version: 1.14.3 OS: Linux mint 19.1 (Tessa) Labels: kubernetes-plugin kubernetes minikube Priority: Blocker Reporter: Michael Douglas Pacheco Gonçalves Dias I'm following the steps in this article to setup Jenkins on top of my Kubernetes (minikube) cluster. When I ask to Kubernetes plugin to test the connection with my cluster this message appears: Error testing connection https://192.168.99.113:8443: Failure executing: GET at: https://192.168.99.113:8443/api/v1/namespaces/default/pods. Message: Forbidden!Configured service account doesn't have access. Service account may have been revoked. pods is forbidden: User "system:serviceaccount:default:default" cannot list resource "pods" in API group "" in the namespace "default".
[JIRA] (JENKINS-35417) Support "last exist" condition.
Title: Message Title Chad Gilman commented on JENKINS-35417 Re: Support "last exist" condition. I added this feature, in my branch, as a new selector called 'Last completed build with artifacts' and will be putting together a pull request soon. Rather than a new selector, maybe it should be an option for the 'Last completed build (ignoring build status)' selector instead? Thoughts? 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-35417) Support "last exist" condition.
Title: Message Title Chad Gilman assigned an issue to Unassigned Jenkins / JENKINS-35417 Support "last exist" condition. Change By: Chad Gilman Assignee: Chad Gilman 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-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title Ryan Tse commented on JENKINS-50751 Re: Link created by naginator plugin contains comma in job numbers over 999 Can this change be reviewed, merged, and released? 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-35417) Support "last exist" condition.
Title: Message Title Chad Gilman assigned an issue to Chad Gilman Jenkins / JENKINS-35417 Support "last exist" condition. Change By: Chad Gilman Assignee: Chad Gilman 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-55786) Lost Connectivity to VSTS
Title: Message Title Mark Waite updated JENKINS-55786 Jenkins / JENKINS-55786 Lost Connectivity to VSTS Change By: Mark Waite Status: Fixed but Unreleased 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-55787) Switch from entry to optional block
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch from entry to optional block Change By: Josh Soref Component/s: git-plugin 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-55786) Lost Connectivity to VSTS
Title: Message Title Mark Waite updated JENKINS-55786 Chris Huddleston you'll get better results requesting help from a larger group than the few people that watch the bug reports in the Jira project for the git plugin. The Jenkins users mailing list and the Jenkins chat channels all have many more readers and many more contributors than the number of people that watch git plugin bug reports. When I was using Visual Studio alternate credentials, there were times that the alternate credentials were disabled by the Visual Studio Team System server. I don't if that was due to detected attacks or due to authentication failures or due to expiration of a time limit on the alternate credentials. Ultimately, I stopped using alternate credentials because I was tired of adapting to the times when they became disabled. I believe Visual Studio provides authorization tokens that can be generated and used as "single purpose credentials". You may want to investigate those. Jenkins / JENKINS-55786 Lost Connectivity to VSTS Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This
[JIRA] (JENKINS-55787) Switch from entry to optional block
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-55787 Switch from entry to optional block Change By: Josh Soref Component/s: github-plugin Component/s: workflow-cps-global-lib-plugin 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-55787) Switch from entry to optional block
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55787 Switch from entry to optional block Issue Type: Bug Assignee: Josh Soref Components: slack-plugin Created: 2019-01-25 21:58 Priority: Minor Reporter: Josh Soref This is the preferred style: As opposed to: or – I'm going to point to this issue for a bunch of plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55786) Lost Connectivity to VSTS
Title: Message Title Chris Huddleston created an issue Jenkins / JENKINS-55786 Lost Connectivity to VSTS Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-01-25 21:45 Environment: Windows 2016 for both mast and slave. Alternate credentials for git Labels: git Priority: Blocker Reporter: Chris Huddleston Overnight, with no changes, an authentication failure occurred which prevented us from using the alternative credentials within VSTS. I made sure that the creds in both Jenkins and VSTS are the same. When I try to manually login on git from the master, I receive this error: fatal: Authentication failed for 'https://prod1.visualstudio.com/_git/prodscripts/' Within Jenkins, I have this error on a job: Failed to connect to repository : Command "git.exe ls-remote -h https://prod1.visualstudio.com/_git/prodscripts HEAD" returned status code 128:stdout:stderr: fatal: Authentication failed for 'https://prod1.visualstudio.com/_git/prodscripts/' I made sure everything is also up to date. I'm at a little bit of a loss on this one.
[JIRA] (JENKINS-54033) GitHub auth fails only for PR builds
Title: Message Title Bryce Schober assigned an issue to rsandell Jenkins / JENKINS-54033 GitHub auth fails only for PR builds Change By: Bryce Schober Assignee: Bryce Schober rsandell 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-54033) GitHub auth fails only for PR builds
Title: Message Title Bryce Schober assigned an issue to Bryce Schober Jenkins / JENKINS-54033 GitHub auth fails only for PR builds Change By: Bryce Schober Assignee: Bryce Schober 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Andrew Bayer resolved as Duplicate Yeah, this is one aspect of JENKINS-44376. Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Andrew Bayer Status: Open Resolved Resolution: Duplicate 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Devin Nusbaum edited a comment on JENKINS-55771 Re: Assign variable from shell output using declarative pipeline There might be an existing issue to track this kind of thing already, but IIUC it is somewhat by design (CC @ [~ abayer ] ). In your example at least you could move your echo into the script you run, but perhaps that is not your real use case. 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-55785) Incorporate clang static analysis HTML output into presentation
Title: Message Title Braden McDaniel created an issue Jenkins / JENKINS-55785 Incorporate clang static analysis HTML output into presentation Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-25 20:05 Priority: Minor Reporter: Braden McDaniel clang's static analysis emits a set of HTML pages that step through clang's analysis of the code. It would be very useful to incorporate these into warnings-ng's presentation of the issues. The pages are written to a directory under /tmp; the full path is printed (by scan-build) at the end of the build log. Add Comment
[JIRA] (JENKINS-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Devin Nusbaum commented on JENKINS-55771 Re: Assign variable from shell output using declarative pipeline There might be an existing issue to track this kind of thing already, but IIUC it is somewhat by design (CC @abayer). In your example at least you could move your echo into the script you run, but perhaps that is not your real use case. 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Devin Nusbaum Assignee: Devin Nusbaum 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Devin Nusbaum Component/s: pipeline-model-definition-plugin Component/s: pipeline Component/s: workflow-durable-task-step-plugin 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Devin Nusbaum Labels: pipeline 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-55771) Assign variable from shell output using declarative pipeline
Title: Message Title Bryce Schober assigned an issue to Devin Nusbaum Jenkins / JENKINS-55771 Assign variable from shell output using declarative pipeline Change By: Bryce Schober Assignee: Devin Nusbaum 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-55784) Multibranch pipeline indexing ignores SVN Exclusion revprop configuration
Title: Message Title Bryce Schober created an issue Jenkins / JENKINS-55784 Multibranch pipeline indexing ignores SVN Exclusion revprop configuration Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: pipeline, subversion-plugin, workflow-multibranch-plugin Created: 2019-01-25 19:55 Environment: Jenkins LTS 2.150.2 with up-to-date plugins Priority: Major Reporter: Bryce Schober The title basically says it all. The multi-branch SVN SCM configuration doesn't support the revprop or user exclusions that the ordinary SVN SCM source options do. So I've set my global Jenkins "Exclusion revprop name" configuration to "branch:skip", a revprop that I've added to all commits that I don't want to re-build... which works fine inside a pipeline Jenkinsfile, but apparently still doesn't apply to multi-branch indexing. Very frustrating. Add Comment
[JIRA] (JENKINS-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Title: Message Title Josh Soref commented on JENKINS-27126 Re: New Scroll bar in Jenkins Build history is showing when shouldn't be https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-wrap ? 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-55489) Update Jenkins upstream version from snapshot
Title: Message Title Matt Sicker updated JENKINS-55489 Merged to master. Jenkins / JENKINS-55489 Update Jenkins upstream version from snapshot Change By: Matt Sicker Status: In Review Resolved 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-55783) Plugin doesn't delete statuses
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-55783
Plugin doesn't delete statuses
Issue Type:
Bug
Assignee:
Jeff Pearce
Components:
github-autostatus-plugin
Created:
2019-01-25 18:45
Priority:
Minor
Reporter:
Josh Soref
we have a pipeline job (well lots actually) which use:
pipeline {
...
triggers { cron('H/20 * * * *') }
...
}
These jobs run essentially forever. Eventually GitHub screams because 1000 contexts have been created for the same sha.
Add Comment
[JIRA] (JENKINS-55774) withCredentials blocked by script approval and errors after approval
Title: Message Title Thibault Doubliez closed an issue as Not A Defect Jenkins / JENKINS-55774 withCredentials blocked by script approval and errors after approval Change By: Thibault Doubliez Status: Open Closed Resolution: Not A Defect 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-55774) withCredentials blocked by script approval and errors after approval
Title: Message Title Thibault Doubliez commented on JENKINS-55774 Re: withCredentials blocked by script approval and errors after approval Silly mistake from me, what broke it is that I defined a variable called "file" just before that... Closing this ticket. 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-34646) High CPU Usage navigating the UI
Title: Message Title Ximei Zhang commented on JENKINS-34646 Re: High CPU Usage navigating the UI We have been experiencing some high CPU issue on our jenkins server for quite a while. Among all the running thread, one of the jenkins.util.Timer thread consumes high CPU usage. There are 10 jenkins.util.Timer thread running, the rest 9 thread consume less than 1% CPU. Anyone has any idea about 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-55782) Found 4 elements with non-unique id #svn.remote.loc
Title: Message Title
Josh Soref created an issue
Jenkins / JENKINS-55782
Found 4 elements with non-unique id #svn.remote.loc
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
subversion-plugin
Created:
2019-01-25 18:35
Priority:
Minor
Reporter:
Josh Soref
I get this when I go to /configure:
[DOM] Found 4 elements with non-unique id #svn.remote.loc: (More info: https://goo.gl/9p2vKq) "remote" _onchange_="{ /* workaround for JENKINS-19124 */ var self=this.targetElement ? this.targetElement : this; var r=findNextFormItem(self,'credentialsId'); r.onchange(r); if (self===document.getElementById('svn.remote.loc')){ r=findNextFormItem(self,'excludedRevprop'); r.onchange(r); } self=null; r=null; }" id="svn.remote.loc" checkurl="/descriptorByName/hudson.scm.SubversionSCM$ModuleLocation/checkRemote" name="_.remote" type="text" class="setting-input validated " value>
"remote" _onchange_="{ /* workaround for JENKINS-19124 */ var self=this.targetElement ? this.targetElement : this; var r=findNextFormItem(self,'credentialsId'); r.onchange(r); if (self===document.getElementById('svn.remote.loc')){ r=findNextFormItem(self,'excludedRevprop'); r.onchange(r); } self=null; r=null; }" id="svn.remote.loc" checkurl="/descriptorByName/hudson.scm.SubversionSCM$ModuleLocation/checkRemote" name="_.remote" type="text"
[JIRA] (JENKINS-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Title: Message Title Daniel Beck edited a comment on JENKINS-27126 Re: New Scroll bar in Jenkins Build history is showing when shouldn't be Not a lot of Java involved with this specific problem ;) Although I wonder how well this handles a number of 'long content' scenarios – many build badges, long build name, long build description, etc.This is probably a reasonable PR to submit to jenkinsci/jenins on GitHub, but don't be too disappointed if it doesn't get picked up if there are due to potential problems – we've done _many_ iterations on this widget because almost every change tends to break someone's use case . 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Title: Message Title Daniel Beck commented on JENKINS-27126 Re: New Scroll bar in Jenkins Build history is showing when shouldn't be Not a lot of Java involved with this specific problem Although I wonder how well this handles a number of 'long content' scenarios – many build badges, long build name, long build description, etc. This is probably a reasonable PR to submit to jenkinsci/jenins on GitHub, but don't be too disappointed if it doesn't get picked up if there are problems. 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-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title Mark Waite updated JENKINS-55781 Jenkins / JENKINS-55781 When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error. Change By: Mark Waite Status: Fixed but Unreleased 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-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title Mark Waite updated JENKINS-55781 This is a duplicate of JENKINS-41066. Work around the bug by defining a credential in Jenkins and then use that credential in the job definition. That "work around" is the preferred method to use credentials in Jenkins. It reduces the risk of plain text credentials being displayed to users reading log files, to administrators configuring job definitions, and to others. Jenkins / JENKINS-55781 When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error. Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Duplicate 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
[JIRA] (JENKINS-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title syed muqeet updated an issue Jenkins / JENKINS-55781 When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error. Change By: syed muqeet Failed to connect to repository : Command "git.exe ls-remote -h http://bitbucket.com/.git HEAD" returned status code 128:stdout: stderr: fatal: remote error: CAPTCHA requiredYour Bitbucket account has been locked. To unlock it and log in again you mustsolve a CAPTCHA. This is typically caused by too many attempts to login with anincorrect password. The account lock prevents your SCM client from accessingBitbucket and its mirrors until it is solved, even if you enter your passwordcorrectly.If you are currently logged in to Bitbucket via a browser you may need tologout and then log back in in order to solve the CAPTCHA.Visit Bitbucket at http://bitbucket.com for more details. 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-55781) When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error.
Title: Message Title syed muqeet created an issue Jenkins / JENKINS-55781 When selecting Git in Source Code Management and updating http://user:passw...@bitbucket.com/.git. It gives an authentication error. Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-01-25 18:06 Priority: Major Reporter: syed muqeet 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-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title Oleg Nenashev commented on JENKINS-55780 Re: User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login The request is not related to the Role Strategy plugin 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-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-55780 User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login Change By: Oleg Nenashev Assignee: Oleg Nenashev 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-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55780 User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login Change By: Oleg Nenashev Component/s: role-strategy-plugin 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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be
Title: Message Title
Tim Sorrells commented on JENKINS-27126
Re: New Scroll bar in Jenkins Build history is showing when shouldn't be
I'm not a contributor to the Jenkins project. I'm not even a Java programmer, but I can provide a workaround that fixed this for me locally. Find the style.css file for your installation of Jenkins. Something like /Users/Shared//home/war/css/style.css. And then I commented out the overflow attribute on this element, like so:
.build-row.multi-line .build-row-cell .block {
display: block;
/*overflow: auto;*/ /* Disabling to prevent unnecessary horizontal scrollbar in the Build History list when the job name gets slightly long */
}
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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Basil Crow commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server I experienced this failure mode twice on January 16, two weeks after upgrading Jenkins from 2.138.1 LTS (with workflow-job 2.25, workflow-cps 2.54, and workflow-durable-task-step 2.21) to 2.150.1 LTS (with workflow-job 2.31, workflow-cps 2.61, and workflow-durable-task-step 2.27). I am not running Java 11. The job has been running daily and has only failed twice with this failure mode, so the error is transient. ERROR: missing workspace /var/tmp/jenkins_slaves/jenkins-ops/workspace/devops-gate/master/sync-ova-into-dcod on scale-dc2 ERROR: missing workspace /var/tmp/jenkins_slaves/jenkins-ops/workspace/devops-gate/master/sync-ova-into-dcod@2 on dc3 When this error occurred on the 16th, I logged into these machines and checked the given directories on the command line. In both cases the directories existed. So I suspect there may have been some transient I/O error at the time. 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-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title
Rick Liu updated an issue
Jenkins / JENKINS-55780
User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Change By:
Rick Liu
When a new user *FIRST-TIME* using LDAP credential to login,Jenkins will create{{*/users//config.xml* file,}}{{and update *LastGrantedAuthoritiesProperty* attribute with the current timestamp:}} {{ }} {{ }} {{ authenticated }} {{ }} {{ *1548376473889* }} {{ }} But any subsequent LDAP login,the *timestamp* of {{*LastGrantedAuthoritiesProperty*}} is not updated anymore.
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-55780) User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Title: Message Title
Rick Liu created an issue
Jenkins / JENKINS-55780
User property LastGrantedAuthoritiesProperty is not updated when LDAP user is login
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
core, ldap-plugin, role-strategy-plugin
Created:
2019-01-25 17:54
Environment:
Ubuntu 16.04.5 OpenJDK 1.8.0.191 Jenkins 2.138.4 LDAP plugin 1.20 Role-based Authorization Strategy 2.9.0
Priority:
Major
Reporter:
Rick Liu
When a new user FIRST-TIME using LDAP credential to login, Jenkins will create /users//config.xml file, and update LastGrantedAuthoritiesProperty attribute with the current timestamp: {{ LastGrantedAuthoritiesProperty>}} {{ }} {{ authenticated}} {{ }} {{ 1548376473889}} {{ }} But any subsequent LDAP login, the timestamp of LastGrantedAuthoritiesProperty is not updated anymore.
Add Comment
[JIRA] (JENKINS-51734) sessionTimeout isn't be honoured
Title: Message Title Martin Spielmann commented on JENKINS-51734 Re: sessionTimeout isn't be honoured Im sorry I won't be able to work I this topic before March. Any help and PR is highly appreciated. 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-55356
Re: Some workflow jobs fail after restart on Java 11 server
{quote}The error message comes from [workflow-durable-task-step|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/20dc6a9bc70e8b6ec598d4836b5c20cf57abd8ea/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L345]. It would be interesting to check whether the directory mentioned in the error actually exists on the agent, or if it is missing, or exists but has a different name (perhaps a randomized suffix or `-` instead of `_` or something, which could be related to recent branch-api changes).{quote}Another thing to point out is that {{FilePath#isDirectory}} will return false in some failure cases (see the [Javadoc for {{File#isDirectory}}|https://docs.oracle.com/javase/7/docs/api/java/io/File.html#isDirectory()]). Perhaps we should update [this line|https://github.com/jenkinsci/jenkins/blob/226f7b4c2bedb14b70f12da90db15574e18364d0/core/src/main/java/hudson/FilePath.java#L1653] to use NIO methods so it throws exceptions instead of returning false in some cases (another case of JENKINS-47324). Edit: I filed [https://github.com/jenkinsci/jenkins/pull/3864] for that issue. Double edit: Also to clarify, if {{FilePath#isDirectory}} _had_ thrown an exception, then [this code|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/20dc6a9bc70e8b6ec598d4836b5c20cf57abd8ea/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L341] would have been called, which would have caused Pipeline to attempt to connect again rather than aborting the build immediately. That issue wouldn't really explain why we are seeing this on Java 11 and not Java 8, but seems worth investigating.
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
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-55356
Re: Some workflow jobs fail after restart on Java 11 server
{quote} The error message comes from [workflow-durable-task-step|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/20dc6a9bc70e8b6ec598d4836b5c20cf57abd8ea/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L345]. It would be interesting to check whether the directory mentioned in the error actually exists on the agent, or if it is missing, or exists but has a different name (perhaps a randomized suffix or `-` instead of `_` or something, which could be related to recent branch-api changes).{quote} Another thing to point out is that {{FilePath#isDirectory}} will return false in some failure cases (see the [Javadoc for {{File#isDirectory}}|https://docs.oracle.com/javase/7/docs/api/java/io/File.html#isDirectory()]). Perhaps we should update [this line|https://github.com/jenkinsci/jenkins/blob/226f7b4c2bedb14b70f12da90db15574e18364d0/core/src/main/java/hudson/FilePath.java#L1653] to use NIO methods so it throws exceptions instead of returning false in some cases (another case of JENKINS-47324). Edit: I filed [https://github.com/jenkinsci/jenkins/pull/3864] for that issue.
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-46376) Allow getting log through RunWrapper
Title: Message Title Brian M commented on JENKINS-46376 Re: Allow getting log through RunWrapper Any update on this? The last update was on "2018-01-12 14:02" 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging This has been released 1.2.1, it should available soon in the update center. Thank you Vlad Uros and Marjo Hartman for the help reporting this. Closing this now, don't mind to reopen or create a new one just in case if there is any issues with this change. Thanks again. 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati updated JENKINS-55194 Jenkins / JENKINS-55194 Add logLevel to support debugging and also reduce default excessive logging Change By: Naresh Rayapati Status: In Review Resolved 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Naresh Rayapati closed an issue as Fixed Jenkins / JENKINS-55194 Add logLevel to support debugging and also reduce default excessive logging Change By: Naresh Rayapati 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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-55356
Re: Some workflow jobs fail after restart on Java 11 server
{quote}The error message comes from [workflow-durable-task-step|https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/20dc6a9bc70e8b6ec598d4836b5c20cf57abd8ea/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L345]. It would be interesting to check whether the directory mentioned in the error actually exists on the agent, or if it is missing, or exists but has a different name (perhaps a randomized suffix or `-` instead of `_` or something, which could be related to recent branch-api changes).{quote}Another thing to point out is that {{FilePath#isDirectory}} will return false in some failure cases (see the [ Javadoc for {{File#isDirectory}} |https://docs.oracle.com/javase/7/docs/api/java/io/File.html#isDirectory( ) ]) . Perhaps we should update [this line|https://github.com/jenkinsci/jenkins/blob/226f7b4c2bedb14b70f12da90db15574e18364d0/core/src/main/java/hudson/FilePath.java#L1653] to use NIO methods so it throws exceptions instead of returning false in some cases (another case of JENKINS-47324).
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-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Devin Nusbaum commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server The error message comes from workflow-durable-task-step. It would be interesting to check whether the directory mentioned in the error actually exists on the agent, or if it is missing, or exists but has a different name (perhaps a randomized suffix or `-` instead of `_` or something, which could be related to recent branch-api changes). Another thing to point out is that FilePath#isDirectory will return false in some failure cases (see the Javadoc for File#isDirectory). Perhaps we should update this line to use NIO methods so it throws exceptions instead of returning false in some cases (another case of JENKINS-47324). 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Jesse Glick commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master mvn -DskipTests clean install && mvn -f test surefire:test -Dtest=WhateverTest\#method if there is a specific test you are interested in, though you can also just use CI (failures look unrelated to your code). In this case I doubt there is any relevant automated test coverage—the issue would need to be verified manually by actually simulating an out of disk space event. 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-36709) Possible duplicate user creation.
Title: Message Title Wadeck Follonier resolved as Fixed PR was merged Jenkins / JENKINS-36709 Possible duplicate user creation. Change By: Wadeck Follonier Status: In Progress Resolved 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Can anyone tell me how can I run tests on my local computer? 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-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Charusheela Bopardikar edited a comment on JENKINS-39107 Re: expose "Stream Codeline" as an environment variable Exposed jenkinsfile path is stored as env variable irrespective of streams 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-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Charusheela Bopardikar edited a comment on JENKINS-39107 Re: expose "Stream Codeline" as an environment variable Please review jenkinsfile path is stored as env variable irrespective of streams 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-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Charusheela Bopardikar updated JENKINS-39107 Please review Jenkins / JENKINS-39107 expose "Stream Codeline" as an environment variable Change By: Charusheela Bopardikar 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-39107) expose "Stream Codeline" as an environment variable
Title: Message Title Charusheela Bopardikar stopped work on JENKINS-39107 Change By: Charusheela Bopardikar Status: In Progress Open 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master https://github.com/jenkinsci/jenkins/pull/3863 In these pull request 4 existing tests got failed. Can you please help me in figuring out what happened? As no code of that modules were changed. 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-42073) Support sorting tags by taggerdate
Title: Message Title Tom Farmer commented on JENKINS-42073 Re: Support sorting tags by taggerdate Any update on this one? Would love to be able to sort and show the branches with the latest activity at the top of the list. 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-54604) checkUpdatesServer fails to use SSL
Title: Message Title Josh Soref commented on JENKINS-54604 Re: checkUpdatesServer fails to use SSL https://github.com/jaliss/securesocial/issues/627 seems interesting... 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-55772) No access without Overall/Read
Title: Message Title Christoph Vogtländer closed an issue as Not A Defect Jenkins / JENKINS-55772 No access without Overall/Read Change By: Christoph Vogtländer Status: Open Closed Resolution: Not A Defect 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-55772) No access without Overall/Read
Title: Message Title Christoph Vogtländer commented on JENKINS-55772 Re: No access without Overall/Read You are right. I overlooked that "authenticated" users got Job and View Read permissions (and the user inherited these). Sometimes you look so hard to find a problem that you simply do not see the obvious 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-51734) sessionTimeout isn't be honoured
Title: Message Title in ka commented on JENKINS-51734 Re: sessionTimeout isn't be honoured sessionEviction also not works for me. Anybody found a work around? 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-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title
Karl Wirth commented on JENKINS-55248
Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time
Hi, Frederico Pratas, We haven't finished the investigation yet but we think it may be due to hard coded workspace names. In the above example you have 'p4_ws_name'. Is this a hard coded name in the real script? This needs to be unique for every node it runs on. Therefore we recommend you use a naming convention such as 'jenkins-${NODE_NAME}${JOB_NAME}${EXECUTOR_NUMBER}'. Are you able to try this and see if it resolves the problem. If not let me know and we can start a support case.
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-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title
Karl Wirth edited a comment on JENKINS-55248
Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time
Hi, [~samica],We haven't finished the investigation yet but we think it may be due to hard coded workspace names.In the above example you have '*p4_ws_name*'. Is this a hard coded name in the real script?This needs to be unique for every node it runs on. Therefore we recommend you use a naming convention such as ' {code:java} jenkins-${NODE_NAME} - ${JOB_NAME} - ${EXECUTOR_NUMBER} '. {code} Are you able to try this and see if it resolves the problem. If not let me know and we can start a support case.
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-55779) BranchIndexing deadlock with health check - Jenkins slowness
Title: Message Title Radhika KV updated an issue Jenkins / JENKINS-55779 BranchIndexing deadlock with health check - Jenkins slowness Change By: Radhika KV Attachment: Thread Dump.docx 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-55779) BranchIndexing deadlock with health check - Jenkins slowness
Title: Message Title
Radhika KV created an issue
Jenkins / JENKINS-55779
BranchIndexing deadlock with health check - Jenkins slowness
Issue Type:
Bug
Assignee:
Lucie Votypkova
Components:
disk-usage-plugin, pipeline-multibranch-defaults-plugin, scm2job-plugin
Created:
2019-01-25 13:48
Priority:
Minor
Reporter:
Radhika KV
Jenkins becomes very slow with the below message in the health-checker.log The branch indexing for My-Multi-Branch-SNAPSHOT succeeds without issues most of the time. But at times, it gets into a deadlock like below. Over time, jenkins completes hangs up and we end up restarting to restore the server. Requesting help in identifying the root cause of the issue and solution for the same. Jenkins version: 2.7.4 Branch indexing log: It hangs forever Branch Indexing Log Started by timer > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to ssh://git@mystash/myproject.git > git config remote.origin.url ssh://git@mystash/myproject.git # timeout=10 Fetching & pruning origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_SSH to set credentials credentails for GIT > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ --prune Getting remote branches... Seen branch in repository origin/develop Seen branch in repository origin/master Seen branch in repository origin/release Seen 3 remote branches Checking branch master No changes detected in master (still at 7c4f090ce09229b6900258a79755a72eb16f5a1e) Checking branch develop health-checker.log Starting health checks at Fri Jan 25 04:48:02 PST 2019 Health check results at Fri Jan 25 04:48:02 PST 2019: * disk-space: Result{isHealthy=true} * mesos: Result{isHealthy=true} * plugins: Result{isHealthy=true, message=No failed plugins} * temporary-space: Result{isHealthy=true} * thread-deadlock: Result{isHealthy=false, message=[Handling GET /job/ENF/ from 10.111.9.36 : RequestHandlerThread225 View/index.jelly LastSuccessColumn/column.jelly locked on
[JIRA] (JENKINS-55778) Github branch source plugin builds untrusted builds during scan
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-55778 Github branch source plugin builds untrusted builds during scan Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-01-25 13:24 Environment: Jenkins 2.150.2 Github Branch Source Plugin 2.4.2 Labels: security Priority: Blocker Reporter: Brian J Murrell I have opened this as a Blocker given the security implications of it. In Projects->Behaviours->Discover pull requests from forks->Trust I have chosen the From users with Admin or Write permission strategy because I don't want PRs from users outside of those with Admin or Write permission to be able to run jobs on my Jenkins server, ever (well, frankly, I would like to be able to "approve" PRs from such but that's a different ticket). However, during a Repository Scan, PRs from users outside of the above group are being run: Checking pull request #28 (not from a trusted source) ‘Jenkinsfile’ found Not mergeable, build likely to fail Met criteria Changes detected: PR-28 ([redacted1]+[redacted2] → [redacted1+[redacted3) Scheduled build for branch: PR-28 The user that submitted that PR is neither an Admin nor has Write permission. I do believe the permissions are being enforced
[JIRA] (JENKINS-55777) Direct field access in super class fails
Title: Message Title
Jon Sten created an issue
Jenkins / JENKINS-55777
Direct field access in super class fails
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
script-security-plugin, workflow-cps-plugin
Created:
2019-01-25 13:20
Environment:
workflow-cps:2.62 script-security 1.50 Jenkins-core:2.150.2
Priority:
Minor
Reporter:
Jon Sten
There seems to be something wrong in the handling of direct field access in the sandbox/cps implementation. Executing the following in a sandboxed pipeline will fail (not the direct field access in the constructor for A, this.@name):
abstract class A {
String name
A(String name) {
this.@name = name
}
}
class B extends A {
B(String name) {
super(name)
}
}
def b = new B("B")
echo b.name
It works as expected when executed without sandboxing or in a normal groovy interpreter. Judging from the stack-trace it looks like it tries to set the field for the class B while it is defined in class A. It throws the following exception:
groovy.lang.MissingFieldException: No such field: name for class: B
at groovy.lang.MetaClassImpl.setAttribute(MetaClassImpl.java:2886)
at groovy.lang.MetaClassImpl.setAttribute(MetaClassImpl.java:3793)
at org.codehaus.groovy.runtime.InvokerHelper.setAttribute(InvokerHelper.java:161)
at
[JIRA] (JENKINS-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Giorgio Sironi commented on JENKINS-50451 Re: Provide badge for Cloudbees Docker Hub Notification We stopped using this, but I went back to an old build and got: "org.jenkinsci.plugins.registry.notification.webhook.dockerhub.DockerHubWebHookCause">Triggered by push of xpub/xpub-elife to docker...@registry.hub.docker.com Hope it helps. 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-55776) export image information to build steps
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-55776 export image information to build steps Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-01-25 12:57 Priority: Major Reporter: Brian J Murrell Due to Jenkins not doing it's own docker image garbage collection I would like to implement my own garbage collection based on which images are actually current and which are stale rather than the more naïve implementation in docker-gc of just removing the oldest images without regard to whether they are actually still currently being used by Pipeline jobs or not. To do so, I need to keep an accounting of which images are being used by which jobs. This would need to be done in the step, or post of a Pipeline job and as such it would be useful if some kind of identifier of the image (image ID, tag, etc.) were exported to the job step and/or post. Add Comment
[JIRA] (JENKINS-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Baptiste Mathus edited a comment on JENKINS-50451 Re: Provide badge for Cloudbees Docker Hub Notification [~giorgiosironi] sorry, I forgot about this one.Could you pretty please provide the associated XML classname for that cause ?See https://wiki.jenkins.io/display/JENKINS/Build+Trigger+Badge+Plugin #BuildTriggerBadgePlugin-Wait,thisdoesnotwork,Iseeaquestionmarkiconformybuilds! doc to see how to. Basically using https://yourjenkinsserver/job/somejob/15/api/xml?xpath=//cause=causes_ and providing the output would help do this very easily. it's a action that should be matter of seconds if you can access your instance. Thank you! 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-50451) Provide badge for Cloudbees Docker Hub Notification
Title: Message Title Baptiste Mathus commented on JENKINS-50451 Re: Provide badge for Cloudbees Docker Hub Notification Giorgio Sironi sorry, I forgot about this one. Could you pretty please provide the associated XML? See https://wiki.jenkins.io/display/JENKINS/Build+Trigger+Badge+Plugin#BuildTriggerBadgePlugin-Wait,thisdoesnotwork,Iseeaquestionmarkiconformybuilds! it's a action that should be matter of seconds if you can access your instance. Thank you! 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Baptiste Mathus updated JENKINS-55252 Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Released As: 2.10 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Baptiste Mathus started work on JENKINS-55252 Change By: Baptiste Mathus Status: Open In Progress 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Baptiste Mathus updated JENKINS-55252 Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Baptiste Mathus Status: In Progress Review 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-55252) Build Trigger Badge plugin shows me question mark for build by parameterized scheduler
Title: Message Title Baptiste Mathus assigned an issue to Jiuk Jeong Jenkins / JENKINS-55252 Build Trigger Badge plugin shows me question mark for build by parameterized scheduler Change By: Baptiste Mathus Assignee: Baptiste Mathus Jiuk Jeong 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-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Karl Wirth commented on JENKINS-55737 Re: "No polling baseline - Changes found" causing runaway polling Hi Deepu Sudhakar. Can you let me know if the error you see is related to the Jenkins master or Jenkins slave. 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-55194) Add logLevel to support debugging and also reduce default excessive logging
Title: Message Title Vlad Uros commented on JENKINS-55194 Re: Add logLevel to support debugging and also reduce default excessive logging Thank you very much Naresh. It does make sense what you suggested, just to see command output when log level set to OFF. 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-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title
Frederico Pratas edited a comment on JENKINS-55248
Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time
Hi,Any update on this one?I get a similar issue on my setup.I've several independent pipeline jobs.Each job, when triggered, does a p4 checkout.When multible jobs are triggered at the same time the P4CLIENT seems to be inconsistent between jobs and some of the jobs fail because they are using the client from a different job. It seems that the P4CLIENT variable is being shared between different checkout processes.The jobs that get the wrong P4CLIENT fail with the error reported previously:ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s):Path '/correct/path/for/this/job/...' is not under client's root '/path/from/parallel/job'.Each job is using the checkout in the following manner:{{def p4_ws_name = 'jenkins_${env.JOB_NAME}'def workspace_view = """\ //my_depot/... //${p4_ws_name}/... """.stripIndent()pipeline { agent any options { timestamps() } stages { stage('Checkout') { steps {checkout perforce( credential: '', populate: autoClean( delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), workspace: manualSpec( charset: 'none', cleanup: false, name: p4_ws_name, pinHost: false, spec: clientSpec( allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: workspace_view ) )) } } stage('Something after') { steps {echo "something something" } } Some help would be appreciated.Thanks,Frederico PS: I've tried with manually triggered builds, timer triggered, and SCM, all produce the same issue if triggered at the same time.
Add Comment
[JIRA] (JENKINS-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title
Frederico Pratas edited a comment on JENKINS-55248
Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time
Hi,Any update on this one?I get a similar issue on my setup.I've several independent pipeline jobs.Each job, when triggered, does a p4 checkout.When multible jobs are triggered at the same time the the P4CLIENT seems to be inconsistent between jobs and some of the jobs fail because they are using the client from a different job. It seems that the P4CLIENT variable is being shared between different checkout processes.The jobs that get the wrong P4CLIENT fail with the error reported previously:ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s):Path '/correct/path/for/this/job/...' is not under client's root '/path/from/parallel/job'.Each job is using the checkout in the following manner:{{def p4_ws_name = 'jenkins_${env.JOB_NAME}'def workspace_view = """\ //my_depot/... //${p4_ws_name}/... """.stripIndent()pipeline { agent any options { timestamps() } stages { stage('Checkout') { steps {checkout perforce( credential: '', populate: autoClean( delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), workspace: manualSpec( charset: 'none', cleanup: false, name: p4_ws_name, pinHost: false, spec: clientSpec( allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: workspace_view ) )) } } stage('Something after') { steps {echo "something something" } } Some help would be appreciated.Thanks,Frederico
Add Comment
[JIRA] (JENKINS-55248) workspace mixup when 2 jobs running on 2 diff nodes at the same time
Title: Message Title
Frederico Pratas commented on JENKINS-55248
Re: workspace mixup when 2 jobs running on 2 diff nodes at the same time
Hi, Any update on this one? I get a similar issue on my setup. I've several independent pipeline jobs. Each job, when triggered, does a p4 checkout. When multible jobs are triggered at the same the the P4CLIENT seems to be inconsistent between jobs and some of the jobs fail because they are using the client from a different job. It seems that the P4CLIENT variable is being shared between different checkout processes. The jobs that get the wrong P4CLIENT fail with the error reported previously: ERROR: P4: Task Exception: hudson.AbortException: P4JAVA: Error(s): Path '/correct/path/for/this/job/...' is not under client's root '/path/from/parallel/job'. Each job is using the checkout in the following manner: {{def p4_ws_name = 'jenkins_${env.JOB_NAME}' def workspace_view = """\ //my_depot/... //${p4_ws_name}/... """.stripIndent() pipeline { agent any options { timestamps() } stages { stage('Checkout') { steps { checkout perforce( credential: '', populate: autoClean( delete: true, modtime: false, parallel: [ enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: true, replace: true, tidy: false), workspace: manualSpec( charset: 'none', cleanup: false, name: p4_ws_name, pinHost: false, spec: clientSpec( allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: workspace_view ) ) ) } } stage('Something after') { steps { echo "something something" } } } }}} Some help would be appreciated. Thanks, Frederico
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
[JIRA] (JENKINS-45388) Default admin user cannot connect to jenkins after running SetupWizard
Title: Message Title Hassaan Sohail edited a comment on JENKINS-45388 Re: Default admin user cannot connect to jenkins after running SetupWizard Same steps I use as mention above. Because I don't want to use Ubuntu and docker to build android application with multiple jobs.I am facing same issue, is there any solution or need to quit to run Jenkins in centos ? 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-45388) Default admin user cannot connect to jenkins after running SetupWizard
Title: Message Title Hassaan Sohail commented on JENKINS-45388 Re: Default admin user cannot connect to jenkins after running SetupWizard 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-45388) Default admin user cannot connect to jenkins after running SetupWizard
Title: Message Title Hassaan Sohail updated an issue Jenkins / JENKINS-45388 Default admin user cannot connect to jenkins after running SetupWizard Change By: Hassaan Sohail Attachment: 2019-01-25_16h46_19.jpg 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-45388) Default admin user cannot connect to jenkins after running SetupWizard
Title: Message Title Hassaan Sohail commented on JENKINS-45388 Re: Default admin user cannot connect to jenkins after running SetupWizard I am facing same issue, is there any solution? 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-55772) No access without Overall/Read
Title: Message Title Daniel Beck commented on JENKINS-55772 Re: No access without Overall/Read It's almost certainly a bad permissions setup. Overall/Read does not grant access to any jobs. Please provide the contents of your global config.xml and indicate which user (in which groups) sees more than they should. 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.
