[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Daniel Gront updated JENKINS-55836 Jenkins / JENKINS-55836 Unable to delete workspace due to locked git .pack file Change By: Daniel Gront Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.6640.1566361323995%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Daniel Gront edited a comment on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Hey [~manishchristian], our release process takes some time in order to ensure that everything works correctly and no bugs are found. We are hoping to release a stable version in October. I am moving this issue to fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.6617.1566361323633%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Daniel Gront commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Hey Manish Christian, our release process takes some time in order to ensure that everything works correctly and no bugs are found. We are hoping to release a stable version in October. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.6594.1566361260778%40Atlassian.JIRA.
[JIRA] (JENKINS-59020) Fix java.io.NotSerializableException: JiraDeploymentInfoResponse
Title: Message Title Rafal Myslek started work on JENKINS-59020 Change By: Rafal Myslek Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201374.1566358243000.6590.1566361140166%40Atlassian.JIRA.
[JIRA] (JENKINS-59020) Fix java.io.NotSerializableException: JiraDeploymentInfoResponse
Title: Message Title Rafal Myslek updated JENKINS-59020 Jenkins / JENKINS-59020 Fix java.io.NotSerializableException: JiraDeploymentInfoResponse Change By: Rafal Myslek Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201374.1566358243000.6591.1566361140210%40Atlassian.JIRA.
[JIRA] (JENKINS-59008) Merge before build, reference is not a tree on second build
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59008 Merge before build, reference is not a tree on second build Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201360.1566299152000.6588.1566358920214%40Atlassian.JIRA.
[JIRA] (JENKINS-59008) Merge before build, reference is not a tree on second build
Title: Message Title Mark Waite commented on JENKINS-59008 Re: Merge before build, reference is not a tree on second build I don't know how to duplicate the conditions you're seeing. Refer to the JENKINS-51638 verification job and its contributor branch in the JENKINS-51638-project-1 branch for an example of what I've attempted. Does the "branches to build" need to be a tag? Does it behave differently if you use a branch instead of a tag? My test case did not attempt to use a tag, just two branches. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201360.1566299152000.6586.1566358920183%40Atlassian.JIRA.
[JIRA] (JENKINS-59020) Fix java.io.NotSerializableException: JiraDeploymentInfoResponse
Title: Message Title Rafal Myslek created an issue Jenkins / JENKINS-59020 Fix java.io.NotSerializableException: JiraDeploymentInfoResponse Issue Type: Bug Assignee: Rafal Myslek Components: atlassian-jira-software-cloud-plugin Created: 2019-08-21 03:30 Priority: Minor Reporter: Rafal Myslek The following issue has been reported regarding the jiraSendDeploymentInfoStep: Caused: java.io.NotSerializableException: com.atlassian.jira.cloud.jenkins.deploymentinfo.service.JiraDeploymentInfoResponseCaused: java.io.NotSerializableException: com.atlassian.jira.cloud.jenkins.deploymentinfo.service.JiraDeploymentInfoResponse at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:926) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:920) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1082) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:1040) ... The underlying root cause seems to be the fact that the step return is not serializable (doesn't implement the Serializable interface)
[JIRA] (JENKINS-59020) Fix java.io.NotSerializableException: JiraDeploymentInfoResponse
Title: Message Title Rafal Myslek updated an issue Jenkins / JENKINS-59020 Fix java.io.NotSerializableException: JiraDeploymentInfoResponse Change By: Rafal Myslek Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201374.1566358243000.6582.1566358260220%40Atlassian.JIRA.
[JIRA] (JENKINS-59019) kubernetes-plugin should allow pre-warming of slaves
Title: Message Title Terry Ewing created an issue Jenkins / JENKINS-59019 kubernetes-plugin should allow pre-warming of slaves Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2019-08-21 03:07 Priority: Minor Reporter: Terry Ewing When using jenkins kubernetes-plugin each jenkins job in my cluster takes an additional 2 minutes to start. This is due to the job kicking-off a new pod and awaiting the pod to start all containers and register itself with the master. Is there a way to have a pod created and available for the next job? Each of our pipelines is constructed from a slightly different podTemplate() so I understand I would need to have an idle pod for each podTemplate(). Add Comment
[JIRA] (JENKINS-59010) As User I would like to have control over the deployment mode
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-59010 As User I would like to have control over the deployment mode Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201363.1566310082000.6579.1566356820243%40Atlassian.JIRA.
[JIRA] (JENKINS-30468) Option to include job configurations and build histories
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-30468 Option to include job configurations and build histories Change By: Allan BURDAJEWICZ Assignee: Steven Christou Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165067.1442335995000.6576.1566355620193%40Atlassian.JIRA.
[JIRA] (JENKINS-59005) Zoom Plugin didn't work well
Title: Message Title zoom us assigned an issue to Unassigned Jenkins / JENKINS-59005 Zoom Plugin didn't work well Change By: zoom us Assignee: zoom us Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201357.1566279388000.6573.1566352740139%40Atlassian.JIRA.
[JIRA] (JENKINS-59001) IssueSelectorStep should handle NullPointerException caused by having no configured sites
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-59001 IssueSelectorStep should handle NullPointerException caused by having no configured sites Change By: Olivier Lamy Labels: jira-plugin-3.0.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201352.1566264473000.6571.1566346218788%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-57899 Jira site configuration lost after a restart Change By: Olivier Lamy Labels: jira-plugin-3.0.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.6569.1566346218762%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title Mark Waite commented on JENKINS-59016 Re: GitHub branch source won't scan with folder scoped credentials Based on the change history between 2.5.4 and 2.5.5, I assume that Liam Newman or Devin Nusbaum or Jose Blas Camacho Taboada are the likely ones to investigate the code. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.6559.1566345360064%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit.||Version||Result2.5.6||Credentials ignored|||2.5.5||Credentials ignored|||2.5.4|Credentials honored|||2.5.3|Credentials honored|||2.4.5|Credentials honored|||2.3.6|Credentials honored| Refer to the [JENKINS-59016 branch in my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-59016] for the Jenkins Pipeline that I use to test this. The jobs are run from inside a Docker image that I use which includes credentials used to access the repository.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Joseph Petersen commented on JENKINS-57899 Re: Jira site configuration lost after a restart Fixed in https://github.com/jenkinsci/jira-plugin/pull/195 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.6550.1566344880270%40Atlassian.JIRA.
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Joseph Petersen commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty easy fix inc Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192863.1533584356000.6544.1566344520206%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit. The problem also exists in GitHub branch source plugin ||Version||Result 2.5. 3 6||Credentials ignored|||2 . It does not seem to be an issue in GitHub branch source plugin 5.5||Credentials ignored||| 2. 5.4||Credentials honored|||2.5. 3 ||Credentials honored|||2 . 6 from a year ago 4 . Needs more investigation to narrow the release which introduced the regression 5||Credentials honored|||2 . 3.6||Credentials honored|
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit.||Version||Result2.5.6||Credentials ignored|||2.5.5||Credentials ignored|||2.5.4| | Credentials honored|||2.5.3| | Credentials honored|||2.4.5| | Credentials honored|||2.3.6| | Credentials honored|
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-43400) Autofavorite broken on remote agents
Title: Message Title Alon Chanukov commented on JENKINS-43400 Re: Autofavorite broken on remote agents I am seeing this in logs often also. on BlueOcean 1.16.0 autofavorite plugin 1.2.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180643.1491509101000.6526.1566340080367%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit.The problem also exists in GitHub branch source plugin 2.5.3 and . It does not seem to be an issue in GitHub branch source plugin 2.3.6 from a year ago. This is a long-standing problem and not a recent Needs more investigation to narrow the release which introduced the regression.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-52906) jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty
Title: Message Title Olivier Lamy commented on JENKINS-52906 Re: jira-plugin: FAILED TO EXPORT hudson.plugins.jira.JiraProjectProperty Joseph Petersen this has probably cause JENKINS-57899 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192863.1533584356000.6518.1566336060557%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Olivier Lamy commented on JENKINS-57899 Re: Jira site configuration lost after a restart might be because of https://issues.jenkins-ci.org/browse/JENKINS-52906 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.6516.1566336060525%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a restart
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-57899 Jira site configuration lost after a restart Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.6500.1566336000406%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Devin Nusbaum commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Kyle Manna That build is based on https://github.com/jenkinsci/sse-gateway-plugin/pull/35, which in addition the logging fixes, switches to using a thread pool with 4 threads where the original code was continually creating new Timer threads, so it should fix the thread leak (but maybe trade it off for a memory leak if the queue of retry events gets too big). I think the logging Olivier added was to try to figure out why so many events are failing to send and being added to the retry queue. That said, I think there is a bug in the version you have installed that means that the tasks in the thread pool never actually get retried, so events that fail to be sent are not actually resent. Does Blue Ocean seem to work correctly in that version? Maybe we should just completely remove all of the retry handling Olivier Lamy? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6487.1566335700398%40Atlassian.JIRA.
[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Title: Message Title Alan Castonguay edited a comment on JENKINS-58810 Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed Appears to be similar to some of the observations in [ https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/213 ] - created [https://github.com/jenkinsci/bitbucket-branch-source-plugin/issues/217] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201122.1565008163000.6475.1566334440258%40Atlassian.JIRA.
[JIRA] (JENKINS-59001) IssueSelectorStep should handle NullPointerException caused by having no configured sites
Title: Message Title Owen Wood commented on JENKINS-59001 Re: IssueSelectorStep should handle NullPointerException caused by having no configured sites https://github.com/jenkinsci/jira-plugin/pull/194 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201352.1566264473000.6473.1566333120136%40Atlassian.JIRA.
[JIRA] (JENKINS-59001) IssueSelectorStep should handle NullPointerException caused by having no configured sites
Title: Message Title Owen Wood updated JENKINS-59001 Jenkins / JENKINS-59001 IssueSelectorStep should handle NullPointerException caused by having no configured sites Change By: Owen Wood Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201352.1566264473000.6471.1566333060358%40Atlassian.JIRA.
[JIRA] (JENKINS-59011) Log web hook exception in the folder events log
Title: Message Title Parichay Barpanda stopped work on JENKINS-59011 Change By: Parichay Barpanda Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201364.1566310227000.6469.156633387%40Atlassian.JIRA.
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Manish Christian commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Radi Berkovich, Thank you so much!!! I can confirm that 5.8.5-beta have fixed workspace delete issue. We are on latest 5.8 version. Any plan on releasing stable version with the fix? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197232.1548765582000.6448.1566332880541%40Atlassian.JIRA.
[JIRA] (JENKINS-59018) GitLab hooks not set for gitlab group job type
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-59018 GitLab hooks not set for gitlab group job type Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-20 20:22 Labels: gsoc-2019 Priority: Major Reporter: Parichay Barpanda As after save is executed the navigatorProjects HashSet is not populated yet so it GitLabHookCreator always says the Group is empty, cannot set hook. Add Comment
[JIRA] (JENKINS-59018) GitLab hooks not set for gitlab group job type
Title: Message Title Parichay Barpanda started work on JENKINS-59018 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201371.156633256.6445.1566332580252%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 Thanks for raising this issue Tomasz Kurcz. You're analysis looks correct to me. The exception stack trace shows the following stack: at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) Would you be able to attach the JSON data that you get for reproducibility? As this plug-in is relying on JRJC library, I can see that there is an active Pull Request that attempts to fix this issue. Unfortunately this PR is 5 months old as of today. Alternatively, we can inject a dummy name value to remove the parsing error. The value can be something like "User name attribute is not available, see https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/". This project is open source, would you be interested to make the code change? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201336.1566200967000.6442.1566330480221%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login
Title: Message Title Bogdan Sukonnov assigned an issue to Bogdan Sukonnov Jenkins / JENKINS-59017 Blank page after login Change By: Bogdan Sukonnov Assignee: Bogdan Sukonnov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201370.1566329791000.6443.1566330480258%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login
Title: Message Title Bogdan Sukonnov commented on JENKINS-59017 Re: Blank page after login I saw this bug previously and know that http:///restart will help. And I wont be able to reproduce bug after restart (I tried before). Luckily, I have VM snapshot. So, this state most likely can be reproduced as many times as needed. The question now is - how i can gather more information without restarting Jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201370.1566329791000.6440.1566330420058%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit. The problem also exists in GitHub branch source plugin 2.5.3 and in GitHub branch source plugin 2.3.6 from a year ago. This is a long-standing problem and not a recent regression.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59017) Blank page after login
Title: Message Title Bogdan Sukonnov created an issue Jenkins / JENKINS-59017 Blank page after login Issue Type: Bug Assignee: Unassigned Attachments: 2019-08-20_22h02_57.png, 2019-08-20_22h04_59.png, Jenkins-Docker-logs.txt Components: core Created: 2019-08-20 19:36 Environment: Docker image jenkins/jenkins created 2019-08-19T02:53:44.000166003Z . Plugins installed by Setup Wizard - Install suggested plugins. Docker installed in Kubuntu 19.04 (64). Kubuntu installed in VMWare Payer VM. Host OS Windows 10 (64). Google Chrome, Mozilla Firefox, IE, Edge. Priority: Minor Reporter: Bogdan Sukonnov Blank page after login from all browsers from every computer. It's freshly installed Jenkins. Just after Setup Wizard with Install suggested plugins. Then in wizard dialogue user was created. And after that all attemts to login with this user lead to nothing.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit. The problem does not appear in GitHub branch source plugin 2.5.3.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.6433.1566329400285%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source won't scan with folder scoped credentials
Change By:
Mark Waite
If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports:{code}Started[Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing...13:00:40 Connecting to https://api.github.com with no credentials, anonymous access{code}Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit. The problem does not appear in GitHub branch source plugin 2.5.3.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.6432.1566329340068%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa closed an issue as Not A Defect Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201216.1565453675000.6431.1566328920228%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa commented on JENKINS-58883 Re: Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin It seems like your JIRA license has expired? I don't think it's related to this plug-in. Try to renew your JIRA license and see if the issue persists. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201216.1565453675000.6429.1566328860090%40Atlassian.JIRA.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa Hi .I have installed the JIRA Plugins as "JIRA trigger plugins", " Jira issue updater", And " Jira integration for Jenkin" Few weeks earlier , While I was making any status change in the JIRA issue, it was triggering the build in Jenkin and parallely i could see the update in the "comment" in JIRA.but from few days , while having a status change of bug in JIRA , it does not allow to trigger the build in Jenkin and also there is no comment update in JIRA. but other options , like activity, user statistics , history get updated.during this execution i am facing licensing issue."TESTAA-1 test_jenkin - 2019-08-10 The license key is expired or invalid. Click here if you are Jira administrator. Digest generated on Aug 10 at 8:14 AMConfigure Powered by Email Notifications Digest add-on for Jira"Please help mei am using jenkin : 2.89.2Test JIRA server : 7.13.0RegardsAbhishek Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-59016) GitHub branch source won't scan with folder scoped credentials
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-59016 GitHub branch source won't scan with folder scoped credentials Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-08-20 19:18 Environment: Jenkins 2.176.2 GitHub Branch Source plugin 2.5.6 Git plugin 3.12.0 Priority: Major Reporter: Mark Waite If I define a credential at the root level, then the GitHub branch source can use the credential to scan the repository for branches. If I define the credential in a folder, then the GitHub branch source accepts the credential, but then the scan log reports: Started [Tue Aug 20 13:00:40 MDT 2019] Starting branch indexing... 13:00:40 Connecting to https://api.github.com with no credentials, anonymous access Without the credentials, scanning of private repositories is not allowed and scanning of public repositories is limited by a much smaller value for the GitHub API rate limit.
[JIRA] (JENKINS-58883) Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin
Title: Message Title Wisen Tanasa updated an issue Jenkins / JENKINS-58883 Facing licensing issue while accessing the Jenkin job triggered through JIRA trigger plugin Change By: Wisen Tanasa Environment: Hi .I have installed the JIRA Plugins as "JIRA trigger plugins", " Jira issue updater", And " Jira integration for Jenkin" Few weeks earlier , While I was making any status change in the JIRA issue, it was triggering the build in Jenkin and parallely i could see the update in the "comment" in JIRA.but from few days , while having a status change of bug in JIRA , it does not allow to trigger the build in Jenkin and also there is no comment update in JIRA. but other options , like activity, user statistics , history get updated.during this execution i am facing licensing issue."TESTAA-1 test_jenkin - 2019-08-10 The license key is expired or invalid. Click here if you are Jira administrator. Digest generated on Aug 10 at 8:14 AMConfigure Powered by Email Notifications Digest add-on for Jira"Please help mei am using jenkin : 2.89.2Test JIRA server : 7.13.0RegardsAbhishek Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201216.1565453675000.6423.1566328740513%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Wisen Tanasa assigned an issue to Wisen Tanasa Jenkins / JENKINS-59003 JENKINS and JIRA integration Change By: Wisen Tanasa Assignee: Kohsuke Kawaguchi Wisen Tanasa Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201355.1566272905000.6419.1566328380159%40Atlassian.JIRA.
[JIRA] (JENKINS-59003) JENKINS and JIRA integration
Title: Message Title Wisen Tanasa commented on JENKINS-59003 Re: JENKINS and JIRA integration Hello, please follow this troubleshooting guideline and post the result back here: https://github.com/jenkinsci/jira-trigger-plugin#build-is-not-triggered Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201355.1566272905000.6416.1566328320123%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 Yes, maybe I should create a new issue, my intent was to discuss that setting a default engine version does not prevent issues or show explicit errors when trying to use engine v2 on v1 (or v1 on v2) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6412.1566328260245%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Brian Saville commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 David Dumas, this sounds like a new problem unrelated to the actual problem fixed in this one, does that sound right? I could see how the summary might lead you to think it's the same issue, but the real problem for us is that the default engine version was 2 for everything instead of 1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6407.1566327780142%40Atlassian.JIRA.
[JIRA] (JENKINS-59015) Ability to disable Emojis in Job Names
Title: Message Title Mike Corum commented on JENKINS-59015 Re: Ability to disable Emojis in Job Names It seems like it would make more sense to include an alias or tag that allows emojis and then allow that alias or tag to become the "display name" but not affect the URL. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201368.1566326742000.6405.1566327420104%40Atlassian.JIRA.
[JIRA] (JENKINS-59015) Ability to disable Emojis in Job Names
Title: Message Title Jason Nance created an issue Jenkins / JENKINS-59015 Ability to disable Emojis in Job Names Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-08-20 18:45 Environment: Jenkins 2.190+ Labels: url-encoding views Priority: Minor Reporter: Jason Nance #23349 introduced support for emojis and other non-UTF-8 characters in job names, etc. While I appreciate the excitement for this support it can cause problems in a corporate environment and [opens the door for potentially misleading and/or malicious URIs|https://krebsonsecurity.com/2018/03/look-alike-domains-and-visual-confusion/]. My ask is for a global setting that can be triggered to disable this support. Add Comment
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas edited a comment on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 1) Updated Hashicorp Vault from 0.9.6 to 1.0+2) Updated plugin from 2.1.1 to 2.3.1 (bumps Java vault driver 2.0.0 to 4.0.0)Result: nothing was working anymore without an explicit error message and engine v2 was set by default globally (Jenkins configured with CasC 1.27)Possible fixes I used: * explicitly set engine v1 usage in CasC* upgrade existing version 1 kv store to version 2 kv store with CLI command vault kv enable-versioning secret/ I don't know if there is a way to have an explicit error when trying to use API v2 on a K/V engine v1, but it might save users from troubles Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6401.1566326760321%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 1) Updated Hashicorp Vault from 0.9.6 to 1.0+ 2) Updated plugin from 2.1.1 to 2.3.1 (bumps Java vault driver 2.0.0 to 4.0.0) Result: nothing was working anymore without an explicit error message and engine v2 was set by default globally (Jenkins configured with CasC 1.27) Possible fixes I used: explicitly set engine v1 usage in CasC upgrade existing version 1 kv store to version 2 kv store with CLI command vault kv enable-versioning secret/ I don't know if there is a way to have an explicit error when trying to use API v2 on a K/V engine v1, but it might save users from troubles Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6397.1566326640169%40Atlassian.JIRA.
[JIRA] (JENKINS-58692) Change in treatment of Success - Stable vs. Unstable
Title: Message Title Jesse Glick commented on JENKINS-58692 Re: Change in treatment of Success - Stable vs. Unstable Is it possible that the plugin is causing side effects within Jenkins - so it isn't the symlinks themselves that matter - but rather something else that it causes within Jenkins when performing the symlink update - which resolves our problem here? That would be my guess, which is why I suspect that the exact sequence of operations matters. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200981.1564306537000.6392.1566326520375%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Kyle Manna commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Update: I installed "sse-gateway-1.20-20190813.033926-2.hpi" at roughly 156576 (shortly after the last peak above 20k) and have been recording data. I've yet to see it peak with largely a similar development cycle and load on the build server. I thought the sse-gateway update was only to improve logging? Seems to have reduced the occurrence? X-axis is Unix timestamp Y-Axis is task cnt for jenkins cgroup I've avoided updating any plugins while testing the sse-gateway changes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6378.1566326040406%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Kyle Manna updated an issue Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Kyle Manna Attachment: Screenshot from 2019-08-20 11-29-37.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6364.1566325920496%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Joseph Petersen commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 David Dumas I know for a fact it will throw an error. Could you share more information on what you're trying to attempt? Since without further details I have no chance of helping you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6360.1566325740181%40Atlassian.JIRA.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Jeff Thompson commented on JENKINS-53322 Re: Remove patched dom4j from Stapler Stapler version 1.258 was released on 19 August 2019 containing changes to move to the standard dom4j library. Jenkins PR https://github.com/jenkinsci/jenkins/pull/4130 depends upon that version and removes dependency on the forked library. This PR is up for review. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193404.153555107.6357.1566325440161%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title
David Dumas edited a comment on JENKINS-58970
Re: Backwards compatibility broken with version 2.3.0 for KV1
I am quite concerned that when enabling v2 in configuration (at any level), if K/V engine v2 is not enabled in Vault after upgrading from v1, not a single explicit error shows up in both Jenkins & Vault logs, secret is retrieved with no data and envVars are not set: ``` {{ No such property: testing for class: groovy.lang.Binding ``` }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6354.1566325260371%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title David Dumas commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 I am quite concerned that when enabling v2 in configuration (at any level), if K/V engine v2 is not enabled in Vault after upgrading from v1, not a single explicit error shows up in both Jenkins & Vault logs, secret is retrieved with no data and envVars are not set: ```No such property: testing for class: groovy.lang.Binding``` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6351.1566325200507%40Atlassian.JIRA.
[JIRA] (JENKINS-58915) Change timeout
Title: Message Title Clark Kromenaker commented on JENKINS-58915 Re: Change timeout Hi, no problem - thanks for taking the time to look into this! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201258.1565762652000.6347.1566324600200%40Atlassian.JIRA.
[JIRA] (JENKINS-59014) Use systemhook manager for system hook events
Title: Message Title Parichay Barpanda started work on JENKINS-59014 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201367.1566321765000.6343.1566321900148%40Atlassian.JIRA.
[JIRA] (JENKINS-59011) Log web hook exception in the folder events log
Title: Message Title Parichay Barpanda started work on JENKINS-59011 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201364.1566310227000.6344.1566321900169%40Atlassian.JIRA.
[JIRA] (JENKINS-59014) Use systemhook manager for system hook events
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-59014 Use systemhook manager for system hook events Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-20 17:22 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding commented on JENKINS-58339 Re: Support new types of credentials (I have seen https://jenkins.io/doc/book/pipeline/jenkinsfile/#handling-credentials but the certificate example does not say what format the certificate’s KeyStore is written out in, eg JKS, PEM, P12, and it does not provide an example of an application actually consuming the bound credential.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.6339.1566321360137%40Atlassian.JIRA.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Chris Kilding commented on JENKINS-58339 Re: Support new types of credentials I have started working on this auto-sensing implementation at https://github.com/jenkinsci/aws-secrets-manager-credentials-provider-plugin/pull/8 Thus far I have got a WIP implementation down that supports Secret Text, Username with Password, SSH Private Key credential types. I’m looking to support the client certificate type but there is a problem - I can’t find any decent examples of: How to use client credentials via withCredentials() Plugins that operate on certificate credentials instances directly (to which we only pass the cert credential ID as a string). Can someone point me to a simple of using Jenkins Certificate credentials to do something in a build? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.6335.1566321000151%40Atlassian.JIRA.
[JIRA] (JENKINS-59013) Cannot uninstall PAM Authentication
Title: Message Title tom peck created an issue Jenkins / JENKINS-59013 Cannot uninstall PAM Authentication Issue Type: Bug Assignee: Matt Sicker Components: pam-auth-plugin Created: 2019-08-20 16:50 Priority: Minor Reporter: tom peck I do not use this plugin on my jenkins server and see the option on the Manage Plugins > Installed Plugins page to uninstall it. I click the uninstall, it says "uninstall pending". I restart the server using `systemctl restart jenkins` but the plugin comes back. For what it's worth the plugin is disabled, I don't know if that makes a difference. Add Comment
[JIRA] (JENKINS-58959) Caused by: java.net.BindException: Address already in use
Title: Message Title Daniel Beck closed an issue as Not A Defect Another process is listening on port 8080. There's no bug here. Please ask for advice on Gitter, the users mailing list, StackOverflow… instead. Jenkins / JENKINS-58959 Caused by: java.net.BindException: Address already in use Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201306.1565936173000.6330.1566319620334%40Atlassian.JIRA.
[JIRA] (JENKINS-58994) Inconsistent design for job sidebar "Delete build" link.
Title: Message Title Daniel Beck closed an issue as Duplicate Fixed as JENKINS-58157 in the latest weekly release. Jenkins / JENKINS-58994 Inconsistent design for job sidebar "Delete build" link. Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201344.1566219395000.6327.1566319560473%40Atlassian.JIRA.
[JIRA] (JENKINS-31464) git-client uses proxy from plugins section of jenkins
Title: Message Title Andreas Mandel commented on JENKINS-31464 Re: git-client uses proxy from plugins section of jenkins We also have different proxy settings on the master and agents. Fortunately a local .gitconfig on the build node has precedence over the setting from the master. So we distribute a /home/jenkins/.gitconfig file with the following content to the build nodes: /home/jenkins/.gitconfig [http "https://git.example.com"] proxy = http://proxy.example.com:3128 [http "https://dev.example.com"] proxy = http://proxy2.example.com:3128 Jenkins still logs Setting http proxy: proxy.masteronly.example.com:3128 during the build - but git selects the proxy from the local .gitconfig. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166331.1447113678000.6303.1566319321120%40Atlassian.JIRA.
[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade
Title: Message Title Daniel Beck updated JENKINS-58595 Jenkins / JENKINS-58595 rssAll feed doesn't have published field after 2.176.2 upgrade Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200752.1563783758000.6298.1566318480559%40Atlassian.JIRA.
[JIRA] (JENKINS-58571) It's possible to use renameTo for AbstractItem that has name NOT editable.
Title: Message Title Daniel Beck commented on JENKINS-58571 Re: It's possible to use renameTo for AbstractItem that has name NOT editable. Needs followup Javadoc fix as I commented in the PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200722.1563538638000.6286.1566318421263%40Atlassian.JIRA.
[JIRA] (JENKINS-58571) It's possible to use renameTo for AbstractItem that has name NOT editable.
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-58571 It's possible to use renameTo for AbstractItem that has name NOT editable. Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200722.1563538638000.6284.1566318421235%40Atlassian.JIRA.
[JIRA] (JENKINS-58734) DefaultCrumbIssuer should use more secure hashing algorithm
Title: Message Title Daniel Beck updated JENKINS-58734 Jenkins / JENKINS-58734 DefaultCrumbIssuer should use more secure hashing algorithm Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201034.1564513818000.6293.1566318421364%40Atlassian.JIRA.
[JIRA] (JENKINS-54772) computer//systemInfo doesn't report full Environment
Title: Message Title Daniel Beck updated JENKINS-54772 Jenkins / JENKINS-54772 computer//systemInfo doesn't report full Environment Change By: Daniel Beck Status: In Review Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195578.1542889383000.6295.1566318421388%40Atlassian.JIRA.
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-58157 "delete build" button is to long Change By: Daniel Beck Status: In Progress Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.6289.1566318421304%40Atlassian.JIRA.
[JIRA] (JENKINS-23349) Item names containing an emoji are not accessible
Title: Message Title Daniel Beck resolved as Fixed Jenkins / JENKINS-23349 Item names containing an emoji are not accessible Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Released As: 2.190 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155495.1402054331000.6275.1566318361252%40Atlassian.JIRA.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Justin Heil edited a comment on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Has there been any update to this? We use other tools for simple Ansible jobs for complex pipelines we need access to basic error handling in Ansible. I'm experiencing the issue with Ansible plugin 1.0, and my specific issue is Jenkins seeming to error before triggering or completely bypass rescue blocks that otherwise work in CLI Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195333.1541773391000.6245.1566318300843%40Atlassian.JIRA.
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Justin Heil commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed Has there been any update to this? We use other tools for simple Ansible jobs for complex pipelines we need access to basic error handling in Ansible. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195333.1541773391000.6214.1566317280760%40Atlassian.JIRA.
[JIRA] (JENKINS-58974) Unable to configure manageWebHooks in JCasC
Title: Message Title Parichay Barpanda updated JENKINS-58974 Jenkins / JENKINS-58974 Unable to configure manageWebHooks in JCasC Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201323.1566065267000.6211.1566316020108%40Atlassian.JIRA.
[JIRA] (JENKINS-58999) Add Job DSL documentation
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-58999 Add Job DSL documentation Change By: Parichay Barpanda Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201349.156622945.6210.1566315960412%40Atlassian.JIRA.
[JIRA] (JENKINS-58995) Unable to configure log success in log comment trait
Title: Message Title Parichay Barpanda updated JENKINS-58995 Jenkins / JENKINS-58995 Unable to configure log success in log comment trait Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201345.1566221579000.6209.1566315960212%40Atlassian.JIRA.
[JIRA] (JENKINS-58970) Backwards compatibility broken with version 2.3.0 for KV1
Title: Message Title Brian Saville commented on JENKINS-58970 Re: Backwards compatibility broken with version 2.3.0 for KV1 Tried it out this morning, and works great. Thanks for the quick turnaround on this! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201317.1565984294000.6207.1566312540228%40Atlassian.JIRA.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Devin Nusbaum commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 Ok, from Kiyoaki Hoshino's logs I think I figured out the problem. Repo plugin doesn't create a changelog file if there are no changes (I guess other SCM plugins create an empty changelog file in that case, which is why this problem only shows up for Repo plugin). Because the changelog file is now actually created in workflow-scm-step if changelogs are enabled, rather than just passing a reference to a file that doesn't exist, we pass the check here that only calls the changelog parser if the file exists. This could be fixed by having workflow-scm-step check if the file's size is 0 before passing it to SCMListener.onCheckout here, or by having Repo plugin create an empty changelog file here instead of leaving the file empty. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199890.1560007155000.6197.1566311280345%40Atlassian.JIRA.
[JIRA] (JENKINS-44860) Disable masking of usernames
Title: Message Title Stefan Thurnherr commented on JENKINS-44860 Re: Disable masking of usernames +1 to fix, parsing the console log with the warnings-ng jenkins plugin doesn't work otherwise: 10:19:08 [Java] [-ERROR-] Can't resolve absolute paths for some files: 10:19:08 [Java] [-ERROR-] - /export/jenkins/workspace/_jenkins-warnings-to-warnings-ng/-core/src/main/java/com/company//mypackage/SomeClass.java [...] 10:19:08 [Java] [-ERROR-] Can't create fingerprints for some files: 10:19:08 [Java] [-ERROR-] - '/export/jenkins/workspace/_jenkins-warnings-to-warnings-ng/-core/src/main/java/com/company//mypackage/SomeClass.java', IO exception has been thrown: java.nio.file.NoSuchFileException: /export/jenkins/workspace/_jenkins-warnings-to-warnings-ng/-core/src/main/java/com/company//mypackage/SomeClass.java [...] 10:19:08 [Java] [-ERROR-] Git blame errors: 10:19:08 [Java] [-ERROR-] - no blame results for request <-core/src/main/java/com/company//mypackage/SomeClass.java - [82]>. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182924.1497380811000.6178.1566311160545%40Atlassian.JIRA.
[JIRA] (JENKINS-58668) Doesn't create a file within docker.inside {}
Title: Message Title
Chad Gilbert commented on JENKINS-58668
Re: Doesn't create a file within docker.inside {}
I've been using this plugin just fine inside docker containers. If targetLocation is set as relative to the workspace (e.g. "foobar" instead of "/foobar") then the file shows up as expected in the workspace, both inside and outside of the container. I'd argue that this use case should not be supported. If you really want to inject a config file outside of the shared workspace folder inside the container, you could subsequently move it out of the workspace folder inside the container. If anything, perhaps this plugin could issue a warning if targetLocation points to somewhere above the workspace directory.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200950.1564129139000.6176.1566310980421%40Atlassian.JIRA.
[JIRA] (JENKINS-59012) Parameters in pipeline are acessible outside the params object
Title: Message Title
hugo charles created an issue
Jenkins / JENKINS-59012
Parameters in pipeline are acessible outside the params object
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-08-20 14:21
Environment:
Jenkins ver. 2.121.3
Priority:
Minor
Reporter:
hugo charles
Parameters are accessible outside the params object, this is potentially harmful.
properties([
parameters([string(defaultValue: 'foo', description: '', name: 'VERSION', trim: false)])
])node () {
echo params.VERSION
echo VERSION
echo env.VERSION
echo vErSiOn
echo env.VerSiOn
}
Result
[Pipeline] {
[Pipeline] echo
foo
[Pipeline] echo
foo
[Pipeline] echo
foo
[Pipeline] echo
foo
[Pipeline] echo
foo
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
It should only work for params.VERSION and return null in the other case.
[JIRA] (JENKINS-59004) Update project page for GSoC submission
Title: Message Title Andrey Falko updated an issue Jenkins / JENKINS-59004 Update project page for GSoC submission Change By: Andrey Falko [This is the page we want to update: https://jenkins.io/projects/gsoc/2019/remoting-over-apache-kafka-docker-k8s-features/|https://jenkins.io/projects/gsoc/2019/remoting-over-apache-kafka-docker-k8s-features/] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201356.1566277958000.6171.1566310800158%40Atlassian.JIRA.
[JIRA] (JENKINS-59011) Log web hook exception in the folder events log
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-59011 Log web hook exception in the folder events log Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-20 14:10 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda This is a bug reported by Joseph Petersen. We need to report the user to use fully qualified url as Jenkins url. Add Comment
[JIRA] (JENKINS-59010) As User I would like to have control over the deployment mode
Title: Message Title Peter Niederlag created an issue Jenkins / JENKINS-59010 As User I would like to have control over the deployment mode Issue Type: Improvement Assignee: Azure DevOps Components: azure-function-plugin Created: 2019-08-20 14:08 Priority: Minor Reporter: Peter Niederlag currently it seems the azure-function-plugin has some super cow power and decides the deployment strategy based on: it's a java app, use zip deployment otherwise, use git deployment It would be cool if the decision on the deployment mode could be made by the user. Also it would be important to drop a note somewhere on these decisions as - to my knowledge - the settings in the function app must correspond to the deployment mode used. (WEBSITE_RUN_FROM_PACKAGE = "1") Add Comment
[JIRA] (JENKINS-58274) Function missing after deployment
Title: Message Title Peter Niederlag commented on JENKINS-58274 Re: Function missing after deployment deploying azure function apps is a real terrible mess from my point of view :-< Are you aware there are some hidden Environment-Settings in the function-app that somehow seem to be important in relation to the deployment? For zip based deployments you might need to set something like this in your function app: WEBSITE_RUN_FROM_PACKAGE = "1" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200338.1561960792000.6165.1566309900342%40Atlassian.JIRA.
[JIRA] (JENKINS-58998) Unable to delete pipeline job - Question about which user is performing the delete
Title: Message Title Curran Lipsett closed an issue as Not A Defect Upgrading 2.187 to 2.190 has resolved our issue. Jenkins / JENKINS-58998 Unable to delete pipeline job - Question about which user is performing the delete Change By: Curran Lipsett Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201348.1566225858000.6166.1566309900354%40Atlassian.JIRA.
[JIRA] (JENKINS-58998) Unable to delete pipeline job - Question about which user is performing the delete
Title: Message Title Curran Lipsett commented on JENKINS-58998 Re: Unable to delete pipeline job - Question about which user is performing the delete It appears our update to 2.190 has resolved this issue - we are now able to delete pipeline jobs remotely on the Jenkins UI. Closing this item. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201348.1566225858000.6162.1566309840058%40Atlassian.JIRA.
[JIRA] (JENKINS-33843) It's not possible to disable/uninstall optional dependencies
Title: Message Title Nick Jones commented on JENKINS-33843 Re: It's not possible to disable/uninstall optional dependencies In case it's helpful to anyone else (as I've just gone through this to uninstall Mask Passwords due to SECURITY-157), Jesse Glick's workaround disables the optional dependency in question (mask-passwords.jpi in my case), after which point the Uninstall button in the Manage Plugins page will enable, and the plugin can be uninstalled as desired. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169319.1459117318000.6143.1566309480679%40Atlassian.JIRA.
[JIRA] (JENKINS-59009) Proxy support
Title: Message Title tony pauvreau created an issue Jenkins / JENKINS-59009 Proxy support Issue Type: Improvement Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2019-08-20 13:55 Priority: Minor Reporter: tony pauvreau Hello, "Jira Site" need direct connection, the environnement proxy is ignored. It should be usefull to let configure proxy or use system proxy if setted to acces "Jira site" Thanks Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-40664) Ecs Plugin fails to launch slave in Version 1.7
Title: Message Title Neeraj Malve reopened an issue If its ok to be reopened as per my last screenshot the issue still exist Jenkins / JENKINS-40664 Ecs Plugin fails to launch slave in Version 1.7 Change By: Neeraj Malve Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177363.1482524683000.6136.1566307380350%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Keith Davis edited a comment on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. I'm on 2.189 and believe I have the same issue - aborting running jobs causes the service to crash . Does not happen 100% of the time (I don't think, but have not confirmed that part). Child process [2064 - c:\Jenkins\jre\bin\java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "c:\Jenkins\jenkins.war" --httpPort=] finished with -1073741510 The jenkins service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 6 milliseconds: Restart the service. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.6125.1566306720269%40Atlassian.JIRA.
[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.
Title: Message Title Keith Davis commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. I'm on 2.189 and believe I have the same issue. Does not happen 100% of the time (I don't think, but have not confirmed that part). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195272.1541539669000.6115.1566306660251%40Atlassian.JIRA.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub -- Does not meet criteria
Title: Message Title Jon Cormier commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub -- Does not meet criteria We encountered this problem today, we have: Jenkins v2.176.2 Branch API Plugin v2.5.4 GitHub Branch Source v2.5.5 Multijob plugin v 1.32 Pipeline: Multibranch 2.21 deleting the files under $JENKINS_HOME/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache resolved the problem. This isn't a viable longterm solution though. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.6030.1566306241980%40Atlassian.JIRA.
