[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Øyvind R commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Thanks Jesse Glick. JENKINS 2111 has a very long thread, and I'm not sure which instructions you are talking about. If it's about adding -Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED, I tried this with no luck. 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-45427) Post steps
Title: Message Title Reinhold Füreder commented on JENKINS-45427 Re: Post steps Andrew Bayer Since all issues in epic are resolved, maybe this epic can be resolved to? (Sorry for this appears picky, I just try to help ) 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-54667) Getting Error while accessing Performance Report
Title: Message Title Satish Ramamuni created an issue Jenkins / JENKINS-54667 Getting Error while accessing Performance Report Issue Type: Bug Assignee: Andrey Pokhilko Attachments: Jenkins Error.txt Components: performance-plugin Created: 2018-11-16 07:02 Priority: Major Reporter: Satish Ramamuni Hi Team I am getting the below error while trying to Access Performance Report. I have even downgraded the version still the same issue. Please help. Error Details attached. Add Comment
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title
Laurens Leeuwis edited a comment on JENKINS-54566
Re: Failed to execute command Pipe.Flush
[~jglick] Using the patched version of the {{workflow-api}} did make the {{Pipe.Flush(-1)}} log disappear! Great :){quote}failure to actually show log output would be a real bug. What step is involved? If {{sh}}, are you running an up-to-date {{durable-task}} & {{workflow-durable-task-step}}?{quote}We still don't see some logging in blue ocean using the patched version of {{workflow-api}} (we do see the logging in the 'normal' Jenkins views). We are making extensive use of {{sh}} steps. We're using {{durable-task}} v1.27 and {{workflow-durable-task-step}} v2.26. I think it might not be related to this {{Pipe.Flush(-1)}} issue after all. I found that we're running an ancient version of {{blueocean}} (v1.0.0-b23). Might be best to ignore this for now .
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-54566) Failed to execute command Pipe.Flush
Title: Message Title Laurens Leeuwis commented on JENKINS-54566 Re: Failed to execute command Pipe.Flush Jesse Glick Using the patched version of the workflow-api did make the Pipe.Flush(-1) log disappear! Great failure to actually show log output would be a real bug. What step is involved? If sh, are you running an up-to-date durable-task & workflow-durable-task-step? We still don't see some logging in blue ocean using the patched version of workflow-api (we do see the logging in the 'normal' Jenkins views). We are making extensive use of sh steps. We're using durable-task v1.27 and workflow-durable-task-step v2.26. I think it might not be related to this Pipe.Flush(-1) issue after all. I found that we're running an ancient version of blueocean (v1.0.0-b23). Might be best to ignore 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-54394) Publish Over SSH plugin jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to change to remote directory [D:]]
Title: Message Title Erhan Karabulut commented on JENKINS-54394 Re: Publish Over SSH plugin jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection. Message: [Failed to change to remote directory [D:]] Error Alex , there is a solution ? 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-54666) vsphere plugin job succesful but VMs in vcenter not created
Title: Message Title Velan Nagarajan created an issue Jenkins / JENKINS-54666 vsphere plugin job succesful but VMs in vcenter not created Issue Type: Bug Assignee: Unassigned Attachments: Config1.png, Config2.png Components: vsphere-cloud-plugin Created: 2018-11-16 06:40 Environment: Jenkins 2.138.2 vSphere Plugin 2.18 Priority: Blocker Reporter: Velan Nagarajan Started by user ***|http://***.com:8080/user/***] [EnvInject] - Loading node environment variables. Building remotely on drake in workspace C:\cygwin\home\current\workspace\DeployVM [vSphere] [vSphere] Performing vSphere build step: "Deploy VM from template" [vSphere] Attempting to use server configuration: "E**Vcenter" [vSphere] Deploying new vm "AUTNEW" from template "***_Template" Finished: SUCCESS Above logs are displayed in console logs of vsphere job, But when i checked the vcenter for the VM existence VM is not created. Still the jenkins says job status success. I am blocked because of this and no VM creation is happening.
[JIRA] (JENKINS-52171) Gitlab plugin uncompatible with Jira plugin in pipeline
Title: Message Title Matej Dro commented on JENKINS-52171 Re: Gitlab plugin uncompatible with Jira plugin in pipeline This version actually crashed my jenkins on boot, so I could not even get to testing conflict. This was the exception: java.lang.NullPointerException at com.dabsquared.gitlabjenkins.connection.GitLabConnection.migrate(GitLabConnection.java:152) Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) Caused: java.lang.Error at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) 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: org.jvnet.hudson.reactor.ReactorException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:47) at jenkins.model.Jenkins.executeReactor(Jenkins.java:1099) at jenkins.model.Jenkins.(Jenkins.java:904) at hudson.model.Hudson.(Hudson.java:86) at hudson.model.Hudson.(Hudson.java:82) at hudson.WebAppMain$3.run(WebAppMain.java:233) Caused: hudson.util.HudsonFailedToLoad at hudson.WebAppMain$3.run(WebAppMain.java:250) Add Comment
[JIRA] (JENKINS-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Title: Message Title Kunal Doddanavar updated an issue Jenkins / JENKINS-36881 Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER Change By: Kunal Doddanavar Priority: Minor Major 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-36881) Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER
Title: Message Title Kunal Doddanavar commented on JENKINS-36881 Re: Promotion build Plugin does not work with jobs which are nested in Jenkins folder FOLDER SUNIJ khatri Oleg Nenashev Can you please list the workaround steps as I see the issue is still unresolved. Any update on when this issue can get fixed ? Thanks Kunal 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-54596) can't parse argument number: changelog.url
Title: Message Title fate king commented on JENKINS-54596 Re: can't parse argument number: changelog.url I also encountered this problem. I deleted the.jenkins in the root directory, and restarted Jenkins temporarily solved the problem. However, all previous configurations have been removed. I think it might be a problem with the latest version of 2.151. The version I returned was 2.149 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-53170) SCM Sync unmaintained
Title: Message Title Craig Rodrigues updated JENKINS-53170 Jenkins / JENKINS-53170 SCM Sync unmaintained Change By: Craig Rodrigues Status: Fixed but Unreleased 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-53170) SCM Sync unmaintained
Title: Message Title Craig Rodrigues updated JENKINS-53170 Jenkins / JENKINS-53170 SCM Sync unmaintained Change By: Craig Rodrigues Status: Open Fixed but Unreleased 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-53170) SCM Sync unmaintained
Title: Message Title Craig Rodrigues commented on JENKINS-53170 Re: SCM Sync unmaintained Antony Gelberg The Jenkins core devs are pushing pipeline heavily, so going in that direction is definitely the way to go for jobs. I understand that it is painful when you have a pile of "legacy" jobs, but going in the direction of Pipeline for jobs is better than dealing with plugins that try to band-aid over functionality lacking in earlier versions of Jenkins. For Configuration As Code, that stuff is newer, but it has received a lot of support via the Jenkins Enhancement Process (JEP), and seems to be the future of how the configuration of Jenkins itself can be handled in a way that can be more "devops" and "SCM" friendly. I would suggest that you try to work with the developers of that via the Gitter channel: https://jenkins.io/chat/ SCM Sync was good for its time, but it is in de-orbit and burn mode now, so I would recommend going with the direction of "modern" Jenkins for this stuff. 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-54665) Allow vSphere credentials overridable from job config page.
Title: Message Title Arun Batra created an issue Jenkins / JENKINS-54665 Allow vSphere credentials overridable from job config page. Issue Type: Improvement Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2018-11-16 04:41 Priority: Minor Reporter: Arun Batra The vsphere configuration including the credentials (which use the credentials plugin) have to be set at the jenkins master level. But we are part of a big enterprise and have credentials configured at folder level (folder plugin) rather than at the global level. This is for security reasons we cannot avoid. If there was an option to either configure the vsphere plugin at folder level or just be simply able to provide the creds to be used at the job level (in which case the credentials scoped at the folder level will be available for selection) at the vsphere build step, it would have been great. Add Comment
[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch
Title: Message Title Gunter Grodotzki commented on JENKINS-54206 Re: Merged PRs not being removed from multibranch Stephen Connolly any chance you could please give me a hint on how I can debug what is going wrong? 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-53952) Linux slaves are not starting anymore
Title: Message Title Gunter Grodotzki commented on JENKINS-53952 Re: Linux slaves are not starting anymore Still having it with c5.xlarge + plugin version 1.41 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-52942) Load Options load directory doesn't substitute a parameter
Title: Message Title Joe Muro commented on JENKINS-52942 Re: Load Options load directory doesn't substitute a parameter It seems that RTC plugin has no support for parameterized builds. I tried substituting a parameter for the workspace and load directory with no success. 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick commented on JENKINS-54566 Re: Failed to execute command Pipe.Flush Laurens Leeuwis if you are able to reproduce the Failed to execute command Pipe.Flush error, please try installing this build via Plugin Manager » Advanced. This plugin patch ought to try to flush a collected stream before its delegate is finalized. I also filed a separate fix for Remoting which would avoid the error in any event, but that could take much longer to appear in core builds. As an aside, my comment of 2018-11-13 can be disregarded: I found (and offered a fix for) a buglet in Remoting that it sometimes printed a message suggesting that it was about to display an explanatory stack trace, even if there was no further stack trace to display. 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title Jesse Glick commented on JENKINS-54128 Re: Deprecated calls to Run.getLogFile You may use Run.getLogText, or really anything besides getLogFile, on any build, Pipeline or freestyle. In your case the simplest fix looks to be to just call Run.getLogReader rather than using ParserRegistry.createReader(File). 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick updated JENKINS-54566 Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick 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-42620) java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error
Title: Message Title Patrick Dayton commented on JENKINS-42620 Re: java.lang.NoSuchMethodError: No such DSL method 'pipeline' found error Also have the same issue. Following the guide still results in weird errors. Error: java.lang.NoSuchMethodError: No such DSL method 'stage' found among steps Using Jenkins 2.138.3 on Ubuntu 16.04 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-54664) Error while trying to update completion status in TFS/Team Services
Title: Message Title
Rafael Camargo updated an issue
Jenkins / JENKINS-54664
Error while trying to update completion status in TFS/Team Services
Change By:
Rafael Camargo
|[Team Foundation Server Plug-in|http://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin] |[5.142.0|https://jenkins2.snsl.com.br/pluginManager/plugin/tfs/thirdPartyLicenses]|Jenkins 2 ERROR: Error while trying to update pending status in TFS/Team Servicesjava.lang.NullPointerException at hudson.plugins.tfs.util.TeamStatus.addStatus(TeamStatus.java:87) at hudson.plugins.tfs.util.TeamStatus.createFromRun(TeamStatus.java:66) at hudson.plugins.tfs.TeamPendingStatusBuildStep.perform(TeamPendingStatusBuildStep.java:44) at hudson.plugins.tfs.listeners.JenkinsRunListener.onStarted(JenkinsRunListener.java:35) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:240) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:295) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) > git rev-parse --is-inside-work-tree # timeout=10Setting origin to ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core > git config remote.origin.url ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core # timeout=10Fetching origin...Fetching upstream changes from origin > git --version # timeout=10 > git config --get remote.origin.url # timeout=10using GIT_SSH to set credentials > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core # timeout=10Fetching without tagsFetching upstream changes from ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core > git --version # timeout=10using GIT_SSH to set credentials > git fetch --no-tags --progress ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core +refs/heads/*:refs/remotes/origin/* > git rev-parse null^\{commit} # timeout=10[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: Error while trying to update completion status in TFS/Team Servicesjava.lang.NullPointerException at hudson.plugins.tfs.util.TeamStatus.addStatus(TeamStatus.java:87) at hudson.plugins.tfs.util.TeamStatus.createFromRun(TeamStatus.java:66) at hudson.plugins.tfs.TeamCompletedStatusPostBuildAction.perform(TeamCompletedStatusPostBuildAction.java:47) at hudson.plugins.tfs.listeners.JenkinsRunListener.onCompleted(JenkinsRunListener.java:48) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) at org.jenkinsci.plugins.workflow.job.WorkflowRun.finish(WorkflowRun.java:807) at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:143) at org.jenkinsci.plugins.workflow.job.WorkflowRun$GraphL.onNewHead(WorkflowRun.java:1220) at
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick commented on JENKINS-54566 Re: Failed to execute command Pipe.Flush the job which always gave the error message was not able to show logging for the steps it executed Unlike the stack trace reported in the original description, which is merely log noise as far as I know, failure to actually show log output would be a real bug. What step is involved? If sh, are you running an up-to-date durable-task & workflow-durable-task-step? 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-54664) Error while trying to update completion status in TFS/Team Services
Title: Message Title Rafael Camargo created an issue Jenkins / JENKINS-54664 Error while trying to update completion status in TFS/Team Services Issue Type: Task Assignee: redsolo Components: tfs-plugin Created: 2018-11-15 23:55 Priority: Minor Reporter: Rafael Camargo ERROR: Error while trying to update pending status in TFS/Team Services java.lang.NullPointerException at hudson.plugins.tfs.util.TeamStatus.addStatus(TeamStatus.java:87) at hudson.plugins.tfs.util.TeamStatus.createFromRun(TeamStatus.java:66) at hudson.plugins.tfs.TeamPendingStatusBuildStep.perform(TeamPendingStatusBuildStep.java:44) at hudson.plugins.tfs.listeners.JenkinsRunListener.onStarted(JenkinsRunListener.java:35) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:240) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:295) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core > git config remote.origin.url ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git config --get remote.origin.url # timeout=10 using GIT_SSH to set credentials > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core # timeout=10 Fetching without tags Fetching upstream changes from ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core > git --version # timeout=10 using GIT_SSH to set credentials > git fetch --no-tags --progress ssh://tfs.seniorsolution.com.br:22/PD/Previdencia/_git/previdencia-core +refs/heads/:refs/remotes/origin/ >
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick Component/s: remoting 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick started work on JENKINS-54566 Change By: Jesse Glick 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick commented on JENKINS-54566 Re: Failed to execute command Pipe.Flush it does the finalize first and flush afterwards Irrelevant since super.finalize() is a no-op. I think the issue is that, at random, ProxyOutputStream.finalize might be called before DelayBufferedOutputStream.finalize. 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-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Swachender Kasarla updated an issue Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Change By: Swachender Kasarla I am unable to run builds successfully from Jenkins using Performance Center. When build is executed , a run id is creatingin PC but not running scenario. Attached Performance Center server logs h1. Console OutputStarted by user [Swach Kasarla|http://qa080:8080/user/skasarla]Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\Testing123Thu 11.15.2018 at 04:29:25 PM EST - plugin version is '5.5'Thu 11.15.2018 at 04:29:25 PM EST - - - -Test description: TestThu 11.15.2018 at 04:29:25 PM EST - Validating parameters before runThu 11.15.2018 at 04:29:25 PM EST - OKThu 11.15.2018 at 04:29:25 PM EST - Trying to login[PCServer='[http://nym-entpc1-cj|http://nym-entpc1-cj/]', User %20User ='skasarla']Thu 11.15.2018 at 04:29:25 PM EST - Login succeededThu 11.15.2018 at 04:29:25 PM EST - Executing Load Test: Test ID: 4856 Test Instance ID: 1052 Timeslot Duration: 0:30(h:mm) Post Run Action: Collate Results Use VUDS: false Thu 11.15.2018 at 04:29:47 PM EST - Error: executeRequest exception: Operation failed. Error code: 1001Thu 11.15.2018 at 04:29:47 PM EST - Error: Run could not start!Thu 11.15.2018 at 04:29:48 PM EST - Logout succeededThu 11.15.2018 at 04:29:48 PM EST - Empty ResultsThu 11.15.2018 at 04:29:48 PM EST - Result Status: FAILURE- - -Build step 'Execute performance test using Performance Center' changed build result to FAILUREFinished: FAILURE Add Comment
[JIRA] (JENKINS-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Swachender Kasarla updated an issue Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Change By: Swachender Kasarla Attachment: Server logs.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-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Swachender Kasarla updated an issue Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Change By: Swachender Kasarla I am unable to run builds successfully from Jenkins using Performance Center. When build is executed , a run id is creatingin PC but not running scenario.h1. Console OutputStarted by user [Swach Kasarla|http://qa080:8080/user/skasarla]Building on master in workspace C:\Program Files (x86)\Jenkins\workspace\Testing123Thu 11.15.2018 at 04:29:25 PM EST - plugin version is '5.5'Thu 11.15.2018 at 04:29:25 PM EST - - - -Test description: TestThu 11.15.2018 at 04:29:25 PM EST - Validating parameters before runThu 11.15.2018 at 04:29:25 PM EST - OKThu 11.15.2018 at 04:29:25 PM EST - Trying to login[PCServer='[http://nym-entpc1-cj|http://nym-entpc1-cj/]', User='skasarla']Thu 11.15.2018 at 04:29:25 PM EST - Login succeededThu 11.15.2018 at 04:29:25 PM EST - Executing Load Test: Test ID: 4856 Test Instance ID: 1052 Timeslot Duration: 0:30(h:mm) Post Run Action: Collate Results Use VUDS: false Thu 11.15.2018 at 04:29:47 PM EST - Error: executeRequest exception: Operation failed. Error code: 1001Thu 11.15.2018 at 04:29:47 PM EST - Error: Run could not start!Thu 11.15.2018 at 04:29:48 PM EST - Logout succeededThu 11.15.2018 at 04:29:48 PM EST - Empty ResultsThu 11.15.2018 at 04:29:48 PM EST - Result Status: FAILURE- - -Build step 'Execute performance test using Performance Center' changed build result to FAILUREFinished: FAILURE Add Comment
[JIRA] (JENKINS-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick Assignee: Jeff Thompson Jesse Glick 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-54566) Failed to execute command Pipe.Flush
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54566 Failed to execute command Pipe.Flush Change By: Jesse Glick Component/s: workflow-api-plugin Component/s: remoting 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-54663) Unable to run Perfromance Center scenario from Jenkins
Title: Message Title Swachender Kasarla created an issue Jenkins / JENKINS-54663 Unable to run Perfromance Center scenario from Jenkins Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-11-15 23:08 Priority: Major Reporter: Swachender Kasarla 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-49669) readJSON returns non serializable JSON object
Title: Message Title Jesse Glick commented on JENKINS-49669 Re: readJSON returns non serializable JSON object BTW I would suggest that readJSON be deprecated and replaced with something which does the JSON parsing but then actually returns a plain old mixture of ArrayList, HashMap, String, and primitive wrappers. 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Ulli Hafner edited a comment on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
Should {{Run#getLogText}} be used for pipelines and freestyle jobs? Or just for pipelines?Are there some recommendation on how to process the {{AnnotatedLargeText}} instance? In the warnings plugin I need to scan the log line by line with a parser. One way I see is to use {{writeLogTo}} and write the output stream to a an intermediate file. Or is this not recommended?
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-42830) No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-42830 No such property: ci for class: groovy.lang.Binding when updating Multibranch plugins Change By: Vivek Pandey Labels: diagnostics triaged-2018-11 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Ulli Hafner commented on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
Should Run#getLogText be used for pipelines and freestyle jobs? Or just for pipelines? Are there some recommendation on how to process the AnnotatedLargeText }} instance? In the warnings plugin I need to scan the log line by line with a parser. One way I see is to use {{writeLogTo and write the output stream to a intermediate file. Or is this not recommended?
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-54128) Deprecated calls to Run.getLogFile
Title: Message Title
Ulli Hafner edited a comment on JENKINS-54128
Re: Deprecated calls to Run.getLogFile
Should {{Run#getLogText}} be used for pipelines and freestyle jobs? Or just for pipelines?Are there some recommendation on how to process the {{AnnotatedLargeText }} instance? In the warnings plugin I need to scan the log line by line with a parser. One way I see is to use {{writeLogTo}} and write the output stream to a intermediate file. Or is this not recommended?
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-48767) Unable to invoke private library
Title: Message Title Andrew Bayer commented on JENKINS-48767 Re: Unable to invoke private library Are the credentials being used folder-scoped? Because that'd be JENKINS-43802 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-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Jesse Glick commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Please follow the diagnostic instructions given in JENKINS-2111. 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace A similar report in JENKINS-54654. Please use that for discussion. 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-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54654 A recent update breaks builds by escaping slashes to percent signs in workspace paths Change By: Jesse Glick Component/s: branch-api-plugin Component/s: pipeline Component/s: pipeline-multibranch-defaults-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-37322) Pipeline documentation missing archiveArtifact documentation
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37322 Pipeline documentation missing archiveArtifact documentation Change By: Vivek Pandey Labels: documentation triaged-2018-11 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-37384) Changes view issues using Mercurial with Multibranch pipeline
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37384 Changes view issues using Mercurial with Multibranch pipeline Change By: Vivek Pandey Labels: multibranch pipeline scm-api-tidy-reject triaged-2018-11 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-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54081 Timestamps missing for agent-based steps in Pipeline Job 2.26 Change By: Vivek Pandey Labels: regression triaged-2018-11 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-54640) Workspace folders are not unique
Title: Message Title Jesse Glick commented on JENKINS-54640 Re: Workspace folders are not unique The fix of JENKINS-2111 removed the long hash from workspace names. However, it introduced a workspaces.txt file which tracks which directory is used for which project. Evidently this is not working in your case. Please provide complete steps to reproduce the problem from scratch, or at a minimum run this build (Plugin Manager » Advanced to upload) and create a custom logger on jenkins.branch.WorkspaceLocatorImpl to assist in remote diagnosis. 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-39233) Duplicate "Tag this build" links in Pipeline
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-39233 Duplicate "Tag this build" links in Pipeline Change By: Vivek Pandey Labels: plugin tag triaged-2018-11 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-38432) Using SimpleTemplateEngine in a pipeline script causes java.io.NotSerializableException: java.io.PrintWriter
Title: Message Title Andrew Bayer resolved as Won't Fix Sorry, this is just an unescapable collision of SimpleTemplateEngine exposing things that make it not work in Pipeline due to how Pipeline works. Jenkins / JENKINS-38432 Using SimpleTemplateEngine in a pipeline script causes java.io.NotSerializableException: java.io.PrintWriter Change By: Andrew Bayer 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-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-37589 Replay link does not show up if Jenkinsfile had a syntax error Change By: Vivek Pandey Labels: community-bee maybe-fixed-by-durability-megafix triaged-2018-11 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-54640) Workspace folders are not unique
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54640 Workspace folders are not unique Change By: Jesse Glick Component/s: branch-api-plugin Component/s: pipeline Component/s: pipeline-multibranch-defaults-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-46503) Pipeline hanging after updating Jenkinsfile but before starting to build
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-46503 Pipeline hanging after updating Jenkinsfile but before starting to build Change By: Andrew Bayer Component/s: jira-plugin Component/s: git-plugin Component/s: pipeline 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-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-50307 While running in parallel for a loop, the index is wrong for each iteration Change By: Vivek Pandey Labels: parallel pipeline triaged-2018-11 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Jesse Glick resolved as Won't Fix This issue became obsolete with the release of the fix of JENKINS-2111. Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Jesse Glick 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.
[JIRA] (JENKINS-46503) Pipeline hanging after updating Jenkinsfile but before starting to build
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-46503 Pipeline hanging after updating Jenkinsfile but before starting to build Change By: Vivek Pandey Labels: pipeline-hangs triaged-2018-11 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-27306) unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-27306 unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[] Change By: Vivek Pandey Labels: pipeline triaged-2018-11 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-47724) Pipeline with parallel jobs performance issue with EC2 slaves
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47724 Pipeline with parallel jobs performance issue with EC2 slaves Change By: Vivek Pandey Issue Type: Bug Improvement 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-39552) After restart, interrupted pipeline deadlocks waiting for executor
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-39552 After restart, interrupted pipeline deadlocks waiting for executor Change By: Vivek Pandey Labels: cloudbees-internal-pipeline pipeline triaged-2018-11 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-39154) Can not edit Pipeline script - text not visible on Configure Page
Title: Message Title Vivek Pandey resolved as Cannot Reproduce Can't reproduce, please reopen if you see this happening. Jenkins / JENKINS-39154 Can not edit Pipeline script - text not visible on Configure Page Change By: Vivek Pandey Status: Reopened 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-39621) Pipeline job loop after polling always find changes
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-39621 Pipeline job loop after polling always find changes Change By: Vivek Pandey Labels: git-plugin triaged-2018-11 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-36956) Pipeline hangs on JUnitResultArchiver step with test publishers
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-36956 Pipeline hangs on JUnitResultArchiver step with test publishers Change By: Vivek Pandey Labels: 2.0 junit pipeline pipeline-build-step-plugin triaged-2018-11 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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Vivek Pandey Labels: regression triaged-2018-11 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-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-44924 pipeline groovy script - Sort a list with custom comparator or closure not sorting Change By: Vivek Pandey Labels: groovy pipeline triaged-2018-11 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-47497) Jenkins Pipeline GDSL Autocompletion does not work in IntelliJ IDEA.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47497 Jenkins Pipeline GDSL Autocompletion does not work in IntelliJ IDEA. Change By: Vivek Pandey Labels: autocomplete gdsl intellij jenkins pipeline triaged-2018-11 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-47299) Multibranch pipelines with Jenkinsfile in big svn repositories is unusable
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-47299 Multibranch pipelines with Jenkinsfile in big svn repositories is unusable Change By: Vivek Pandey Labels: multibranch pipeline svn triaged-2018-11 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-43176) MercurialChangeLogParser fails in parallel checkouts
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-43176 MercurialChangeLogParser fails in parallel checkouts Change By: Vivek Pandey Labels: checkout mercurial threads triaged-2018-11 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-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Vivek Pandey Labels: diagnostics groovy kohsuke-plane-project triaged-2018-11 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-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-40057 Stage view is completely missing for long durations after restarts Change By: Vivek Pandey Labels: configuration jenkins pipeline plugin triaged-2018-11 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-29326) Workflow sidebar has duplicated Git Build Data links
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-29326 Workflow sidebar has duplicated Git Build Data links Change By: Vivek Pandey Labels: community-bee multibranch triaged-2018-11 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-43802) Shared Library using folder-scoped credential fails to authenticate
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-43802 Shared Library using folder-scoped credential fails to authenticate Change By: Vivek Pandey Labels: cloudbees-internal-steel pipeline-improvement shared-libraries triaged-2018-11 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-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52362 Jenkins hangs due to "Running CpsFlowExecution unresponsive" Change By: Vivek Pandey Labels: pipeline threads triaged-2018-11 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-32766) groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-32766 groovy.xml.MarkupBuilder fails in Pipeline with NoSuchMethodError Change By: Vivek Pandey Labels: groovy triaged-2018-11 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-29840) when workflow uses multiple git repos the "git build data" and "tags" become next to useless.
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-29840 when workflow uses multiple git repos the "git build data" and "tags" become next to useless. Change By: Vivek Pandey Labels: community-bee triaged-2018-11 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-41339) Environment variables referencing other variables broken
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-41339 Environment variables referencing other variables broken Change By: Vivek Pandey Labels: blue-pipeline-scrub regression triaged-2018-11 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-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-34256 Preparing Jenkins For Shutdown Hangs Running Pipelines Change By: Vivek Pandey Labels: 1.651.1 2.0 2.0-rc lts testfest triaged-2018-11 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-38706) Workspace directory names mangled in multibranch pipeline
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-38706 Workspace directory names mangled in multibranch pipeline Change By: Vivek Pandey Labels: pipeline triaged-2018-11 workspace 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-52876) gitlab-oauth breaks slaves auth
Title: Message Title Chris Meisinger commented on JENKINS-52876 Re: gitlab-oauth breaks slaves auth As a heads up, I just ran into this exact problem. The answer was to go and create a Personal Access Token for the user that Swarm is trying to authenticate as and use that in place of the -password option. I also created a matrix based auth strategy, and assigned the swarm-client user's group to the appropriate permissions to create a CI node. Hope that helps! 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-32469) Allow falling back to on demand when spot prices are higher then limit.
Title: Message Title Brian Melanson edited a comment on JENKINS-32469 Re: Allow falling back to on demand when spot prices are higher then limit. Agree, this would be a very useful feature, useful in this situation (https://issues.jenkins-ci.org/browse/JENKINS-39283 ) , often because a spot instance of a certain type is unavailable for allocation. 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-32469) Allow falling back to on demand when spot prices are higher then limit.
Title: Message Title Brian Melanson commented on JENKINS-32469 Re: Allow falling back to on demand when spot prices are higher then limit. Agree, this would be a very useful feature, useful in this situation (https://issues.jenkins-ci.org/browse/JENKINS-39283 ) 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-54662) hudson.model.UsageStatistics not compatible with CasC plugin
Title: Message Title Daniel Garzon created an issue Jenkins / JENKINS-54662 hudson.model.UsageStatistics not compatible with CasC plugin Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-11-15 21:24 Priority: Minor Reporter: Daniel Garzon When trying to configure Jenkins through CASC plugin, one desired feature is to enable / disable "Usage Statistics". Unfortunately, the hudson.model.UsageStatistics descriptor is lacking a @DataBoundSetter and just relies on the configure function to apply the appropriate configuration to the Jenkins instance. According to: https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/REQUIREMENTS.md, we need a boolean field with a getter and setter annotated with @DataBoundSetter so that we can configure it from within the CASC plugin. We would also have to modify the configure function according to the requirements of the CASC plugin, which should follow best-practices. I would like to contribute with this change if one of the Core Developers agree. Add Comment
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Stu Farish commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 "An easy workaround that has been used for several pipelines that have run into this issue is to rename the pipeline. Not ideal but can add a suffix or prefix to the pipeline until you run into the issue again. " I don't understand what that means? In terms of this, what's the pipeline? 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Gabriel Loewen updated JENKINS-49723 Jenkins / JENKINS-49723 Powershell execution within GIT Multibranch pipeline failing Change By: Gabriel Loewen Status: Fixed but Unreleased Resolved 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-49723) Powershell execution within GIT Multibranch pipeline failing
Title: Message Title Gabriel Loewen updated JENKINS-49723 Jenkins / JENKINS-49723 Powershell execution within GIT Multibranch pipeline failing Change By: Gabriel Loewen Status: Open Fixed but Unreleased 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-54661) DataSource properties are ignored
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-54661 DataSource properties are ignored Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-11-15 20:56 Priority: Minor Reporter: Cyrille Le Clerc 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-54661) DataSource properties are ignored
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-54661 DataSource properties are ignored Change By: Cyrille Le Clerc DataSource properties are ignored 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-54660) CPU load at 100% across all cores requires machine restart to resolve
Title: Message Title Joe Rioux created an issue Jenkins / JENKINS-54660 CPU load at 100% across all cores requires machine restart to resolve Issue Type: Bug Assignee: Unassigned Attachments: jenkins.log.20181107_0723am_lockup_happened-ERROR, thread_dump.txt Components: core Created: 2018-11-15 20:49 Environment: Jenkins 2.148 System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_181-b13 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_181 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.181-b13 jenkins.install.runSetupWizard false JENKINS_HOME /var/lib/jenkins jetty.git.hash 27208684755d94a92186989f695db2d7b21ebc51 jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna3091412087555830160.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-862.14.4.el7.x86_64 path.separator : permissive-script-security.enabled true sun.arch.data.model 64 sun.boot.class.path
[JIRA] (JENKINS-54659) broken layout at setup
Title: Message Title peterdd peterdd created an issue Jenkins / JENKINS-54659 broken layout at setup Issue Type: Bug Assignee: Unassigned Attachments: jenkins_csslineheight.png Components: core Created: 2018-11-15 20:03 Environment: Jenkins 2.138.3 (current jenkins/jenkins:lts docker image) Safari,Firefox,Chrome Labels: UI installation gui Priority: Minor Reporter: peterdd peterdd Wanted jenkins give a try, installed it with docker run --name=jenkins --publish 8080:8080 --publish 5:5 jenkins/jenkins:lts (in a Vagrantfile) After inserting the generated key by the installation the next page has the broken text layout as shown in the attached screenshot. All 3 browsers Safari, Chrome, Firefox show the broken layout. CSS font-size: 57px and line-height: 1.4em seems related to the body font-size, not the h1 font-size, which leads to the small line-height and the garbled title text.
[JIRA] (JENKINS-54320) Move audit log plugin to jenkinsci organization
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54320 Move audit log plugin to jenkinsci organization Change By: Matt Sicker Labels: audit-logging 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-54658) Add Jenkins build for audit log plugin
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54658 Add Jenkins build for audit log plugin Change By: Matt Sicker Labels: audit-logging 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-54636) Configure default audit logging output configuration
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54636 Configure default audit logging output configuration Change By: Matt Sicker Labels: audit-logging 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-54089) Create an audit log destination global configuration
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54089 Create an audit log destination global configuration Change By: Matt Sicker Labels: audit-logging newbie-friendly 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-54637) Create a servlet filter to prepopulate audit log attributes
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54637 Create a servlet filter to prepopulate audit log attributes Change By: Matt Sicker Labels: audit-logging 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-54088) Log audit events for user creation
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54088 Log audit events for user creation Change By: Matt Sicker Labels: audit-logging newbie-friendly 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-54087) Log an audit event for user login/logout actions
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54087 Log an audit event for user login/logout actions Change By: Matt Sicker Labels: audit-logging newbie-friendly 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-54087) Log an audit event for user login/logout actions
Title: Message Title Matt Sicker commented on JENKINS-54087 Re: Log an audit event for user login/logout actions Unassigning for now as this task is much further down the list. Feel free to self-assign the higher listed tasks, though! 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-54087) Log an audit event for user login/logout actions
Title: Message Title Matt Sicker assigned an issue to Unassigned Jenkins / JENKINS-54087 Log an audit event for user login/logout actions Change By: Matt Sicker Assignee: Latha Sekar 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-54658) Add Jenkins build for audit log plugin
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-54658 Add Jenkins build for audit log plugin Issue Type: Task Assignee: Unassigned Components: core Created: 2018-11-15 19:51 Priority: Minor Reporter: Matt Sicker After migrating to the jenkinsci organization as in JENKINS-54320, a Jenkinsfile should be added to run automated tests. This should only require a minimal buildPlugin() style Jenkinsfile as with most Jenkins plugins. By setting this up, we will be able to remove the Travis setup and have automated testing of pull requests for faster feedback. Add Comment
[JIRA] (JENKINS-54089) Create an audit log destination global configuration
Title: Message Title Matt Sicker assigned an issue to Unassigned Jenkins / JENKINS-54089 Create an audit log destination global configuration Change By: Matt Sicker Assignee: Ales Blaze 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-50298 Use p4trust file if credential's Trust fingerprint is blank Change By: Joel Brown If the credential's Trust field is blank, just use the fingerprint from the p4trust file.This means any node using this credential must have a P4TRUST file that already trusts the server. 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-50298) Use p4trust file if credential's Trust fingerprint is blank
Title: Message Title Joel Brown updated an issue Jenkins / JENKINS-50298 Use p4trust file if credential's Trust fingerprint is blank Change By: Joel Brown Labels: P4_SUPPORT P4_VERIFY 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.
