[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Darin Pope started work on JENKINS-59527 Change By: Darin Pope 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.202156.1569432268000.6361.1569531960344%40Atlassian.JIRA.
[JIRA] (JENKINS-59527) Trim white space from pipeline library name and version field
Title: Message Title Darin Pope updated an issue Jenkins / JENKINS-59527 Trim white space from pipeline library name and version field Change By: Darin Pope Labels: hacktoberfest newbie-friendly 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.202156.1569432268000.6359.1569531900149%40Atlassian.JIRA.
[JIRA] (JENKINS-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope updated an issue Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Change By: Darin Pope 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-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope created an issue Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Issue Type: Improvement Assignee: Unassigned Components: other Created: 2019-09-26 21:02 Labels: hacktoberfest newbie-friendly Priority: Minor Reporter: Darin Pope We have recently introduced support of GitHub documentation on the Jenkins Plugin Site. 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. 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
[JIRA] (JENKINS-59555) Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub
Title: Message Title Darin Pope assigned an issue to Darin Pope Jenkins / JENKINS-59555 Migrate workflow-cps-global-lib-plugin documentation from Wiki to GitHub Change By: Darin Pope Assignee: Darin Pope 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.202187.1569531759000.6356.1569531780219%40Atlassian.JIRA.
[JIRA] (JENKINS-38942) Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap
Title: Message Title Darin Pope created an issue Jenkins / JENKINS-38942 Stopped EC2 agents not waking up if the number of stopped EC2 agents equals the global Instance Cap Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Oct/12 9:57 PM Environment: ec2-plugin 1.34; aws-java-sdk 1.10.50 Priority: Minor Reporter: Darin Pope Steps to reproduce: set the global Instance Cap to 5 (or some other number) check the box for "Stop/Disconnect on Idle Timeout" so the instances stop instead of terminate set the "Idle termination time" to a low number so you don't have to wait too long after the jobs complete run a few jobs so you have some EC2 agents available to be stopped give some time for the EC2 agents to idle and stop change the global Instance Cap to equal the number of stopped EC2 agents Queue up some jobs to run again. The EC2 agents will not wake up and the following entry is in the log: hudson.plugins.ec2.EC2Cloud#provisionSlaveIfPossible: Cannot provision - no capacity for instances: -1 Variation on the issue: If you change the global Instance Cap to + 1 and you start running your jobs,
