[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57412 Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Change By: Oleg Nenashev Labels: LTS lts-candidate regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.591.1557638760657%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Oleg Nenashev commented on JENKINS-57412 Re: Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 https://jenkins.io/download/lts/#backporting-process Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.589.1557638760622%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Rick commented on JENKINS-57412 Re: Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Do we have any documents about describing how to deal this situation. If there's not I'd like to start file one. What I'm tring to say is that how to add a lable or other things like that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.587.1557635880100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48175) Powershell 'Hello World' Task Hangs
Title: Message Title Gao Jun commented on JENKINS-48175 Re: Powershell 'Hello World' Task Hangs I have the same problem described above, but sometimes Jenkins job can finish, sometimes cannot. When I start a powershell script, if the Jenkins cannot finish, pipeline icon displayed as under processing. Jenkins Version: 2.89.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186743.151137645.574.1557633540350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Josh Soref commented on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 There wasn't anything obvious in the scan repository logs. I'll check the master log… Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.572.1557626820155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46988) String.eachLine only reads first line
Title: Message Title Kevin Nuckolls commented on JENKINS-46988 Re: String.eachLine only reads first line I lost an afternoon to this bug and it's real and still open. The workaround mentioned of the split each works great. Just chiming in that this does actually need to be fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185366.1505906799000.564.1557626280221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57418) Plugin Over SSH
Title: Message Title Jader Oliveira created an issue Jenkins / JENKINS-57418 Plugin Over SSH Issue Type: Task Assignee: Unassigned Attachments: Bug_jenkins_01.jpg, Bug_jenkins_02.jpg Components: publish-over-ssh-plugin Created: 2019-05-12 01:22 Environment: Plugin: Publish Over SSH v1.20.1 java.runtime.name: OpenJDK Runtime Environment java.runtime.version: 1.8.0_181-8u181-b13-1~deb9u1-b13 Jenkins war: org.jenkins-ci.main:jenkins-war:2.164.3 Browsers: Chrome, Firefox - latest Labels: plugins Priority: Critical Reporter: Jader Oliveira What is wrong im my conf. I have tested via cli scp to another remote and work´s great. Just in jenkins by plugin dont transfer the file. All permissions is OK.
[JIRA] (JENKINS-54746) Can't connect via SSH on 1.29.1
Title: Message Title Alexey Vazhnov commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 From SECURITY-440 / CVE-2018-1000601 fix: SSH Credentials Plugin no longer supports SSH credentials from files on the Jenkins master file system, neither user-specified file paths nor ~/.ssh. Existing SSH credentials of these kinds are migrated to "directly entered" SSH credentials. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195549.1542789679000.544.1557611760443%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title
Alexey Vazhnov edited a comment on JENKINS-52232
Re: Credentials not usable after upgrade to 1.14
I've just installed fresh Jenkins and found I can't use SSH private key from Jenkins home directory, {{~/.ssh/id_rsa}}. As workaround, I put SSH key into Jenkins Credentials, it works. * SSH Slaves v1.29.4, * SSH Credentials Plugin v1.16, * Jenkins v2.164.3, * host and slave OS: Ubuntu 18.04.2 with all updates, * OpenSSH v7.6p1. *Update*: found [this|https://jenkins.io/security/advisory/2018-06-25/]:bq. SSH Credentials Plugin no longer supports SSH credentials from files on the Jenkins master file system, neither user-specified file paths nor ~/.ssh. Existing SSH credentials of these kinds are migrated to "directly entered" SSH credentials.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191996.1530173857000.533.1557611580253%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52232) Credentials not usable after upgrade to 1.14
Title: Message Title Alexey Vazhnov commented on JENKINS-52232 Re: Credentials not usable after upgrade to 1.14 I've just installed fresh Jenkins and found I can't use SSH private key from Jenkins home directory, ~/.ssh/id_rsa. As workaround, I put SSH key into Jenkins Credentials, it works. SSH Slaves v1.29.4, SSH Credentials Plugin v1.16, Jenkins v2.164.3, host and slave OS: Ubuntu 18.04.2 with all updates, OpenSSH v7.6p1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191996.1530173857000.523.1557610980340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56671) Allow empty results (Do not fail the build on empty test results)
Title: Message Title Nikolas Falco commented on JENKINS-56671 Re: Allow empty results (Do not fail the build on empty test results) What do you mean for empty result? The file has been created but empty (this sounds more like an error of the program that generates the reports) or the report is generated not empty compliant with some format but reports 0 runs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198306.1553213522000.521.1557594900128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title FABRIZIO MANFREDI resolved as Fixed Fix Released in 1.43 Jenkins / JENKINS-57357 NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: FABRIZIO MANFREDI Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.507.1557593100175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Oleg Nenashev updated JENKINS-57412 Merged towards the next weekly Jenkins / JENKINS-57412 Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.503.1557592680250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57412 Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Change By: Oleg Nenashev Labels: LTS lts-candidate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199218.1557561012000.505.1557592680276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title
Richard Davis created an issue
Jenkins / JENKINS-57417
configFileProvider / withCredentials not working in declarative pipeline
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
config-file-provider-plugin, credentials-binding-plugin, token-macro-plugin
Created:
2019-05-11 15:11
Environment:
Jenkins 2.174 Config File Provider Plugin 3.6 Credentials Bind Plugin 1.18
Priority:
Major
Reporter:
Richard Davis
From what I read which googling the issue, I am under the impression that: 1) The credentials bind plugin does not assign environment variables, but rather groovy variables; and even if it did, environment variables do not propagate "up" to the parent context. 2) The "glue" that is available using scripted pipelines does not work in declarative pipelines; specifically the ability to define local variables and assign environment variables within a stage, and access them via the underlying token macro plugin that backs the configFileProvider.
Use of groovy variables, ${PIP_USERNAME}, resulted in an "Unrecoginzed macro" error.
Use of ${env.PIP_USERNAME} did not substitute the variable at all.
Use of ${ENV, var = "PIP_USERNAME"} substitutes the variable with null string.
Custom Config File - 05f48227-0980-4313-ab24-f007d78090cf
[JIRA] (JENKINS-57283) Trend Carousel (in Details View)
Title: Message Title Andreas Neumeier started work on JENKINS-57283 Change By: Andreas Neumeier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199049.1556744617000.480.1557586740182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57416) [GSoC] Role Strategy Plugin Performance Improvements: Phase 1
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-57416 [GSoC] Role Strategy Plugin Performance Improvements: Phase 1 Change By: Abhyudaya Sharma Summary: Ticket for tracking [GSoC] Role Strategy Plugin Performance Improvements: Phase 1 of the GSoC project Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199222.1557584298000.476.1557584520125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57416) Ticket for tracking Phase 1 of the GSoC project
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-57416 Ticket for tracking Phase 1 of the GSoC project Issue Type: Epic Assignee: Abhyudaya Sharma Components: role-strategy-plugin Created: 2019-05-11 14:18 Priority: Major Reporter: Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199222.1557584298000.472.1557584340161%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57415) [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-57415 [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period Change By: Abhyudaya Sharma Summary: Ticket for tracking community [GSoC] Role Strategy Plugin Performance Improvements: Community bonding period of the GSoC project Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199221.1557584264000.474.1557584400113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57415) Ticket for tracking community bonding period of the GSoC project
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-57415 Ticket for tracking community bonding period of the GSoC project Issue Type: Epic Assignee: Abhyudaya Sharma Components: role-strategy-plugin Created: 2019-05-11 14:17 Priority: Major Reporter: Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199221.1557584264000.470.1557584280230%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57414) Azure VM agent is not able to use existing resource group in different regions
Title: Message Title
Christian Meyer updated an issue
Jenkins / JENKINS-57414
Azure VM agent is not able to use existing resource group in different regions
Change By:
Christian Meyer
We are using a Jenkins hosted in Azure.Now we have created the first VM agents in west-europe, the and reuse an existing resource group which is also linked to west-europe.When we want to create another VM agent within another region e.g. east-us2 , we are getting the following message and the VM agent will get not deployed: _ {"code":"InvalidResourceGroupLocation","message":"Invalid resource group location 'eastus2'. The Resource group already exists in location 'westeurope'."} _ It seems that the plugin trys to create a new resource group in each region, but we want to reuse the existing resource group. Within the Azure Portal we are able to create in our resource group (west-europe) also VMs, which are hosted in different regions e.g. east-us2. Could you please help and support us?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-57414) Azure VM agent is not able to use existing resource group in different regions
Title: Message Title
Christian Meyer created an issue
Jenkins / JENKINS-57414
Azure VM agent is not able to use existing resource group in different regions
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-05-11 09:16
Priority:
Minor
Reporter:
Christian Meyer
We are using a Jenkins hosted in Azure. Now we have created the first VM agents in west-europe, the resource group is also linked to west-europe. When we want to create another VM agent within another region e.g. east-us2 we are getting the following message and the VM agent will get not deployed: {"code":"InvalidResourceGroupLocation","message":"Invalid resource group location 'eastus2'. The Resource group already exists in location 'westeurope'."} Within the Azure Portal we are able to create in our resource group (west-europe) also VMs, which are hosted in different regions e.g. east-us2. Could you please help and support us?
Add Comment
[JIRA] (JENKINS-54723) EC2 Plugin: Include tags in created EBS volumes
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54723 Re: EC2 Plugin: Include tags in created EBS volumes I missed to merge for the 1.43, it will be in 1.44 in a couple of weeks. It is already in the master you can try the snapshoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195525.1542713511000.453.1557565560152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57413) Issue while deleting organization
Title: Message Title Neha Shrivastava created an issue Jenkins / JENKINS-57413 Issue while deleting organization Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-05-11 08:12 Priority: Blocker Reporter: Neha Shrivastava org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.164.2.jar!/lib/hudson/actions.jelly:39:70: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) Add Comment
[JIRA] (JENKINS-57412) Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176
Title: Message Title Rick created an issue Jenkins / JENKINS-57412 Incorrect deletion for setup wizard of Chinese localization files on Jenkins LTS 2.176 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-05-11 07:50 Labels: LTS Priority: Major Reporter: Rick Should always keep install wizard localization files in the core. See also [JEP-216|https://github.com/jenkinsci/jep/blob/master/jep/216/README.adoc] Add Comment
[JIRA] (JENKINS-55987) Use of when buildingTag does not work in Declarative pipeline
Title: Message Title Connor Love commented on JENKINS-55987 Re: Use of when buildingTag does not work in Declarative pipeline Any update on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197402.1549442533000.443.1557554760128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
