[JIRA] (JENKINS-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: Raul Arabaolaza Path: essentials.yml http://jenkins-ci.org/commit/jenkins/bdf82bcb0fa2192afddb925eb4b6ec17a63dffc9 Log: JENKINS-49269 Metadata file for ath runs 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: Raul Arabaolaza Path: Jenkinsfile essentials.yml http://jenkins-ci.org/commit/jenkins/122ce9a048624bd7fc33b80318543a904ace2300 Log: JENKINS-49269 Fix jenkinsfile and use latest commit of ath 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: Raul Arabaolaza Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins/36e9eb03445fcd1779927773c5e29c38739a2cde Log: JENKINS-49269 Use correct maven env to buld war for ATH 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: Raul Arabaolaza Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins/198850a120fed452be7f5cb27dab17385900bae7 Log: JENKINS-49269 Cautious deleteDir 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: Raul Arabaolaza Path: Jenkinsfile http://jenkins-ci.org/commit/jenkins/41c006d5ed11daf5eeac7bb1424599cdfad1d8ee Log: JENKINS-49269 Run ATH SmokeTest category on core builds 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-49269) Upgrade Jenkins core flow to run the ath test defined in 49263
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49269 Re: Upgrade Jenkins core flow to run the ath test defined in 49263 Code changed in jenkins User: R. Tyler Croy Path: Jenkinsfile essentials.yml http://jenkins-ci.org/commit/jenkins/3b5c715ae0d00ec3a38c63d8c9bf9de2a76b9e29 Log: Merge pull request #3350 from daniel-beck/JENKINS-49269-2 JENKINS-49269 Add ATH SmokeTest runs to the core build Compare: https://github.com/jenkinsci/jenkins/compare/ca61ed7e3545...3b5c715ae0d0 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-50315) Editable mode not offering selection once a selection has been made
Title: Message Title Serge Landry updated an issue Jenkins / JENKINS-50315 Editable mode not offering selection once a selection has been made Change By: Serge Landry The editable mode that now offers dynamic filtering as you type in the field has a user unfriendly issue.The dynamic filtering of the combo box items as you type is okay. But once an item has been selected, the "filtering state" of the combo box stays, resulting in having only the selected item displayed in the combo box. All selected items of the combo box should be displayed once a valid selection has been made, otherwise you need to clear out the field in order to have all your items displayed and selectable again.This is especially obvious when, for instance, you configure your Extensible Choice as Editable, with the Default Choice as the Top Most Value. The result is that your combo box is shown with the top most item, but with absolutely no way to make a selection other than clearing , as if the combo box only had the top most item available. It took me quite a few minutes to realize that I had to clear the field, which is not the most user friendly or obvious way of interacting with the combo box. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Aleksandr Gamoskin created an issue Jenkins / JENKINS-50317 Pipeline job is failed with java.lang.StackOverflowError Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile, log.txt Components: pipeline Created: 2018-03-21 13:18 Environment: Jenkins Master WIndows Server 2012, Jenkins version 2.112, 2 slaves, Jenkins Slave Windows 10 and Jenkins Slave Debian 9.3(Stretch) Labels: pipeline windows Priority: Critical Reporter: Aleksandr Gamoskin We use Multi branch job. Sometimes pipeline job is failed with java.lang.StackOverflowError.I send you our Jenkinsfile and pipeline.log. Maybe is job name too long? Also sometimes parallel stages hang when one stage is failed(failFast true) via this exception but I think it's other bug. Please write if you need some additional logs or system information. Jenkinsfile log.txt
[JIRA] (JENKINS-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-50318 Refusing to marshal com.google.common.util.concurrent.SettableFuture Issue Type: Bug Assignee: Chad Schmutzer Components: ec2-fleet-plugin Created: 2018-03-21 13:25 Environment: Jenkins 2.107.1 ec2-fleet 1.1.4 Labels: JEP-200 Priority: Minor Reporter: Christopher Orr To reproduce: 1. Open /computer/(master)/configure 2. Hit "Save" Possibly as a prerequisite, `EC2FleetCloud#plannedNodes` may need to have some entries (so that `SettableFuture`s exist), e.g. by setting up a cloud, and filling the build queue, so that some nodes start to become provisioned. Mar 21, 2018 1:07:23 PM WARNING jenkins.security.ClassFilterImpl lambda$isBlacklisted$1 com.google.common.util.concurrent.SettableFuture in file:/var/jenkins_home/war/WEB-INF/lib/guava-11.0.1.jar might be dangerous, so rejecting; see https://jenkins.io/redirect/class-filter/ Mar 21, 2018 1:07:24 PM WARNING org.eclipse.jetty.server.handler.ContextHandler$Context log Error while serving https://ci.example.com/computer/(master)/configSubmit java.lang.UnsupportedOperationException: Refusing to marshal com.google.common.util.concurrent.SettableFuture for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at
[JIRA] (JENKINS-50272) NoClassDefFoundError "hudson/tools/JDKInstaller$FileSystem" at SSHLauncher after Jenkins Update 2.111->2.112
Title: Message Title Devin Nusbaum commented on JENKINS-50272 Re: NoClassDefFoundError "hudson/tools/JDKInstaller$FileSystem" at SSHLauncher after Jenkins Update 2.111->2.112 Glad to hear that everything is working! why not version 1.1 that is already available? Plugins like this that have been split from core are explicitly bundled in the war file and listed in split-plugins.txt to enable the automatic installation. jdk-tool:1.0 had to be released before Jenkins 2.112 was released, so it depends on Jenkins 2.111. This means that there is a short time where a 2.111 user could install the plugin and have multiple instances of the same class on the classpath, which is bad, so once Jenkins 2.112 was released, I updated jdk-tool to depend on Jenkins 2.112 and released 1.1, so that 1.0 is no longer available from the update center for 2.111 users. There is no issue with bundling 1.0 or 1.1 in core, but if later releases of jdk-tool have significant changes, such as adding new dependencies, we would probably not want to make those versions be bundled in Jenkins core, so it's easiest to just leave 1.0 as the bundled version, and let people upgrade naturally through the update center. Logging of Jenkins version downgrading is missing I'm not sure offhand, but feel free to open a new issue requesting that logging be added (or a pull request to https://github.com/jenkinsci/jenkins, I think the right place would be this method). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50314) Using or not caches should be configurable in servers global configuration
Title: Message Title benoit guerin assigned an issue to benoit guerin Jenkins / JENKINS-50314 Using or not caches should be configurable in servers global configuration Change By: benoit guerin Assignee: benoit guerin 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-42066) Pipelines support for openstack-cloud-plugin
Title: Message Title Oliver Gondža resolved as Fixed I am closing this as the plugin can be used from pipeline using the node step. There is the openstackMachine step as well. Support for declarative pipeline is coming in https://issues.jenkins-ci.org/browse/JENKINS-47742 Jenkins / JENKINS-42066 Pipelines support for openstack-cloud-plugin Change By: Oliver Gondža Status: Open 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
[JIRA] (JENKINS-42051) configure cloud Slave shows 404 Reason not found
Title: Message Title Oliver Gondža resolved as Fixed Configure link was hidden from UI as well. Jenkins / JENKINS-42051 configure cloud Slave shows 404 Reason not found Change By: Oliver Gondža Status: Open 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-46541) Openstack plugin uses login sessions past their expiry date
Title: Message Title Oliver Gondža updated JENKINS-46541 I presume this is resolved Jenkins / JENKINS-46541 Openstack plugin uses login sessions past their expiry date Change By: Oliver Gondža 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-50315) Editable mode not offering selection once a selection has been made
Title: Message Title Serge Landry created an issue Jenkins / JENKINS-50315 Editable mode not offering selection once a selection has been made Issue Type: Bug Assignee: ikedam Components: extensible-choice-parameter-plugin Created: 2018-03-21 12:07 Environment: Jenkins v2.107.1 Extensible Choice Parameter Plugin v1.5.0 Labels: plugin user-experience Priority: Major Reporter: Serge Landry The editable mode that now offers dynamic filtering as you type in the field has a user unfriendly issue. The dynamic filtering of the combo box items as you type is okay. But once an item has been selected, the "filtering state" of the combo box stays, resulting in having only the selected item displayed in the combo box. All selected items of the combo box should be displayed once a valid selection has been made, otherwise you need to clear out the field in order to have all your items displayed and selectable again. This is especially obvious when, for instance, you configure your Extensible Choice as Editable, with the Default Choice as the Top Most Value. The result is that your combo box is shown with the top most item, but with absolutely no way to make a selection other than clearing the field, which is not the most user friendly or obvious way of interacting with the combo box.
[JIRA] (JENKINS-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title
Yoram Michaeli updated an issue
Jenkins / JENKINS-50307
While running in parallel for a loop, the index is wrong for each iteration
Change By:
Yoram Michaeli
When using a parallel step for an indexed loop, using the loop-iterator-index for internal usage results with wrong value (showing the max-index-value for all iterations). A workaround for it is to set a local variable for saving the current iteration-index and use the local variable. The following pipeline demonstrates the problem (the issue is demonstrated with the internal 'echo' steps):{code:java} // code placeholder{code} pipeline \ { agent any stages \ { stage('Explore bug') \ { steps \ { script \ { int maxIndex1=3 def loopers1 = [:] for (int loopIndex1 = 0; loopIndex1 < maxIndex1; loopIndex1++) \ { echo "loopIndex1=$ \ {loopIndex1}" loopers1["loop-$\{loopIndex1}"] = \ { echo "loopIndex1=$ \ {loopIndex1}" } } parallel loopers1 } } } stage('Bug workaround') \ { steps \ { script \ { int maxIndex2=3 def loopers2 = [:] for (int loopIndex2 = 0; loopIndex2 < maxIndex2; loopIndex2++) \ { int index2=loopIndex2 echo "index2=$ \ {index2}" loopers2["loop-$\{index2}"] = \ { echo "index2=$ \ {index2}" } } parallel loopers2 } } } } } {code}
Add Comment
[JIRA] (JENKINS-50316) Bitbucket repo not being dicsovered in project during pipeline creation
Title: Message Title
GLen Currier created an issue
Jenkins / JENKINS-50316
Bitbucket repo not being dicsovered in project during pipeline creation
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
repoReadHang.jpg
Components:
blueocean-plugin
Created:
2018-03-21 12:47
Priority:
Blocker
Reporter:
GLen Currier
Jenkins 2.107, Blue Ocean 1.4.2 BitBucket Server v5.9.0 During pipeline creation, after selecting "Bitbucket Server", adding the Server URL and admin credentials for the Bitbucket server (uses git repos), I can retrieve and view the list of available projects. However, after selecting the project where the required repo is located, everything just "hangs".
The progress bar at the top does gradually increase, but also gradually slows to a stop.
Bitbucket Webhooks is installed and configured on the Bitbucket Server ("TestConnection" returns an HTTP 200...) and is set to "Active"
There are no errors being registered either in Chrome, Internet Explorer or Firefox, all of which are up-to-date.
The URL I used to install the Blue Ocean plugin: https://updates.jenkins.io/update-center.json
[JIRA] (JENKINS-50303) Mesos Offer Selection Attributes Mesos Plugin JEP-200
Title: Message Title Jesse Glick commented on JENKINS-50303 Re: Mesos Offer Selection Attributes Mesos Plugin JEP-200 Apparently slaveAttributes are null in the existing test suites, so PCT didn't capture it More to the point, all the existing tests use mocks, so they would not have captured any behavioral regressions of any kind. 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-50303) Mesos Offer Selection Attributes Mesos Plugin JEP-200
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-50303 Mesos Offer Selection Attributes Mesos Plugin JEP-200 Change By: Jesse Glick Assignee: Vinod Kone Jesse Glick 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-49810) Define the evergreen-client -> status service API contract
Title: Message Title R. Tyler Croy commented on JENKINS-49810 Re: Define the evergreen-client -> status service API contract Mentioned to Baptiste Mathus in Gitter, there's a challenge with secure registration of the evergreen-client that must be handled along side this contract. 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-50328) Pipeline editor not working if Script Path is set
Title: Message Title Vitor Durante created an issue Jenkins / JENKINS-50328 Pipeline editor not working if Script Path is set Issue Type: Bug Assignee: Kirill Merkushev Attachments: image-2018-03-21-20-14-50-270.png Components: blueocean-pipeline-editor-plugin, blueocean-plugin, github-plugin Created: 2018-03-21 23:19 Environment: Jenkins 2.107.1 Priority: Major Reporter: Vitor Durante I have created a pipeline from a GitHub repository. Inside this repository, there is a subfolder called jenkins with a Jenkinsfile inside, just like in the example app: https://github.com/jenkins-docs/creating-a-pipeline-in-blue-ocean. Blue Ocean prompted me to design a new pipeline. Instead, I went to the settings and set the Script Path manually to 'jenkins/Jenkinsfile': It does work as intended. The hooks are activated and the pipeline is run properly, but if I try to edit the pipeline using pipeline editor, it shows an empty pipeline. If I do implement a pipeline in the editor and save it, a Jenkinsfile is created in the root path of my repository. It seems the pipeline editor is not getting the Jenkinsfile path from 'Script Path' setting
[JIRA] (JENKINS-50241) Add Maven details tab to build result page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50241 Re: Add Maven details tab to build result page Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenArtifact.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenDependency.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/MavenSpyLogProcessor.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2Dao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginNullDao.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesFingerprintPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesLister.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/JGivenTestsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/index.jelly jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/dao/PipelineMavenPluginH2DaoTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/DependenciesListerTest.java http://jenkins-ci.org/commit/pipeline-maven-plugin/76c092469f3eaecbaad48a2ed6ed101a0680e1fa Log: JENKINS-50241 Add "dependencies" on the Maven details screen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48346) Unable to add userdata config on GCP
Title: Message Title Tim Robinson commented on JENKINS-48346 Re: Unable to add userdata config on GCP I've installed a recent SNAPSHOT release 7301897 the list in Init Script is listing the options but the User-data list is showing "Not supported with jclouds and this provider." for both "aws-ec2" and "google-compute-engine". I seem to be able to work around the issue editing the config.xml directly. 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-49721) withMaven requires maven argument when using with takari wrapper
Title: Message Title Cyrille Le Clerc started work on JENKINS-49721 Change By: Cyrille Le Clerc 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-50241) Add Maven details tab to build result page
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-50241 Add Maven details tab to build result page Change By: Cyrille Le Clerc Add Maven details tab to build result page:* Upstream and downstream pipelines* Generated artifacts* ... !JENKINS-50241. png jpg |thumbnail! 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-48136) Unable to toggle favorite for (pipeline) jobs with slash in their name
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48136 Re: Unable to toggle favorite for (pipeline) jobs with slash in their name Code changed in jenkins User: David Pärsson Path: src/main/resources/hudson/plugins/favorite/assets.js http://jenkins-ci.org/commit/favorite-plugin/983893f61c6de2586010f3062d2cfdb8e21bf118 Log: JENKINS-48136 Encode job name (#21) URI encoded characters (such as forward slashes) were decoded when they should not be, preventing jobs with such characters in their names from being manually added/removed from the favorites list. Fixes JENKINS-48136. 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-50241) Add Maven details tab to build result page
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-50241 Add Maven details tab to build result page Change By: Cyrille Le Clerc Attachment: JENKINS-50241.jpg 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-47301) JClouds aws-ec2 always tries to use default subnet
Title: Message Title Tim Robinson commented on JENKINS-47301 Re: JClouds aws-ec2 always tries to use default subnet I'm also seeing this issue on AWS. Also tested against a recent SNAPSHOT but got the same error. 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-46386) Agent sometimes fails to launch in custom cloud provider
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-46386 Agent sometimes fails to launch in custom cloud provider Change By: Daniel Beck Labels: lts-candidate 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-49721) withMaven requires maven argument when using with takari wrapper
Title: Message Title Cyrille Le Clerc updated JENKINS-49721 Jenkins / JENKINS-49721 withMaven requires maven argument when using with takari wrapper Change By: Cyrille Le Clerc 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-50328) Pipeline editor not working if Script Path is set
Title: Message Title Vitor Durante updated an issue Jenkins / JENKINS-50328 Pipeline editor not working if Script Path is set Change By: Vitor Durante I have created a pipeline from a GitHub repository. Inside this repository, there is a subfolder called jenkins with a Jenkinsfile inside, just like in the example app: [https://github.com/jenkins-docs/creating-a-pipeline-in-blue-ocean]. Blue Ocean prompted me to design a new pipeline. Instead, I went to the settings and set the Script Path manually to 'jenkins/Jenkinsfile':!image-2018-03-21-20-14-50-270.png!It does work as intended. The hooks are activated and the pipeline is run properly, but if I try to edit the pipeline using pipeline editor, it shows an empty pipeline. If I do implement a pipeline in the editor and save it, a Jenkinsfile is created in the root path of my repository.It seems the pipeline editor is not getting the Jenkinsfile path from 'Script Path' setting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-47611) RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-47611 RejectedAccessException: Scripts not permitted to use method org.apache.maven.model.Model getVersion Change By: Marc Benstein Labels: JEP-200 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-49972) Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins
Title: Message Title Rohan Donthoji commented on JENKINS-49972 Re: Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins Hi, Please let me know where is it doing wrong. Thank you. Regards, Rohan Donthoji 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-49972) Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins
Title: Message Title Rohan Donthoji commented on JENKINS-49972 Re: Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins Hi, Please let me know where is it doing wrong. Thank you. Regards, Rohan Donthoji 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-40199) API to list available tools for the Editor
Title: Message Title
Guillaume Boucherie commented on JENKINS-40199
Re: API to list available tools for the Editor
Hi, When I try to use the endpoint in a browser I never get the details of available tools. See this example :
[
{
"_class": "io.blueocean.rest.pipeline.editor.ExportedToolDescriptor",
"installations": [
{}
],
"symbol": "maven",
"toolName": "Maven",
"type": "hudson.tasks.Maven$MavenInstallation$DescriptorImpl"
}
]
The problem is that defaultVisibility of ExportedToolInstallation is 1, by changing this to 2 details will be displayed.
[
{
"_class": "io.blueocean.rest.pipeline.editor.ExportedToolDescriptor",
"installations": [
{
"name": "apache-maven-3.5.2",
"type": "hudson.tasks.Maven$MavenInstallation"
}
],
"symbol": "maven",
"toolName": "Maven",
"type": "hudson.tasks.Maven$MavenInstallation$DescriptorImpl"
}
]
I need this to provide a endpoint to allow my Jenkins user discover what tools is available in pipeline. Could you make the change ? Let me now if I need to create another ticket.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50303) Mesos Offer Selection Attributes Mesos Plugin JEP-200
Title: Message Title
Jesse Glick commented on JENKINS-50303
Re: Mesos Offer Selection Attributes Mesos Plugin JEP-200
What you would expect the plugin to save:
{"somekey": "somevalue"}
What the current plugin saves:
false
"org.apache.commons.collections.map.ListOrderedMap" serialization="custom">
somekey
somekey
somevalue
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-41239) Error during always block skips execution of remaining steps
Title: Message Title Moritz Baumann edited a comment on JENKINS-41239 Re: Error during always block skips execution of remaining steps When I discovered this problem, my first instinct was to add a second _always_ closure, but this failed Jenkins didn't accept that . Maybe allowing this would be a good solution to the underlying 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-41239) Error during always block skips execution of remaining steps
Title: Message Title Moritz Baumann commented on JENKINS-41239 Re: Error during always block skips execution of remaining steps When I discovered this problem, my first instinct was to add a second always closure, but this failed. Maybe allowing this would be a good solution to the underlying 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-50258) Per test mode is not available for throughput and error graphs
Title: Message Title Li Zhu updated an issue Jenkins / JENKINS-50258 Per test mode is not available for throughput and error graphs Change By: Li Zhu Attachment: currentBuildReport.PNG Attachment: perTestLevel.PNG Attachment: summaryLevel.PNG 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-50258) Per test mode is not available for throughput and error graphs
Title: Message Title Li Zhu commented on JENKINS-50258 Re: Per test mode is not available for throughput and error graphs Hi Robin Björklin, sorry, I don't think we are talking the same thing. Hi Artem Fedorov, I uploaded three pictures captchered on Jenkins. In the summaryLevel.PNG and the perTestLevel.PGN, we can see the difference in the "Response time" graph, because the perTestLevel shows gx and gy separately with two different line of trends. Gx and gy are two single tests. You can check the data in currentBuildReport.PNG. However, in "Throughput" or "Error" graph, there's only one trend line that is the summary. My point is they should show two trend lines, one for gx, and the other for gy as well. If you check your code, either in the index.jelly or in the java code, the processing of "Response time" and the other two graphs are different. There's only iteration for each URL during processing "Response time". Thank you for your quick response. 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-50268) Preexisting pods contribute towards instanceCap
Title: Message Title Carlos Sanchez commented on JENKINS-50268 Re: Preexisting pods contribute towards instanceCap If you are creating objects in groovy you'll need to set the labels yourself Readresolve is used to handle upgrades without overriding existing configuration 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-50319) NPE during dynamic insatll
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-50319 NPE during dynamic insatll Issue Type: Bug Assignee: Stephen Connolly Components: gitea-plugin Created: 2018-03-21 14:03 Priority: Minor Reporter: Stephen Connolly Error firing ExtensionListListener.onChange(). java.lang.NullPointerException at org.jenkinsci.plugin.gitea.GiteaSCMNavigator$DescriptorImpl.newInstance(GiteaSCMNavigator.java:389) at jenkins.branch.CustomOrganizationFolderDescriptor.doAddSpecificDescriptors(CustomOrganizationFolderDescriptor.java:181) at jenkins.branch.CustomOrganizationFolderDescriptor.access$100(CustomOrganizationFolderDescriptor.java:54) at jenkins.branch.CustomOrganizationFolderDescriptor$ListenerImpl.onChange(CustomOrganizationFolderDescriptor.java:157) at hudson.ExtensionList.fireOnChangeListeners(ExtensionList.java:345) at hudson.ExtensionList.refresh(ExtensionList.java:338) at jenkins.model.Jenkins.refreshExtensions(Jenkins.java:2688) at hudson.PluginManager.dynamicLoad(PluginManager.java:875) at hudson.PluginManager.dynamicLoad(PluginManager.java:821) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1889) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-50318 Refusing to marshal com.google.common.util.concurrent.SettableFuture Change By: Oleg Nenashev Assignee: Chad Schmutzer Oleg Nenashev 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-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev commented on JENKINS-50318 Re: Refusing to marshal com.google.common.util.concurrent.SettableFuture I doubt there is a real need to persist SettableFuture objects on the disk. Will investigate 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-41239) Error during always block skips execution of remaining steps
Title: Message Title
Moritz Baumann commented on JENKINS-41239
Re: Error during always block skips execution of remaining steps
The workaround mentioned here doesn't work for me. Are there any plans to address this issue? Currently, I have to use
post { always { catchError { ... } cleanWs() } }
everywhere to make sure I always clean up my workspaces. This workaround introduces another bug, though: Incorrect archiveArtifacts configurations in the catchError block will be completely ignored.
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-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev started work on JENKINS-50318 Change By: Oleg Nenashev 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-50303) Mesos Offer Selection Attributes Mesos Plugin JEP-200
Title: Message Title Jesse Glick updated JENKINS-50303 Jenkins / JENKINS-50303 Mesos Offer Selection Attributes Mesos Plugin JEP-200 Change By: Jesse Glick 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-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50320 Adjust JEP 301 once snapshotting data JEP is accepted Issue Type: Task Assignee: R. Tyler Croy Components: essentials Created: 2018-03-21 14:40 Priority: Minor Reporter: Baptiste Mathus JENKINS_HOME is referred to in https://github.com/jenkinsci/jep/tree/master/jep/301#mutable-data when the JENKINS-49406 JEP totally restructures the filesystem organization for Jenkins data. Add Comment This message was sent by
[JIRA] (JENKINS-32062) Arrays may not be passed directly to methods
Title: Message Title
Gerard Ryan commented on JENKINS-32062
Re: Arrays may not be passed directly to methods
I think I might have experienced this same issue just now with pipeline plugin v2.5 and pipeline groovy plugin v2.42. I'm just reporting because looking at the release dates of versions there and the timing of when this issue was closed, seem to indicate that it should have been in releases before the one I'm on. I see in the release notes for pipeline groovy v2.44 it says: "Pick up recent groovy-cps fixes including resolving a quirk with field initialization and CPS transforms", so I'll try again after I can update past that, to see if that fixes it. Here's a small reproducer pipeline:
String[] xs = ["one", "two", "three", "four", "five"]
Closure f = { nums ->
return nums.collect { num ->
return "${num}-${num}"
}
}
println f(xs)
This prints [o-o, n-n, e-e] rather than the expected [one-one, two-two, three-three, four-four, five-five]. If I change xs to List then I get the expected result.
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-50319) NPE during dynamic insatll
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50319 Re: NPE during dynamic insatll Code changed in jenkins User: Stephen Connolly Path: CHANGES.md src/main/java/org/jenkinsci/plugin/gitea/GiteaSCMNavigator.java http://jenkins-ci.org/commit/gitea-plugin/d8c79bce8e42c0823479039a78ae7aef238c1b73 Log: [FIXED JENKINS-50319] Fix NPE during dynamic installation of the plugin 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-50319) NPE during dynamic insatll
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-50319 NPE during dynamic insatll Change By: SCM/JIRA link daemon Status: Open 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-41239) Error during always block skips execution of remaining steps
Title: Message Title Moritz Baumann edited a comment on JENKINS-41239 Re: Error during always block skips execution of remaining steps When I discovered this problem, my first instinct was to add a second _always_ closure, but Jenkins didn't accept that. Maybe allowing this would be a good solution to the underlying problem? *Edit*: Sorry, completely missed that this is already mentioned above. 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-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title R. Tyler Croy assigned an issue to Baptiste Mathus Jenkins / JENKINS-50320 Adjust JEP 301 once snapshotting data JEP is accepted Change By: R. Tyler Croy Assignee: R. Tyler Croy Baptiste Mathus 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-50320) Adjust JEP 301 once snapshotting data JEP is accepted
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50320
Adjust JEP 301 once snapshotting data JEP is accepted
Change By:
Baptiste Mathus
{{JENKINS_HOME}} is referred to in [https://github.com/jenkinsci/jep/tree/master/jep/301#mutable-data] when the {{JENKINS-49406}} JEP totally restructures the filesystem organization for Jenkins data. PR for review: https://github.com/jenkinsci/jep/pull/67
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-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title Yoram Michaeli commented on JENKINS-50307 Re: While running in parallel for a loop, the index is wrong for each iteration Someone showed me this: https://jenkins.io/doc/pipeline/examples/#parallel-from-list which explains that this is not a bug but a feature (loopIndex1 byRef not byVal)). Still, I think that intuitively it looks like a bug since I expect it to behave in one way while it acts differently. 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-50329) HPE Loadrunner Plugin wont accept parameters for particular settings
Title: Message Title
Neil Cosgrove created an issue
Jenkins / JENKINS-50329
HPE Loadrunner Plugin wont accept parameters for particular settings
Issue Type:
Bug
Assignee:
Ofir Shaked
Attachments:
image-2018-03-22-14-31-10-017.png
Components:
hp-application-automation-tools-plugin
Created:
2018-03-22 01:34
Environment:
Jenkins v2.89.2 on Win 2012R2, HP-Application-automation-tools-plugin v5.3.5-beta-snapshot
Priority:
Major
Reporter:
Neil Cosgrove
I create a job within Jenkins with parameters, I Add a choice parameter (ScenarioDuration) with a selection of integers (minutes or seconds of scenario run time) and set the default to 5 minutes or 300 seconds. I use the 'Execute HPE tests from file system' build step. I enter '${ScenarioDuration}' in the 'Timeout' field (or the 'Scenario Execution Timeout' field in LoadRunner Settings) I receive the error message 'Timeout name must be a number' (or 'Per Scenario Timeout must be a number') and the value is not evaluated or replaced at job run time. This is the same issue as JENKINS-48652 but in the Run from File System rather than Performance Centre build step.
[JIRA] (JENKINS-50281) After upgrade OOPS is displayed for New multiconfiguration project or configuring exiting project after jenkins update to 2.107.1
Title: Message Title ARULANANTH SUBRAMANIAM commented on JENKINS-50281 Re: After upgrade OOPS is displayed for New multiconfiguration project or configuring exiting project after jenkins update to 2.107.1 Dear Oleg Nenashev, While uninstalling jenkins i did "apt-get purge jenkins", so all the jenkins logs got removed. Sorry for the inconvenience. Thanks, Arul 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-42643) Conditional application of triggers in Declarative
Title: Message Title Zach Weg edited a comment on JENKINS-42643 Re: Conditional application of triggers in Declarative We could really use a way to conditionally trigger scheduled multibranchpipeline builds by branch name with declarative dsl. [~ljbd]'s suggestion to use a "when" directive within the "trigger" block seems preferable. Any status update on this issue? 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-42643) Conditional application of triggers in Declarative
Title: Message Title Zach Weg commented on JENKINS-42643 Re: Conditional application of triggers in Declarative We could really use a way to conditionally trigger multibranchpipeline builds by branch name with declarative dsl. Łukasz Dudek's suggestion to use a "when" directive within the "trigger" block seems preferable. Any status update on this issue? 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-50330) checkJobName api always return an extra blank line in response body: " "
Title: Message Title pan xu updated an issue Jenkins / JENKINS-50330 checkJobName api always return an extra blank line in response body: " " Change By: pan xu Summary: checkJobName api always return Incomplete an extra blank line in response body: " " Attachment: jenkinsbug.png on create job page, when typing in the job name text box, Jenkins call checkJobName api to check the item name, but this api always return an Incomplete extra blank line in response body : " " . It caused the UI disable the submit button and I could never create a job. Please see the screenshot attached. An example of the checkJobName api call and response:Request URL: [ http://myjenkins.com/view/all/checkJobName?value=dfd ] Response:HTTP/1.1 200 OK Date: Thu, 22 Mar 2018 02:33:27 GMT Content-Type: text/html;charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding X-Content-Type-Options: nosniff Server: Tengine/Aserver Strict-Transport-Security: max-age=0 Timing-Allow-Origin: * EagleEye-TraceId: 0a67792f15216860072187973e2e7b RequestUri: jenkins.qa.umeng.com/view/all/checkJobName RequestApp: jenkins.qa.umeng.com Content-Encoding: gzip Add Comment
[JIRA] (JENKINS-50330) checkJobName api always return an extra blank line in response body: " "
Title: Message Title pan xu updated an issue Jenkins / JENKINS-50330 checkJobName api always return an extra blank line in response body: " " Change By: pan xu Attachment: jenkinsbug.png 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-50330) checkJobName api always return Incomplete body: " "
Title: Message Title pan xu created an issue Jenkins / JENKINS-50330 checkJobName api always return Incomplete body: " " Issue Type: Bug Assignee: Unassigned Attachments: jenkinsbug.png Components: jobgenerator-plugin Created: 2018-03-22 02:37 Environment: Linux 2.6.32-220.23.2.ali927.el5.x86_64 x86_64 Jenkins ver. 2.112 Priority: Blocker Reporter: pan xu on create job page, when typing in the job name text box, Jenkins call checkJobName api to check the item name, but this api always return an Incomplete response body : " ". It caused the UI disable the submit button and I could never create a job. An example of the checkJobName api call and response: Request URL: http://myjenkins.com/view/all/checkJobName?value=dfd Response: HTTP/1.1 200 OK Date: Thu, 22 Mar 2018 02:33:27 GMT Content-Type: text/html;charset=utf-8 Transfer-Encoding: chunked Connection: keep-alive Vary: Accept-Encoding X-Content-Type-Options: nosniff Server: Tengine/Aserver Strict-Transport-Security: max-age=0 Timing-Allow-Origin: * EagleEye-TraceId: 0a67792f15216860072187973e2e7b RequestUri: jenkins.qa.umeng.com/view/all/checkJobName RequestApp: jenkins.qa.umeng.com Content-Encoding: gzip
[JIRA] (JENKINS-50330) checkJobName api always return an extra blank line in response body: " "
Title: Message Title pan xu commented on JENKINS-50330 Re: checkJobName api always return an extra blank line in response body: " " compare to another Jenkins server on Mac, the Difference between response body is: the linux server return an extra empty line before the "", please see the screenshot attached. I update the bug description 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-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title Baptiste Mathus updated JENKINS-50164 Jenkins / JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Change By: Baptiste Mathus Status: In Review 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-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Jason Juang commented on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system Justin Georgeson Another problem I ran into is it is quite difficult to update the windows AMI. Say I have a collection of external libraries required to build my project in the AMI and I want to update it. I will create an instance of this AMI, update the libraries and then sysprep it to create a new AMI. However, there is a limitation in the numbers of sysprep I can do, so I had to create the AMI from scratch periodically which is quite troublesome compare to linux where you can create an image of an instance infinite amount of times. If I have a window server on 24/7 I won't run into the problem but it's too expensive to do so. Were you able to figure out a better solution? 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-50251) Rejected: org.apache.maven.model.Notifier
Title: Message Title Jesse Glick updated JENKINS-50251 pending release Jenkins / JENKINS-50251 Rejected: org.apache.maven.model.Notifier Change By: Jesse Glick 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-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Jason Juang edited a comment on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system [~jg_lgc] Another problem I ran into is it is quite difficult to update the windows AMI. Say I have a collection of external libraries required to build my project in the AMI and I want to update it. I will create an instance of this AMI, update the libraries and then sysprep it to create a new AMI. However, there is a limitation in the numbers of sysprep I can do, so I had to create the AMI from scratch periodically which is quite troublesome compare to linux where you can create an image of an instance infinite amount of times. If I have a window server on 24/7 I won't run into the this problem but it's too expensive to do so. Were you able to figure out a better solution? 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-50322) Option to select quality gate status to fail the build
Title: Message Title Marcos Nunes created an issue Jenkins / JENKINS-50322 Option to select quality gate status to fail the build Issue Type: New Feature Assignee: Rafael Ramos Components: sonar-quality-gates-plugin Created: 2018-03-21 16:17 Labels: plugin Priority: Major Reporter: Marcos Nunes Sonar have two Quality Gate problem status: Warning and Failed. I notice that warning status failed the Jenkins build, I would like to select what kind of problem (Warning or Failed) will fail the build on Jenkins. Will be great to select to failure only if the quality gate be failed. Add Comment
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Justin Georgeson commented on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system We use Packer to build our AMIs. 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-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Sam Van Oort commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Mike Kozell Several questions, then: 1. Are you on the latest versions of Artifactory plugin if you are using it? It had a memory leak with its Pipeline step in older versions, the latter has fixes that prevent leaks from occurring. 2. Are you using ConfigSlurper or extending java.util.Level in your Pipelines? Both can cause memory leaks and are discouraged now. 3. Do you have a fairly simple Pipeline that will reproduce the issue? My suspicion is that this represents an edge case perhaps linked to the failures above or a bad plugin interaction, because we have explicit tests for memory leaks in Pipeline. Finally... if you are by any chance a CloudBees customer, please open a support case with a support bundle & heap dump, because a heap dump + support bundle will give us the fastest route to a fix. While wearing my Open Source hat and not my CloudBees hat there's not a good & secure way to transfer a heap dump. Either way I consider memory leaks to be critical issues needing an urgent fix, but it's exponentially easier to do that with the additional information in a heap dump. 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-50323) PullRequestSCMHead and PullRequestSCMRevision external use
Title: Message Title Steven Foster created an issue Jenkins / JENKINS-50323 PullRequestSCMHead and PullRequestSCMRevision external use Issue Type: Task Assignee: Unassigned Components: github-branch-source-plugin Created: 2018-03-21 16:34 Environment: Github Branch Source 2.3.3 Priority: Minor Reporter: Steven Foster While working on an extension filter plugin for GitHub PR labels which adds an SCMHeadEvent implementation I noticed that the constructors for PullRequestSCMHead and PullRequestSCMRevision were package private. Using more generic classes, the scm source rejects the heads returned by the event and so the subscriber cannot operate. A locally modified version of GHBS with public constructors allowed the new plugin to work correctly. Discussion at https://groups.google.com/forum/#!topic/jenkinsci-dev/bLoYi3munDw Add Comment
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Justin Georgeson commented on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system Jason Juang We couldn't get that to work either. We have resigned ourselves to either adding User data in the AMI config to add a local admin user or set the admin password, or build our AMI with a fixed local admin user. 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-49539) Jenkins cannot trigger load runner scenario
Title: Message Title Rolando-Mihai Vlad edited a comment on JENKINS-49539 Re: Jenkins cannot trigger load runner scenario Hello Yojana Joshi, Could you please provide the file props14022018113427368.txt . ? Regards,Rolando 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-49539) Jenkins cannot trigger load runner scenario
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-49539 Re: Jenkins cannot trigger load runner scenario Hello Yojana Joshi, Could you please provide the file props14022018113427368.txt. Regards, Rolando 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-35359) Limit concurrent builds for 1 MultiBranch project
Title: Message Title
Jóhann Sigurðsson edited a comment on JENKINS-35359
Re: Limit concurrent builds for 1 MultiBranch project
For anyone so inclined, I came up with a workaround by: # Limiting Master node executors to 1 Pipeline builds # Creating a local slave agent and hooking it up to Jenkins to take care of other jobs # Forcing pipeline builds to only run on the Master node Declarative script example:{code:java}agent { label {label "Master" }}{code}
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-49752) Hudson returned status code -1
Title: Message Title Dasitha Karunajeewa commented on JENKINS-49752 Re: Hudson returned status code -1 Hi Boguslaw Klimas any update on this matter ? 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-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson created an issue Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Issue Type: Bug Assignee: Mark Waite Attachments: 20180321T164155.656172294.log Components: git-plugin, github-branch-source-plugin Created: 2018-03-21 15:50 Environment: Jenkins 2.89.4 GitHub Branch Source Plugin 2.3.3 (latest) Git plugin 3.8.0 (latest) git 2.11.0 git-lfs 2.4.0 Priority: Major Reporter: David Pärsson In a job created by the GitHub Branch Source plugin, git lfs pull fails with Bad credentials when building pull requests merged with the target branch. It works fine when building any branch separately. Here's the build log: Started by user Anonymous Connecting to https://api.github.com using github-user/** (GitHub username and password for github-user) Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Fetching without tags Fetching upstream changes from
[JIRA] (JENKINS-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev started work on JENKINS-50318 Change By: Oleg Nenashev 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-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev stopped work on JENKINS-50318 Change By: Oleg Nenashev Status: In Progress Open 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-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev updated JENKINS-50318 Jenkins / JENKINS-50318 Refusing to marshal com.google.common.util.concurrent.SettableFuture Change By: Oleg Nenashev 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-50318) Refusing to marshal com.google.common.util.concurrent.SettableFuture
Title: Message Title Oleg Nenashev commented on JENKINS-50318 Re: Refusing to marshal com.google.common.util.concurrent.SettableFuture I have created https://github.com/jenkinsci/ec2-fleet-plugin/pull/24 , but it is totally untested. Any feedback will be appreciated 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-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-50321
Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Change By:
David Pärsson
In a job created by the GitHub Branch Source plugin, {{git lfs pull}} fails with {{Bad credentials}} when building pull requests merged with the target branch.It works fine when building any branch separately. Here's the build log:{code:java}Started by user AnonymousConnecting to https://api.github.com using github-user/** (GitHub username and password for github-user)Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile> git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10Cleaning workspace> git rev-parse --verify HEAD # timeout=10Resetting working tree> git reset --hard # timeout=10> git clean -fdx # timeout=10Fetching without tagsFetching upstream changes from https://github.com/acme-inc/repo.git> git --version # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git fetch --no-tags --progress https://github.com/acme-inc/repo.git +refs/pull/512/head:refs/remotes/origin/PR-512 +refs/heads/master:refs/remotes/origin/masterMerging remotes/origin/master commit ac1ba744ee37a24027fb05a662b8ad79a675a19f into PR head commit f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeafEnabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull origin> git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f # timeout=10Enabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull originGitHub has been notified of this commit’s build resulthudson.plugins.git.GitException: Command "git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f" returned status code 128:stdout: stderr: Downloading path/to/some_file.zip (292 KB)Error downloading object: path/to/some_file.zip (b7bf2ce): Smudge error: Error downloading path/to/some_file.zip (b7bf2ceb57d399cd89d339f2cddf5c355979b580861346d7e1251a60bc3fbfe9): batch response: Bad credentialsErrors logged to /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script/.git/lfs/logs/20180321T163523.475698065.logUse `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failedfatal: path/to/some_file.zip: smudge filter lfs failedat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964)at
[JIRA] (JENKINS-49195) If we run multiple BlazeMeter tests every BlazeMeter Report link point to the first test
Title: Message Title Artem Fedorov resolved as Fixed Fixed in 4.1 Jenkins / JENKINS-49195 If we run multiple BlazeMeter tests every BlazeMeter Report link point to the first test Change By: Artem Fedorov Status: Open 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
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title
David Pärsson updated an issue
Jenkins / JENKINS-50321
Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Change By:
David Pärsson
In a job created by the GitHub Branch Source plugin, {{git lfs pull}} fails with {{Bad credentials}} when building pull requests merged with the target branch.It works fine when building any branch separately. Here's the build log:{code:java}Started by user AnonymousConnecting to https://api.github.com using github-user/** (GitHub username and password for github-user)Checking out git https://github.com/acme-inc/repo.git into /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script to read Jenkinsfile> git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> git config remote.origin.url https://github.com/acme-inc/repo.git # timeout=10Cleaning workspace> git rev-parse --verify HEAD # timeout=10Resetting working tree> git reset --hard # timeout=10> git clean -fdx # timeout=10Fetching without tagsFetching upstream changes from https://github.com/acme-inc/repo.git> git --version # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git fetch --no-tags --progress https://github.com/acme-inc/repo.git +refs/pull/512/head:refs/remotes/origin/PR-512 +refs/heads/master:refs/remotes/origin/masterMerging remotes/origin/master commit ac1ba744ee37a24027fb05a662b8ad79a675a19f into PR head commit f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeafEnabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull origin> git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f # timeout=10Enabling Git LFS pull> git config core.sparsecheckout # timeout=10> git checkout -f f2ccaf9bd99cf9596c9b0bfc9ae9e92bd747eeaf> git config --get remote.origin.url # timeout=10using GIT_ASKPASS to set credentials GitHub username and password for github-user> git lfs pull originGitHub has been notified of this commit’s build resulthudson.plugins.git.GitException: Command "git merge ac1ba744ee37a24027fb05a662b8ad79a675a19f" returned status code 128:stdout: stderr: Downloading path/to/some_file.zip (292 KB)Error downloading object: path/to/some_file.zip (b7bf2ce): Smudge error: Error downloading path/to/some_file.zip (b7bf2ceb57d399cd89d339f2cddf5c355979b580861346d7e1251a60bc3fbfe9): batch response: Bad credentialsErrors logged to /var/jenkins_home/jobs/some-job/branches/PR-512/workspace@script/.git/lfs/logs/20180321T163523.475698065.logUse `git lfs logs last` to view the log.error: external filter 'git-lfs filter-process' failedfatal: path/to/some_file.zip: smudge filter lfs failedat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964)at
[JIRA] (JENKINS-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title Mark Waite resolved as Duplicate Refer to JENKINS-45228 as the original description of this issue. The git plugin assumes that `git merge` does not require credentials. When LFS support was added to the git plugin, LFS credentials support was not added to the merge portion of the git plugin. Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Change By: Mark Waite Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this
[JIRA] (JENKINS-50164) 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50164 'Build Record Root Directory' is a UI option but is unsafe to change while Jenkins is running Change By: Baptiste Mathus Sprint: Essentials - Milestone 1 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-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Change By: Mark Waite Assignee: Mark Waite 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-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Mike Kozell commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace I switched a test Jenkins master back to MAX_SURVIVABILITY and still see the memory leak when failed builds occur. I'm going to test if the issue occurs on successful builds. 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-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson commented on JENKINS-50321 Re: Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin All right, I'll watch that. Thanks for a very fast response! 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-50321) Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin
Title: Message Title David Pärsson updated an issue Jenkins / JENKINS-50321 Git LFS fails for pull requests merged with the target branch with the GitHub Branch Source Plugin Change By: David Pärsson Component/s: github-branch-source-plugin 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.
