[JIRA] (JENKINS-53088) Node Xml is not valid to updateAlmEntity Rest Service. (Testset)
Title: Message Title Daniel Gront commented on JENKINS-53088 Re: Node Xml is not valid to updateAlmEntity Rest Service. (Testset) Roy Lu, is this step yours? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53159) Analysis Launch Error in Jenkins
Title: Message Title Daniel Gront closed an issue as Fixed Jenkins / JENKINS-53159 Analysis Launch Error in Jenkins Change By: Daniel Gront Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53271) Pipeline step of SSE and upload and SSE AUT missing client type
Title: Message Title Daniel Gront commented on JENKINS-53271 Re: Pipeline step of SSE and upload and SSE AUT missing client type Roy Lu, when opening tickets please add your product to the "Labels". 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53271) Pipeline step of SSE and upload and SSE AUT missing client type
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53271 Pipeline step of SSE and upload and SSE AUT missing client type Change By: Daniel Gront Labels: ALM 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52505) ci.jenkins.io builds failing on windows
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-52505 ci.jenkins.io builds failing on windows Change By: Daniel Gront Priority: Minor Critical 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51993) Failing to parse nunit 2 results file
Title: Message Title Tomas Zaleniakas commented on JENKINS-51993 Re: Failing to parse nunit 2 results file https://issues.jenkins-ci.org/browse/JENKINS-53034 fixes this issue 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53243) Clearcase SCM polling is failling because of working directory is not available
Title: Message Title Manikandan Chenthamarai updated an issue Jenkins / JENKINS-53243 Clearcase SCM polling is failling because of working directory is not available Change By: Manikandan Chenthamarai Clearcase scm polling is not working because of the below issue. These logs are captured from base clearcase polling log. [] $ cleartool catcs -tag FATAL: Process working directory 'C:\eps_deploy\' doesn't exist! Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from sgdc08150.zf-lenksysteme.net/ \ 10.99.4.130:60956 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.plugins.clearcase.HudsonClearToolLauncher.getLaunchedProc(HudsonClearToolLauncher.java:71) at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:143) at hudson.plugins.clearcase.ClearToolExec.runAndProcessOutput(ClearToolExec.java:915) at hudson.plugins.clearcase.ClearToolExec.catcs(ClearToolExec.java:104) at hudson.plugins.clearcase.ClearCaseSCM.hasNewConfigSpec(ClearCaseSCM.java:501) at hudson.plugins.clearcase.AbstractClearCaseScm.compareRemoteRevisionWith(AbstractClearCaseScm.java:887) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1406) at hudson.model.AbstractProject._poll(AbstractProject.java:1376) at hudson.model.AbstractProject.poll(AbstractProject.java:1287) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:594) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:640) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.io.IOException: Process working directory '' doesn't exist! Add Comment
[JIRA] (JENKINS-53243) Clearcase SCM polling is failling because of working directory is not available
Title: Message Title Manikandan Chenthamarai updated an issue Jenkins / JENKINS-53243 Clearcase SCM polling is failling because of working directory is not available Change By: Manikandan Chenthamarai Clearcase scm polling is not working because of the below issue. These logs are captured from base clearcase polling log. [ Jenkins_CI_SDK3_Var6_Init_16 ] $ cleartool catcs -tag CI_SDK3_Var6_Init FATAL: Process working directory 'C:\eps_deploy\ Jenkins_CI_SDK3_Var6_Init_16 ' doesn't exist!Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from sgdc08150.zf-lenksysteme.net/10.99.4.130:60956 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1693) at hudson.remoting.UserResponse.retrieve(UserRequest.java:310) at hudson.remoting.Channel.call(Channel.java:908) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1053) at hudson.Launcher$ProcStarter.start(Launcher.java:450) at hudson.plugins.clearcase.HudsonClearToolLauncher.getLaunchedProc(HudsonClearToolLauncher.java:71) at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:143) at hudson.plugins.clearcase.ClearToolExec.runAndProcessOutput(ClearToolExec.java:915) at hudson.plugins.clearcase.ClearToolExec.catcs(ClearToolExec.java:104) at hudson.plugins.clearcase.ClearCaseSCM.hasNewConfigSpec(ClearCaseSCM.java:501) at hudson.plugins.clearcase.AbstractClearCaseScm.compareRemoteRevisionWith(AbstractClearCaseScm.java:887) at hudson.scm.SCM.poll(SCM.java:408) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1406) at hudson.model.AbstractProject._poll(AbstractProject.java:1376) at hudson.model.AbstractProject.poll(AbstractProject.java:1287) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:594) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:640) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)java.io.IOException: Process working directory ' C:\eps_deploy\Jenkins_CI_SDK3_Var6_Init_16 ' doesn't exist!
[JIRA] (JENKINS-53243) Clearcase SCM polling is failling because of working directory is not available
Title: Message Title Manikandan Chenthamarai assigned an issue to sunfire Jenkins / JENKINS-53243 Clearcase SCM polling is failling because of working directory is not available Change By: Manikandan Chenthamarai Assignee: Praqma Support sunfire 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53301) Refusing to marshal org.jenkinsci.plugins.nvm.NvmWrapper
Title: Message Title Tomas Salazar updated an issue Jenkins / JENKINS-53301 Refusing to marshal org.jenkinsci.plugins.nvm.NvmWrapper Change By: Tomas Salazar Environment: nvm wrapper 0.1.6 on core version 2.102 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53301) Refusing to marshal org.jenkinsci.plugins.nvm.NvmWrapper
Title: Message Title Tomas Salazar created an issue Jenkins / JENKINS-53301 Refusing to marshal org.jenkinsci.plugins.nvm.NvmWrapper Issue Type: Bug Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2018-08-29 04:10 Environment: nvm wrapper on core version 2.102 Labels: JEP-200 Priority: Major Reporter: Tomas Salazar java.lang.UnsupportedOperationException: Refusing to marshal org.jenkinsci.plugins.nvm.NvmWrapper for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:530) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at
[JIRA] (JENKINS-49445) Cache/save external assets
Title: Message Title Tomas Salazar commented on JENKINS-49445 Re: Cache/save external assets solved in 0.0.16 it validate if it is nvm is installed. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46585) Do not generate *.env files in the workspace
Title: Message Title Tomas Salazar updated JENKINS-46585 Jenkins / JENKINS-46585 Do not generate *.env files in the workspace Change By: Tomas Salazar Status: In Progress Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46585) Do not generate *.env files in the workspace
Title: Message Title Tomas Salazar commented on JENKINS-46585 Re: Do not generate *.env files in the workspace solved in 0.0.16 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46585) Do not generate *.env files in the workspace
Title: Message Title Tomas Salazar started work on JENKINS-46585 Change By: Tomas Salazar 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Tomas Salazar commented on JENKINS-49720 Re: NVM wrapper hard-coded path I had published 0.0.16 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Tomas Salazar updated JENKINS-49720 Jenkins / JENKINS-49720 NVM wrapper hard-coded path Change By: Tomas Salazar Status: In Progress Review 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53300) test
Title: Message Title arun varma started work on JENKINS-53300 Change By: arun varma 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53300) test
Title: Message Title arun varma created an issue Jenkins / JENKINS-53300 test Issue Type: Bug Assignee: arun varma Components: test-stability-plugin Created: 2018-08-29 03:12 Environment: new env Priority: Minor Reporter: arun varma hi is to test how the Jenkins works Add Comment This
[JIRA] (JENKINS-53299) Cloud does not exist: kubernetes
Title: Message Title Kevin Cai updated an issue Jenkins / JENKINS-53299 Cloud does not exist: kubernetes Change By: Kevin Cai While I did the configuration for kubernetes plugin in "Manage Jenkins" -> "Configure System" -> "Cloud", I give the kubernetes cluster a different name other than "kubernetes". Then I created pipeline job with any config that uses PodTemplate to create kubernetes agents, it reported *ERROR: Cloud does not exist: kubernetes* I find no where to ** fix it until I get back to the system configuration and change my cloud name to the default "kubernetes". I think A proper behavior would be, if my cloud is configured a different name other than the default one, Kubernetes Pipeline should would be able to allow me specify the cloud name other than sticks to the default 'kubernetes' cloud name somewhere . 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53299) Cloud does not exist: kubernetes
Title: Message Title Kevin Cai commented on JENKINS-53299 Re: Cloud does not exist: kubernetes I have checked "kubernetes-plugin" source code on GitHub, looks like there is an interface "setCloud" in class org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStep. However these is nowhere this interface get called, so the actual pipeline step will always search the DEFAULT_CLOUD. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53299) Cloud does not exist: kubernetes
Title: Message Title Kevin Cai created an issue Jenkins / JENKINS-53299 Cloud does not exist: kubernetes Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-29 02:23 Environment: Jenkins ver. 2.121.3 Kubernetes-plugin 1.12.4 Priority: Minor Reporter: Kevin Cai While I did the configuration for kubernetes plugin in "Manage Jenkins" -> "Configure System" -> "Cloud", I give the kubernetes cluster a different name other than "kubernetes". Then I created pipeline job with any config that uses PodTemplate to create kubernetes agents, it reported ERROR: Cloud does not exist: kubernetes I find no where to ** fix it until I get back to the system configuration and change my cloud name to the default "kubernetes". I think Kubernetes Pipeline should be able to specify the cloud name other than sticks to the default 'kubernetes' cloud name. Add Comment
[JIRA] (JENKINS-43386) Not sending mail to user with permission to view
Title: Message Title David van Laatum commented on JENKINS-43386 Re: Not sending mail to user with permission to view Todd B That suggests that the email attached to the jenkins user is not the email it's trying to send to, they must match or it will put them into the no access category. And by jenkins user I mean the one they login to not the fake users you see under the people link that it creates for each seen committer 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53298) Typo in plugin Name
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-53298 Typo in plugin Name Issue Type: Bug Assignee: Nicolas De Loof Components: changes-since-last-success-plugin Created: 2018-08-29 01:02 Environment: Jenkins-2.121.3 changes-since-last-success-0.5 Priority: Trivial Reporter: Ian Williams In available plugins, name shows as found in pom.xml: Changes since last successfull build Plugin Should read: "successful", one "L". Add Comment
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Vinicius Xavier created an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-29 00:54 Environment: Jenkins 2.121.3 Kubernetes IKS 1.11 (Bluemix) Kubernetes Plugin 1.12.4 Labels: kubernetes-plugin jenkins Priority: Blocker Reporter: Vinicius Xavier I've Jenkins running on Kubernetes Cluster (Bluemix IKS). I am using the kubernetes plugin to create dynamic agents. The jenkins connection with agent is made in the standard way: Jenkins URL: jenkins:8080 Jenkins Tunnel: jenkins-agent:5 When i start a job, the agent connect with Jenkins master successfully. But he keeps long time and not execute pipeline steps. Agent logs: Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorAug 29, 2018 12:07:02 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up
[JIRA] (JENKINS-47501) 2 pods are started instead of 1 after update to version 1.1
Title: Message Title Erik Kristensen commented on JENKINS-47501 Re: 2 pods are started instead of 1 after update to version 1.1 I can confirm this is happening in 1.12.4 still. I'm seeing that if you have multiple jobs pending, and your jnlp container is crashing or and additional containers crash, the plugin exponentially tries to create more agents. It basically DDoS my k8s cluster. I had 64 workloads in the process of being added/removed due to a typo in the Jenkins Hostname for the jnlp agents to connect to. I had 20 jobs pending and the maximum for containers and instances are both set to 1. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53296) Screen jumping around when parallel stages are running
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-53296 Screen jumping around when parallel stages are running Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2018-08-28 23:12 Environment: Blue Ocean 1.8.2, Chrome latest version. Priority: Major Reporter: Naresh Rayapati We have about 10+ parallel steps each would run some shell script, takes random time to finish, say ~2 to ~10mins. When user is on one of the steps looking at the logs being tailed, the UI is getting refreshed automatically and suddenly it is taking us to other stage and is happening very frequently like within couple of seconds, causing a lot of confusion, not sure if we are missing something. It would be nice to have some kind of configuration to disable this auto refresh and allow users to select one of the stages (within parallel stages) and be on it while other stages are being executed. Please let me know if you need more information, I can provide an example but it may be hard to capture this behavior with that example, but I can try. Thanks for the consideration.
[JIRA] (JENKINS-53295) error log should be collapsed by default too
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-53295 error log should be collapsed by default too Change By: Naresh Rayapati Attachment: JenkinsRetryWithPrompt.gif 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53295) error log should be collapsed by default too
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-53295 error log should be collapsed by default too Change By: Naresh Rayapati Attachment: JenkinsRetryWithPrompt.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53295) error log should be collapsed by default too
Title: Message Title
Naresh Rayapati created an issue
Jenkins / JENKINS-53295
error log should be collapsed by default too
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
JenkinsRetryWithPrompt.png
Components:
blueocean-plugin
Created:
2018-08-28 22:57
Environment:
Blue Ocean 1.8.2
Priority:
Critical
Reporter:
Naresh Rayapati
We have implemented something called `retryWithPrompt` to avoid sudden failures on long running pipelines like environmental and other known issues. And also we have commands tailing long text before those actually fail, and retries on these steps doesn't guarantee that they would go through this time. This is leaving multiple error steps on the same stage and being those very long text when we initially land on that stage the page is too hard to browse, it would be very nice if we can make this configurable or make it default similar to other steps, like in progress step. Exampl
e:
node('LINUX') {
writeFile file: 'test.sh', text: "for i in {1..500}; do echo -n 'Loop \$i'; date ; sleep 1; done; exit 1"
waitUntil {
try {
sh 'chmod +x test.sh'
sh './test.sh'
return true
}
catch(e) {
println "Error: ${e}"
println "StackTrace: ${e.getStackTrace()}"
def userInput
timeout(900) {
userInput = input(id: 'userInput', message:
[JIRA] (JENKINS-53294) Pipeline build fails with GHFileNotFoundException not a user
Title: Message Title
Tyler Esser updated an issue
Jenkins / JENKINS-53294
Pipeline build fails with GHFileNotFoundException not a user
Change By:
Tyler Esser
Pipeline build fails during permissions check (with trust level set to "From users with Admin or Write permission"). Seems to be caused by the git commit {{_user.name_}} not being a GitHub username.Expected results of a user not being a GitHub user is to fail the permissions trust check, but not the build. Failed build URL: [https://singleb.cse.ucdavis.edu/blue/organizations/jenkins/aspect/detail/PR-2533/13/pipeline]Build log:{noformat}Started by user tjesserConnecting to https://api.github.com using **/** (**)Connecting to https://api.github.com to check permissions of obtain list of hfmarkp for geodynamics/aspectGitHub has been notified of this commit's build resultjava.io.FileNotFoundException: https://api.github.com/repos/geodynamics/aspect/collaborators/hfmarkp/permission at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at org.kohsuke.github.Requester.parse(Requester.java:617) at org.kohsuke.github.Requester.parse(Requester.java:599) at org.kohsuke.github.Requester._to(Requester.java:277)Caused: org.kohsuke.github.GHFileNotFoundException: {"message":"hfmarkp is not a user","documentation_url":"https://developer.github.com/v3/repos/collaborators/#review-a-users-permission-level"} at org.kohsuke.github.Requester.handleApiError(Requester.java:691) at org.kohsuke.github.Requester._to(Requester.java:298) at org.kohsuke.github.Requester.to(Requester.java:239) at org.kohsuke.github.GHRepository.getPermission(GHRepository.java:510) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource$DeferredPermissionsSource.fetch(GitHubSCMSource.java:2393) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSourceRequest.getPermissions(GitHubSCMSourceRequest.java:474) at org.jenkinsci.plugins.github_branch_source.ForkPullRequestDiscoveryTrait$TrustPermission.checkTrusted(ForkPullRequestDiscoveryTrait.java:340) at org.jenkinsci.plugins.github_branch_source.ForkPullRequestDiscoveryTrait$TrustPermission.checkTrusted(ForkPullRequestDiscoveryTrait.java:323) at jenkins.scm.api.trait.SCMHeadAuthority.isTrusted(SCMHeadAuthority.java:101) at jenkins.scm.api.trait.SCMSourceRequest.isTrusted(SCMSourceRequest.java:215) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.getTrustedRevision(GitHubSCMSource.java:1540) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:99) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{noformat}
[JIRA] (JENKINS-53294) Pipeline build fails with GHFileNotFoundException not a user
Title: Message Title Tyler Esser created an issue Jenkins / JENKINS-53294 Pipeline build fails with GHFileNotFoundException not a user Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2018-08-28 22:18 Environment: Kubernetes cluster - Helm install : stable/jenkins - jenkins/jenkins:2.138 - jenkins/jnlp-slave:3.23-1 - blueocean:1.8.2 - kubernetes:1.12.3 - workflow-aggregator:2.5 - xunit:2.2.3 Priority: Minor Reporter: Tyler Esser Pipeline build fails during permissions check (with trust level set to "From users with Admin or Write permission"). Seems to be caused by the git commit user.name not being a GitHub username. Expected results of a user not being a GitHub user is to fail the permissions check, but not the build. Failed build URL: https://singleb.cse.ucdavis.edu/blue/organizations/jenkins/aspect/detail/PR-2533/13/pipeline Build log: Started by user tjesser Connecting to https://api.github.com using **/** (**) Connecting to https://api.github.com to check permissions of obtain list of hfmarkp for geodynamics/aspect GitHub has been notified of this commit's build result java.io.FileNotFoundException: https://api.github.com/repos/geodynamics/aspect/collaborators/hfmarkp/permission at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getInputStream(HttpURLConnectionImpl.java:243) at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getInputStream(DelegatingHttpsURLConnection.java:210) at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:25) at
[JIRA] (JENKINS-52358) Jenkins 2.128 Broken Http/2 support
Title: Message Title Oleg Nenashev commented on JENKINS-52358 Re: Jenkins 2.128 Broken Http/2 support optimistically, next weekly 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52358) Jenkins 2.128 Broken Http/2 support
Title: Message Title Samuel Gabriel commented on JENKINS-52358 Re: Jenkins 2.128 Broken Http/2 support Any idea when this will be merged to Jenkins. I see it was already merged to winstone? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53293) when updating a job, if the logout times out, POST erases the job
Title: Message Title Brian Minton created an issue Jenkins / JENKINS-53293 when updating a job, if the logout times out, POST erases the job Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-08-28 22:04 Environment: Jenkins version 2.121.2 on CentOS linux 7 64 bit, with Java 1.8.0_152 Installed plugins: simple-theme-plugin: 0.4 scriptler: 2.9 workflow-step-api: 2.16 apache-httpcomponents-client-4-api: 4.5.5-3.0 ws-cleanup: 0.34 ivy: 1.28 jquery-detached: 1.2.1 workflow-durable-task-step: 2.19 nodelabelparameter: 1.7.2 mapdb-api: 1.0.9.0 ssh-slaves: 1.26 cvs: 2.14 run-condition: 1.0 instant-messaging: 1.35 workflow-support: 2.19 pipeline-stage-tags-metadata: 1.3.1 build-timeout: 1.19 pipeline-model-api: 1.3.1 junit: 1.24 ircbot: 2.30 javadoc: 1.4 jobgenerator: 1.22 gradle: 1.29 email-ext: 2.62 pipeline-stage-view: 2.10 artifactory: 2.16.2 any-buildstep: 0.1 resource-disposer: 0.11 script-security: 1.44 antisamy-markup-formatter: 1.5 text-finder-run-condition: 0.1 pipeline-model-extensions: 1.3.1 pipeline-input-step: 2.8 conditional-buildstep: 1.3.6 matrix-project: 1.13 cloudbees-folder: 6.5.1 ssh: 2.6.1 workflow-aggregator: 2.5 display-url-api: 2.2.0 command-launcher: 1.2 workflow-multibranch: 2.20 structs: 1.14 slack: 2.3 branch-api: 2.0.20 ldap: 1.20 extensible-choice-parameter: 1.6.0 powershell: 1.3 jsch: 0.1.54.2 log-parser: 2.0 jackson2-api: 2.8.11.3 bouncycastle-api: 2.16.3 http-trigger: 1.0-SNAPSHOT (private-09/21/2015 13:16-rmk) flexible-publish: 0.15.2 pipeline-rest-api: 2.10 pipeline-graph-analysis: 1.7 git-server: 1.7 ansicolor: 0.5.2 docker-commons: 1.13 ssh-credentials: 1.14 dynamic-axis: 1.0.3 momentjs: 1.1.1 elastic-axis: 1.2 workflow-job: 2.23 docker-workflow: 1.17 pipeline-model-definition: 1.3.1 managed-scripts: 1.4 rebuild: 1.28 plain-credentials: 1.4 authentication-tokens: 1.3 Parameterized-Remote-Trigger: 3.0.3 config-file-provider: 2.18 shelve-project-plugin: 2.1 workflow-basic-steps: 2.9 github: 1.29.2 pipeline-build-step: 2.7 parameterized-trigger: 2.35.2 workflow-cps: 2.54 scm-api: 2.2.7 extended-choice-parameter: 0.76 credentials-binding: 1.16 icon-shim: 2.0.3 mailer: 1.21 uno-choice: 2.1 pipeline-model-declarative-agent: 1.1.1 ssh-agent: 1.15 token-macro: 2.5 matrix-auth: 2.3 confluence-publisher: 2.0.1 git: 3.9.1 JiraTestResultReporter: 2.0.6 subversion: 2.11.1 workflow-api: 2.28 windows-slaves: 1.3.1 jdk-tool: 1.1 dynamic_extended_choice_parameter: 1.0.1 external-monitor-job: 1.7 active-directory: 2.8 multi-branch-project-plugin: 0.7 promoted-builds:
[JIRA] (JENKINS-45571) "likely stuck" job is not actually stuck.
Title: Message Title Sam Van Oort commented on JENKINS-45571 Re: "likely stuck" job is not actually stuck. Note from investigation: so, separate from JENKINS-50199 there appears to be a different but related failure mode: 1. The symptoms described by Anna will be reproduced if the build completes (WorkflowRun#finish is called), but the copyLogsTask never gets invoked or fails, since that is what actually removes the FlyWeightTask and kills the OneOffExecutor. See the CopyLogsTask logic - https://github.com/jenkinsci/workflow-job-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java#L403 2. If the AsynchronousExecution is never completed, we'll see a "likelyStuck" executor for each OneOffExecutor 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Sam Van Oort commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Observations from digging in together: 1. We can reproduce the restarted builds simply by setting the FlowExecution to completed for an incomplete build and dirty-restarting. 2. On restart that will trigger the build to be able to resume even when it shouldn't – we can avoid this by marking the build completed upon loading if the execution is done 3. The only place where the message about the build being done can be printed is WorkflowRun line 815 where it gets the StreamBuildListener and calls #finished on it (that prints the build completed message) 4. The build record has non-null logsToCopy - since that's nulled a few lines down from where the "build completed" message prints, just before saving the build, something prevented saving the build after that mutation - Devin Nusbaum speculates that it might be due to the BulkChange logic in WorkflowRun.save, which early-exits if there's a BulkChange containing the WorkflowRun – if the BulkChange aborts, the WorkflowRun's save operation will be a no-op (and it may not ever be saved). I have a small patch which closes the loophole around the completed execution but incomplete build (and passes a basic testcase), but point 4 still needs some thought. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53292) Create API for moving jobs
Title: Message Title Aaron Jensen created an issue Jenkins / JENKINS-53292 Create API for moving jobs Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-08-28 21:31 Environment: OS: Windows 2012 R2 Jenkins: 2.121.2 Priority: Minor Reporter: Aaron Jensen Please create an API endpoint for moving a job from one folder into another. We like to retain old jobs for 90 days, so we move jobs into a "Graveyard" folder. After 90 days, another process deletes them. I've tried POST'ing to the JOB_NAME/move endpoint, but that doesn't do anything. Add Comment
[JIRA] (JENKINS-48516) When adding a new Global Pipeline Libraries the previous repository information is lost
Title: Message Title Jim Stripsky edited a comment on JENKINS-48516 Re: When adding a new Global Pipeline Libraries the previous repository information is lost I have the same issue loading libraries with GIT in TeamForge. The issue exists using Chrome on Windows or Mac or Safari on Mac. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48516) When adding a new Global Pipeline Libraries the previous repository information is lost
Title: Message Title Jim Stripsky commented on JENKINS-48516 Re: When adding a new Global Pipeline Libraries the previous repository information is lost I have the same issue loading libraries with GIT in TeamForge. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 1-A-pipeline-en-root.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 1-B-blue-ocean-editor-ok.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 2-B-blue-ocean-editor-not-found.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 2-A-pipeline-en-folder.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 2-B-blue-ocean-editor-not-found.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 1-A-pipeline-en-root.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 2-A-pipeline-en-folder.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano updated an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Change By: Mariano Attachment: 1-B-blue-ocean-editor-ok.jpg 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53291) Visual Pipeline Editor does not work if the job is inside folders
Title: Message Title Mariano created an issue Jenkins / JENKINS-53291 Visual Pipeline Editor does not work if the job is inside folders Issue Type: Bug Assignee: Unassigned Attachments: 1-A-pipeline-en-root.jpg, 1-B-blue-ocean-editor-ok.jpg, 2-A-pipeline-en-folder.jpg, 2-B-blue-ocean-editor-not-found.png Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2018-08-28 20:09 Environment: OS: Windows Server R2 2008 Fundation (x64) Jenkins Version : Jenkins ver. 2.121.3 LTS - Plugins - - Blue Ocean 1.8.2 - - Blue Ocean Pipeline Editor 1.8.2 Priority: Minor Reporter: Mariano When the pipeline is located in the main view (root) of the Jenkins, from the Blue Ocean Dashboard you can access the Visual Pipeline Editor The pen is displayed in the top menu and allows access to the Pipeline edition. When the pipeline is moved inside a Folder (CloudBees Folders Plugin), the pen disappears to access the Pipeline edition.
[JIRA] (JENKINS-53290) Remoting changelog does not mention releases 3.24 or 3.25
Title: Message Title alison chan created an issue Jenkins / JENKINS-53290 Remoting changelog does not mention releases 3.24 or 3.25 Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2018-08-28 19:58 Priority: Minor Reporter: alison chan https://github.com/jenkinsci/remoting/blob/master/CHANGELOG.md Remoting changelog hasn't been updated since 29 June and does not mention releases 3.24 or 3.25, which occurred on 12 July and 31 July. Add Comment This message was sent by
[JIRA] (JENKINS-41996) Using a specific global library version in consumers sometimes causes notifications of build success/failure on the library that they consume
Title: Message Title benoit guerin commented on JENKINS-41996 Re: Using a specific global library version in consumers sometimes causes notifications of build success/failure on the library that they consume Using version 2.2.12, I still see this issue too. Both my pipeline librairies, configured as global with implicit load, and the repository being built are notified of build status. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title benoit guerin commented on JENKINS-41214 Re: bitbucket branch source plugin notifies wrong repository I think also this is a dupe of JENKINS-41996 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47932) VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure
Title: Message Title Ronnie Zhou updated an issue Jenkins / JENKINS-47932 VSTest Runner plugin is not shown in manage jenkins nor jenkins job configure Change By: Ronnie Zhou Environment: Jenkins LTS 2.73.3 / Jenkins LTS 2.89.3.4 VSTest plguin 1.0.5 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50154) Webhook delivery failed as X-Hub-Signature did not match calculated
Title: Message Title Josh McCullough commented on JENKINS-50154 Re: Webhook delivery failed as X-Hub-Signature did not match calculated BUMP! This is getting worse for us. We have more failed webhooks than succeeded now. We recently moved to multi-branch config, and now most of our webhook requests from GitHub are showing the "Provided signature [...] did not match to calculated" message. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Carlos Sanchez commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token it would be easier if questions are asked in the jenkins-user mailing list the post issue is a known one, filed somewhere you don't need any credentials or service account name when running in k8s. The serviceaccount name you want to use is set when you launch the jenkins master in its pod configuration 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token Found this article which says to copy the token from the secrets and paste as the secret text but when I did that and ran Test Connection it failed... I had to get that token and pipe to base64 -D to decode and then pasted that and connection successful. Also without using any credentials the connection was successful and I would believe that is because it's deployed from within k8s using helm stable/jenkins but the helm chart says to add the serviceaccount from helm status to Jenkins Credentials. https://github.com/helm/charts/blob/master/stable/jenkins/README.md (RBAC Section) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen edited a comment on JENKINS-40717 Re: Enable authentication using Kubernetes service account token [https://medium.com/containerum/how-to-setup-ci-cd-workflow-for-node-js-apps-with-jenkins-and-kubernetes-360fd0499556] Found this article which says to copy the token from the secrets and paste as the secret text but when I did that and ran Test Connection it failed... I had to get that token and pipe to base64 -D to decode and then pasted that and connection successful.Also without using any credentials the connection was successful and I would believe that is because it's deployed from within k8s using helm stable/jenkins but the helm chart says to add the serviceaccount from helm status to Jenkins Credentials.[https://github.com/helm/charts/blob/master/stable/jenkins/README.md] (RBAC Section) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token Yeah I'm running jenkins from inside k8s so wouldn't the Kubernetes Service Account work? Nothing allows you to specify which service-account to use. I also just attached another screenshot showing POST error. I'm guessing this is because it's inside k8s? How do you get around 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-40717 Enable authentication using Kubernetes service account token Change By: Chris Denneen Attachment: Screen Shot 2018-08-28 at 1.37.02 PM.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Carlos Sanchez commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token the other types read the token from filesystem when running inside k8s it's not the most obvious UX for sure 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title Carlos Sanchez commented on JENKINS-53002 Re: Resource request in declarative pod template ignored well, because you are not overriding the requests nor limits fields you inherit them from parent. Then the yaml in the child template is added. After that yaml is merged with other fields and the fields take precedence. It is hard to merge all the possible combinations in the yaml field 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token OK thanks... if the rest of those types are deprecated is there any reason they haven't been removed? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12610) Util.deleteRecursive fails for files using unmappable characters
Title: Message Title Valeriy Pastushenko commented on JENKINS-12610 Re: Util.deleteRecursive fails for files using unmappable characters Hello! Does anyone know of any workaround? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53002) Resource request in declarative pod template ignored
Title: Message Title Matt Buckland commented on JENKINS-53002 Re: Resource request in declarative pod template ignored Thanks. Yeah, that's it. I used a helm chart to deploy jenkins and it is indeed setting the limits on the default pod template. I thought I'd be able to override it here though. Isn't that the point of being able to inherit? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53129) Parallel stages in Blue Ocean showing wrong status
Title: Message Title Elie Kassis commented on JENKINS-53129 Re: Parallel stages in Blue Ocean showing wrong status Nicolae Pascu Vivek Pandey is there any estimation when this issue will 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Carlos Sanchez commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token You need to use the "Secret text" type and paste the token there 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token Even trying OpenShift OAuth Token provides no field to paste Token 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token Ok but as you can see from the attached screenshot there is no text field to paste 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan updated an issue Jenkins / JENKINS-33412 Jenkins locks when started in HTTPS mode on a host with 37+ processors Change By: Shaun Keenan Attachment: lwps.txt 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I see 1 parent with 112 LWPs. Attached lwps.txt 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53263) indeo-buildmaster Create Package not passing variables
Title: Message Title Jon Starbird commented on JENKINS-53263 Re: indeo-buildmaster Create Package not passing variables Andrew, that did fix it. Thank you so much for the fast turn around! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Carlos Sanchez commented on JENKINS-40717 Re: Enable authentication using Kubernetes service account token you don't need a serviceaccount name to connect to k8s, just the token 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Jesse Glick commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Check to see if you actually need run-condition + conditional-buildstep + parameterized-trigger. As noted elsewhere, these are not useful for Pipeline workflows. If there is a hard dependency chain from the latest version of some plugin you are bundling, that is probably fixable. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53285) Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages
Title: Message Title Jesse Glick commented on JENKINS-53285 Re: Update plugins used in Evergreen to remove "Created .../WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness" messages Check to see if you actually need run-condition + conditional-buildstep + parameterized-trigger. As noted elsewhere, these are not useful for Pipeline workflows. If there is a hard dependency chain from the latest version of some plugin you are bundling, that is probably fixable. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Craig Rodrigues commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Shaun Keenan any idea of how many proceses and threads were used by Jenkins when you started your test container? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42948) NullPointerException when parameterized project option is enabled but any parameter is set
Title: Message Title Mike Chmielewski commented on JENKINS-42948 Re: NullPointerException when parameterized project option is enabled but any parameter is set going to change component to core. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42948) NullPointerException when parameterized project option is enabled but any parameter is set
Title: Message Title Mike Chmielewski updated an issue Jenkins / JENKINS-42948 NullPointerException when parameterized project option is enabled but any parameter is set Change By: Mike Chmielewski Component/s: core Component/s: parameter-separator-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43977) Git checkout fails if submodule defined in .gitmodules don't exist
Title: Message Title Greg Hull commented on JENKINS-43977 Re: Git checkout fails if submodule defined in .gitmodules don't exist Just in case this helps someone else. The url in .gitmodules is case sensitive for the plugin. Running git in a command line is not case sensitive. This caused me some confusion since the git submodule update --init –recursive command would work from a command line, but I would get the following exception from the plugin. Once I changed the case in .gitmodules to match the case in the git repo the plugin worked. hudson.plugins.git.GitException: Command "git config --get submodule.x/xxx.url" returned status code 1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1964) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1960) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1597) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1609) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSubmoduleUrl(CliGitAPIImpl.java:1209) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1135) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:207) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:358) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused: java.io.IOException: Could not perform submodule update at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:113) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1238) at hudson.scm.SCM.checkout(SCM.java:495) at hudson.model.AbstractProject.checkout(AbstractProject.java:1202) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1724) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors Would love to know when we can expect to see this change in LTS - until this is in, I'll be stuck on 2.107.3, which has quite a few vulnerabilities we'd like to mitigate. The nodes this runs on are 72-core amd64 kubernetes nodes. FWIW, here's an example node: Capacity: cpu: 72 memory: 528332604Ki pods: 110 System Info: Machine ID: 833e0926ee21aed71ec075d726cbcfe0 System UUID: ----0CC47AC64A64 Boot ID: 786d3795-f026-4556-9047-923f95a9a331 Kernel Version: 4.14.44-coreos-r1 OS Image: Container Linux by CoreOS 1745.5.0 (Rhyolite) Operating System: linux Architecture: amd64 Container Runtime Version: docker://18.3.1 Kubelet Version: v1.8.10+coreos.0 Kube-Proxy Version: v1.8.10+coreos.0 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen updated an issue Jenkins / JENKINS-40717 Enable authentication using Kubernetes service account token Change By: Chris Denneen Attachment: Screen Shot 2018-08-28 at 12.03.43 PM.png 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40717) Enable authentication using Kubernetes service account token
Title: Message Title Chris Denneen reopened an issue Carlos Sanchez I agree with Nitin Padalia When you add this type of Kubernetes Service Account in the Jenkins UI there is no Value field so it shows "Secret text" and you have no control over the value to add the serviceaccount name used or add a token needed for that serviceaccount name. Anyway to validate with 1.12.0 and 1.12.4 with LTS 2.121.3 Jenkins / JENKINS-40717 Enable authentication using Kubernetes service account token Change By: Chris Denneen Resolution: Fixed Status: Closed Reopened 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title
Shaun Keenan edited a comment on JENKINS-33412
Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors
I just tested this on a 72-core k8s node and it worked perfectly. Published a docker image built off of this at ` {code:java} skeenan947/jenkinstest ` {code}
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33412) Jenkins locks when started in HTTPS mode on a host with 37+ processors
Title: Message Title Shaun Keenan commented on JENKINS-33412 Re: Jenkins locks when started in HTTPS mode on a host with 37+ processors I just tested this on a 72-core k8s node and it worked perfectly. Published a docker image built off of this at `skeenan947/jenkinstest` 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53076) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
Title: Message Title Mike Chmielewski resolved as Won't Fix Jenkins / JENKINS-53076 Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Change By: Mike Chmielewski Status: Open Resolved Resolution: Won't Fix 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53076) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
Title: Message Title Mike Chmielewski closed an issue as Won't Fix Jenkins / JENKINS-53076 Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Change By: Mike Chmielewski Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53076) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
Title: Message Title Mike Chmielewski commented on JENKINS-53076 Re: Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Please see JENKINS-23570 for why this won't be fixed. Between hard-coded-ness of the button, and this better being determined by job types, and therefore something closer to core functionality, this won't be fixed in this plugin, sorry. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50796) Parameters to pass one by one
Title: Message Title Mike Chmielewski updated an issue Jenkins / JENKINS-50796 Parameters to pass one by one Change By: Mike Chmielewski Component/s: core Component/s: parameter-separator-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50796) Parameters to pass one by one
Title: Message Title Mike Chmielewski commented on JENKINS-50796 Re: Parameters to pass one by one This has nothing to do with this parameter, as this is solely a UI enhancement, and won't ever touch the job execution engine. I will remove the parameter-separator-plugin from the components. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43070) Allow naming of parameter separators
Title: Message Title Mike Chmielewski resolved as Cannot Reproduce Jenkins / JENKINS-43070 Allow naming of parameter separators Change By: Mike Chmielewski Status: Open Resolved Resolution: Cannot Reproduce 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43070) Allow naming of parameter separators
Title: Message Title Mike Chmielewski closed an issue as Cannot Reproduce Jenkins / JENKINS-43070 Allow naming of parameter separators Change By: Mike Chmielewski Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43070) Allow naming of parameter separators
Title: Message Title Mike Chmielewski commented on JENKINS-43070 Re: Allow naming of parameter separators This can already be done by expanding the parameter in the job configuration screen, as of release 0.6 I believe. Closing for now, but if I am wrong, please reopen! 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42948) NullPointerException when parameterized project option is enabled but any parameter is set
Title: Message Title Mike Chmielewski commented on JENKINS-42948 Re: NullPointerException when parameterized project option is enabled but any parameter is set Sorry for the late follow up, but Is this actually an issue with the plugin? The stack trace makes no reference to it. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39138) no change in groovy still causes job xml to change
Title: Message Title Mike Chmielewski commented on JENKINS-39138 Re: no change in groovy still causes job xml to change This appears fixed by https://github.com/jenkinsci/parameter-separator-plugin/pull/7 I hope to release this soon-ish. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39138) no change in groovy still causes job xml to change
Title: Message Title Mike Chmielewski updated JENKINS-39138 See: https://github.com/jenkinsci/parameter-separator-plugin/pull/7 Jenkins / JENKINS-39138 no change in groovy still causes job xml to change Change By: Mike Chmielewski 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41712) NullPointerException when using parameter separator in a pipeline
Title: Message Title Mike Chmielewski updated JENKINS-41712 Jenkins / JENKINS-41712 NullPointerException when using parameter separator in a pipeline Change By: Mike Chmielewski 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27768) key=value parameter content causes build failure due to property conversion and windows bug
Title: Message Title Mike Chmielewski updated an issue Jenkins / JENKINS-27768 key=value parameter content causes build failure due to property conversion and windows bug Change By: Mike Chmielewski Component/s: parameter-separator-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Tomas Salazar commented on JENKINS-49720 Re: NVM wrapper hard-coded path Hi, I had some progress on this, I will try to push the changes to end of the day. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Rob Winch commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release Thanks for the response and thoughts. It might make sense to use bytecode-compatability-transformer since there are probably plugins that we don't know about. I'm not very familiar with this project. Is it something you would be able to take on? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27768) key=value parameter content causes build failure due to property conversion and windows bug
Title: Message Title Mike Chmielewski commented on JENKINS-27768 Re: key=value parameter content causes build failure due to property conversion and windows bug Removing parameter-separator-plugin from components, as it does not seem to be causing the problem. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23570) Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes
Title: Message Title Mike Chmielewski resolved as Won't Fix Jenkins / JENKINS-23570 Allow the paremetrised "Build" button to instead say "Deploy" instead of "Build" if the user wishes Change By: Mike Chmielewski Status: Reopened Resolved Resolution: Won't Fix 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. For more options, visit https://groups.google.com/d/optout.
