[JIRA] (JENKINS-58230) how to disable automatic build by default?
Title: Message Title Jan Breuer commented on JENKINS-58230 Re: how to disable automatic build by default? At the bottom of the configuration page, there is "Branch names to build automatically" so just specify pattern you need. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200291.156160679.4565.1569394140167%40Atlassian.JIRA.
[JIRA] (JENKINS-52112) Private Gitea repositories are not visible
Title: Message Title Jan Breuer commented on JENKINS-52112 Re: Private Gitea repositories are not visible Verified it again and it does not work for me. If the jenkins account in gitea is not admin, it still can't see private repositories even if the account is listed in organisation members. It also fail to create web hooks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.191709.1529592502000.4561.1569393900174%40Atlassian.JIRA.
[JIRA] (JENKINS-57484) Improve API Token "API" capability, esp. for scripting
Title: Message Title blastik . commented on JENKINS-57484 Re: Improve API Token "API" capability, esp. for scripting as requested in https://github.com/jenkinsci/jenkins/pull/4027#issuecomment-534558658 I'm deploying a new Jenkins from scratch on a single host using Docker all on top of AWS. Its authentication mode is set to SAML (using Okta) and we configure it using JCasC (Configuration as code). The deployment strategy we decided is to deploy a new instance each time a configuration change is made. However, in order to give a good experience to our end users, we want to make 2 steps before swapping between old and new release: Put the old instance in Quiet mode. Query running builds When running query builds = 0 then swap the instance. We have no problem on doing that with the API but... the problem is that we depend on one single thing: the API token! Ideally we would like to add a fix token into JCasC file to be able to connect to the API once Jenkins the host has been configured. jenkins saml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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 ht
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Jeremy Mathevet commented on JENKINS-43820 Re: Stage name must be a string literal Please reconsider! There are some cases where this could be useful. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.181338.1493122184000.4532.1569393720625%40Atlassian.JIRA.
[JIRA] (JENKINS-56834) Build permission on agents is not working
Title: Message Title Wei Leong commented on JENKINS-56834 Re: Build permission on agents is not working I'm experiencing the same issue as well. Nuno Costa would you mind sharing how you got it working with RUN AS USER WHO TRIGGERED BUILD? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198493.1554129738000.4524.1569384422519%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title Jeff Y commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) +1 for this. Is there any workaround besides downgrading or manually going to the filesystem and looking at the log? I'm on a new Jenkins instance and can't downgrade, and checking the filesystem is pretty tedious as it sits on a box which only a few people have access to look at. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200683.1563381278000.4512.1569376980325%40Atlassian.JIRA.
[JIRA] (JENKINS-59467) Issue Template: Migrate documentation from Wiki to GitHub
Title: Message Title Zbynek Konecny updated an issue Jenkins / JENKINS-59467 Issue Template: Migrate documentation from Wiki to GitHub Change By: Zbynek Konecny We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site| [ https://plugins.jenkins.io/]. ] See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. Jenkins users seeking documentation will have a better user experience on plugins.jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. Documentation changes will be reviewed as part of pull requests and documentation contributors will be recognized, especially when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve, clone this issue and assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. The next time the plugin releases, the documentation will appear on https://plugins.jenkins.io/. Add Comment
[JIRA] (JENKINS-59520) EC2 Plugin 'Maximum Total Uses' counter resets itself when Stop/Disconnect on Idle Timeout is used
Title: Message Title Marc Jay created an issue Jenkins / JENKINS-59520 EC2 Plugin 'Maximum Total Uses' counter resets itself when Stop/Disconnect on Idle Timeout is used Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-09-24 22:38 Environment: EC2 Plugin 1.45 Jenkins 2.176.3 Priority: Minor Reporter: Marc Jay My expectation of selecting 'Stop/Disconnect on Idle Timeout' and setting a Maximum Total Uses value of, say, 10, would be that after running 5 jobs, the instance being stopped due to idle timeout, then 5 more jobs running on that instance, the instance would be terminated and the next job would launch on a new instance. What I am seeing is that after running 5 jobs and the Maximum Total Uses number dropping to 5, after the agent instance stops, and is then started again, the Maximum Total Uses remaining number resets itself to 10. The same instance has been used 5 times but that information is lost. Is this behaviour expected? If not, would a pull request be accepted or a fix be available to maintain the number of uses remaining across starting and stopping of an instance? Many thanks
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Richard Bywater commented on JENKINS-59511 Re: Error opening report with HTML Publisher Hi Henry Wilson - are you able to share a screenshot or similar of the HTML Publishing configuration too for reference? Also did this work on a previous version of the plugin and it has stopped working with the release of 1.19? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202133.1569334207000.4500.1569362880087%40Atlassian.JIRA.
[JIRA] (JENKINS-59519) Unable to install latest ssh-credentials-plugin
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-59519 Unable to install latest ssh-credentials-plugin Issue Type: Bug Assignee: Matt Sicker Components: ssh-credentials-plugin Created: 2019-09-24 22:06 Priority: Blocker Reporter: Gunter Grodotzki Throws 404: https://updates.jenkins.io/2.176/latest/ssh-credentials-plugin.hpi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master This does look like something caused by a change in Jenkins 2.168. I don't think it has anything to do with htmlpublisher plugin, so I've removed it from the components field. Specifically it is highly likely that the change for JENKINS-56114 caused this. This is similar to JENKINS-56249. Though the exact manifestations and cause are different, they concern the same areas of code. I'll see if I can figure something out to make it work better. It may take a while to get that change put together. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198193.1552641703000.4494.1569362160267%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Mark Waite commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo Vincenzo Melandri that seems like a separate bug report is needed. Pipeline has some overhead compared to Freestyle but that much overhead is beyond what I expected. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202115.1569286759000.4491.1569362100112%40Atlassian.JIRA.
[JIRA] (JENKINS-59518) Unable to uninstall windows-slaves plugin
Title: Message Title Gunter Grodotzki created an issue Jenkins / JENKINS-59518 Unable to uninstall windows-slaves plugin Issue Type: Bug Assignee: Emilio Escobar Components: windows-slaves-plugin Created: 2019-09-24 21:50 Environment: Jenkins ver. 2.176.3 Priority: Minor Reporter: Gunter Grodotzki For some reason it is not possible to uninstall the windows-slaves plugin. Add Comment
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title Timothy Klopotoski commented on JENKINS-59337 Re: "No such DSL method 'call'" when calling step within dynamically loaded library a second time If I modify the Jenkinsfile to import the parent and the child library, so that the dynamic import is redundant (i.e, it prints "Only using first definition of library child"), everything works. So, this problem seems scoped to libraries dynamically loaded using the `library` step. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201888.1568317781000.4484.1569361680438%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-56578 Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master Change By: Jeff Thompson Component/s: htmlpublisher-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198193.1552641703000.4480.1569361680344%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson edited a comment on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master ( I 'm trying to clarify the situations that lead to deleted this problem. It doesn't seem to be a general failure with htmlpublisher, as comment because it seems to work fine for me and there are relatively few people chiming in on this looks like I misread who was saying what . As [~rvangoethem] describes their experience, this issue involves junctions or symlinks further up the directory tree (somewhere in the job I ' s directory parentage) ll try again . By changing the configuration to not use symlinks, they no longer experienced these problems. Is that an accurate summary?[~r2b2_nz], is your configuration similar? Do you symlinks or junctions somewhere in the directory tree?I can see that 2.168 may have introduced changes that would cause problems in these sorts of configurations. ) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198193.1552641703000.4475.1569361620195%40Atlassian.JIRA.
[JIRA] (JENKINS-56578) Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master
Title: Message Title Jeff Thompson commented on JENKINS-56578 Re: Jenkins 2.168 prevent HTML Publisher to copy html report from agent to master I'm trying to clarify the situations that lead to this problem. It doesn't seem to be a general failure with htmlpublisher, as it seems to work fine for me and there are relatively few people chiming in on this. As Remi Van Goethem describes their experience, this issue involves junctions or symlinks further up the directory tree (somewhere in the job's directory parentage). By changing the configuration to not use symlinks, they no longer experienced these problems. Is that an accurate summary? Richard Bywater, is your configuration similar? Do you symlinks or junctions somewhere in the directory tree? I can see that 2.168 may have introduced changes that would cause problems in these sorts of configurations. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198193.1552641703000.4470.1569361020209%40Atlassian.JIRA.
[JIRA] (JENKINS-59239) Pipeline job's builds are missing in bulk after failure
Title: Message Title Ariel M closed an issue as Cannot Reproduce Jenkins / JENKINS-59239 Pipeline job's builds are missing in bulk after failure Change By: Ariel M Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201696.1567669735000.4467.1569358200110%40Atlassian.JIRA.
[JIRA] (JENKINS-58179) Jenkins builds disappearing from Unix machine due to open shift sync plugin issue
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58179 Jenkins builds disappearing from Unix machine due to open shift sync plugin issue Change By: Ariel M Comment: I don't think it's related to openshift... I've opened new case for it: https://issues.jenkins-ci.org/browse/JENKINS-59239BTW, I've found one case where they said "the whole _problem disappears after I uninstalled the JobConfigHistoryPlugin":_https://issues.jenkins-ci.org/browse/JENKINS-50595_ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200230.1561449713000.4465.1569358080166%40Atlassian.JIRA.
[JIRA] (JENKINS-58281) Pipeline job's builds are missing randomly in bulk
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58281 Pipeline job's builds are missing randomly in bulk Change By: Ariel M Comment: anyone is checking? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200345.1561974734000.4447.1569357960631%40Atlassian.JIRA.
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-50595 build history disappeared after upgrade to 2.107.1 Change By: Ariel M Comment: [~swf] do you think the uninstall of _JobConfigHistoryPlugin_ can help me solve this issue:https://issues.jenkins-ci.org/browse/JENKINS-59239 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.189669.1522939372000.4449.1569357960682%40Atlassian.JIRA.
[JIRA] (JENKINS-59467) Issue Template: Migrate documentation from Wiki to GitHub
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59467 Issue Template: Migrate documentation from Wiki to GitHub Change By: Mark Waite We have recently introduced support of GitHub documentation on the [Jenkins Plugin Site|[https://plugins.jenkins.io/].] See [https://groups.google.com/forum/#!topic/jenkinsci-dev/VSdfVMDIW-A] for the announcement. By supporting such source in plugin site we provide good user experience to Jenkins users who look for seeking documentation will have a better user experience on plugins . jenkins.io than they do on wiki.jenkins.io. At the same time, maintainers can follow the documentation-as-code approach and make documentation changes a part of pull requests. It gives an opportunity to review the documentation Documentation changes will be reviewed as part of pull requests and to add documentation contributor recognition contributors will be recognized , especially if the story is when combined with [Release Drafter|https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.adoc]. So, we We recommend all plugins to migrate documentation to GitHub.Steps: * Select a plugin you want to improve, clone this issue and set a proper assign the correct component ID * Review the plugin page on the Wiki and in the GitHub README. If there is missing information in the README, suggest submit a pull request with the documentation update * Modify the documentation URL in the project file: [https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Referencingthedocumentationpagefromtheprojectfile]Once the steps are completed and your pull request is merged by the maintainer, the GitHub landing page will be updated. After that, a The next time the plugin release will be needed to make this releases, the documentation will appear on the plugin site https://plugins.jenkins.io/. Add Comment
[JIRA] (JENKINS-59517) How can I add groovy code to String parameter fields in pipeline?
Title: Message Title Ariel M created an issue Jenkins / JENKINS-59517 How can I add groovy code to String parameter fields in pipeline? Issue Type: Bug Assignee: vjuranek Components: groovy-plugin, pipeline Created: 2019-09-24 20:32 Priority: Minor Reporter: Ariel M I have a pipeline job with some String parameters. I want to hide/disable them in case I'm choosing some active choice parameter, and I understood I can do it using groovy code. But I don't see such an option when choosing String parameter. Add Comment
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title Jesse Glick commented on JENKINS-44808 Re: Unable to print stacktrace on jenkins pipeline Or hudson.Functions.printThrowable, which displays causes a bit more nicely. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.182865.1497172331000.4434.1569354900275%40Atlassian.JIRA.
[JIRA] (JENKINS-59516) There is no way to pull LFS files for submodules in GIT
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59516 There is no way to pull LFS files for submodules in GIT Change By: Mark Waite Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202139.1569349462000.4432.1569351960196%40Atlassian.JIRA.
[JIRA] (JENKINS-59516) There is no way to pull LFS files for submodules in GIT
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59516 There is no way to pull LFS files for submodules in GIT Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202139.1569349462000.4430.1569351901539%40Atlassian.JIRA.
[JIRA] (JENKINS-59497) Git clone in pipeline ignoring reference repo
Title: Message Title Vincenzo Melandri commented on JENKINS-59497 Re: Git clone in pipeline ignoring reference repo I made a brand new job that just checkouts the repo and cats a file to isolate it from interference and I found out that it works, but there is still a massive difference: A test freestyle jobs checks out the repo in under 5 seconds, while the job defined with pipeline takes upward of 40s, which is still faster than a non-referenced checkout, which takes about 400 seconds.. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202115.1569286759000.4428.1569351720157%40Atlassian.JIRA.
[JIRA] (JENKINS-39374) Add ability to get SCM authentication tokens from Vault
Title: Message Title Richard Vodden assigned an issue to Richard Vodden Jenkins / JENKINS-39374 Add ability to get SCM authentication tokens from Vault Change By: Richard Vodden Assignee: Peter Tierno Richard Vodden Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175898.1477892147000.4419.1569350640663%40Atlassian.JIRA.
[JIRA] (JENKINS-59516) There is no way to pull LFS files for submodules in GIT
Title: Message Title Lucas Vander Wal commented on JENKINS-59516 Re: There is no way to pull LFS files for submodules in GIT See https://stackoverflow.com/q/58085269/6322589 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202139.1569349462000.4412.1569349560121%40Atlassian.JIRA.
[JIRA] (JENKINS-59516) There is no way to pull LFS files for submodules in GIT
Title: Message Title Lucas Vander Wal updated an issue Jenkins / JENKINS-59516 There is no way to pull LFS files for submodules in GIT Change By: Lucas Vander Wal Labels: git git-lfs git-submodule Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202139.1569349462000.4410.1569349500689%40Atlassian.JIRA.
[JIRA] (JENKINS-59516) There is no way to pull LFS files for submodules in GIT
Title: Message Title Lucas Vander Wal created an issue Jenkins / JENKINS-59516 There is no way to pull LFS files for submodules in GIT Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-09-24 18:24 Labels: git git-lfs Priority: Major Reporter: Lucas Vander Wal As far as I can tell, there is no way to checkout LFS files for git submodules using the Source Code Management tab of the configure screen. This means that I am currently unable to build projects with jenkins that are dependent on a git project with submodules that have LFS files. Add Comment
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Basil Crow commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Another option is to use Throwables#getStackTraceAsString:
try {
error 'foo'
} catch (err) {
echo Throwables.getStackTraceAsString(err)
}
Note that this requires approving the following method in Script Security:
staticMethod com.google.common.base.Throwables getStackTraceAsString java.lang.Throwable
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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.182865.1497172331000.4406.1569349500637%40Atlassian.JIRA.
[JIRA] (JENKINS-59515) Create reference documentation for Docker Workflow plugin
Title: Message Title Ovidiu-Florin Bogdan created an issue Jenkins / JENKINS-59515 Create reference documentation for Docker Workflow plugin Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-09-24 18:20 Labels: plugin pipeline user-experience plugins Priority: Minor Reporter: Ovidiu-Florin Bogdan The Docker Workflow documentation is structured as a tutorial/introduction on how to use the plugin. Because of this finding all the arguments a function can have, and finding all the functions an object has is difficult, if they are all listed in that documentation. A reference documentation page would greatly help with finding the information needed about how to use the functionality this plugin provides. For example check any of the declarative pipeline steps documentation: https://jenkins.io/doc/pipeline/steps/kubernetes-pipeline-steps/. Add Comment
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick updated JENKINS-58770 Jenkins / JENKINS-58770 Reconsider GAV scheme Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201075.156467412.4398.1569348480214%40Atlassian.JIRA.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Andrew Widdersheim commented on JENKINS-57528 Re: Jenkins in Docker does not install detached plugins when there is no UC data Daniel Beck any update on this? Was an issue ever made that I can track? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.199434.155810265.4391.1569346980350%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Travis Donia commented on JENKINS-59161 Re: ERROR: 530 Authentication required Can also say 1.28 doesn't resolve this for us either Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201598.1567204978000.4378.1569345600335%40Atlassian.JIRA.
[JIRA] (JENKINS-59514) Use @POST instead of @RequirePOST for form submission endpoints
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-59514 Use @POST instead of @RequirePOST for form submission endpoints Issue Type: Bug Assignee: Daniel Beck Components: core Created: 2019-09-24 16:52 Labels: robustness Priority: Minor Reporter: Daniel Beck Jenkins should not allow "attempt with POST" resubmissions of GET requests to form submission endpoints. They usually expects a form ( getSubmittedForm / structured form submission) with unexpected results when submission without a form is attempted (typically an exception stack trace, but who knows…) Add Comment
[JIRA] (JENKINS-39374) Add ability to get SCM authentication tokens from Vault
Title: Message Title Richard Vodden commented on JENKINS-39374 Re: Add ability to get SCM authentication tokens from Vault I did have a look at this, and then real life got in the way. Let me have a look at how far I got and at the very least push a branch up or something. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175898.1477892147000.4366.1569342900508%40Atlassian.JIRA.
[JIRA] (JENKINS-54499) Loosing connection to Docker container
Title: Message Title pjdarton closed an issue as Fixed This was fixed in PR-693 and that was released in version 1.1.6 Jenkins / JENKINS-54499 Loosing connection to Docker container Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.go
[JIRA] (JENKINS-58712) Docker tool configuration over Jenkins slaves
Title: Message Title pjdarton closed an issue as Not A Defect It doesn't work that way... Builds run on slave nodes. If your slave nodes don't have the docker client on them and don't have access to a docker daemon then your slave nodes have no docker capabilities, which is why your attempts to use those missing capabilities are failing. A machine without the docker daemon on it (and running) can't contain docker containers. A machine without a docker client on it can't talk to a docker daemon about docker containers. The docker-commons-plugin provides a Java docker client that's used by the docker-plugin to talk to docker daemons, but that capability is there for the Jenkins master and isn't really exposed to the slave nodes. If you want to run docker commands as part of a build process on a build slave node then you need to have build slave nodes that have the docker client on them and they either a link to another docker daemon (whether that's via the DOCKER_HOST env var or by cross-mounting /var/lib/docker.sock from the docker host into a docker container) or (to keep things nice and simple and isolated) their own running docker daemon (less efficient, but much simpler as every build gets its own docker daemon, so you don't get nasty collisions). TL;DR: If you want docker on your slave nodes, you need to install docker on your slave nodes. Jenkins / JENKINS-58712 Docker tool configuration over Jenkins slaves Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-59505) Minor typo fix to the pluginSetupWizard.properties file
Title: Message Title Mike Ajala assigned an issue to Mike Ajala Jenkins / JENKINS-59505 Minor typo fix to the pluginSetupWizard.properties file Change By: Mike Ajala Assignee: Mike Ajala Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202127.1569317932000.4359.1569340860166%40Atlassian.JIRA.
[JIRA] (JENKINS-59513) Defunct hyperlink in PULL_REQUEST_TEMPLATE.md
Title: Message Title Mike Ajala commented on JENKINS-59513 Re: Defunct hyperlink in PULL_REQUEST_TEMPLATE.md Created issue #4222 to that effect. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202136.1569338752000.4357.1569340680109%40Atlassian.JIRA.
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-58561 Seeing issue when i tried to push an image to ECR using docker pipeline plugin Change By: pjdarton Component/s: docker-workflow-plugin Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200711.1563472694000.4350.1569340140347%40Atlassian.JIRA.
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title pjdarton commented on JENKINS-58561 Re: Seeing issue when i tried to push an image to ECR using docker pipeline plugin Wrong component, sorry. You're using the docker-workflow-plugin, not the docker-plugin. I'll edit the "component affected" field... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200711.1563472694000.4347.1569340140298%40Atlassian.JIRA.
[JIRA] (JENKINS-58582) pending—'Jenkins' doesn't have label 'agent'
Title: Message Title pjdarton commented on JENKINS-58582 Re: pending—'Jenkins' doesn't have label 'agent' My guess is that your docker container doesn't have a /home/jenkins/ folder which is why, when you try to start a container using a template that's saying remoteFs='/home/jenkins', it's blowing up with a "not found" error. You need to ensure that the template configuration is correct for the docker image you're using. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200736.1563683406000.4344.1569340020384%40Atlassian.JIRA.
[JIRA] (JENKINS-58390) Docker cloud provisioning 1 slave behind
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58390 Docker cloud provisioning 1 slave behind Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200514.1562609303000.4322.1569339780203%40Atlassian.JIRA.
[JIRA] (JENKINS-58712) Docker tool configuration over Jenkins slaves
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58712 Docker tool configuration over Jenkins slaves Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201004.1564419517000.4325.1569339840408%40Atlassian.JIRA.
[JIRA] (JENKINS-58582) pending—'Jenkins' doesn't have label 'agent'
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58582 pending—'Jenkins' doesn't have label 'agent' Change By: pjdarton Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200736.1563683406000.4335.1569339840533%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) SPAM-Not an issue
Title: Message Title pjdarton closed an issue as Not A Defect Jenkins / JENKINS-58983 SPAM-Not an issue Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201332.1566190633000.4319.1569339600434%40Atlassian.JIRA.
[JIRA] (JENKINS-58983) SPAM-Not an issue
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-58983 SPAM-Not an issue Change By: pjdarton Summary: Jual Obat Erogan Asli Di Riau 0812 SPAM - 8282-3454 Gratis Ongkir Not an issue URL: https://agenobatbentrap.siterubix.com/ Priority: Minor Trivial Labels: plugin Released As: Jual Obat Erogan Asli Di Riau, Jual Obat Erogan Di Riau, Jual Erogan Di Riau, Erogan Asli Di Riau, Harga Jual Obat Erogan Di Riau, Erogan Di Riau, Agen Jual Erogan Di Riau. Environment: Jual Obat Erogan Asli Di Riau 081-2828-23454 Sprint: Post-launch Assignee: Joseph Petersen Add Comment
[JIRA] (JENKINS-59190) SPAM-Not an issue
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-59190 SPAM-Not an issue Change By: pjdarton Summary: Pusat Jual Obat Viagra Asli Dari Dokter Obat Kuat Herbal Di Apotik Bali SPAM-Not an issue URL: https://jualtitangelbali.com/jual-viagra-asli-bali/ Priority: Minor Trivial Labels: obatkuat viagra Assignee: Piyex Tokwae Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59190) SPAM-Not an issue
Title: Message Title pjdarton closed an issue as Not A Defect Jenkins / JENKINS-59190 SPAM-Not an issue Change By: pjdarton Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201631.1567441109000.4314.1569339480389%40Atlassian.JIRA.
[JIRA] (JENKINS-59513) Defunct hyperlink in PULL_REQUEST_TEMPLATE.md
Title: Message Title Mike Ajala updated an issue Jenkins / JENKINS-59513 Defunct hyperlink in PULL_REQUEST_TEMPLATE.md Change By: Mike Ajala Replaced a defunct The hyperlink in at the Pull Request Template top of [this file |https://github.com/jenkinsci/jenkins/blob/master/.github/PULL_REQUEST_TEMPLATE.md] is defunct and needs to be replaced with a simple, human-readable directive. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202136.1569338752000.4310.1569339180146%40Atlassian.JIRA.
[JIRA] (JENKINS-59513) Defunct hyperlink in PULL_REQUEST_TEMPLATE.md
Title: Message Title Mike Ajala updated an issue Jenkins / JENKINS-59513 Defunct hyperlink in PULL_REQUEST_TEMPLATE.md Change By: Mike Ajala Summary: Updated Defunct hyperlink in PULL_REQUEST_TEMPLATE.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202136.1569338752000.4306.1569339120237%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title pjdarton commented on JENKINS-59226 Re: Add support for declarative pipeline I have no idea how to do that ... but if you can find another plugin whose functionality can be called from a pipeline like that (and provide an example of its use), then I might take a look at how to do the same thing with this plugin. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201683.1567606546000.4308.1569339120272%40Atlassian.JIRA.
[JIRA] (JENKINS-59226) Add support for declarative pipeline
Title: Message Title pjdarton assigned an issue to Unassigned Jenkins / JENKINS-59226 Add support for declarative pipeline Change By: pjdarton Assignee: tspengler Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201683.1567606546000.4304.1569339060189%40Atlassian.JIRA.
[JIRA] (JENKINS-59513) Updated PULL_REQUEST_TEMPLATE.md
Title: Message Title Mike Ajala created an issue Jenkins / JENKINS-59513 Updated PULL_REQUEST_TEMPLATE.md Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-09-24 15:25 Labels: jenkins typo Priority: Trivial Reporter: Mike Ajala Replaced a defunct hyperlink in the Pull Request Template file with a simple, human-readable directive. Add Comment
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton resolved as Fixed Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-46375 vSphere template definition doesn't allow environment variables to be defined Change By: pjdarton Status: In Progress Resolved Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received t
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title pjdarton resolved as Fixed Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-41428 Tool Location Configuration Removed when Configuring System Change By: pjdarton Status: In Progress Resolved Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message becaus
[JIRA] (JENKINS-58136) vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration
Title: Message Title pjdarton updated JENKINS-58136 Fixed in plugin version 2.21, which was released a few minutes ago. Jenkins / JENKINS-58136 vSphere cloud plugin 2.19, Shutdown gracefully option is always unchecked when opening Configuration Change By: pjdarton Status: Fixed but Unreleased Resolved Assignee: Rudolf-Walter Kiss-Szakacs Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenk
[JIRA] (JENKINS-58711) "Container does not exist" error using "sh" in a declarative pipeline
Title: Message Title Panos Koumantos commented on JENKINS-58711 Re: "Container does not exist" error using "sh" in a declarative pipeline This issue seems to affect the kubernetes plugin version 1.12.4 as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201003.1564417291000.4286.1569337560218%40Atlassian.JIRA.
[JIRA] (JENKINS-26008) Use of compression during copying of artifacts cut throughput by a factor of 3
Title: Message Title Marat Radchenko commented on JENKINS-26008 Re: Use of compression during copying of artifacts cut throughput by a factor of 3 Fixed in PR#4205 and released in Jenkins-2.196. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.159586.1418239582000.4278.1569337380326%40Atlassian.JIRA.
[JIRA] (JENKINS-59512) I am getting timedout error while testing HP ALM connection throu Jenkins
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Aleksei Badyaev updated an issue Jenkins / JENKINS-59503 Plugin does not save settings Change By: Aleksei Badyaev Environment: Host: Debian 10 (buster) host. Jenkins ver. 2.176.3$ java -versionopenjdk version "11.0.4" 2019-07-16OpenJDK Runtime Environment (build 11.0.4+11-post-Debian-1deb10u1)OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Debian-1deb10u1, mixed mode, sharing) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202124.1569316263000.4268.1569336300247%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Aleksei Badyaev updated an issue Jenkins / JENKINS-59503 Plugin does not save settings Change By: Aleksei Badyaev Environment: Host: Debian 10 (buster)Jenkins ver. 2.176.3$ java -versionopenjdk version "11.0.4" 2019-07-16OpenJDK Runtime Environment (build 11.0.4+11-post-Debian-1deb10u1)OpenJDK 64-Bit Server VM (build 11.0.4+11-post-Debian-1deb10u1, mixed mode, sharing) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202124.1569316263000.4270.1569336300270%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Aleksei Badyaev updated an issue Jenkins / JENKINS-59503 Plugin does not save settings Change By: Aleksei Badyaev I can't save plugin settings in the job configuration in Jenkins.In the screenshot "Rocket.Chat plugin 1.png" I set up notifications.Then clicked "save".Then again open the job settings and saw that in the screenshot "Rocket.Chat plugin 2.png".In the file " confix config .xml" I put the node of the plugin settings in the job configuration file. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202124.1569316263000.4264.1569336240188%40Atlassian.JIRA.
[JIRA] (JENKINS-36720) Investigate/cleanup medium-severity FindBugs issues in the Jenkins core
Title: Message Title Daniel Beck commented on JENKINS-36720 Re: Investigate/cleanup medium-severity FindBugs issues in the Jenkins core Is this done completely in 2.191, or just partially? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.172755.1468600777000.4261.1569336060210%40Atlassian.JIRA.
[JIRA] (JENKINS-59406) Unable to open view with emoji and then a space at beginning of name
Title: Message Title Daniel Beck updated JENKINS-59406 Jenkins / JENKINS-59406 Unable to open view with emoji and then a space at beginning of name Change By: Daniel Beck Status: Fixed but Unreleased Closed Released As: jenkins-2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201964.1568717826000.4254.1569336001245%40Atlassian.JIRA.
[JIRA] (JENKINS-26008) Use of compression during copying of artifacts cut throughput by a factor of 3
Title: Message Title Daniel Beck closed an issue as Fixed Jenkins / JENKINS-26008 Use of compression during copying of artifacts cut throughput by a factor of 3 Change By: Daniel Beck Status: Open Closed Resolution: Fixed Released As: jenkins-2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.159586.1418239582000.4252.1569336001221%40Atlassian.JIRA.
[JIRA] (JENKINS-53322) Remove patched dom4j from Stapler
Title: Message Title Daniel Beck closed an issue as Fixed Jenkins / JENKINS-53322 Remove patched dom4j from Stapler Change By: Daniel Beck Status: Open Closed Resolution: Fixed Released As: jenkins-2.194 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.4257.1569336001284%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Daniel Beck updated JENKINS-58779 Jenkins / JENKINS-58779 LogRotator stops cleaning, if a build directory has been deleted externally Change By: Daniel Beck Status: Fixed but Unreleased Closed Released As: jenkins-2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201089.1564737737000.4245.1569335940391%40Atlassian.JIRA.
[JIRA] (JENKINS-59231) Improve test coverage on the RSS feature
Title: Message Title Daniel Beck closed an issue as Fixed Jenkins / JENKINS-59231 Improve test coverage on the RSS feature Change By: Daniel Beck Status: Open Closed Resolution: Fixed Released As: jenkins-2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201688.1567615347000.4243.1569335940351%40Atlassian.JIRA.
[JIRA] (JENKINS-59503) Plugin does not save settings
Title: Message Title Peter Daum commented on JENKINS-59503 Re: Plugin does not save settings Same issue on our system. We using Jenkins 2.196 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202124.1569316263000.4241.1569335880165%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Valentin Delaye commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 Hi! Thanks for the updates! Do you think it's something that can be fix "easily" ? Thanks for the help and confirming the issue. Regards, Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201849.156813782.4234.1569335340245%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Marat Radchenko commented on JENKINS-59152 Re: Jenkins fails to properly abort "bat" step See comments to PR#4216 for additional technical analysis. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201589.1567181048000.4232.1569335220051%40Atlassian.JIRA.
[JIRA] (JENKINS-59511) Error opening report with HTML Publisher
Title: Message Title Henry Wilson created an issue Jenkins / JENKINS-59511 Error opening report with HTML Publisher Issue Type: Bug Assignee: Richard Bywater Attachments: CodeCoverage.zip, Screenshot 2019-09-24 at 15.07.17.png, Screenshot 2019-09-24 at 15.07.29.png Components: htmlpublisher-plugin Created: 2019-09-24 14:10 Environment: Jenkins 2.176.3, HTML Publisher 1.19 Priority: Minor Reporter: Henry Wilson Our CodeCoverage reports on Jenkins are no longer viewable - when you click the link in the menu we now see a blank screen with no tabs and no content, just the "Back to build" and "zip" links. Clicking the "zip" link allows the report to be downloaded, and it can be opened locally. Opening the Chrome dev tools, there is an error "Uncaught TypeError: Cannot read property 'setAttribute' of null" I've attached screenshots, and the report zip.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title candrews commented on JENKINS-59493 Re: Must include region in s3 bucket URL; support for GovCloud Here's a pull request: https://github.com/jenkinsci/artifact-manager-s3-plugin/pull/97 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202109.1569270343000.4229.1569332400108%40Atlassian.JIRA.
[JIRA] (JENKINS-58033) error when remove docker slave
Title: Message Title pjdarton closed an issue as Not A Defect It's not a bug. The docker-plugin uses the dockerjava library and the dockerjava library (needlessly) logs a lot of exceptions as "SEVERE" that are part of its official API, that are perfectly normal and are passed up to the calling code (the docker-plugin) to decide what to do about it. The dockerjava library is a bit of a drama queen - you can ignore 99.999% of these exceptions. Most of what it logs is just saying something line "OMG! Red alert! Panic! Something normal happened!" e.g. if you ask it (dockerjava) to stop a container that's already stopped, it'll tell you that the container has already stopped, so you know that you can then go ahead and then ask it to remove it ... but it'll also log an error along the lines of "It's a total disaster! We didn't actually need to do anything after all". Similarly, when we're making sure a container is gone, we'll ask it to remove the container and, if there's nothing to be done because the container no longer exists, it'll log severe exceptions as it panics about the fact that what it'd been asked to do had already been done and no further action was necessary. Sadly, there's no way of telling it not to log the exceptions that it's also passing back to whatever called it (the docker-plugin code in this case, which knows that no panic is necessary in this situation). All you can do is filter those out of the log. The problem is that sometimes dockerjava really does have something worth mentioning and, in such cases, an exception will get passed up by the dockerjava code to whatever was calling it, and "whatever was calling it" will have an exception it doesn't know how to handle ... at which point "whatever was calling it" will log an error, so you'll see the dockerjava exception is immediately followed by the "whatever was calling it" error. In such circumstances, the exception that dockerjava logged may provide useful additional information as to what actually went wrong. TL;DR: Ignore everything logged by dockerjava unless it's also accompanied by an error raised by other (less shouty) code. Jenkins / JENKINS-58033 error when remove docker slave Change By: pjdarton Status: Open Closed Assignee: Nicolas De Loof Resolution: Not A Defect
[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage
Title: Message Title runze xia updated JENKINS-47591 Jenkins / JENKINS-47591 Allow each Kubernetes slave pod to use unique Persistent Volume / Storage Change By: runze xia Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.186064.1508775809000.4218.1569330300579%40Atlassian.JIRA.
[JIRA] (JENKINS-56624) docker.build
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-56624 docker.build Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.198251.1553020753000.4216.1569330240184%40Atlassian.JIRA.
[JIRA] (JENKINS-54155) Jobs using docker agents disrupt each other if triggered simultaneously
Title: Message Title pjdarton commented on JENKINS-54155 Re: Jobs using docker agents disrupt each other if triggered simultaneously This is probably because docker containers are specifically designed to do one and only one job and then be destroyed. If you're having more than one bit of work run on a container then that's not going to go well - you need to ensure that your pipeline code takes over one node exclusively and uses it exclusively until it's done with it - no sharing. If you've got multiple pipelines all after the same template then Jenkins should spin up multiple containers for that workload - we shouldn't have any jobs sharing containers... I'm sorry I don't have a specific answer for this one - if it's still an problem with the latest release then please do see what else you can find out; of not, please close the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.194784.1539930502000.4213.1569330180159%40Atlassian.JIRA.
[JIRA] (JENKINS-59510) Unable to use User scoped credentials in Matrix Job
Title: Message Title Manuel Cardenas updated an issue Jenkins / JENKINS-59510 Unable to use User scoped credentials in Matrix Job Change By: Manuel Cardenas * Create a Matrix Job. * Define Credentials parameter. * Define Credentials binding AWS access key and secret.Try to pass a user scoped credential as parameter , assign the parameter to the binding and use it in the job. It will not work. The same setup works for a freestyle job.It would be great if the user scoped credential could work in a matrix job. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202132.1569329832000.4211.1569329940323%40Atlassian.JIRA.
[JIRA] (JENKINS-59510) Unable to use User scoped credentials in Matrix Job
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-59510 Unable to use User scoped credentials in Matrix Job Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2019-09-24 12:57 Environment: Jenkins 2.164.x matrix-project 1.14 Credentials binding 1.18 Credentials 2.1.18 Priority: Minor Reporter: Manuel Cardenas Create a Matrix Job. Define Credentials parameter. Define Credentials binding AWS access key and secret. Try to pass a user scoped credential as parameter and use it in the job. It will not work. The same setup works for a freestyle job. It would be great if the user scoped credential could work in a matrix job. Add Comment
[JIRA] (JENKINS-53668) hudson.remoting.ChannelClosedException
Title: Message Title pjdarton closed an issue as Incomplete Without further information, it won't be possible to debug this. If you're still experiencing this issue, and getting it with a recent version of the plugin, please add log information (see https://github.com/jenkinsci/docker-plugin/blob/master/CONTRIBUTING.md for hints about this) and re-open the issue. Jenkins / JENKINS-53668 hudson.remoting.ChannelClosedException Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title pjdarton commented on JENKINS-53259 Re: Jenkins Pipeline build fails when trying to jenkins docker plugin FYI pipeline code like withDockerServer means you're using the docker-workflow-plugin not the docker-plugin. I've updated the "components" field accordingly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193334.1535391573000.4199.1569329580261%40Atlassian.JIRA.
[JIRA] (JENKINS-53259) Jenkins Pipeline build fails when trying to jenkins docker plugin
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53259 Jenkins Pipeline build fails when trying to jenkins docker plugin Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193334.1535391573000.4191.1569329520323%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53208 Split main configuration page, takes too long to load Change By: pjdarton Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193234.1535030695000.4189.1569329340401%40Atlassian.JIRA.
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton updated an issue Jenkins / JENKINS-53208 Split main configuration page, takes too long to load Change By: pjdarton Over time, we encountered that the main Jenkins configuration page took longer and longer to load. We suspect that this stems from an ever increasing number of Docker agent templates defined in clouds , which also multiplies by the number of configured Docker clouds.It would therefor be nice if some parts were seprated separated from the main configuration, namely said Docker clouds incl. agent templates and maybe the global environment variables (we also have quite a few of them). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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/msg
[JIRA] (JENKINS-53208) Split main configuration page, takes too long to load
Title: Message Title pjdarton commented on JENKINS-53208 Re: Split main configuration page, takes too long to load I think that this issue isn't really about the docker-plugin, but it's more about the core - when there are a lot of "cloud" instances configured, the main config page takes ages to load. We've got the same symptoms, but that's mostly from vSphere and OpenStack clouds - there's a lot of field verification going on all at once, and this takes time. FYI one of the changes I made to the docker plugin was to hide a lot of information within "optional" sections so that the web-page wasn't horribly long by default, allowing the Jenkins admin to only "expand" the sections they were interested in, but this doesn't make much difference to loading speed, only to the visual appearance and navigability of the page. I think the solution here is for the core to automatically split out the "Clouds" bit into multiple pages when it starts to get large. That isn't an enhancement that belongs to the docker-plugin, that's a wider issue. What I would suggest is that the Jenkins main jelly code has some sort of "if clouds.size>=1 then punt Clouds into its own page" logic, e.g. have a separate "Clouds" section that magically appears when clouds.size>=1 and have the "Clouds" section in the main config magically turn from the current menu/list (that can become huge and slow) into a link to that new page whenever clouds.size >= 1. ...or, alternatively, make it unconditional, much like what was done when the Jenkins "thread dump" functionality was moved to its own page. Either way, it's not something that the docker-plugin can do on its own - that's a core issue. I'll amend the "components" field accordingly... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58770) Reconsider GAV scheme
Title: Message Title Jesse Glick started work on JENKINS-58770 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201075.156467412.4183.1569329040164%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Pavly Farag commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Hi Team, We are also having the same bahavior listing lot of idle executors only for master whenever master executor is set to 0. and it keeps increasing with time.. for now it reached 112 lines, we are using Jenkins 2.189 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.199072.1556795988000.4177.1569328980200%40Atlassian.JIRA.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Pavly Farag updated an issue Jenkins / JENKINS-57304 Multiple "idle" entries on Build Executor Status for non-existant executors Change By: Pavly Farag Attachment: image-2019-09-24-14-41-25-787.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.199072.1556795988000.4175.1569328920412%40Atlassian.JIRA.
[JIRA] (JENKINS-59509) unable to read config file
Title: Message Title Victor Martinez commented on JENKINS-59509 Re: unable to read config file This is not an issue with the jenkinslint plugin but something else, besides it seems an environmental issue based on the stacktrace details. I just unassigned myself, as I'm not an expert on this matter, but for what I see the /var/jenkins_home/jobs/OMI-Runner/config.xml seems to cause that issue, so worth to check whether the file exists in the JENKINS_HOME, with the right user/group and privileges. Besides whether the content fo the file follows the xml specification. Cheers Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202131.1569325561000.4167.1569328560308%40Atlassian.JIRA.
[JIRA] (JENKINS-59509) unable to read config file
Title: Message Title Victor Martinez assigned an issue to Unassigned Jenkins / JENKINS-59509 unable to read config file Change By: Victor Martinez Assignee: Victor Martinez Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202131.1569325561000.4169.1569328560337%40Atlassian.JIRA.
[JIRA] (JENKINS-59509) unable to read config file
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59509 unable to read config file Change By: Victor Martinez Component/s: other Component/s: jenkinslint-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202131.1569325561000.4165.1569328440390%40Atlassian.JIRA.
[JIRA] (JENKINS-59509) unable to read config file
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59509 unable to read config file Change By: Victor Martinez Priority: Critical Trivial Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202131.1569325561000.4163.1569328440361%40Atlassian.JIRA.
[JIRA] (JENKINS-45227) Need support for docker labels ( --label )
Title: Message Title pjdarton closed an issue as Fixed Jenkins / JENKINS-45227 Need support for docker labels ( --label ) Change By: pjdarton Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.183357.1498777378000.4159.1569328260725%40Atlassian.JIRA.
[JIRA] (JENKINS-45227) Need support for docker labels ( --label )
Title: Message Title pjdarton commented on JENKINS-45227 Re: Need support for docker labels ( --label ) Support for setting user-specified labels was added by PR-747. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.183357.1498777378000.4157.1569328260702%40Atlassian.JIRA.
[JIRA] (JENKINS-33627) Docker Plug-in: Changelog is not generated
Title: Message Title pjdarton closed an issue as Incomplete Jenkins / JENKINS-33627 Docker Plug-in: Changelog is not generated Change By: pjdarton Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.169074.1458231512000.4152.1569328020276%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title pjdarton commented on JENKINS-58837 Re: withDockerRegistry on multiple clusters FYI withDockerRegistry etc come from the docker-workflow-plugin, not the docker-plugin. I've updated the components field accordingly. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201152.1565148699000.4150.1569327840380%40Atlassian.JIRA.
