[JIRA] (JENKINS-49781) Please provide a means for securely providing credentials for Kubernetes deployments.
Title: Message Title Menghua Xiao resolved as Fixed Resolved in release 0.2.0. Now you can configure "Kubernetes configuration (kubeconfig)" in the Jenkins credentials store, and reference the kubeconfig using the credentials ID in your job configuration. Jenkins / JENKINS-49781 Please provide a means for securely providing credentials for Kubernetes deployments. Change By: Menghua Xiao Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-50649) Warning on path to python executables
Title: Message Title Antonio Alaniz created an issue Jenkins / JENKINS-50649 Warning on path to python executables Issue Type: Bug Assignee: Unassigned Components: shiningpanda-plugin Created: 2018-04-08 00:52 Environment: Jenkins 2.113 ShiningPanda 0.23 Priority: Minor Reporter: Antonio Alaniz Similar to JENKINS-29651, a path to /usr/bin/python3.6 yields a warning-- /usr/bin/python.36 is not a directory on the Jenkins master (but perhaps it exists on some agents) Documentation seems to indicate that either is acceptable. Add Comment
[JIRA] (JENKINS-50648) Update Dynamic Choice Parameter plugin to use Script Security Plugin
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-50648 Update Dynamic Choice Parameter plugin to use Script Security Plugin Issue Type: New Feature Assignee: Unassigned Components: dynamicparameter-plugin Created: 2018-04-08 00:40 Priority: Minor Reporter: Sam Gleske As an admin of Jenkins, I wish to install the Dynamic Choice Parameter plugin and use it from the Jenkins Update Center. Please update this plugin to use the Script Security plugin so that it can be added back to the JUC to be available for users to download. Add Comment
[JIRA] (JENKINS-50647) Remove Scriptler as a hard dependency to Dynamic Parameter Plugin
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-50647 Remove Scriptler as a hard dependency to Dynamic Parameter Plugin Issue Type: New Feature Assignee: Unassigned Components: dynamicparameter-plugin Created: 2018-04-08 00:37 Priority: Minor Reporter: Sam Gleske I don't like using the scriptler plugin and don't want it installed. I like keeping my Jenkins instance as slim as possible. I want to use the Dynamic Choice Parameter script. Please remove the Scriptler plugin as a hard dependency so that I can use my own Groovy scripts from an embedded value. Add Comment
[JIRA] (JENKINS-50177) Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Title: Message Title
Long Vu edited a comment on JENKINS-50177
Re: Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Hi [~daspilker],Brown bag on face here, I forgot to change from pipelineJob to multibranchPipelineJob !So jobDSL does work, but the created job is not working.Now I get a different error when the job tries to scan of existing branches:{noformat}[Sat Apr 07 14:40:18 EDT 2018] Starting branch indexing...ERROR: No configured Mercurial installation[Sat Apr 07 14:40:18 EDT 2018] Finished branch indexing. Indexing took 1 ms{noformat}It is exactly like this error - - JENKINS-47040- - and solution there was to go onto the GUI and add it. But that completely defeat the purpose of using JobDSL because we want to fully automate job creating. I tried to add the mercurial installation via the GUI anyways, then the job does work but next run of JobDSL will remove it.We will also need to add "clean build" in addition to "mercurial installation" for this multibranchPipelineJob to work properly, like for [https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-definition-cpsScm-scm-hg].Let me know if I should open a new issue or reopen this one , because as it stands, mercurial support for multibranchPipelineJob is there but is not usable .Thanks.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-50177) Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Title: Message Title Long Vu commented on JENKINS-50177 Re: Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob Hi Daniel Spilker, Brown bag on face here, I forgot to change from pipelineJob to multibranchPipelineJob ! So jobDSL does work, but the created job is not working. Now I get a different error when the job tries to scan of existing branches: [Sat Apr 07 14:40:18 EDT 2018] Starting branch indexing... ERROR: No configured Mercurial installation [Sat Apr 07 14:40:18 EDT 2018] Finished branch indexing. Indexing took 1 ms It is exactly like this error JENKINS-47040 and solution there was to go onto the GUI and add it. But that completely defeat the purpose of using JobDSL because we want to fully automate job creating. I tried to add the mercurial installation via the GUI anyways, then the job does work but next run of JobDSL will remove it. We will also need to add "clean build" in addition to "mercurial installation" for this multibranchPipelineJob to work properly, like for https://jenkinsci.github.io/job-dsl-plugin/#path/pipelineJob-definition-cpsScm-scm-hg. Let me know if I should open a new issue or reopen this one. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Varun Reddy commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. After setting the PATH_MAX = 0 the issue with long path has been resolved. I am still having issues with / as my branch name is release/1.0.0. Is there a solution for this problem? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25910) Nodes are not sorted on label overview page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25910 Re: Nodes are not sorted on label overview page Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/Label.java core/src/main/resources/hudson/model/Label/index.jelly http://jenkins-ci.org/commit/jenkins/70c408cedf429ce79fdec8998635f58b4f7a02ca Log: [FIXED JENKINS-25910] Sort nodes for label for UI (#1498) [FIXED JENKINS-25910] Sort nodes for label for UI JENKINS-25910 Sort Jenkins master at beginning Consistent sort order JENKINS-25910 Instead use dedicated UI support method Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50585) Extend pipeline-library runAth() function to allow calling full ATH suite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50585 Re: Extend pipeline-library runAth() function to allow calling full ATH suite Code changed in jenkins User: Oleg Nenashev Path: essentials.yml http://jenkins-ci.org/commit/jenkins/b6dc5038c9103727d40b7725a6128bfc7041932e Log: Merge pull request #3381 from olivergondza/JENKINS-50585 JENKINS-50585 Explicitly declared core builds against ATH smoke tests only Compare: https://github.com/jenkinsci/jenkins/compare/4eb3496a9e31...b6dc5038c910 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50585) Extend pipeline-library runAth() function to allow calling full ATH suite
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50585 Re: Extend pipeline-library runAth() function to allow calling full ATH suite Code changed in jenkins User: Oliver Gondža Path: essentials.yml http://jenkins-ci.org/commit/jenkins/e2c2e35cc5c2b2672eb3f6d6969178688ac78d9c Log: JENKINS-50585 Explicitly declared core builds against ATH smoke tests only Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati updated JENKINS-50026 Jenkins / JENKINS-50026 Hubot Steps 2.0.0 Enhancements List Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50615) Plugin documentation update.
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50615 Plugin documentation update. Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50615) Plugin documentation update.
Title: Message Title Naresh Rayapati commented on JENKINS-50615 Re: Plugin documentation update. PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. For now just update readme, will log a follow to make github pages. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50612) Support sending custom data to hubot server
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50612 Support sending custom data to hubot server Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50612) Support sending custom data to hubot server
Title: Message Title Naresh Rayapati commented on JENKINS-50612 Re: Support sending custom data to hubot server PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50614) Provide hubot examples for slack attachments
Title: Message Title Naresh Rayapati commented on JENKINS-50614 Re: Provide hubot examples for slack attachments PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50613) Send envVars to hubot to support more smart messages
Title: Message Title Naresh Rayapati commented on JENKINS-50613 Re: Send envVars to hubot to support more smart messages PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50613) Send envVars to hubot to support more smart messages
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50613 Send envVars to hubot to support more smart messages Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50614) Provide hubot examples for slack attachments
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50614 Provide hubot examples for slack attachments Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50611) Support Tokens Macro
Title: Message Title Naresh Rayapati commented on JENKINS-50611 Re: Support Tokens Macro PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50610) Build Notifications
Title: Message Title Naresh Rayapati commented on JENKINS-50610 Re: Build Notifications PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch (last value wins) 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch (first value wins) # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional.I'll start the work to adjust the git client plugin and/or the git plugin to adapt to the OpenSSH behavior change.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50610) Build Notifications
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50610 Build Notifications Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50611) Support Tokens Macro
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50611 Support Tokens Macro Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50609) Folder Level configuration (sites)
Title: Message Title Naresh Rayapati commented on JENKINS-50609 Re: Folder Level configuration (sites) PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50609) Folder Level configuration (sites)
Title: Message Title Naresh Rayapati resolved as Fixed Jenkins / JENKINS-50609 Folder Level configuration (sites) Change By: Naresh Rayapati Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44401) Enhance hubotApprove to allow more fields that input step supports
Title: Message Title Naresh Rayapati commented on JENKINS-44401 Re: Enhance hubotApprove to allow more fields that input step supports PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44401) Enhance hubotApprove to allow more fields that input step supports
Title: Message Title Naresh Rayapati updated JENKINS-44401 Jenkins / JENKINS-44401 Enhance hubotApprove to allow more fields that input step supports Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50608) Global Configuration to support multiple hubot servers
Title: Message Title Naresh Rayapati updated JENKINS-50608 Jenkins / JENKINS-50608 Global Configuration to support multiple hubot servers Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50608) Global Configuration to support multiple hubot servers
Title: Message Title Naresh Rayapati commented on JENKINS-50608 Re: Global Configuration to support multiple hubot servers PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50608) Global Configuration to support multiple hubot servers
Title: Message Title Naresh Rayapati updated JENKINS-50608 Jenkins / JENKINS-50608 Global Configuration to support multiple hubot servers Change By: Naresh Rayapati Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44401) Enhance hubotApprove to allow more fields that input step supports
Title: Message Title Naresh Rayapati updated JENKINS-44401 Jenkins / JENKINS-44401 Enhance hubotApprove to allow more fields that input step supports Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati updated JENKINS-50026 Jenkins / JENKINS-50026 Hubot Steps 2.0.0 Enhancements List Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlierProblem is specific to OpenSSH 7.7 which is included with the Windows version of git 2.17.0. The behavior of the "-l" command line argument changed in the ssh command in OpenSSH 7.7. Previously the last argument value was used and did not override the username in the connection string ("URI"). Now the first argument value is used and it overrides the username in the connection string. The same problem is likely visible with OpenBSD 6.3, the first version that includes OpenSSH 7.7.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati commented on JENKINS-50026 Re: Hubot Steps 2.0.0 Enhancements List PR: https://github.com/jenkinsci/hubot-steps-plugin/pull/11 merged to master, Will release it after further testing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
I've duplicated the problem in my environment. Alternatives include:# Enable JGit in your installation and configure the job to use JGit instead of command line git# Use Windows command line git 2.16.2 or earlier I'll start a conversation with the git for windows team to understand what may have changed in the handling of GIT_SSH authentication settings. The git plugin may need to be updated to follow the technique recommended in JENKINS-32883 if it detects a modern enough version of command line git. Problem appears to be is specific to OpenSSH 7.7 which is included with the Windows version of git 2.17.0. I compiled git 2 The behavior of the "-l" command line argument changed in the ssh command in OpenSSH 7 . 17 7 . 0 on Ubuntu 16.04 Previously the last argument value was used and did not override the username in the connection string ("URI"). Now the first argument value is used and it successfully with overrides the Jenkins git plugin username in the connection string .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional. I'll start the work to adjust the git client plugin and/or the git plugin to adapt to the OpenSSH behavior change.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used.[OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change.Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849 [ ] |http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change is intentional.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Mark Waite edited a comment on JENKINS-50573
Re: Wrong username used for clone with Git 2.17 on Windows
OpenSSH 7.7 changed the order of evaluation of login_name. OpenSSH 7.7 is first bundled in Git for Windows 2.17.0. [OpenSSH bug 2385|http://bugzilla.mindrot.org/show_bug.cgi?id=2385] describes the prior order as:{quote}1. user specified before @ character in hostname string 2. login_name specified using -l switch 3. User option provided as a parameter to -o switch 4. User option in matching Host block from per-user config ~/.ssh/config 5. User option in matching Host block from systemwide config /etc/ssh/ssh_config If there is nothing from above specified, username on local terminal is used.{quote}The OpenSSH 7.7 login_name evaluation order is: # login_name specified using -l switch # user specified before @ character in hostname string # User option provided as a parametr to -o switch # User option in matching Host block from per-user config ~/.ssh/config # User option in matching Host block from systemwide config /etc/ssh/ssh_configIf there is nothing from above specified, username on local terminal is used. [OpenSSH Portable bug 2849|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] has been submitted to track the change. Johannes Schindelin of the Git for Windows project has submitted a [pull request|https://github.com/openssh/openssh-portable/pull/91] to the OpenSSH Portable project. It is not yet clear if The OpenSSH project has closed the [bug report|http://bugzilla.mindrot.org/show_bug.cgi?id=2849[]|http://bugzilla.mindrot.org/show_bug.cgi?id=2849] as "Won't Fix". Damien Miller states that the behavior change of order of evaluation is intentional or not .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50646) There is no way to trigger a branch build in BO when no build exists yet
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-50646 There is no way to trigger a branch build in BO when no build exists yet Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-04-07 at 12.26.24.png, Screen Shot 2018-04-07 at 12.26.30.png Components: blueocean-plugin Created: 2018-04-07 12:09 Environment: 1.4.2 · Core 2.107.1 · e5955c2 · 16th February 2018 10:54 PM Priority: Minor Reporter: Daniel Beck I opened a PR to jenkins infra, and it got the 'building' status on GitHub. Something happened in Jenkins, and there's no build of the branch project. Clicking on the link to BO (to the PR project) just redirects to the repo folder at https://ci.jenkins.io/blue/organizations/jenkins/Infra%2Fjenkins.io/activity (rather than the branch job), and there's no obvious way to start a build of the branch. Screenshots of GitHub and Jenkins (non BO) attached.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Hao RUIJIE updated JENKINS-50638 Jenkins / JENKINS-50638 windows agent via SSH - Slave JVM has terminated. Exit code Change By: Hao RUIJIE Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50638) windows agent via SSH - Slave JVM has terminated. Exit code
Title: Message Title Hao RUIJIE started work on JENKINS-50638 Change By: Hao RUIJIE Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-50645 Post failure condition should be evaluated after other conditions Change By: Liam Newman Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50645) Post failure condition should be evaluated after other conditions
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-50645 Post failure condition should be evaluated after other conditions Issue Type: Task Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-04-07 07:10 Priority: Major Reporter: Liam Newman The post "failure" condition fires after the "always" condition (and I number of others), but before the "success" condition and "aborted" conditions. This means that if there is a failure in the "always" condition steps, the "failure" condition steps will fire. But if there is a failure in the "success" condition steps, the "failure" condition steps will not fire. This would make sense if the the "failure" condition only fired if the stage steps failed but never fired if one of the post condition steps failed. But that is not the case. Add Comment
[JIRA] (JENKINS-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging
Title: Message Title Sam Gleske commented on JENKINS-31866 Re: Attempts to restrict Pipeline jobs from running on master result in job hanging I ran a quick test. Looks like the solution works. Does not allow users to define master in their Jenkinsfile. The pipeline runs but hangs on the master node step indefinitely. Looks good to me. A build timeout could cancel hung jobs. In the future it would be nice if pipelines were officially supported. Some support could include: JENKINS-50644 - allow admins to define master node steps in global shared libraries. Throw a security warning to the admin when a user attempts to run on the master node via a Jenkinsfile. Prevent the job from ever starting so it doesn't hang indefinitely taking up resources. It could just kill the job as a failure. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34238) Flyweight Job Support For Docker Plugin
Title: Message Title Sam Gleske edited a comment on JENKINS-34238 Re: Flyweight Job Support For Docker Plugin This feature no longer affects me in project matrix job types. I've since moved on to the pipeline plugin in my open source projects which does matrix building just fine. A lot has changed since I made that comment in 2016. Pipelines have improved. You can see how I set up matrix jobs in pipeline similar to how they used to be done in my matrix project type jobs.https://github.com/samrocketman/jervis/blob/f283197fa9267429b5bca84c376e43edb46e6d03/vars/buildViaJervis.groovy#L223-L268 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34238) Flyweight Job Support For Docker Plugin
Title: Message Title Sam Gleske edited a comment on JENKINS-34238 Re: Flyweight Job Support For Docker Plugin This feature no longer affects me in project matrix job types. I've since moved on to the pipeline plugin in my open source projects which does matrix building just fine. A lot has changed since I made that comment in 2016. Pipelines have improved. Blue ocean was released so parallel matrix building is no longer ugly. You can see how I set up matrix jobs in pipeline similar to how they used to be done in my matrix project type jobs.https://github.com/samrocketman/jervis/blob/f283197fa9267429b5bca84c376e43edb46e6d03/vars/buildViaJervis.groovy#L223-L268 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34238) Flyweight Job Support For Docker Plugin
Title: Message Title Sam Gleske commented on JENKINS-34238 Re: Flyweight Job Support For Docker Plugin This feature no longer affects me in project matrix job types. I've since moved on to the pipeline plugin in my open source projects which does matrix building just fine. A lot has changed since I made that comment in 2016. Pipelines have improved. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging
Title: Message Title
Sam Gleske edited a comment on JENKINS-31866
Re: Attempts to restrict Pipeline jobs from running on master result in job hanging
Question about your class filter configuration.Can normal pipeline users arbitrarily execute code on the master node if a user defines in their Jenkinsfile the following?{noformat}node('master') {//user does something malicious on master}{noformat} I basically want to reserve the master executors to be available to admins only.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging
Title: Message Title
Sam Gleske edited a comment on JENKINS-31866
Re: Attempts to restrict Pipeline jobs from running on master result in job hanging
Question about your class filter configuration . .. Can normal pipeline users arbitrarily execute code on the master node if a user defines in their Jenkinsfile the following?{noformat}node('master') {//user does something malicious on master}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31866) Attempts to restrict Pipeline jobs from running on master result in job hanging
Title: Message Title
Sam Gleske commented on JENKINS-31866
Re: Attempts to restrict Pipeline jobs from running on master result in job hanging
Question... Can normal pipeline users arbitrarily execute code on the master node if a user defines in their Jenkinsfile the following?
node('master') {
//user does something malicious on master
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
