[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Sverre Moe Ad "cleaned up": Sorry for my lack of clarity => due to the OOM there were remaining running Docker Containers that I had to stop and remove; and it also appeared that about 2xx "EventDispatcher.retryProcessor" threads were remaining inside Jenkins Java process... Other notes (~15h after Jenkins master restart): This morning no "EventDispatcher.retryProcessor" threads are there (or remaining) yet. Interestingly there are 25 "org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep" threads, even though just one pipeline build is running (without any parallelism) 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.7580.1566453540437%40Atlassian.JIRA.
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Ahuhu uhuhuh commented on JENKINS-59000 Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 I dont have an option to roll back as azure kubernetes doesnt let me do it. Is the community doing something about this issue? carlos canchez is the person who wrote that plugin, please message him as well 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.201351.1566264399000.7569.1566449470263%40Atlassian.JIRA.
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Ahuhu uhuhuh commented on JENKINS-59000 Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 I dont have an option to roll back as azure kubernetes doesnt let me do it. Is the community doing something about this issue? carlos canchez is the person who wrote that plugin, please message him as well 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.201351.1566264399000.7576.1566449520016%40Atlassian.JIRA.
[JIRA] (JENKINS-59043) Build with parameters plugin does not input type=file
Title: Message Title A Trelinski updated an issue Jenkins / JENKINS-59043 Build with parameters plugin does not input type=file Change By: A Trelinski Please add support for [https: Can't pass argument to parameter that is type=file ()In the "$JENKINS / job / wiki.jenkins.io $JOB / display/ build" page such type is represented as button!image-2019-08-22-04-39-36-009.png!In the "$ JENKINS/ Parameter+Separator+Plugin.] It's rendered really ugly when using . job / $JOB/ parambuild " page is it represented as text input, but the biggest problem is that parameter value from URL is not passed to this field at all 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.201397.1566441318000.7567.1566441780125%40Atlassian.JIRA.
[JIRA] (JENKINS-59043) Build with parameters plugin does not input type=file
Title: Message Title A Trelinski updated an issue Jenkins / JENKINS-59043 Build with parameters plugin does not input type=file Change By: A Trelinski Attachment: image-2019-08-22-04-39-36-009.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.201397.1566441318000.7565.1566441600131%40Atlassian.JIRA.
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Ivan Lefkate commented on JENKINS-59000 Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 I got the same issue and also confirmed that rolling back to 1.15.2 fixes it. 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.201351.1566264399000.7558.1566441480193%40Atlassian.JIRA.
[JIRA] (JENKINS-58989) Amazon ECS Plugin not supporting controlled slaves
Title: Message Title Raihaan Shouhell assigned an issue to Jan Roehrich Jenkins / JENKINS-58989 Amazon ECS Plugin not supporting controlled slaves Change By: Raihaan Shouhell Assignee: FABRIZIO MANFREDI Jan Roehrich 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.201338.1566204915000.7556.1566441420179%40Atlassian.JIRA.
[JIRA] (JENKINS-58989) Amazon ECS Plugin not supporting controlled slaves
Title: Message Title Raihaan Shouhell commented on JENKINS-58989 Re: Amazon ECS Plugin not supporting controlled slaves Changed component to ECS plugin as the description seems to be related to that 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.201338.1566204915000.7548.1566441360347%40Atlassian.JIRA.
[JIRA] (JENKINS-59043) Build with parameters plugin does not input type=file
Title: Message Title A Trelinski updated an issue Jenkins / JENKINS-59043 Build with parameters plugin does not input type=file Change By: A Trelinski Summary: CLONE - build Build with params parameters plugin does not support ParameterSeparatorDefinition input type=file 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.201397.1566441318000.7552.1566441360420%40Atlassian.JIRA.
[JIRA] (JENKINS-59043) CLONE - build with params plugin does not support ParameterSeparatorDefinition
Title: Message Title A Trelinski created an issue Jenkins / JENKINS-59043 CLONE - build with params plugin does not support ParameterSeparatorDefinition Issue Type: Improvement Assignee: Ivan Sugonyak Components: build-with-parameters-plugin Created: 2019-08-22 02:35 Priority: Minor Reporter: A Trelinski Please add support for https://wiki.jenkins.io/display/JENKINS/Parameter+Separator+Plugin. It's rendered really ugly when using ./parambuild Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-58989) Amazon ECS Plugin not supporting controlled slaves
Title: Message Title Raihaan Shouhell updated an issue Jenkins / JENKINS-58989 Amazon ECS Plugin not supporting controlled slaves Change By: Raihaan Shouhell Component/s: amazon-ecs-plugin Component/s: ec2-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201338.1566204915000.7545.1566441300166%40Atlassian.JIRA.
[JIRA] (JENKINS-59005) Zoom Plugin didn't work well
Title: Message Title Alex Earl assigned an issue to zoom us Jenkins / JENKINS-59005 Zoom Plugin didn't work well Change By: Alex Earl Assignee: Alex Earl 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.7535.1566441240374%40Atlassian.JIRA.
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Ahuhu uhuhuh commented on JENKINS-59000 Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 I am having the same issue on aks 1.13.10 version. Any one looking at it yet 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.201351.1566264399000.7537.1566441240443%40Atlassian.JIRA.
[JIRA] (JENKINS-59005) Zoom Plugin didn't work well
Title: Message Title Alex Earl commented on JENKINS-59005 Re: Zoom Plugin didn't work well I don't know why this is assigned to me. When you develop a plug-in, it is your responsibility to debug customer issues. 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.7533.1566441180132%40Atlassian.JIRA.
[JIRA] (JENKINS-59005) Zoom Plugin didn't work well
Title: Message Title zoom us commented on JENKINS-59005 Re: Zoom Plugin didn't work well Hi Alex Earl, can you give any help 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.201357.1566279388000.7531.1566440460110%40Atlassian.JIRA.
[JIRA] (JENKINS-59005) Zoom Plugin didn't work well
Title: Message Title zoom us assigned an issue to Alex Earl Jenkins / JENKINS-59005 Zoom Plugin didn't work well Change By: zoom us Assignee: Alex Earl 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.7529.1566440400196%40Atlassian.JIRA.
[JIRA] (JENKINS-59042) Add no-download option
Title: Message Title Natasha Stopa started work on JENKINS-59042 Change By: Natasha Stopa 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.201396.1566435357000.7525.1566438300182%40Atlassian.JIRA.
[JIRA] (JENKINS-59042) Add no-download option
Title: Message Title Natasha Stopa commented on JENKINS-59042 Re: Add no-download option PR: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/68 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.201396.1566435357000.7527.1566438300249%40Atlassian.JIRA.
[JIRA] (JENKINS-59042) Add no-download option
Title: Message Title Natasha Stopa updated JENKINS-59042 Jenkins / JENKINS-59042 Add no-download option Change By: Natasha Stopa 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.201396.1566435357000.7526.1566438300230%40Atlassian.JIRA.
[JIRA] (JENKINS-59042) Add no-download option
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-59042 Add no-download option Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-22 00:55 Labels: plugin-manager gsoc-2019 Priority: Minor Reporter: Natasha Stopa Some users want to be able to download plugins and see the security warnings at the same time. By adding a --no-download option, the user can chose to not download plugins when they look at other information about the plugins, but by default plugins will be downloaded. Add Comment
[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 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.201374.1566358243000.7523.1566433860129%40Atlassian.JIRA.
[JIRA] (JENKINS-59041) help people understand how to tune the log
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59041 help people understand how to tune the log Issue Type: Task Assignee: Kirill Merkushev Components: github-plugin Created: 2019-08-22 00:12 Priority: Minor Reporter: Josh Soref https://github.com/jenkinsci/github-plugin/blob/29e7aec/src/main/resources/org/jenkinsci/plugins/github/admin/GitHubHookRegisterProblemMonitor/index.properties#L12 help.for.page.and.debug.info=This page shows problems with webhooks, and ignored projects. A detailed stacktrace for any of the problems can be found in the system log. \ For improved debugging in the Jenkins interface, enable these logs: That isn't very helpful. More helpful would be: Linking to https://wiki.jenkins.io/display/JENKINS/Logging Linking to /log/levels for adjusting the levels Linking to /log/all for viewing the logs
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Marc Benstein commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log This seems similar to my issue with v0.6.2. This was working in v0.5.x I have a freestyle project where I have enabled ansi color with xterm. A single shell command with: echo "testing-1.2.300" | grep -E --color=always '[0-9]+.[0-9]+.[0-9]+' Results in: 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.196206.1544605559000.7501.1566430380434%40Atlassian.JIRA.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-55139 ansicolor 0.6.0 shows terminal escape sequences in console log Change By: Marc Benstein Attachment: image-2019-08-21-16-31-39-960.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.196206.1544605559000.7479.1566430320725%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 and newer ignores credentials based on credential domain when scanning repositories
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59016 GitHub branch source 2.5.5 and newer ignores credentials based on credential domain when scanning repositories Change By: Mark Waite Summary: GitHub branch source scan 2.5.5 and newer ignores credentials based on credential domain when scanning repositories 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.7475.1566429120220%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59016 GitHub branch source scan ignores credentials based on credential domain Change By: Mark Waite Comment: Based on the change history between 2.5.4 and 2.5.5, I assume that [~lnewman] or [~dnusbaum] or [~jtaboada] 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.7474.1566429120207%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source scan ignores credentials based on credential domain For anyone, looking at the comments (and not the full history view), Mark helped us analyze this issue and then updated the description. Same people are likely to be the ones to work on this further, but the regression is much lower priority/severity that initially thought. 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.7472.1566428760109%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES: * OkHttp 2.x and 3.x exist and separate packages and can run side-by-side without conflict. However, different versions of 3.x may be incompatible if clients are using obsolete classes/methods.* OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones.* OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults.* OkHttp 3.14.1 removes UrlFactory which is a serious version-incompatible API change for several plugins.Early exploration of this upgrade was started to test whether it would address issues such ass JENKINS-54126. Finding so far while using 3.12.2: * okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded.* (Last updated May 29, 2019):Please give this version of the plugin a try: [ https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5. 4 7 - rc849 rc892 . b58a1bae7fce e46ec862f6f7 / ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source scan ignores credentials based on credential domain
Change By:
Mark Waite
The GitHub branch source plugin uses the GitHub REST API to scan remote repositories for changes. I had incorrectly defined my GitHub credential in a credential domain that only included the {{github.com}} domain. The GitHub branch source plugin allowed me to select that credential, but then would not use that credential because it was making the request to {{api.github.com}} rather than {{github.com}}.My working credential domains had defined the domain as {{github.com,*.github.com}}. That working definition matched {{api.github.com}}. When the My incorrect credential domain was specified as only including {{github.com}}. With that incorrect domain specificiation , the repository scan log would report:{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 if assigned incorrect domain|||2.5.5||Credentials ignored if assigned incorrect domain|||2.5.4|Credentials honored if assigned incorrect domain|||2.5.3|Credentials honored if assigned incorrect domain|||2.4.5|Credentials honored if assigned incorrect domain|||2.3.6|Credentials honored if assigned incorrect domain|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
[JIRA] (JENKINS-59040) Show "Build Now" when all build parameters are hidden
Title: Message Title Nathan Schulte created an issue Jenkins / JENKINS-59040 Show "Build Now" when all build parameters are hidden Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-08-21 21:56 Priority: Minor Reporter: Nathan Schulte When using a parameterized build, change the link to "build now" (single click) when all build parameters are hidden, the same as if there are no build parameters. Currently, the link is "Build with Parameters" even when all parameters are hidden; the next page is blank, requiring an unnecessary second click. Possibly use the text "Build now (with hidden parameters)" or such to indicate the situation if suitable. Add Comment
[JIRA] (JENKINS-59039) Add switch for choose `checkApiRateLimit` implementation
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-59039 Add switch for choose `checkApiRateLimit` implementation Issue Type: Improvement Assignee: Liam Newman Components: github-branch-source-plugin Created: 2019-08-21 21:50 Priority: Minor Reporter: Liam Newman See https://github.com/jenkinsci/github-branch-source-plugin/pull/237 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-59038) Submit GSoC Project for Final Evaluation
Title: Message Title Natasha Stopa started work on JENKINS-59038 Change By: Natasha Stopa 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.201392.1566423589000.7465.1566423960085%40Atlassian.JIRA.
[JIRA] (JENKINS-59038) Submit GSoC Project for Final Evaluation
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-59038 Submit GSoC Project for Final Evaluation Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-21 21:39 Priority: Minor Reporter: Natasha Stopa Make sure to merge and release the work which have not been integrated yet. Please prioritize it over adding new features to your projects. Students evaluation submission should include a link to the page which summarizes all contributions. It is highly recommended to use your project pages on https://jenkins.io/projects/gsoc/ as a submission. Please make sure to update them to reflect the final state, to link your blogposts and presentations, and to link the code you have written during GSoC There will be Jenkins Online Meetups with final demos. The format is similar to what we had. We will conduct the meetings in Zoom, I plan to publish the announcements by Tuesday Presentation slots: Aug 23, 2:00-3:30PM UTC && Aug 26, 3:00-4:30PM UTC Please update your presentation abstracts here We expect all students to publish blogposts summarizing their work over Phase 2 and 3. It is preferable to have technical blogposts announcing new features released during these phases. If you have not already done that, please make sure to submit the drafts this week
[JIRA] (JENKINS-52189) GraphListener does not receive FlowStartNode
Title: Message Title Devin Nusbaum resolved as Fixed The new FlowExecutionListener.onCreated method was released in Pipeline API Plugin 2.36, and is activated by Pipeline Job Plugin 2.34. Jenkins / JENKINS-52189 GraphListener does not receive FlowStartNode Change By: Devin Nusbaum Status: Reopened Resolved Assignee: Thomas Weißschuh Resolution: Fixed Released As: workflow-cps 2.63 , workflow-api 2.36, workflow-job 2.34 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to
[JIRA] (JENKINS-59037) Environment from CasC yaml to job dsl script
Title: Message Title
Rudolf-Walter Kiss-Szakacs created an issue
Jenkins / JENKINS-59037
Environment from CasC yaml to job dsl script
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-08-21 21:24
Labels:
configuration-as-code
Priority:
Minor
Reporter:
Rudolf-Walter Kiss-Szakacs
When executing job dsl scripts from configuration-as-code, there should be a way to pass values from the yaml files into the job dsl groovy. This would be useful in cases where one wishes to generate the same jobs from CasC on multiple masters, with minor variations. Example:
common_jobs.groovy
job('awesome-job') {
description("favorite job of ${SUPERHERO}")
}
master_one.yml
jobs:
- providedEnv:
SUPERHERO: 'Wonder Woman'
- file: common_jobs.groovy
[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3
Title: Message Title Dakota Pollard commented on JENKINS-59000 Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3 Our K8s clusters were just upgraded to v1.15.3 and we are also experiencing the same issue. Our Jenkins uses this plugin for agents so all of our pipelines are blocked and we aren't able to roll back our cluster. Does anyone have an idea of a workaround for this? Any idea what needs to be fixed in the plugin or if someone is already looking into it? 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.201351.1566264399000.7453.1566422640157%40Atlassian.JIRA.
[JIRA] (JENKINS-59029) Build is successful but at end it fails with fatal remote call on slave failed
Title: Message Title Steve Hill closed an issue as Not A Defect Jenkins / JENKINS-59029 Build is successful but at end it fails with fatal remote call on slave failed Change By: Steve Hill 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.201383.1566396948000.7451.1566421440291%40Atlassian.JIRA.
[JIRA] (JENKINS-59029) Build is successful but at end it fails with fatal remote call on slave failed
Title: Message Title Steve Hill commented on JENKINS-59029 Re: Build is successful but at end it fails with fatal remote call on slave failed Hi Naresh Kumar, This is not a problem with the gradle-jpi-plugin. The gradle-jpi-plugin is a gradle plugin to build jenkins plugins, not a jenkins plugin to run gradle builds. I suppose you may be using the gradle plugin in your build step, but this looks like it's more related to the mismatched java versions. Caused by: java.lang.NoSuchMethodException: java.lang.UNIXProcess.destroyProcess(int) Here is a related ticket that is already marked resolved: JENKINS-21341 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.201383.1566396948000.7449.1566421440260%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" I filed a PR that should fix at least some variants of this issue: https://github.com/jenkinsci/blueocean-plugin/pull/2017. I think the main ways to hit this bug are when the Pipeline's execution path in terms of steps/stages changes from one run to the next (for example if a when condition is activated in one build but not in the next, or perhaps if you have a Scripted Pipeline that does something like when using Groovy, or if you changed the Jenkinsfile manually). If anyone has simple reproducer (just a Jenkinsfile that runs without needing to configure anything special in Jenkins) that does not involve any of those things (or even if it does involve those things), I would be interested to see it to check if my patch fixes it or not. 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.200110.1560887329000.7426.1566421380473%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title William Brode commented on JENKINS-40292 Re: More Control of p4 task logging Bruce Evans That's okay, I welcome your feedback as we want to make a change that works for everyone. 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.176946.1481141079000.7422.1566421320181%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59016 GitHub branch source scan ignores credentials based on credential domain Change By: Mark Waite Priority: Critical Trivial 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.7419.1566420960352%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source scan ignores credentials based on credential domain
Change By:
Mark Waite
The GitHub branch source plugin uses the GitHub REST API to scan remote repositories for changes. I had incorrectly defined my GitHub credential in a credential domain that only included to If I define a credential at the root level, then the {{github.com}} domain. The GitHub branch source can plugin allowed me to select that credential, but then would not use the that credential to scan because it was making the repository for branches request to {{api . If I define the github.com}} rather than {{github.com}}.My working credential in a folder domains had defined the domain as {{github.com , then *.github.com}}. That working definition matched {{api.github.com}}.When the GitHub branch source accepts the incorrect credential domain was specified , but then the repository scan does not use the credential and the scan log reports would report :{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 if assigned incorrect domain |||2.5.5||Credentials ignored if assigned incorrect domain |||2.5.4|Credentials honored if assigned incorrect domain |||2.5.3|Credentials honored if assigned incorrect domain |||2.4.5|Credentials honored if assigned incorrect domain |||2.3.6|Credentials honored if assigned incorrect domain |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
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title Bogdan Sukonnov edited a comment on JENKINS-59017 Re: Blank page after login just after finishing Setup Wizard So I see 3 problems here: # SetupWizardFilter works still do filtering in spite of isSetupComplete() == true # SetupWizardFilter is still in filters list when Setup Wizard is complete - this can indicate general problems with deleting filters # http:///setupWizard/ works on every Jenkins, but doesn't give user any information or interface with possible actions 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.7417.1566420900243%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title Bogdan Sukonnov commented on JENKINS-59017 Re: Blank page after login just after finishing Setup Wizard So I see 3 problems here: SetupWizardFilter works in spite of isSetupComplete() == true SetupWizardFilter still in filters list when Setup Wizard is complete http:///setupWizard/ works on every Jenkins, but doesn't give user any information or interface with possible actions 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.7416.1566420696695%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum started work on JENKINS-58085 Change By: Devin Nusbaum 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.200110.1560887329000.7394.1566420690202%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.7371.1566420676899%40Atlassian.JIRA.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Kiyoaki Hoshino commented on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 Dear Devin, Thank you for your analysis and solution. I hope the next Pipeline SCM Step plugin release. 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.7361.1566420670971%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title Bogdan Sukonnov commented on JENKINS-59017 Re: Blank page after login just after finishing Setup Wizard The same blank page can be reached in any Jenkins by http:///setupWizard/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201370.1566329791000.7358.1566419940054%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59016
GitHub branch source scan ignores credentials based on credential domain
Change By:
Mark Waite
The GitHub branch source plugin uses the GitHub REST API to scan remote repositories for changes. I had incorrectly defined my GitHub credential in a credential domain that only included to 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 does not use the credential and 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
[JIRA] (JENKINS-59016) GitHub branch source scan ignores credentials based on credential domain
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59016 GitHub branch source scan ignores credentials based on credential domain Change By: Mark Waite Summary: GitHub branch source won't scan with folder scoped ignores credentials based on credential domain 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.7356.1566419400068%40Atlassian.JIRA.
[JIRA] (JENKINS-59036) Write DevOps World Blog Post
Title: Message Title Natasha Stopa commented on JENKINS-59036 Re: Write DevOps World Blog Post Created PR here: https://github.com/jenkins-infra/jenkins.io/pull/2434 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.201390.1566418316000.7355.1566418980050%40Atlassian.JIRA.
[JIRA] (JENKINS-59036) Write DevOps World Blog Post
Title: Message Title Natasha Stopa started work on JENKINS-59036 Change By: Natasha Stopa 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.201390.1566418316000.7353.1566418740361%40Atlassian.JIRA.
[JIRA] (JENKINS-59036) Write DevOps World Blog Post
Title: Message Title Natasha Stopa updated JENKINS-59036 Jenkins / JENKINS-59036 Write DevOps World Blog Post Change By: Natasha Stopa 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.201390.1566418316000.7354.1566418740421%40Atlassian.JIRA.
[JIRA] (JENKINS-59036) Write DevOps World Blog Post
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-59036 Write DevOps World Blog Post Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-08-21 20:11 Priority: Minor Reporter: Natasha Stopa After successfully attending and demoing at Devops World - Jenkins World, a blog post should be written about the experience. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title Tony Wallace updated an issue Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: Tony Wallace Environment: Jenkins ver. 1.650 ( , 2.176.1 Copy Artifact Plugin 1.37 , 1.42.1 Promoted builds plugin 2.25 , 3.2 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.168891.1457697475000.7350.1566417960385%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title Tony Wallace updated an issue Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: Tony Wallace Environment: Jenkins ver. 1.650 ( Copy Artifact Plugin 1.37Promoted builds plugin 2.25 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.168891.1457697475000.7346.1566417840716%40Atlassian.JIRA.
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title Rudolf-Walter Kiss-Szakacs assigned an issue to Rudolf-Walter Kiss-Szakacs Jenkins / JENKINS-58136 vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration Change By: Rudolf-Walter Kiss-Szakacs Assignee: Rudolf-Walter Kiss-Szakacs 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.200181.1561105641000.7343.1566417840676%40Atlassian.JIRA.
[JIRA] (JENKINS-25340) lost trend history after skipping build
Title: Message Title Ilya Ilba commented on JENKINS-25340 Re: lost trend history after skipping build Could somebody please try my fix (incremental build here). Cannot verify it myself as I'm stuck with the old version of jenkins which is incompatible with the latest junit. 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.158855.1414504729000.7313.1566417780826%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title
Bogdan Sukonnov edited a comment on JENKINS-59017
Re: Blank page after login just after finishing Setup Wizard
but Script Console{code:java}println(Jenkins.get().getSetupWizard().hasSetupWizardFilter());{code}prints _false_ {code:java}println(Jenkins.get().getInstallState().isSetupComplete());{code} prints _true_
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.7311.1566416760050%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title Bogdan Sukonnov commented on JENKINS-59017 Re: Blank page after login just after finishing Setup Wizard but Script Console println(Jenkins.get().getSetupWizard().hasSetupWizardFilter()); prints false 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.7310.1566416580054%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba commented on JENKINS-52711 Re: JUnit Results Trend graph doesn't show all build results if builds have been deleted There are other manifestations of the same issue in the code, e.g. JENKINS-31926, JENKINS-26153, JENKINS-25340. But this ticket is unique in that it describes specifically deleted builds - which is exactly the issue which I had. 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.192600.1532377276000.7306.1566415980231%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title Tony Wallace updated JENKINS-33476 Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: Tony Wallace Resolution: Cannot Reproduce Status: Resolved In 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.168891.1457697475000.7303.1566415320427%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title
Tony Wallace commented on JENKINS-33476
Re: copyartifact uses incorrect permalink for promoted build
I encountered this problem independently. The existing description seems accurate enough. I am providing a new test case to reproduce. It should take less than 15 minutes. See below, with attachments as noted. Jenkins 2.176.1 Promoted Builds Plugin 3.2 (downgraded from 3.3 because JENKINS-58337) Copy Artifacts Plugin 1.42.1 Steps to reproduce
Create a new freestyle job with
1 manual promotion including a copy artifacts step (a-JobConfig-1)
1 archived artifact (b-JobConfig-2)
Run two builds
(c-RunTwoBuilds)
Manually promote the second build
(d-PromoteSecondBuildFirst, e-PromoteSecondBuildFirst-console)
Manually promote the first build
(f-PromoteFirstBuildLast, g-PromoteFirstBuildLast-console)
The log of the first build's promotion (g-PromoteFirstBuildLast-console) shows that the second build actually got promoted. Fortunately, there is a workaround for this bug that meets my requirements. Instead of specifying "Which build" as "Specified by Permalink" with Permalink = , I now use "Specific build" with build number = "${PROMOTED_NUMBER}" Since this build selection method seems to do the job, and the "Permalink -> " build selection method can be misleading, perhaps it makes sense to remove the "Permalink -> " build selection method from CopyArtifacts.
Add Comment
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title Tony Wallace updated an issue Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: Tony Wallace Attachment: a-JobConfig-1.PNG Attachment: b-JobConfig-2.PNG Attachment: c-RunTwoBuilds.PNG Attachment: d-PromoteSecondBuildFirst.PNG Attachment: e-PromoteSecondBuildFirst-console.PNG Attachment: f-PromoteFirstBuildLast.PNG Attachment: g-PromoteFirstBuildLast-console.PNG Attachment: h-JobConfig-3-Workaround.PNG Add Comment
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-56217 allow to hide version number Change By: Matt Sicker Component/s: extended-security-settings-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1550676909000.7288.1566414120260%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Jesse Glick commented on JENKINS-52711 Re: JUnit Results Trend graph doesn't show all build results if builds have been deleted Very likely a duplicate of something much older. 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.192600.1532377276000.7284.1566414061259%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-56217 allow to hide version number Change By: Matt Sicker Assignee: Matt Sicker 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.19.1550676909000.7269.1566414061002%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker started work on JENKINS-56217 Change By: Matt Sicker 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.19.1550676909000.7275.1566414061102%40Atlassian.JIRA.
[JIRA] (JENKINS-56217) allow to hide version number
Title: Message Title Matt Sicker commented on JENKINS-56217 Re: allow to hide version number New approach: https://github.com/jenkinsci/jenkins/pull/4164 I'll have a follow up PR for extended-security-settings-plugin which implements the actual permission check to complete this feature. 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.19.1550676909000.7281.1566414061214%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Jesse Glick assigned an issue to Ilya Ilba Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Jesse Glick Assignee: Ilya Ilba 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.192600.1532377276000.7261.1566414000277%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Bruce Evans commented on JENKINS-40292 Re: More Control of p4 task logging Apologies!! William – I misunderstood. you were asking Paul to discuss with 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.176946.1481141079000.7257.1566413520196%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title Bruce Evans commented on JENKINS-40292 Re: More Control of p4 task logging Paul - thank you for responding and considering this! I'm finding in my environment, that we report lots of stuff when something fails, but when it works we just move on. I typically write the output of a command to a logfile, and if the operation fails, I echo the logfile to the console, otherwise, I just delete the logfile. It doesn't need to be a logfile, perhaps just storing the lines in an array, but you get the picture. Specifically about this "p4 sync" or "p4 unshelve", etc... I look at "node" step in console (or most other Jenkins API steps), and I see one line when node starts, and one line when the closure ends. Same for "stage", and quite a few others. For normal ops, I think that would be sufficient. Because there are many actual P4 commands being executed for each Jenkins API step, that is where the logging/fail/success comes in. I hope I'm answering your question. I see this as default logging is absolute minimum, but if something goes wrong, it shows on the console. The user has to do nothing. 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.176946.1481141079000.7250.1566413477955%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Sverre Moe commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Cleaned up, how? We also have experienced this problem that past few months. Recently we upgraded our Jenkins server Linux distribution from SLES12.3 to SLES15.0. This was done by creating a new VM and copied over the JENKINS_HOME. It has been running for 4 days now and we have not gotten the OutOfMemoryError. More time will tell if it is truly stable again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.7235.1566412800681%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba assigned an issue to Unassigned Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Ilya Ilba Assignee: Ilya Ilba 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.192600.1532377276000.7230.1566412440191%40Atlassian.JIRA.
[JIRA] (JENKINS-59028) Git Blamer: MissingObjectException: Missing commit
Title: Message Title Ulli Hafner closed an issue as Won't Fix The analysis-plugin is end-of-life. Please upgrade to the warnings-ng plugin. Jenkins / JENKINS-59028 Git Blamer: MissingObjectException: Missing commit Change By: Ulli Hafner Status: Open Closed Resolution: Won't 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.201382.1566392823000.7228.1566412140274%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba updated an issue Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Ilya Ilba Labels: junit-plugin user-experience 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.192600.1532377276000.7224.1566412020348%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba updated JENKINS-52711 Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Ilya Ilba 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.192600.1532377276000.7220.1566411840635%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba started work on JENKINS-52711 Change By: Ilya Ilba 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.192600.1532377276000.7218.1566411840574%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba assigned an issue to Ilya Ilba Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Ilya Ilba Assignee: Ilya Ilba 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.192600.1532377276000.7212.1566411780188%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba updated an issue Jenkins / JENKINS-52711 JUnit Results Trend graph doesn't show all build results if builds have been deleted Change By: Ilya Ilba 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.192600.1532377276000.7208.1566411480309%40Atlassian.JIRA.
[JIRA] (JENKINS-59035) Cannot configure oic-auth plugin with JCasC
Title: Message Title Tim Jacomb assigned an issue to Michael Bischoff Jenkins / JENKINS-59035 Cannot configure oic-auth plugin with JCasC Change By: Tim Jacomb Assignee: Ewelina Wilkosz Michael Bischoff 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.201389.1566406098000.7206.1566411420366%40Atlassian.JIRA.
[JIRA] (JENKINS-59035) Cannot configure oic-auth plugin with JCasC
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-59035 Cannot configure oic-auth plugin with JCasC Change By: Tim Jacomb Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201389.1566406098000.7202.1566411420277%40Atlassian.JIRA.
[JIRA] (JENKINS-52711) JUnit Results Trend graph doesn't show all build results if builds have been deleted
Title: Message Title Ilya Ilba commented on JENKINS-52711 Re: JUnit Results Trend graph doesn't show all build results if builds have been deleted I have made a pull request to fix this. https://github.com/jenkinsci/junit-plugin/pull/123 How can I get it reviewed? 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.192600.1532377276000.7197.1566411240160%40Atlassian.JIRA.
[JIRA] (JENKINS-57918) SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1
Title: Message Title Igor Sarkisov edited a comment on JENKINS-57918 Re: SCM Checkout: java.lang.ArrayIndexOutOfBoundsException: -1 We are experienced same problem after upgrading all Pipeline plugins, had to revert everything. 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.7188.1566411180573%40Atlassian.JIRA.
[JIRA] (JENKINS-33476) copyartifact uses incorrect permalink for promoted build
Title: Message Title Tony Wallace updated an issue Jenkins / JENKINS-33476 copyartifact uses incorrect permalink for promoted build Change By: Tony Wallace Summary: copyatrifact copyartifact uses incorrect permalink for promoted 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.168891.1457697475000.7184.1566408660269%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title William Brode commented on JENKINS-40292 Re: More Control of p4 task logging Paul Allen I care about this quite a bit and am willing to try to fix it. I wonder if you would be willing to talk with me about what you are/are not okay with in terms of the default logging and how people can control it? 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.176946.1481141079000.7179.1566408540339%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 does not use the credential and 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
[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
[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
[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 Priority: Major Critical 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.7173.1566407160107%40Atlassian.JIRA.
[JIRA] (JENKINS-32784) Update the "Integration Build" field in associated TFS work items
Title: Message Title Brian M commented on JENKINS-32784 Re: Update the "Integration Build" field in associated TFS work items Any update on this? It would be very useful for our QA folks. 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.167939.1454616051000.7171.1566406860202%40Atlassian.JIRA.
[JIRA] (JENKINS-59034) Shared library loading with credentials failed when a tag is used
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-59034 Shared library loading with credentials failed when a tag is used 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.201388.1566403456000.7167.1566406200165%40Atlassian.JIRA.
[JIRA] (JENKINS-59035) Cannot configure oic-auth plugin with JCasC
Title: Message Title CJ Harmath created an issue Jenkins / JENKINS-59035 Cannot configure oic-auth plugin with JCasC Issue Type: Bug Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin, oic-auth-plugin Created: 2019-08-21 16:48 Labels: jcasc-compatibility Priority: Major Reporter: CJ Harmath configuration-as-code/viewExport fails to display the oic-auth-plugin settings after manual configuration jenkins: agentProtocols: - "JNLP4-connect" - "Ping" disableRememberMe: false markupFormatter: "plainText" mode: NORMAL myViewsTabBar: "standard" numExecutors: 2 primaryView: all: name: "all" projectNamingStrategy: "standard" quietPeriod: 5 remotingSecurity: enabled: false scmCheckoutRetryCount: 0 securityRealm: |- FAILED TO EXPORT hudson.model.Hudson#securityRealm: io.jenkins.plugins.casc.ConfiguratorException: Can't read attribute 'automanualconfigure' from org.jenkinsci.plugins.oic.OicSecurityRealm@55ca3037 at io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:392) at io.jenkins.plugins.casc.Attribute.getValue(Attribute.java:214) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:283) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:283) at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201) at
[JIRA] (JENKINS-59034) Shared library loading with credentials failed when a tag is used
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59034 Shared library loading with credentials failed when a tag is used 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.201388.1566403456000.7164.1566406140356%40Atlassian.JIRA.
[JIRA] (JENKINS-57429) SYSTEM; is prohibited as a username for security reasons.
Title: Message Title Bogdan Grosu commented on JENKINS-57429 Re: SYSTEM; is prohibited as a username for security reasons. Anthony Green did you found a fix for 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.199241.1557750187000.7160.1566404940121%40Atlassian.JIRA.
[JIRA] (JENKINS-59034) Shared library loading with credentials failed when a tag is used
Title: Message Title L V created an issue Jenkins / JENKINS-59034 Shared library loading with credentials failed when a tag is used Issue Type: Bug Assignee: Mark Waite Components: git-plugin, workflow-cps-global-lib-plugin Created: 2019-08-21 16:04 Environment: os: rhel 6.6.0 jenkins: 2.164.3 Pipeline: Shared Groovy Libraries: 2.15 Git plugin: 3.12.0 Git client plugin: 2.8.0 Labels: pipeline jenkins plugin Priority: Major Reporter: L V Looks like JENKINS-52678 but with recent version of git-plugin (3.12.0) and with usage of credentials: lib = library( identifier: "mylib@tag", retriever: modernSCM( [$class: 'GitSCMSource', remote: "GITLAB_URL/mylib.git", credentialsId: 'MY_SSH_KEY'] ) ) When using a branch name as version (identifier: "mylib@branch_name"), the library is well loaded: Attempting to resolve branch_name from remote references... > git --version # timeout=10 using GIT_SSH to set credentials Cle SSH pour la connexion au gitlab > git ls-remote git@gitlab/mylib.git # timeout=10 Found match: refs/heads/branch_name revision
[JIRA] (JENKINS-40033) Tap Plugin not not calculating duration properly
Title: Message Title Ralf Payer commented on JENKINS-40033 Re: Tap Plugin not not calculating duration properly Could you please fix this bug. The wrong duration is very annoying to me and the fix seems to be very easy: dividing by 1000 at the right location(s). 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.176662.1480068463000.7156.1566403201099%40Atlassian.JIRA.
[JIRA] (JENKINS-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title Bogdan Sukonnov started work on JENKINS-59017 Change By: Bogdan Sukonnov 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.201370.1566329791000.7149.1566402540178%40Atlassian.JIRA.
[JIRA] (JENKINS-59033) Jenkinsfile Active Choice Parameter
Title: Message Title
Rashmi Nair updated an issue
Jenkins / JENKINS-59033
Jenkinsfile Active Choice Parameter
Change By:
Rashmi Nair
I am using jenkinsfile active choice reactive parameter as below: properties([ parameters([ [$class: 'ChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: 'Select templo code branch name', name: 'code_release_branch', script: [$class: 'GroovyScript', fallbackScript: [classpath: [], sandbox: false, script: 'return ["ERROR"]'], script: [classpath: [], sandbox: false, script: '6cd2a674-c02d-44b0-87cb-b32f1fcdc0c3']]], ]) ]) So in the script, I am passing the managed files id of the below groovy script. This works fine when I pass it as a parameter and pass this groovy script but when I pass it in jenkins file as mentioned above, it just populates "ERROR" in code_branch_name. |def gettags = ("git ls-remote -t -h [ https://USER:p...@bitbucket.org/project_name.git ] ").execute()|| |return gettags.text.readLines().collect {|| |it.split()[1].replaceAll('refs/heads/', '').replaceAll('refs/tags/', '').replaceAll("\\^ \ \ {\\} ", '')|| |}|
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-59017) Blank page after login just after finishing Setup Wizard
Title: Message Title
Bogdan Sukonnov updated an issue
Jenkins / JENKINS-59017
Blank page after login just after finishing Setup Wizard
Change By:
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. *For those who just need to fix it right now:*You can restart Jenkins with this URL: {code:java} http:///restart {code} or you can restart host, where Jenkins installed, or restart Jenkins in another way, depending of your installation.
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.7148.1566402480312%40Atlassian.JIRA.
