[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Usama Tariq, Did you managed to create fix for this? Wisen Tanasa Please let us know once you merge the fix from Usama. 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.201336.1566200967000.4896.1585807020283%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist
Title: Message Title krishna prasad edited a comment on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Hi Boguslaw Kilmas,Yes I am already using use-repository option. so that it will select appropriate branches before the Jenkins build start .In this case I am confused since origin1 remote branch is not existing in repository as you can see in the above comments . So how this is getting populated in the parameter branch list. 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.205606.1585757549000.4893.1585806900125%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist
Title: Message Title krishna prasad updated an issue Jenkins / JENKINS-61769 git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Change By: krishna prasad Summary: git-parameter-plugin in declarative pipeline producing showing origin1 and origin as remote branches but actually did'nt exist 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.205606.1585757549000.4891.1585806060284%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches
Title: Message Title krishna prasad updated an issue Jenkins / JENKINS-61769 git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Change By: krishna prasad Priority: Minor Major 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.205606.1585757549000.4889.1585805520289%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Wisen Tanasa commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Usama Tariq https://github.com/jenkinsci/jira-trigger-plugin 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.201336.1566200967000.4879.1585804620284%40Atlassian.JIRA.
[JIRA] (JENKINS-54028) Not able to install jenkins latest war file on windows 10 getting error as plain credentials plugin 1.4 failed to load
Title: Message Title Mark Waite closed an issue as Not A Defect User configuration error that was correctly reported by Jenkins. Message tells the user that they need to install a specific plugin and the version of that plugin. Jenkins / JENKINS-54028 Not able to install jenkins latest war file on windows 10 getting error as plain credentials plugin 1.4 failed to load Change By: Mark Waite Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-22174) Can Jenkins be installed in Windows 2012 Std R2 64 bit VM Ware server
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins issue tracker is not for question and answer. Use chat channels and mailing lists for question and answer. Jenkins / JENKINS-22174 Can Jenkins be installed in Windows 2012 Std R2 64 bit VM Ware server Change By: Mark Waite Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-33850) Git auto-install not usable with Git for Windows 2.x
Title: Message Title Mark Waite updated JENKINS-33850 Jenkins / JENKINS-33850 Git auto-install not usable with Git for Windows 2.x Change By: Mark Waite Status: Fixed but Unreleased Closed 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.169327.1459177618000.4872.1585802400732%40Atlassian.JIRA.
[JIRA] (JENKINS-33850) Git auto-install not usable with Git for Windows 2.x
Title: Message Title Mark Waite updated JENKINS-33850 Zip files for MinGit are provided (as noted in the comment) on github.com. 64 bit Windows 32 bit Windows PortableGit can be downloaded as a self-extracting archive and then used to create a local zip file as well. Git for Windows is apparently not usable in that way, since PortableGit specifically exists so that the MSI installer is not required to install and configure it. Jenkins / JENKINS-33850 Git auto-install not usable with Git for Windows 2.x Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Released As: Git for WIndows 2.26.0 Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-61775) Support ARM 64 in Jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Support ARM 64 in Jenkins Change By: Mark Waite Support IBM PowerPC ARM 64 processors running Linux JVM's in the Jenkins project, including:* Agents (ssh, JNLP, WebSockets) with Java 8 Hotspot and Java 11 Hotspot* Masters with Java 8 Hotspot and Java 11 Hotspot* Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure (PowerPC and s390x) 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.205614.1585801513000.4867.1585801620358%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Support ARM 64 in Jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Support ARM 64 in Jenkins Change By: Mark Waite Epic Name: IBM PowerPC ARM 64 support 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.205614.1585801513000.4866.1585801620298%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Support ARM 64 in Jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61775 Support ARM 64 in Jenkins Change By: Mark Waite Environment: Jenkins agents (Java 8 OpenJ9 Hotspot , Java 11 OpenJ9, Java 11 Hotspot)Jenkins docker agents (Java 8 OpenJ9 Hotspot , Java 11 OpenJ9, Java 11 Hotspot)Jenkins docker master (Java 8 OpenJ9 Hotspot , Java 11 OpenJ9, Java 11 Hotspot)Jenkins master (Java 8 OpenJ9 Hotspot , Java 11 OpenJ9, Java 11 Hotspot) 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.205614.1585801513000.4865.1585801620138%40Atlassian.JIRA.
[JIRA] (JENKINS-61775) Support ARM 64 in Jenkins
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61775 Support ARM 64 in Jenkins Issue Type: Epic Assignee: Unassigned Components: core Created: 2020-04-02 04:25 Environment: Jenkins agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Labels: platform-sig Priority: Major Reporter: Mark Waite Support IBM PowerPC running Linux JVM's in the Jenkins project, including: Agents (ssh, JNLP, WebSockets) with Java 8 Hotspot and Java 11 Hotspot Masters with Java 8 Hotspot and Java 11 Hotspot Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure (PowerPC and s390x)
[JIRA] (JENKINS-61774) Support IBM PowerPC in Jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Support IBM PowerPC in Jenkins Change By: Mark Waite Support IBM s390x PowerPC running Linux JVM's in the Jenkins project, including:* Agents (ssh, JNLP, WebSockets) with Java 8 OpenJ9, Java 11 Hotspot , and Java 11 OpenJ9 Hotspot * Masters with Java 8 OpenJ9, Java 11 Hotspot , and Java 11 OpenJ9 Hotspot * Masters in Docker with Java 8 and Java 11See INFRA-2519 for the necessary infrastructure (PowerPC and s390x) 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.205613.1585800393000.4863.1585800720066%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Support IBM PowerPC in Jenkins
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61774 Support IBM PowerPC in Jenkins Change By: Mark Waite Epic Name: IBM s390x PowerPC support 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.205613.1585800393000.4862.1585800540063%40Atlassian.JIRA.
[JIRA] (JENKINS-61774) Support IBM PowerPC in Jenkins
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61774 Support IBM PowerPC in Jenkins Issue Type: Epic Assignee: Unassigned Components: core Created: 2020-04-02 04:06 Environment: Jenkins agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Labels: platform-sig Priority: Major Reporter: Mark Waite Support IBM s390x running Linux JVM's in the Jenkins project, including: Agents (ssh, JNLP, WebSockets) with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9 Masters with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9 Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure
[JIRA] (JENKINS-49362) Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-49362 Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols Change By: Mark Waite Summary: Unable Master unable to connect to GitHub using IBM JDK 8 - Unable to find acceptable protocols 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.188229.1517798676000.4858.1585799460193%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) Slave not persistent in 1.532.2 stable release
Title: Message Title Mark Waite edited a comment on JENKINS-22006 Re: Slave not persistent in 1.532.2 stable release I've been running 2.204.x on a Linux master in Docker and am now running Jenkins 2.222.1 on the same Linux master. An IBM s390x agent is connected to that Linux master. The Linux Docker master is running OpenJDK 8u242 Hotspot while the IBM s390x agent is running JDK 8u242 OpenJ9. I use that agent to build and run various tests, including:* Compile and test the Jenkins git plugin 4.x* Compile and test the Jenkins git client plugin 3x* Compile and test the Jenkins platform labeler pluginUnless there is new information on this bug report, I propose to close it. I'm also running an OpenJDK 8u242 agent on PowerPC 64 running Ubuntu. Also working very well. 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.153783.1393673328000.4851.1585798740388%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) IBM JDK agent disconnects in 1.532.2
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-22006 IBM JDK agent disconnects in 1.532.2 Change By: Mark Waite Summary: Slave not persistent IBM JDK agent disconnects in 1.532.2 stable release 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.153783.1393673328000.4853.1585798740461%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) Slave not persistent in 1.532.2 stable release
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-22006 Slave not persistent in 1.532.2 stable release Change By: Mark Waite Component/s: core Component/s: slave-setup-plugin 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.153783.1393673328000.4843.1585798620214%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) Slave not persistent in 1.532.2 stable release
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-22006 Slave not persistent in 1.532.2 stable release Change By: Mark Waite Assignee: Kohsuke Kawaguchi Mark Waite 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.153783.1393673328000.4838.1585798560272%40Atlassian.JIRA.
[JIRA] (JENKINS-22006) Slave not persistent in 1.532.2 stable release
Title: Message Title Mark Waite commented on JENKINS-22006 Re: Slave not persistent in 1.532.2 stable release I've been running 2.204.x on a Linux master in Docker and am now running Jenkins 2.222.1 on the same Linux master. An IBM s390x agent is connected to that Linux master. The Linux Docker master is running OpenJDK 8u242 Hotspot while the IBM s390x agent is running JDK 8u242 OpenJ9. I use that agent to build and run various tests, including: Compile and test the Jenkins git plugin 4.x Compile and test the Jenkins git client plugin 3x Compile and test the Jenkins platform labeler plugin Unless there is new information on this bug report, I propose to close it. 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.153783.1393673328000.4832.1585798500250%40Atlassian.JIRA.
[JIRA] (JENKINS-61773) Support IBM s390x in Jenkins
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61773 Support IBM s390x in Jenkins Issue Type: Epic Assignee: Unassigned Components: core Created: 2020-04-02 03:27 Environment: Jenkins agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker agents (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins docker master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Jenkins master (Java 8 OpenJ9, Java 11 OpenJ9, Java 11 Hotspot) Labels: platform-sig Priority: Major Reporter: Mark Waite Support IBM s390x running Linux JVM's in the Jenkins project, including: Agents (ssh, JNLP, WebSockets) with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9 Masters with Java 8 OpenJ9, Java 11 Hotspot, and Java 11 OpenJ9 Masters in Docker with Java 8 and Java 11 See INFRA-2519 for the necessary infrastructure
[JIRA] (JENKINS-56679) SecurityException when trying to run a maven job with OpenJ9 JVM
Title: Message Title Mark Waite closed an issue as Won't Do Jenkins will never support Java 12. Current support includes Java 8 and Java 11. The next Java release to be supported will be coordinated by the Platform Special Interest Group and will likely not happen until the next Java LTS release. Upcoming plans for Java support are likely to be discussed in one of the April 2020 Platform SIG meetings. OpenJ9 is already being used to run a Jenkins agent on s390x running Ubuntu Linux. It is also used to compile and test the Jenkins platform labeler plugin, the git client plugin, and the git plugin. Work is in progress through INFRA-2519 to add s390x infrastructure to ci.jenkins.io. When that is added, then OpenJ9 on JDK 8 and JDK 11 will be available for core PR's and plugin PR's. Jenkins / JENKINS-56679 SecurityException when trying to run a maven job with OpenJ9 JVM Change By: Mark Waite Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-52785) Multi Architecture Docker image
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-52785
Multi Architecture Docker image
Change By:
Mark Waite
Jenkins Docker image available currently *jenkins/jenkins:lts* isn't multi architecture. On x86 it works perfectly well but on platforms like s390x , ppc64 it isn't supported.Can we make the jenkins image multi-arch ? What would it take to add Docker image support for s390x ?*Current Problem:*{noformat}docker run --name jenkins_s390x -P jenkins/jenkins:lts standard_init_linux.go:185: exec user process caused "exec format error" {noformat}However, if i clone jenkinsci/docker and then do a "docker build " and run , it works fine (check attachment for the same).So we will need a mechanism to run the docker build on the platform and then push the image to the repository. Refer to conversations and progress reports in the [Platform Special Interest Group|https://docs.google.com/document/d/1bDfUdtjpwoX0HO2PRnfqns_TROBOK8tmP6SgVhubr2Y/edit] where s390x progress is regularly being reported. One or more pull requests are in progress, along with hardware provided to the Jenkins project for connection to ci.jenkins.io.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches
Title: Message Title krishna prasad commented on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Hi Boguslaw Kilmas, Yes I am already using use-repository option. 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.205606.1585757549000.4814.1585792980282%40Atlassian.JIRA.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the [^config.xml] you uploaded with the [config.xml of my test job|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-61515-using-JENKINS-26100-repo/config.xml]. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references [my bug check repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-26100-declarative-skipDefaultCheckout]. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access to a repository on your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat}#!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.There is another possible difference between the job you're running and the job that I'm running. [ My Jenkinsfile |https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] is probably different from yours. I would hope that whatever differences there are between those two files, they would be irrelevant to this case. However, you might experiment with a variant of [my Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] in your environment, just to see if the contents of my Jenkinsfile make polling work, while yours does not.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the [^config.xml] you uploaded with the [config.xml of my test job|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-61515-using-JENKINS-26100-repo/config.xml]. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references [my bug check repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-26100-declarative-skipDefaultCheckout]. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and to a git server that is repository on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat}#!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.There is another possible difference between the job you're running and the job that I'm running. My Jenkinsfile is probably different from yours. I would hope that whatever differences there are between those two files, they would be irrelevant to this case. However, you might experiment with a variant of [my Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] in your environment, just to see if the contents of my Jenkinsfile make polling work, while yours does not.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the [^ config.xml ] you uploaded with the [config.xml of my test job|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-61515-using-JENKINS-26100-repo/config.xml]. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references [my bug check repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-26100-declarative-skipDefaultCheckout]. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and a git server that is on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat}#!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.There is another possible difference between the job you're running and the job that I'm running. My Jenkinsfile is probably different from yours. I would hope that whatever differences there are between those two files, they would be irrelevant to this case. However, you might experiment with a variant of [my Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] in your environment, just to see if the contents of my Jenkinsfile make polling work, while yours does not.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the config.xml you uploaded with the [ config.xml of my test job |https://github . com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-61515-using-JENKINS-26100-repo/config.xml]. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references [my bug check repository| https://github.com/MarkEWaite/jenkins . - bugs /tree/JENKINS-26100-declarative-skipDefaultCheckout] . I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and a git server that is on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat}#!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.There is another possible difference between the job you're running and the job that I'm running. My Jenkinsfile is probably different from yours. I would hope that whatever differences there are between those two files, they would be irrelevant to this case. However, you might experiment with a variant of [my Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] in your environment, just to see if the contents of my Jenkinsfile make polling work, while yours does not.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the config.xml you uploaded with the config.xml of my test job. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references https://github.com/MarkEWaite/jenkins.bugs. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and a git server that is on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat}#!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider. There is another possible difference between the job you're running and the job that I'm running. My Jenkinsfile is probably different from yours. I would hope that whatever differences there are between those two files, they would be irrelevant to this case. However, you might experiment with a variant of [my Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-26100-declarative-skipDefaultCheckout/Jenkinsfile] in your environment, just to see if the contents of my Jenkinsfile make polling work, while yours does not.
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title
Mark Waite edited a comment on JENKINS-61515
Re: Git SCM polling fails with skipDefaultCheckout() in pipeline
I'm unable to duplicate the problem, even with your config.xml file.I compared the config.xml you uploaded with the config.xml of my test job. The differences included:* Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling* Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant* Your config.xml references /path/to/my/repository.git. My config.xml references https://github.com/MarkEWaite/jenkins.bugs. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and a git server that is on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the masterBased on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected.I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the {{hooks}} directory of that repository, I have an executable script named {{post-receive}} like this:{noformat} I #!/bin/bashcurl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="">{noformat}That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "[polling must die|https://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/]". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.
Add Comment
[JIRA] (JENKINS-61515) Git SCM polling fails with skipDefaultCheckout() in pipeline
Title: Message Title Mark Waite commented on JENKINS-61515 Re: Git SCM polling fails with skipDefaultCheckout() in pipeline I'm unable to duplicate the problem, even with your config.xml file. I compared the config.xml you uploaded with the config.xml of my test job. The differences included: Your config.xml polls every minute. Mine is configured with polling but with no schedule so that the job will respond to notifyCommit without wasting the effort polling Your config.xml file is XML 1.0, mine is 1.1. That difference should be irrelevant Your config.xml references /path/to/my/repository.git. My config.xml references https://github.com/MarkEWaite/jenkins.bugs. I'm using a network based git server and I assume you are also using a network based git server. If instead you are using file system access and a git server that is on the same computer as your Jenkins server, you might try using a network protocol to access the git repository rather than file system access. I rarely test direct file system access to git repositories because it would limit jobs to only run on the master Based on the differences between my config.xml and yours, I configured my job to poll every minute. I committed a change to the repository, waited one minute, and confirmed that the change was detected and the job ran. I committed two changes to the repository, waited for the next polling, and confirmed that the changes were detected and the job ran. I committed three changes to the repository, waited for the next poll, and confirmed the changes were detected. I also confirmed that if I use a notifyCommit hook in the central git repository to alert the Jenkins server that it should poll, the changes are detected as soon as they are applied, without the overhead of polling once a minute. My central git repository is a small computer hosting ssh based git repositories. In the hooks directory of that repository, I have an executable script named post-receive like this: I#!/bin/bash curl -s http://mark-pc2.markwaite.net/git/notifyCommit?url="" That script is automatically executed by git each time a commit arrives at that repository. That script is an example of the concept that Kohsuke Kawaguchi described in his blog post, "polling must die". It may be worth experimenting with notifyCommit to avoid the overhead of polling and the delay of polling. Alternately, if you're using a git hosting system like GitHub, Bitbucket, GitLab, or Gitea, they offer web hooks which can do the same thing. The web hooks are often managed by Jenkins plugins focused on the specific provider.
[JIRA] (JENKINS-38699) Confine git commands to workspace directory
Title: Message Title
Mark R edited a comment on JENKINS-38699
Re: Confine git commands to workspace directory
Looks like a good feature. We ran into this because we have a git mechanism that backs up job config.xmls, nextBuildNumber, and a few other files to git nightly. Every now and then a pipeline jobs git gets corrupted somehow (not sure how) and it picks up the git workspace at the root jobs level. This causes it to checkout git at the root jobs level and causes problems.The workaround of setting the GIT_CEILING_DIRECTORIES worked though we did find it is case sensitive (we set to home ${HOME} /jobs).
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.175097.1475592084000.4778.1585780020221%40Atlassian.JIRA.
[JIRA] (JENKINS-38699) Confine git commands to workspace directory
Title: Message Title
Mark R commented on JENKINS-38699
Re: Confine git commands to workspace directory
Yes we set it to ${HOME}/jobs. I was wondering where workspace came from.
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.175097.1475592084000.4775.1585779960142%40Atlassian.JIRA.
[JIRA] (JENKINS-38699) Confine git commands to workspace directory
Title: Message Title Mark R edited a comment on JENKINS-38699 Re: Confine git commands to workspace directory Looks like a good feature. We ran into this because we have a git mechanism that backs up job config.xmls, nextBuildNumber, and a few other files to git nightly. Every now and then a pipeline jobs git gets corrupted somehow (not sure how) and it picks up the git workspace at the root jobs level. This causes it to checkout git at the root jobs level and causes problems.The workaround of setting the GIT_CEILING_DIRECTORIES worked though we did find it is case sensitive (we set to home/jobs) . 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.175097.1475592084000.4772.1585779900175%40Atlassian.JIRA.
[JIRA] (JENKINS-59069) Security Issue in latest version
Title: Message Title Matthias Doering commented on JENKINS-59069 Re: Security Issue in latest version Wadeck Follonier Do you know something about the planned time for the release? 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.201451.1566719982000.4758.1585777200283%40Atlassian.JIRA.
[JIRA] (JENKINS-45231) Windows Slave fails to start with error errorCode: 0x8001FFFF
Title: Message Title Paul Clark commented on JENKINS-45231 Re: Windows Slave fails to start with error errorCode: 0x8001 Did you get this to work somehow? 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.183362.1498822494000.4755.1585776900348%40Atlassian.JIRA.
[JIRA] (JENKINS-61154) Pipeline: Groovy 2.79 does not abort the build if a pipeline stage fails
Title: Message Title Liam Reimers updated JENKINS-61154 Cannot reproduce with 2.80. Jenkins / JENKINS-61154 Pipeline: Groovy 2.79 does not abort the build if a pipeline stage fails Change By: Liam Reimers Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-61281) Render matrixes better in Blue Ocean
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61281 Render matrixes better in Blue Ocean Change By: Stefan Drissen Priority: Minor Major 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.204856.1582989094000.4749.1585775460254%40Atlassian.JIRA.
[JIRA] (JENKINS-61281) Render matrixes better in Blue Ocean
Title: Message Title Stefan Drissen commented on JENKINS-61281 Re: Render matrixes better in Blue Ocean Just in case anyone is wondering how bad the user experience of the matrix pipeline is, it currently (2.226) looks like this: If you hover over the matrix steps then a tooltip indicating the axis values pops up. IMHO this is not a minor issue (changed prio to major) 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.204856.1582989094000.4751.1585775460286%40Atlassian.JIRA.
[JIRA] (JENKINS-61281) Render matrixes better in Blue Ocean
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61281 Render matrixes better in Blue Ocean Change By: Stefan Drissen Attachment: image-2020-04-01-23-00-41-772.png 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.204856.1582989094000.4747.1585774860178%40Atlassian.JIRA.
[JIRA] (JENKINS-52391) Restarting Parallel Stages
Title: Message Title Joan Touzet commented on JENKINS-52391 Re: Restarting Parallel Stages Gabriel Herisanu This bug is about declarative language features - see the Epic Link and Sprint tagging above. Your suggestion isn't declarative. 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.192185.1530793849000.4720.1585774560631%40Atlassian.JIRA.
[JIRA] (JENKINS-61771) Local Maven repository default path not working
Title: Message Title
Manuel Gonzalez created an issue
Jenkins / JENKINS-61771
Local Maven repository default path not working
Issue Type:
Bug
Assignee:
Unassigned
Components:
maven-plugin
Created:
2020-04-01 20:31
Environment:
Jenkins Version: 2.176.3.2 Maven plugin version 3.4 (Maven Integration plugin)
Priority:
Minor
Reporter:
Manuel Gonzalez
The maven dependencies are not being downloaded to the default ~/m2/repository location when this option is setup to default. Instead, the local repository is sent to the workspace folder "jenkins_home/workspace/job_name/". The only way to avoid this was setting the path in the setting.xml file, although this was not an option as this would only resolve for Windows or Linux agents, and therefore the local repository path was set to ${user.home}/.m2/repository, which is resolved by Maven as: Windows OS: C:/Users//.m2/repository Linux OS: /home//.m2/repository
Add Comment
[JIRA] (JENKINS-61772) Multibranch pipeline cannot be disabled in GUI, only in config.xml
Title: Message Title Jaroslav Lhotak created an issue Jenkins / JENKINS-61772 Multibranch pipeline cannot be disabled in GUI, only in config.xml Issue Type: Improvement Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-04-01 20:31 Environment: Jenkins ver. 2.204.1 (in official docker LTS image) Pipeline: Multibranch ver 2.21 Oracle OpenJDK Runtime Environment 1.8.0_232 CentOS Linux release 7.6.1810 (Core) Priority: Major Reporter: Jaroslav Lhotak It would be great to let users disable/enable multibranch pipeline job, similarly as onther jobs. Especially if the logic is there already and working. If I manually edit the config.xml and set true the job can't be executed, but it does not indicate that's disabled - this should be rated as a bug actually. Thank you for hearing us! Add Comment
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Oleg Nenashev commented on JENKINS-61480 Re: Dark Theme It might be easier to just poll all CSS files from GitHub: https://github.com/search?q=org%3Ajenkinsci+extension%3Acss=Code 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.205164.1584202104000.4712.1585773060384%40Atlassian.JIRA.
[JIRA] (JENKINS-59257) [Git publisher error] Tag to push name could not aware jenkins variable
Title: Message Title
Boguslaw Klimas commented on JENKINS-59257
Re: [Git publisher error] Tag to push name could not aware jenkins variable
Hi I'am not sure if this issue is reported in good component. But when it comes to way to use variables, please look at a small example
echo '$S1_$S2: '$S1_$S2
echo '${S1}_${S2}: '${S1}_${S2}
output:
[Test] $ /bin/sh -xe /tmp/jenkins502055521052004613.sh
+ echo $S1_$S2: CDE
$S1_$S2: CDE
+ echo ${S1}_${S2}: XYZ_CDE
${S1}_${S2}: XYZ_CDE
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.201724.1567745391000.4709.1585771860142%40Atlassian.JIRA.
[JIRA] (JENKINS-38699) Confine git commands to workspace directory
Title: Message Title
David Bouman commented on JENKINS-38699
Re: Confine git commands to workspace directory
Given this issue was reported almost four years ago, I no longer understand why I suggested ${HOME}/workspace as a good value for GIT_CEILING_DIRECTORIES. In its current version (2.229) Jenkins's home directory does not contain a workspace subdirectory. Perhaps some previous version had a different directory layout, but now it would seem saner to set GIT_CEILING_DIRECTORIES to ${HOME}/jobs.
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.175097.1475592084000.4705.1585770180159%40Atlassian.JIRA.
[JIRA] (JENKINS-48578) Create BOM for components included into the Core
Title: Message Title Daniel Beck commented on JENKINS-48578 Re: Create BOM for components included into the Core James Nord If you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146 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.187218.151334614.4699.1585770120670%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61279 Update version number dependency to 1.7 Change By: Daniel Beck Issue Type: New Feature Improvement 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.204854.1582987621000.4701.1585770120696%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Daniel Beck commented on JENKINS-61279 Re: Update version number dependency to 1.7 Tim JacombIf you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146 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.204854.1582987621000.4703.1585770120720%40Atlassian.JIRA.
[JIRA] (JENKINS-48578) Create BOM for components included into the Core
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-48578 Create BOM for components included into the Core Change By: Daniel Beck Labels: lts-candidate 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.187218.151334614.4682.158577417%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi edited a comment on JENKINS-61480 Re: Dark Theme So I'm working on it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this: !regex.png| width=488,height=413, thumbnail!How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? [~oleg_nenashev], [~fqueiruga]By the way, the current design looks like this !dark.png|width=981,height=484! 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.205164.1584202104000.4679.1585769700183%40Atlassian.JIRA.
[JIRA] (JENKINS-41690) JiraProjectProperty.setSites() doesn't set sites, it adds them (resulting in duplicate sites)
Title: Message Title Radek Antoniuk closed an issue as Fixed Fixed via https://github.com/jenkinsci/jira-plugin/pull/168 Jenkins / JENKINS-41690 JiraProjectProperty.setSites() doesn't set sites, it adds them (resulting in duplicate sites) Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed 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
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: regex.png 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.205164.1584202104000.4676.1585769642685%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi edited a comment on JENKINS-61480 Re: Dark Theme So I'm working on it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this: !regex.png|width= 685 488 ,height= 539 413,thumbnail !How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? [~oleg_nenashev], [~fqueiruga]By the way, the current design looks like this !dark.png|width=981,height=484! 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.205164.1584202104000.4673.1585769642075%40Atlassian.JIRA.
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi updated an issue Jenkins / JENKINS-61480 Dark Theme Change By: Gábor Tasnádi Attachment: regex.png 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.205164.1584202104000.4666.1585769640796%40Atlassian.JIRA.
[JIRA] (JENKINS-5711) Ability to send user credentials in header
Title: Message Title Radek Antoniuk closed an issue as Won't Do No interest for 10 years, I think we can close it. Jenkins / JENKINS-5711 Ability to send user credentials in header Change By: Radek Antoniuk Status: Open Closed Resolution: Won't Do 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
[JIRA] (JENKINS-61480) Dark Theme
Title: Message Title Gábor Tasnádi edited a comment on JENKINS-61480 Re: Dark Theme So I'm working on it and thought it would be nice for it to be compatible with whoever wants his plugin to be compatible with it. I made a regex that can find css colors in a file and replace it with another color like this: !regex.png|width=685,height=539!How I imagined it would get all css files that being rendered on a page, search it in the static resources, make a copy with substituted colors and re-link them in the header. But now I got kinda stuck on how could it get all css links on a currently rendered page, first thought was I should get the StaplerResponse and crawl it from the html response, but it doesn't have a body. Any suggestions guys? [~oleg_nenashev], [~fqueiruga]By the way, the current design looks like this !dark.png|width=981,height=484! 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.205164.1584202104000.4661.1585769460173%40Atlassian.JIRA.
[JIRA] (JENKINS-2792) Support for HTTP basic authentication on Jira server
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-2792 Support for HTTP basic authentication on Jira server Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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.132865.1231247935000.4654.1585769160547%40Atlassian.JIRA.
[JIRA] (JENKINS-13364) Can Not Change JIRA Password
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-13364 Can Not Change JIRA Password Change By: Radek Antoniuk Status: Reopened Closed Resolution: Not A Defect 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.143828.1333648541000.4643.1585769100801%40Atlassian.JIRA.
[JIRA] (JENKINS-42803) Configuring two jira instances fails
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce I believe this is working in the current version, feel free to open a new issue with version details if that is still happening. Jenkins / JENKINS-42803 Configuring two jira instances fails Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-44378) dockerPushStep in Artifactory plugin conflicts with Jira plugin over Jersey implementation
Title: Message Title Radek Antoniuk closed an issue as Fixed Since that report a lot of dependencies were updated, feel free to open an issue if that still happens with the current version or even better a Pull Request addressing it Jenkins / JENKINS-44378 dockerPushStep in Artifactory plugin conflicts with Jira plugin over Jersey implementation Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed 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
[JIRA] (JENKINS-20389) Merge commits trigger uneccessary builds when Include/Exclude regions are defined
Title: Message Title Giannis Sialmas commented on JENKINS-20389 Re: Merge commits trigger uneccessary builds when Include/Exclude regions are defined Karl Shultz is there any update on this? A lot of people are working with monorepos, myself included, which causes a lot of unwanted builds from this issue. 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.151909.1383332931000.4617.1585768980793%40Atlassian.JIRA.
[JIRA] (JENKINS-45724) Fails to authenticate
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce I believe this was a configuration error, feel free to open a new issue with the current version if that still applies. Jenkins / JENKINS-45724 Fails to authenticate Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-44971) Error when update a JIRA Issue
Title: Message Title Radek Antoniuk closed an issue as Fixed Jenkins / JENKINS-44971 Error when update a JIRA Issue Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed 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.183054.1497882239000.4613.1585768860501%40Atlassian.JIRA.
[JIRA] (JENKINS-48609) Unable to query JIRA
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-48609 Unable to query JIRA Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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.187257.1513615676000.4609.1585768800234%40Atlassian.JIRA.
[JIRA] (JENKINS-46695) NullPointer Exception and possible downstream pipeline issue
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-46695 NullPointer Exception and possible downstream pipeline issue Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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.185038.1504736204000.4607.1585768740177%40Atlassian.JIRA.
[JIRA] (JENKINS-48878) if user is deleted what happens for the issues
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-48878 if user is deleted what happens for the issues Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect 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.187673.1515582421000.4603.1585768680361%40Atlassian.JIRA.
[JIRA] (JENKINS-48876) Inprogress Stories from current sprint when closed in future sprint. Will the story points be credited to sprint where stories were burned or into the original sprint where it w
Title: Message Title Radek Antoniuk closed an issue as Not A Defect Jenkins / JENKINS-48876 Inprogress Stories from current sprint when closed in future sprint. Will the story points be credited to sprint where stories were burned or into the original sprint where it was created Change By: Radek Antoniuk Status: Open Closed Resolution: Not A Defect 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.187671.1515582347000.4605.1585768680404%40Atlassian.JIRA.
[JIRA] (JENKINS-56417) Jenkins cannot release Jira version 'No content to map to Object due to end of input'
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-56417 Jenkins cannot release Jira version 'No content to map to Object due to end of input' Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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.198008.1551797348000.4596.1585768621577%40Atlassian.JIRA.
[JIRA] (JENKINS-55982) JIRA Plugin does not respect proxy in some requests
Title: Message Title Radek Antoniuk closed an issue as Incomplete Reporter timeout. Jenkins / JENKINS-55982 JIRA Plugin does not respect proxy in some requests Change By: Radek Antoniuk Status: Open Closed Resolution: Incomplete 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
[JIRA] (JENKINS-54486) Not created JIRA issue after build failed
Title: Message Title Radek Antoniuk closed an issue as Cannot Reproduce Jenkins / JENKINS-54486 Not created JIRA issue after build failed Change By: Radek Antoniuk Status: Open Closed Resolution: Cannot Reproduce 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.195256.1541502017000.4600.1585768621688%40Atlassian.JIRA.
[JIRA] (JENKINS-57004) Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED
Title: Message Title Radek Antoniuk commented on JENKINS-57004 Re: Error with jira plugin: Request cannot be executed; I/O reactor status: STOPPED Alexey Grigorov in 3.0.12 there were quite big changes to the Java Client used, can you give it a shot with the current version? 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.198705.1555286407000.4594.1585768560118%40Atlassian.JIRA.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated JENKINS-57619 Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Status: Fixed but Unreleased Closed 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.199547.1558546618000.4592.1585768500372%40Atlassian.JIRA.
[JIRA] (JENKINS-57619) Unable to find valid certification path
Title: Message Title Radek Antoniuk updated JENKINS-57619 Jenkins / JENKINS-57619 Unable to find valid certification path Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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.199547.1558546618000.4590.1585768500332%40Atlassian.JIRA.
[JIRA] (JENKINS-61244) Jira issue: getting error while assigning issue to a assginee
Title: Message Title Radek Antoniuk updated JENKINS-61244 Jenkins / JENKINS-61244 Jira issue: getting error while assigning issue to a assginee Change By: Radek Antoniuk Status: Fixed but Unreleased Closed 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.204810.1582747506000.4587.1585768320571%40Atlassian.JIRA.
[JIRA] (JENKINS-61244) Jira issue: getting error while assigning issue to a assginee
Title: Message Title Radek Antoniuk updated JENKINS-61244 No version information was provided, so I'm assuming this was fixed in 3.0.12. https://github.com/jenkinsci/jira-plugin/releases/tag/3.0.12 Jenkins / JENKINS-61244 Jira issue: getting error while assigning issue to a assginee Change By: Radek Antoniuk Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-61361) Replace "accountId" workaround when jira-rest-java-client is updated
Title: Message Title Radek Antoniuk commented on JENKINS-61361 Re: Replace "accountId" workaround when jira-rest-java-client is updated Stefan Cordes would you mind creating a Pull Request for this so that it just sits and waits for the needed dependencies? that would be really helpful, thank you! 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.205013.1583485957000.4582.1585768080131%40Atlassian.JIRA.
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Radek Antoniuk commented on JENKINS-61661 Re: Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Andreas Nusser indeed that makes sense, would you like to give it a shot and contribute with a Pull Request to add a logger? 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.205393.1585048689000.4580.1585768020117%40Atlassian.JIRA.
[JIRA] (JENKINS-57500) Update outdated dependencies
Title: Message Title Radek Antoniuk closed an issue as Fixed Jenkins / JENKINS-57500 Update outdated dependencies Change By: Radek Antoniuk Status: Open Closed Resolution: Fixed 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.199363.1557993399000.4578.1585767780267%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches
Title: Message Title Boguslaw Klimas commented on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Hi, Are you try used 'use-repository' option? https://github.com/jenkinsci/git-parameter-plugin#use-repository 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.205606.1585757549000.4556.1585766220213%40Atlassian.JIRA.
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title
Shivaji Thanneeru updated an issue
Jenkins / JENKINS-61762
Intermittent Socket closed or Read timed out error
Change By:
Shivaji Thanneeru
jiraEditIssue, jiraNewIssue and jiraJqlSearch are some time failing with "Socket Closed" or "Read timed out" error. {code:java}JIRA: Site - JIRA-PROD - Updating issue: Ticket-1234Error Code: -1Error Message: Socket closed[Pipeline] }[Pipeline] // scriptError when executing always post condition:hudson.AbortException: Socket closed at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.EditIssueStep$Execution.run(EditIssueStep.java:80){code} {code:java}JIRA: Site - JIRA-PROD - Creating new issue: IssueInput(update=null, fields={project={key=REI}, summary=Build Error., description=New JIRA Created from Jenkins., issuetype={name=Bug}})Error Code: -1Error Message: Socket closed[Pipeline] }[Pipeline] // scriptError when executing regression post condition:hudson.AbortException: Socket closed at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:84) at org.thoughtslive.jenkins.plugins.jira.steps.NewIssueStep$Execution.run(NewIssueStep.java:53) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code} {code:java}JIRA: Site - JIRA-PROD - Search JQL: project = "Release Engineering Internal" AND description ~ "New JIRA Created from Jenkins" ORDER BY id DESC startAt: 0 maxResults: 1Error Code: -1Error Message: Read timed out[Pipeline] }[Pipeline] // scriptError when executing failure post condition:hudson.AbortException: Read timed out at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:89) at org.thoughtslive.jenkins.plugins.jira.steps.JqlSearchStep$Execution.run(JqlSearchStep.java:65) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}
[JIRA] (JENKINS-61762) Intermittent Socket closed or Read timed out error
Title: Message Title Shivaji Thanneeru updated an issue Jenkins / JENKINS-61762 Intermittent Socket closed or Read timed out error Change By: Shivaji Thanneeru Summary: Intermittent Socket closed or Read timed out error 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.205599.1585716788000.4552.1585765560235%40Atlassian.JIRA.
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title Ulli Hafner updated JENKINS-61768 I noticed that as well a couple of days ago. In https://github.com/jenkinsci/analysis-model/pull/336 I removed the transitive dependency to SLF4J 1.8. Jenkins / JENKINS-61768 plugin bundles slf4j-api causing no test output for plugins that depend on it. Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-61768) plugin bundles slf4j-api causing no test output for plugins that depend on it.
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-61768 plugin bundles slf4j-api causing no test output for plugins that depend on it. Change By: Ulli Hafner Component/s: analysis-model Component/s: analysis-model-api-plugin URL: https://github.com/jenkinsci/analysis-model/pull/336 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.205605.1585754769000.4548.1585764960114%40Atlassian.JIRA.
[JIRA] (JENKINS-61770) Directive-Generator Omits "Extensible Choice" Parameter
Title: Message Title Tim Black created an issue Jenkins / JENKINS-61770 Directive-Generator Omits "Extensible Choice" Parameter Issue Type: Improvement Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 2020-04-01 18:10 Environment: Jenkins ver. 2.190.3 Extensible Choice 1.6.0 Extended Choice 0.78 Priority: Major Reporter: Tim Black Directive-Generator on my Jenkins instance includes "Extended Choice" and other param types just fine, but does not include "Extensible Choice" Parameter type. Is this a documentation omission, or does Extensible Choice not support pipeline (declarative)? If it doesn't support declarative pipeline and this is the reason it's not in directive generator, I would like to see a reference to the scripted pipeline syntax somewhere in the documentation. Add Comment
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite edited a comment on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
A declarative pipeline with {{skipDefaultCheckout} } and the first step as {{checkout scm}} is the same as not declaring {{skipDefaultCheckout}} and not specifying {{checkout scm}} as the first step.
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.205560.1585492427000.4527.1585763460213%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite commented on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
A declarative pipeline with skipDefaultCheckout} and the first step as {{checkout scm is the same as not declaring skipDefaultCheckout and not specifying checkout scm as the first step.
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.205560.1585492427000.4525.1585763460185%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated JENKINS-30182 Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Status: Fixed but Unreleased Resolved 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.164765.1440703818000.4514.1585763401118%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: Fixed but Unreleased Resolved 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.190437.1525450293000.4516.1585763401206%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title Brian J Murrell commented on JENKINS-61732 Re: additional refspecs at the organisational level is unworkable OK. So then, is using a "bare" checkout command effectively do the same thing as not specifying skipDefaultCheckout? 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.205560.1585492427000.4508.1585763160116%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30182 view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column Change By: Jesse Glick Released As: 2.2 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.164765.1440703818000.4500.1585762381140%40Atlassian.JIRA.
[JIRA] (JENKINS-51143) List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-51143 Jenkins / JENKINS-51143 List view section: Job Statuses Filter on disabled doesn't work for pipeline jobs Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 2.2 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.190437.1525450293000.4498.1585762381096%40Atlassian.JIRA.
[JIRA] (JENKINS-61732) additional refspecs at the organisational level is unworkable
Title: Message Title
Mark Waite edited a comment on JENKINS-61732
Re: additional refspecs at the organisational level is unworkable
[~brianjmurrell] There are several sample jobs like [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-42860/Jenkinsfile], [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/master/Jenkinsfile], and [this one|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-52844/Jenkinsfile] which show techniques like echoing the values of parts of the scm object to see them. Since the default checkout settings are defined in the multibranch pipeline job itself, the {{scm}} object is the best way to find them. Many of my multibranch pipeline jobs define a reference repository and declare that the checkout should honor the refsepec in checkout. Others do not.
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.205560.1585492427000.4486.1585762260169%40Atlassian.JIRA.
[JIRA] (JENKINS-61601) Unable to trigger job on deletion of branch when configured with job DSL.
Title: Message Title Levi Blaney commented on JENKINS-61601 Re: Unable to trigger job on deletion of branch when configured with job DSL. Adding the include filter to our JobDSL did put it in the config.xml and the plugin is now working perfectly Aytunc BEKEN, I will ping Neha Singh and have her close this issue =) Thanks! 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.205299.1584706587000.4489.1585762260214%40Atlassian.JIRA.
[JIRA] (JENKINS-30182) view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Title: Message Title
Jesse Glick updated JENKINS-30182
Not sure about the rest, but the {{java.lang.ClassCastException: hudson.views.BuildFilterColumn$JobWrapper cannot be cast to hudson.model.TopLevelItem at jenkins.model.Jenkins.getRootDirFor(Jenkins.java:306)}} should have been fixed by PR 17 (was causing a test failures when updating the Jenkins baseline).
Jenkins / JENKINS-30182
view-job-filters plugin, parameterized jobs filter, does not work. exceptions thrown from build filter (wrapper) column
Change By:
Jesse Glick
Status:
Open Fixed but Unreleased
Assignee:
Jacob Robertson Jesse Glick
Resolution:
Fixed
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Labels: folders 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.20.1564983968000.4477.1585762080188%40Atlassian.JIRA.
[JIRA] (JENKINS-58801) Enable filter View by type "Folder"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58801 Enable filter View by type "Folder" Change By: Jesse Glick Component/s: cloudbees-folder-plugin 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.20.1564983968000.4474.1585762020186%40Atlassian.JIRA.
[JIRA] (JENKINS-56813) Job filter: exclude disabled jobs does not work
Title: Message Title Jesse Glick resolved as Not A Defect To create a view showing all enabled jobs, add a Job Statuses Filter with Disabled checked and select Include Unmatched - Add jobs that don't match this filter. Do not select jobs or check the regular _expression_ filter option. Or you can use the core built-in filter without using this plugin. See JENKINS-51143 for a fuller explanation. Using a GUI to define a boolean predicate is not great, and the particular way this is handled in Jenkins list views is especially confusing. Jenkins / JENKINS-56813 Job filter: exclude disabled jobs does not work Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
