[JIRA] [active-directory-plugin] (JENKINS-35515) Role Strategy 2.3 with Active Directory Plugin cause poor UI performance
Title: Message Title Kurt commented on JENKINS-35515 Re: Role Strategy 2.3 with Active Directory Plugin cause poor UI performance We're seeing same poor performance here. Effectively we, too, had to downgrade to 2.2 version as 2.3 was unusably slow (it got completely stuck - no more response from Web UI within 15 minutes). Environment: Oracle JDK8 (_66) 64bit, Jenkins 2.8, AD Plugin 1.47 (no Domain name or other advanced settings entered, I guess that means we're using ADSI), Windows Server 2008R2 64 bit (Domain Member), Hardware is a VM with 24 GB RAM (of which 9 GB are dedicated to Java mem pool), 6 CPU cores and using an SSD storage cluster. Most significant difference to initial report: We're NOT using AD groups at all. Roles are assigned only to users. We currently have 37 roles (31 regex-based project roles, 6 global roles) which are assigned to roughly 100 users. The Jenkins instance contains ~5 jobs (organized in folders). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-35518) dir() does not change directory when used insider docker.inside block
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-35518
dir() does not change directory when used insider docker.inside block
Change By:
Michael Neale
If you use dir() inside a docker.inside block - it will not work as expected. Take the following script, which works as expected with dir():{noformat}node("docker") {deleteDir()stage 'build blueocean' dir('blueocean') {git url: 'https://github.com/jenkinsci/blueocean-plugin.git'sh 'ls -lah' } stage 'prepare acceptance test harness' dir("acceptance") { git url: 'https://github.com/cloudbees/blueocean-acceptance-test.git', branch: 'master' sh 'ls -lah'}}{noformat}The contents of ear dir are correct. However, tweaking it slightly: {noformat}node("docker") {deleteDir()docker.image('cloudbees/java-build-tools').inside {stage 'build blueocean' dir('blueocean') {git url: 'https://github.com/jenkinsci/blueocean-plugin.git'sh 'ls -lah' } stage 'prepare acceptance test harness' dir("acceptance") { git url: 'https://github.com/cloudbees/blueocean-acceptance-test.git', branch: 'master' sh 'ls -lah'}}}{noformat}And the listings show a level above the dir, even though each dir is created, ie: {noformat}+ ls -lahtotal 16Kdrwxrwxr-x 4 jenkins jenkins 4.0K Jun 10 05:24 .drwxr-xr-x 4 rootroot4.0K Jun 10 05:24 ..drwxrwxr-x 13 jenkins jenkins 4.0K Jun 10 05:24 blueoceandrwxrwxr-x 3 jenkins jenkins 4.0K Jun 10 05:24 blueocean@tmp..+ ls -lahtotal 24Kdrwxrwxr-x 6 jenkins jenkins 4.0K Jun 10 05:24 .drwxr-xr-x 4 rootroot4.0K Jun 10 05:24 ..drwxrwxr-x 4 jenkins jenkins 4.0K Jun 10 05:24 acceptancedrwxrwxr-x 3 jenkins jenkins 4.0K Jun 10 05:24 acceptance@tmpdrwxrwxr-x 13 jenkins jenkins 4.0K Jun 10 05:24 blueoceandrwxrwxr-x 2 jenkins jenkins 4.0K Jun 10 05:24 blueocean@tmp{noformat}Just a little bit maddening as I thought I was going insane. dir outside of docker block works just fine, as expected.
Add Comment
[JIRA] [docker-workflow-plugin] (JENKINS-35518) dir() does not change directory when used insider docker.inside block
Title: Message Title Michael Neale commented on JENKINS-35518 Re: dir() does not change directory when used insider docker.inside block May still be insane, but hopefully not due to this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-35518) dir() does not change directory when used insider docker.inside block
Title: Message Title
Michael Neale created an issue
Jenkins / JENKINS-35518
dir() does not change directory when used insider docker.inside block
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
docker-workflow-plugin
Created:
2016/Jun/10 5:27 AM
Priority:
Major
Reporter:
Michael Neale
If you use dir() inside a docker.inside block - it will not work as expected.
Take the following script, which works as expected with dir():
node("docker") {
deleteDir()
stage 'build blueocean'
dir('blueocean') {
git url: 'https://github.com/jenkinsci/blueocean-plugin.git'
sh 'ls -lah'
}
stage 'prepare acceptance test harness'
dir("acceptance") {
git url: 'https://github.com/cloudbees/blueocean-acceptance-test.git', branch: 'master'
sh 'ls -lah'
}
}
The contents of ear dir are correct. However, tweaking it slightly:
node("docker") {
deleteDir()
docker.image('cloudbees/java-build-tools').inside {
stage 'build blueocean'
dir('blueocean') {
[JIRA] [windows-slaves-plugin] (JENKINS-34125) Slave service installation on Win 10 and Win 8.1 64bit doesnt work
Title: Message Title ahmed daniel closed an issue as Fixed Jenkins / JENKINS-34125 Slave service installation on Win 10 and Win 8.1 64bit doesnt work Change By: ahmed daniel Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-34125) Slave service installation on Win 10 and Win 8.1 64bit doesnt work
Title: Message Title ahmed daniel commented on JENKINS-34125 Re: Slave service installation on Win 10 and Win 8.1 64bit doesnt work Found the solution to this issue from stackoverflow... Here is it's link http://stackoverflow.com/questions/36500231/installing-jenkins-slave-as-service-on-win8-1-and-win10/37147085?noredirect=1#comment62929396_37147085. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33895) build-pipeline-plugin does not support the pipeline (workflow) jobs
Title: Message Title Dan Alvizu closed an issue as Won't Fix Not sure what the feature being requested is here. Sorry you find the plugin useless. Jenkins / JENKINS-33895 build-pipeline-plugin does not support the pipeline (workflow) jobs Change By: Dan Alvizu Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-34208) NullPointerException pops up randomly at different steps of a pipeline build
Title: Message Title Dan Alvizu updated an issue Jenkins / JENKINS-34208 NullPointerException pops up randomly at different steps of a pipeline build Change By: Dan Alvizu Component/s: maven-plugin Component/s: build-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-34208) NullPointerException pops up randomly at different steps of a pipeline build
Title: Message Title Dan Alvizu commented on JENKINS-34208 Re: NullPointerException pops up randomly at different steps of a pipeline build I don't think this is the right component. There's nothing in the stack trace indicating you're using the build pipeline plugin. It looks like you may be using the pipeline plugin, but I'm not sure if it's related. This part: Caused by: java.lang.NullPointerException at hudson.maven.Maven3Builder$MavenExecutionListener.sessionEnded(Maven3Builder.java:469) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64) Makes it seem like a maven plugin problem? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-33363) BuildFlow support
Title: Message Title Dan Alvizu closed an issue as Won't Fix Implementation is in pull request - build flow supported as another plugin Jenkins / JENKINS-33363 BuildFlow support Change By: Dan Alvizu Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-usage-plugin] (JENKINS-35517) java.net.ProtocolException: Server redirected too many times (5)
Title: Message Title VENKATA SUBBA REDDY YERRAGUDI updated an issue Jenkins / JENKINS-35517 java.net.ProtocolException: Server redirected too many times (5) Change By: VENKATA SUBBA REDDY YERRAGUDI Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-usage-plugin] (JENKINS-35517) java.net.ProtocolException: Server redirected too many times (5)
Title: Message Title VENKATA SUBBA REDDY YERRAGUDI created an issue Jenkins / JENKINS-35517 java.net.ProtocolException: Server redirected too many times (5) Issue Type: Bug Assignee: Unassigned Components: plugin-usage-plugin Created: 2016/Jun/10 4:12 AM Environment: DEV Priority: Major Reporter: VENKATA SUBBA REDDY YERRAGUDI java.net.ProtocolException: Server redirected too many times (5) at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:837) at weblogic.net.http.SOAPHttpURLConnection.getInputStream(SOAPHttpURLConnection.java:41) at hudson.model.DownloadService.loadJSON(DownloadService.java:166) at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:176) at hudson.PluginManager.doCheckUpdatesServer(PluginManager.java:1508) 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 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:52) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at
[JIRA] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Brian Wu edited a comment on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi [~raphc]Please refer to below deployment logs details: * when i specified the "WebLogic Deployment Command" in advance configuration, deployment log would be like below. * ARTIFACT UNDEPLOYMENT Error: Could not find or load main class weblogic.Deployer ARTIFACT DEPLOYMENT Error: Could not find or load main class weblogic.Deployer * when the "WebLogic Deployment Command" is not specified, deployment log goes like this: * TASK EXECUTION Error: Could not find or load main class weblogic.DeployerThanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Brian Wu commented on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi Raphael CHAUMIER Please refer to below deployment logs details: when i specified the "WebLogic Deployment Command" in advance configuration, deployment log would be like below. ARTIFACT UNDEPLOYMENT Error: Could not find or load main class weblogic.Deployer ARTIFACT DEPLOYMENT Error: Could not find or load main class weblogic.Deployer when the "WebLogic Deployment Command" is not specified, deployment log goes like this: TASK EXECUTION Error: Could not find or load main class weblogic.Deployer Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title Michael Neale commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Jesse Glick yes I have not heard any complaints about the naming, only when things break on the path. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-choices-plugin] (JENKINS-29969) groovy script can not run on node specified for the job
Title: Message Title Bruno P. Kinoshita commented on JENKINS-29969 Re: groovy script can not run on node specified for the job Hi Bikas, From JENKINS-35495 "It seems ActiveChoiceParamer team is reluctant to provide this feature. ". Not really. Just not enough time. We try to squeeze as many issues as possible in each release, but sometimes issues are prioritised, and other issues take a longer time to be implemented. This is easier to implement in active-choices, then to port the reactive parameter type to dynamic-parameter (the reactive parameter was created with _javascript_, and by some Java code as well). That said, once we start another development cycle for BioUno, will start triaging issues in our plug-ins and tools, and try our best at releasing new versions. Should you have a pull request (to either active-choices or dynamic-parameter), feel free to submit it. Most pull requests are merged when we cut a new release as long as we do not break backward compatibility. Sorry for the delay to fix this issue everyone. Cheers, Bruno Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-35516) Loading user details throws bad exceptions
Title: Message Title Ivan Meredith closed an issue as Duplicate Jenkins / JENKINS-35516 Loading user details throws bad exceptions Change By: Ivan Meredith Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-35516) Loading user details throws bad exceptions
Title: Message Title Ivan Meredith commented on JENKINS-35516 Re: Loading user details throws bad exceptions Confirmed this is fixed in latest version Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-35516) Loading user details throws bad exceptions
Title: Message Title Ivan Meredith commented on JENKINS-35516 Re: Loading user details throws bad exceptions Nvm i was looking at wrong source code, it looks like that has been fixed... trying to figure out why we are setting this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth-plugin] (JENKINS-35516) Loading user details throws bad exceptions
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-35516 Loading user details throws bad exceptions Issue Type: Bug Assignee: Sam Gleske Components: github-oauth-plugin Created: 2016/Jun/10 12:25 AM Priority: Minor Reporter: Ivan Meredith loadUserByUsername has some issues that I can see. GithubAuthenticationToken authToken = (GithubAuthenticationToken) SecurityContextHolder.getContext().getAuthentication(); failes with class cast exception when an anonymous user is accessing. It should throw a UserNotFoundException for anonymous users I believe. Also, possibly when the github token has timed out and is invalid, the plugin does not redo the login. I'm pretty sure its failing in loadUserByUsername but I'm not totally sure. Will update if I find out. Add Comment
[JIRA] [ssh-agent-plugin] (JENKINS-35337) Finds credentials but unable to read key: null
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-35337 Re: Finds credentials but unable to read key: null Are you able to reproduce with the latest version of SSH Agent 1.11? This version now uses the Bouncycastle API and that part of the code has been reworked. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26130) Print progress of pending pickles
Title: Message Title Jesse Glick commented on JENKINS-26130 Re: Print progress of pending pickles Have a rudimentary implementation. Have not yet tried to implement cancellability of pickle dehydration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-35513) Multijob view, cannot display results of more than one build of same job
Title: Message Title hector CALDERON updated an issue Jenkins / JENKINS-35513 Multijob view, cannot display results of more than one build of same job Change By: hector CALDERON When configuring a multi job, one job is built with two different parameters. Both builds run independently under the multijob. But the status ball displayed on the left side is the same for both builds.. the latest build status, rather than the result status of each build. To reproduce this problem, I created 'singlejob' [freestyle project] with a conditional build step to fail the build on a parameter string match. I configure 'MultijobTest' to build 'singlejob' with pass parameters, then again with fail parameters. The Then the multijobview only shows red status for all the builds, yet the console shows one PASS and one FAIL. This bug produces misleading information on builds making it difficult to understand and move forward.Thank you in advance. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G updated an issue Jenkins / JENKINS-26345 "CVS Symbolic Name parameter" not working any more Change By: Fred G Priority: Blocker Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G assigned an issue to Michael Clarke Jenkins / JENKINS-26345 "CVS Symbolic Name parameter" not working any more Change By: Fred G Assignee: Michael Clarke Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs-plugin] (JENKINS-26345) "CVS Symbolic Name parameter" not working any more
Title: Message Title Fred G commented on JENKINS-26345 Re: "CVS Symbolic Name parameter" not working any more Added a potential fix in this pull request: https://github.com/jenkinsci/cvs-plugin/pull/43 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35450) Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT
Title: Message Title Liam Newman commented on JENKINS-35450 Re: Rename environment variable: JENKINS_SLAVE_AGENT_PORT to JENKINS_AGENT_PORT The originally agreement was that the term slave would be removed from the UI, but left in the APIs to avoid breaking compatibility both for plugins and customer tools/scripts. The problem is that line of where the UI stops and the API begins is a somewhat fluid when your users are engineers. I understand that env vars are effectively part of the API and so changing them is problematic and could be considered out of scope. But they are also part of the end-user experience (the UI) for every Jenkins user. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26130) Print progress of pending pickles
Title: Message Title Jesse Glick started work on JENKINS-26130 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26130) Print progress of pending pickles
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-26130 Print progress of pending pickles Change By: Jesse Glick Assignee: Kohsuke Kawaguchi Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35452) Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35452 Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp" Change By: Liam Newman Found when launching a jnlp agent from command line:"java ... -jnlpUrl http://localhost/computer/agent_name/slave-agent.jnlp"The name of this file should match agreed naming guidelines - "agent.jnlp" or "jenkins-agent.jnlp". The originally agreement was that the term slave would be removed from the UI, but left in the APIs to avoid breaking compatibility both for plugins and customer tools/scripts. The problem is that line of where the UI stops and the API begins is a somewhat fluid when your users are engineers. I understand that filenames and urls are effectively part of the API and so changing them is problematic and could be considered out of scope. But filenames and urls are also part of the end-user experience (the UI) for every Jenkins user. And the files and urls related to adding an agent are some of the first and most commonly used. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35451) Change name of "slave.jar" to "agent.jar"
Title: Message Title Liam Newman edited a comment on JENKINS-35451 Re: Change name of "slave.jar" to "agent.jar" Is eternal backward compatibility a core requirement? Can we create a plan for phasing these out? Provide both for some time period and then remove the old. File names in particular heavily influence the terms people use when talking about the product and features. Keeping "slave" in the file names essentially defeats any effort to remove the term "slave" from association with our product. As part of this transition, we're seeing people add the term "agent" but not remove the term "slave" from descriptions. "I'm have a problem with my jenkins slave agent." To get people to drop "slave", I think we need to not show them "slave-blah" every time they start an agent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35451) Change name of "slave.jar" to "agent.jar"
Title: Message Title Liam Newman commented on JENKINS-35451 Re: Change name of "slave.jar" to "agent.jar" The originally agreement was that the term slave would be removed from the UI, but left in the APIs to avoid breaking compatibility both for plugins and customer tools/scripts. The problem is that line of where the UI stops and the API begins is a somewhat fluid when your users are engineers. I understand that filenames and urls are effectively part of the API and so changing them is problematic and could be considered out of scope. But filenames and urls are also part of the end-user experience (the UI) for every Jenkins user. And the files and urls related to adding an agent are some of the first and most commonly used. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35449) Review and document all remaining uses of the term "slave" in core
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35449 Review and document all remaining uses of the term "slave" in core Change By: Liam Newman JENKINS-27268 has been resolved but there are still many occurrences of the term "slave" in Jenkins core. Some of these are too hard to fix others are not, but it is unclear which are which. We've put significant effort into removing this term. To make good on that investment, any publich public -facing stragglers, bugs need to be filed and linked for all remaining usages of "slave" in Jenkins core. Otherwise, the term will continue to be part of the project's vernacular. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-35515) Role Strategy 2.3 with Active Directory Plugin cause poor UI performance
Title: Message Title Reilly Brogan created an issue Jenkins / JENKINS-35515 Role Strategy 2.3 with Active Directory Plugin cause poor UI performance Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin, role-strategy-plugin Created: 2016/Jun/09 9:42 PM Environment: Centos 7.2, OpenJDK 1.8.0.91, Jenkins 2.8, Active Directory plugin 1.47, Role Strategy 2.3 Labels: performance ui Priority: Major Reporter: Reilly Brogan Hello, we recently updated the Role Strategy plugin to 2.3 and after the restart Jenkins UI performance became extremely slow. We isolated the issue to using Active Directory groups in our roles, when we switched to explicitly using users the issue went away. When we downgraded the version of Role Strategy to 2.2 the issue also went way.
[JIRA] [core] (JENKINS-35514) Ability to disable script console
Title: Message Title Dmitry Erastov created an issue Jenkins / JENKINS-35514 Ability to disable script console Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Jun/09 9:23 PM Labels: security script console Priority: Minor Reporter: Dmitry Erastov The administrative script console allows very broad access to Jenkins, and this has been a source of vulnerabilities in the past, e.g. https://www.rapid7.com/db/modules/exploit/multi/http/jenkins_script_console https://duckduckgo.com/?q=jenkins+script+console+java+execution=web My team never uses this feature, and we'd like to reduce our attack surface by disabling the console completely, preferably from the system-level Jenkins config (/etc/sysconfig/jenkins on Linux). Is there an existing undocumented option for that? If not, will it be possible to add such an option? We do have mandatory auth and access control, but still would like to disable this feature.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-35484) if jenkins user lookup is expensive, requesting changelogs can place undue burden on the master
Title: Message Title
Sam Van Oort commented on JENKINS-35484
Re: if jenkins user lookup is expensive, requesting changelogs can place undue burden on the master
The property can be set at runtime to disable user resolution by running the following in the script console:
import java.util.Properties;
systemProperties.setProperty("com.cloudbees.workflow.rest.external.ChangeSetExt.avoidResolvingCommitAuthors", "true");
This will disable user lookup.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-35484) if jenkins user lookup is expensive, requesting changelogs can place undue burden on the master
Title: Message Title Sam Van Oort started work on JENKINS-35484 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-skip-plugin] (JENKINS-35509) ci skip is not working
Title: Message Title Ramesh Babu started work on JENKINS-35509 Change By: Ramesh Babu Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-skip-plugin] (JENKINS-35509) ci skip is not working
Title: Message Title Ramesh Babu stopped work on JENKINS-35509 Change By: Ramesh Babu Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-branch-source-plugin] (JENKINS-33507) Bitbucket Server webhooks and Bitbucket Cloud build status notifications
Title: Message Title Mike Kobit updated an issue Jenkins / JENKINS-33507 Bitbucket Server webhooks and Bitbucket Cloud build status notifications Change By: Mike Kobit Auto xAuto -register webhooks for Bitbucket Server and build status notifications for Bitbucket Cloud (only PR comments are sent currently). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-35317) Null pointer exception with credentials (GIT)
Title: Message Title stephenconnolly assigned an issue to Kirill Merkushev Jenkins / JENKINS-35317 Null pointer exception with credentials (GIT) Change By: stephenconnolly Assignee: stephenconnolly Kirill Merkushev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-35317) Null pointer exception with credentials (GIT)
Title: Message Title stephenconnolly updated an issue Jenkins / JENKINS-35317 Null pointer exception with credentials (GIT) Change By: stephenconnolly Component/s: credentials-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-35306) Credentials Providers need to be able to list credentials without retrieving the backing secret
Title: Message Title stephenconnolly resolved as Fixed Jenkins / JENKINS-35306 Credentials Providers need to be able to list credentials without retrieving the backing secret Change By: stephenconnolly Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-35488) System credentials store showing twice for credentials parameter add drop down
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35488 Re: System credentials store showing twice for credentials parameter add drop down Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsSelectHelper.java http://jenkins-ci.org/commit/credentials-plugin/a70824187a8db509eb3d4459f0b55a2f953a68aa Log: [FIXED JENKINS-35488] Ensure we only ever add each store once Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-plugin] (JENKINS-35488) System credentials store showing twice for credentials parameter add drop down
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-35488 System credentials store showing twice for credentials parameter add drop down Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title Ilya Ivanov commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Somebody, publish the new version please. Apparently, the fix is already in the source code on GitHub. Can someone else (other than the maintainer) release the new version? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-34753) Sec-170-releated: gerrit-trigger needs to declare parameters
Title: Message Title James Ladan commented on JENKINS-34753 Re: Sec-170-releated: gerrit-trigger needs to declare parameters I (foolishly) updated to Jenkins 1.651.2 and Gerrit Trigger 2.21.1 yesterday and the problem is not resolved for 1.651.2. [separate issue] On top of that, after downgrading Jenkins back to 1.651.1, the 'retrigger' option was gone from our Gerrit monitor jobs, meaning I couldn't retrigger the jobs that failed due to the parameter declaration problem. I had to downgrade the Gerrit Trigger plugin back to 2.20.0 to get the retrigger option back. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-34222) Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job
Title: Message Title Steve Layman edited a comment on JENKINS-34222 Re: Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job We're running in to into the same issue. Job hangs while compiling the test reports. We finally stopped the build after about 3.5 hours of waiting and got the NPE as well.I see the new test cases have been created, but no new cycle or execution statuses were added to them.[ZapiTestResultReporter] [INFO] Examining test results...11:55:33 Build result is UNSTABLE11:55:33 Total Test Cases : 498ERROR: Build step failed with exception15:30:00 java.lang.NullPointerException15:30:00 at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.assignTests(TestCaseUtil.java:218)15:30:00 at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:413)15:30:00 at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:98)15:30:00 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785)15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)15:30:00 at hudson.model.Build$BuildExecution.post2(Build.java:185)15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)15:30:00 at hudson.model.Run.execute(Run.java:1766)15:30:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)15:30:00 at hudson.model.ResourceController.execute(ResourceController.java:98)15:30:00 at hudson.model.Executor.run(Executor.java:410)15:30:00 Build step 'Publish test result to Zephyr for JIRA' marked build as failureJenkins v1.637Zephyr v1.3Jira v6.3.15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title Patrick Reinhart edited a comment on JENKINS-33020 Re: Unable to Trigger builds remotely (e.g., from scripts) Screenshot multibranch pipeline setup dialog with the "Trigger Remote Build" as visible within Jenkins ver. 1.642.2 and Pipeline plugin version 1.13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35506) Add a Pipeline step to the hpi Maven archetype
Title: Message Title Jesse Glick started work on JENKINS-35506 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-34222) Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job
Title: Message Title Steve Layman commented on JENKINS-34222 Re: Zephyr for JIRA hangs while recording results, and throws NPE while stopping the hanged job We're running in to the same issue. Job hangs while compiling the test reports. We finally stopped the build after about 3.5 hours of waiting and got the NPE as well. I see the new test cases have been created, but no new cycle or execution statuses were added to them. [ZapiTestResultReporter] [INFO] Examining test results... 11:55:33 Build result is UNSTABLE 11:55:33 Total Test Cases : 498ERROR: Build step failed with exception 15:30:00 java.lang.NullPointerException 15:30:00 at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.assignTests(TestCaseUtil.java:218) 15:30:00 at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:413) 15:30:00 at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:98) 15:30:00 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) 15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) 15:30:00 at hudson.model.Build$BuildExecution.post2(Build.java:185) 15:30:00 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) 15:30:00 at hudson.model.Run.execute(Run.java:1766) 15:30:00 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 15:30:00 at hudson.model.ResourceController.execute(ResourceController.java:98) 15:30:00 at hudson.model.Executor.run(Executor.java:410) 15:30:00 Build step 'Publish test result to Zephyr for JIRA' marked build as failure Jenkins v1.637 Zephyr v1.3 Jira v6.3.15 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [workflow-plugin] (JENKINS-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title Patrick Reinhart updated an issue Jenkins / JENKINS-33020 Unable to Trigger builds remotely (e.g., from scripts) Screenshot multibranch pipeline setup dialog with the "Trigger Remote Build" Change By: Patrick Reinhart Attachment: pipeline_config.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-35513) Multijob view, cannot display results of more than one build of same job
Title: Message Title hector CALDERON created an issue Jenkins / JENKINS-35513 Multijob view, cannot display results of more than one build of same job Issue Type: Bug Assignee: Unassigned Attachments: consoleview.PNG, multijobview.PNG Components: multijob-plugin Created: 2016/Jun/09 7:46 PM Environment: Jenkins 2.2 centos jenkins on tomcat Labels: workflow jenkins user-experience plugins build Priority: Blocker Reporter: hector CALDERON When configuring a multi job, one job is built with two different parameters. Both builds run independently under the multijob. But the status ball displayed on the left side is the same for both builds.. the latest status, rather than the result
[JIRA] [workflow-plugin] (JENKINS-33020) Unable to Trigger builds remotely (e.g., from scripts)
Title: Message Title Patrick Reinhart updated an issue Jenkins / JENKINS-33020 Unable to Trigger builds remotely (e.g., from scripts) Change By: Patrick Reinhart Attachment: build_trigger.tiff Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy-plugin] (JENKINS-35214) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Raphael CHAUMIER commented on JENKINS-35214 Re: Unable to deploy the ear file using weblogic-deployer-plugin Hi Brian Wu Send to me the deployment log (available from the link on the job dashboard) not the job logs. Regards Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-35444) @NonCPS not lexically inherited
Title: Message Title
Trevor Hartman edited a comment on JENKINS-35444
Re: @NonCPS not lexically inherited
Yes, the {{ println("matched") }} was placeholder logic.{{ matcher }} couldn't be inlined from my experience. It kept throwing {{ java.io.NotSerializableException: java.util.regex.Matcher }} until I put it in a lambda with {{ @NonCPS }}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-35444) @NonCPS not lexically inherited
Title: Message Title
Trevor Hartman commented on JENKINS-35444
Re: @NonCPS not lexically inherited
Yes, the {{ println("matched") }} was placeholder logic.
{{ matcher }} couldn't be inlined from my experience. It kept throwing {{ java.io.NotSerializableException: java.util.regex.Matcher }} until I put it in a lambda with {{ @NonCPS }}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15063) support for multiple security realms with failover
Title: Message Title Jesse Glick commented on JENKINS-15063 Re: support for multiple security realms with failover Would it be feasible to have a special security realm plugin that functions somewhat like pam, in the sense that it could be configured to call a number of other security modules? As noted above, not without a new API, which would best live in core, and calls to it from existing security realm plugins. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35512) Blank screen when creating new item after upgrading to 2.7
Title: Message Title Omar Haq created an issue Jenkins / JENKINS-35512 Blank screen when creating new item after upgrading to 2.7 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/09 7:20 PM Environment: Tomcat: tomcat-7.0.42 Java: 1.8.0_25-b17 Priority: Minor Reporter: Omar Haq I upgraded to jenkins 2.7. After which, i am unable to create a new item either through the interface or through CLI. This jenkins is running behind a tomcat server. I looked at the thread dump, but I dont see anything that I could paste that is relevant. Is there some other spot where I can look and provide you with more information about the error? Add Comment
[JIRA] [core] (JENKINS-35508) Invoking Config.xml through REST returns BOM
Title: Message Title Shawn Cole resolved as Fixed Issue is due to me posting a UTF-8-BOM type file to the REST api to update it originally Jenkins / JENKINS-35508 Invoking Config.xml through REST returns BOM Change By: Shawn Cole Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35452) Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35452 Change Jnlp url from "slave-agent.jnlp" to "agent.jnlp" Change By: Liam Newman Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35451) Change name of "slave.jar" to "agent.jar"
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-35451 Change name of "slave.jar" to "agent.jar" Change By: Liam Newman Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [drupal-developer-plugin] (JENKINS-35511) Drupal developer plugin doesn't work on master/slave configuration
Title: Message Title daniel mozo created an issue Jenkins / JENKINS-35511 Drupal developer plugin doesn't work on master/slave configuration Issue Type: Bug Assignee: Feng Tan Components: drupal-developer-plugin Created: 2016/Jun/09 6:56 PM Environment: Linux Priority: Minor Reporter: daniel mozo In a master/slave configuration, with the drupal developer plugin, if you configure a jenkins slave to execute a job that perform a revision on code it fails with a directory not found thought the directory exits and is writeable in the slave. The problem is the slave pulls the code from git repository and executes drush commands, but when writes coder-review.xml, it does in the master node workspace instead in the slave node workspace that perform the job. If you create the same directory in the master, the jobs works ok, but results aren't published to checkstyle. If you copy the coder-review.xml to the slave workspace logs directory, then you can see that results are readed from the workspace of the slave. Drush coder review -> writes to the master workspace Checkstyle results -> read from slave workspace As a workaround, workspace in a nfs share does the trick.
[JIRA] [workflow-plugin] (JENKINS-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title Jesse Glick commented on JENKINS-35444 Re: java.io.NotSerializableException issues even with @NonCPS I assume this was a prototype on the way to a working function, since latency seems to be left empty, and matcher could simply be inlined. Probably the issue is just that @NonCPS is not inherited lexically. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-35444) @NonCPS not lexically inherited
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35444 @NonCPS not lexically inherited Change By: Jesse Glick Summary: java.io.NotSerializableException issues even with @NonCPS not lexically inherited Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-35444
java.io.NotSerializableException issues even with @NonCPS
Change By:
Jesse Glick
I get {{ java.io.NotSerializableException: java.util.regex.Matcher }} on:{code :groovy }@NonCPSdef extractLatency(linesArr) { latency = [:] println "extractLatency" for (int j = 0; j < linesArr.size(); j++) {line = linesArr[j]println("looping over line: $line")// Matches lines like: Connect:01 0.1 1 1abPattern = /(\w+)\:\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)/def matcher = { (line =~ abPattern) }if (matcher().size > 1) { println("matched")}matcher = nullabPattern = null } return latency}{code}If I throw a @NonCPS on the inner `def matcher` it fixes it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-35444) java.io.NotSerializableException issues even with @NonCPS
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-35444
java.io.NotSerializableException issues even with @NonCPS
Change By:
Jesse Glick
I get {{java.io.NotSerializableException: java.util.regex.Matcher}} on:{code}@NonCPSdef extractLatency(linesArr) { latency = [:] println "extractLatency" for (int j = 0; j < linesArr.size(); j++) {line = linesArr[j]println("looping over line: $line")// Matches lines like: Connect:01 0.1 1 1abPattern = /(\w+)\:\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)\s+(\d+\.?\d*)/def matcher = { (line =~ abPattern) }if (matcher().size > 1) { println("matched")}matcher = nullabPattern = null } return latency}{code}If I throw a {{ @NonCPS }} on the inner ` {{ def matcher ` }} it fixes it.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-35322) NPE when trying to pull Docker image as first build step
Title: Message Title Stephen Donner closed an issue as Not A Defect This ended up being my mistake, of course - I hadn't specified the Docker REST API url/endpoint. Jenkins / JENKINS-35322 NPE when trying to pull Docker image as first build step Change By: Stephen Donner Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-34762) PR status cannot be updated due to filtered parameters
Title: Message Title Arnaud Héritier commented on JENKINS-34762 Re: PR status cannot be updated due to filtered parameters https://wiki.jenkins-ci.org/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170 is saying that this fix is removed in 1.32.2 ? thus the issue should be reopened ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35493) severe performance regression after SECURITY-243
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-35493 severe performance regression after SECURITY-243 Change By: Jesse Glick Labels: performance regression Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom
Title: Message Title Kristin Whetstone commented on JENKINS-35510 Re: Migrate git-server-plugin to parent pom This plugin relies on an older version of Jenkins, 1.480. I've been testing migrating to 1.580.1 to grab SECURITY-144, but there are some fundamental changes between versions. Because this plugin has been pretty much functionally untouched since 2014 (findbugs and maven dependency bumps) and it's popularity is rising meteorically, it might be worth keeping the jenkins.version at 1.480. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom
Title: Message Title Kristin Whetstone started work on JENKINS-35510 Change By: Kristin Whetstone Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35244 Re: [EWM] Implement the exws step Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/1f845e34d8eb6e5f50c04a0b9d197c5ebae86213 Log: JENKINS-35244 Implement the exws step Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35244 Re: [EWM] Implement the exws step Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/definitions/Disk.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsAllocateExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsStep.java src/main/java/org/jenkinsci/plugins/ewm/steps/model/ExternalWorkspace.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/ecc5225bca3fd5c9850c4ea70e6658815e5aadc0 Log: Merge pull request #12 from alexsomai/exws-step-implementation JENKINS-35244 Implement the exws step Compare: https://github.com/jenkinsci/external-workspace-manager-plugin/compare/b22286a9aeb9...ecc5225bca3f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [external-workspace-manager-plugin] (JENKINS-35244) [EWM] Implement the exws step
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35244 Re: [EWM] Implement the exws step Code changed in jenkins User: Alexandru Somai Path: src/main/java/org/jenkinsci/plugins/ewm/steps/ExwsExecution.java http://jenkins-ci.org/commit/external-workspace-manager-plugin/adf87a5c271d018253b6a1bb39f370f468a76e32 Log: JENKINS-35244 Enhance exception messages Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-server-plugin] (JENKINS-35510) Migrate git-server-plugin to parent pom
Title: Message Title Kristin Whetstone created an issue Jenkins / JENKINS-35510 Migrate git-server-plugin to parent pom Issue Type: Improvement Assignee: Kristin Whetstone Components: git-server-plugin Created: 2016/Jun/09 6:01 PM Priority: Minor Reporter: Kristin Whetstone For improved test-ability and upgrades, upgrade the parent pom to the 2.x line. The jenkins.version might also be a candidate for upgrades since it's on a line that's old. Add Comment
[JIRA] [ci-skip-plugin] (JENKINS-35509) ci skip is not working
Title: Message Title Ramesh Babu created an issue Jenkins / JENKINS-35509 ci skip is not working Issue Type: Bug Assignee: Kohei Hasegawa Attachments: Capture.PNG Components: ci-skip-plugin Created: 2016/Jun/09 5:46 PM Environment: github public repository Labels: plugins Priority: Major Reporter: Ramesh Babu I have submitted an commit with ci skip and created a pull request. ex: git commit -m "testing jenkins [ci skip]" . I could see Jenkins build started message on PR. I have installed ci-skip plugin and checked " Enable ci-skip" option on Jenkins UI. But still I could see build process for CI skip.. Could you please help me what's wrong with the approach?
[JIRA] [delivery-pipeline-plugin] (JENKINS-35507) Paging not usable with large number of historical builds
Title: Message Title Suresh Kumar assigned an issue to Suresh Kumar Jenkins / JENKINS-35507 Paging not usable with large number of historical builds Change By: Suresh Kumar Assignee: Patrik Boström Suresh Kumar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29922) Promote delegates of metasteps to top-level functions, deprecate $class
Title: Message Title
Andrew Bayer commented on JENKINS-29922
Re: Promote delegates of metasteps to top-level functions, deprecate $class
I'd lean strongly towards the builder syntax, but I admit to personal preference there. Also worth mentioning though that the builder syntax will (I believe) require some changes in groovy-cps} (or at least {{workflow-cps) to not treat the nested closures as instances of CpsClosure, or we'll hit the always-fun over-eager returning of first completed nested closure issue.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-35507) Paging not usable with large number of historical builds
Title: Message Title Suresh Kumar commented on JENKINS-35507 Re: Paging not usable with large number of historical builds Yes what you said is correct, probably as you said we have to pass pagination information to pipeline class. -Suresh Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy-plugin] (JENKINS-18377) Improve the performance when listing many jobs
Title: Message Title Oleg Nenashev commented on JENKINS-18377 Re: Improve the performance when listing many jobs Croesus Kall Caching of roles should have helped, but maybe there're some downsides. Do you have any metrics from your setup? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-26583) Env-inject plugin suppress variables contributed by extension points
Title: Message Title Noam Manos commented on JENKINS-26583 Re: Env-inject plugin suppress variables contributed by extension points Still relevant on Jenkins 2.7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pipeline-stage-view-plugin] (JENKINS-35484) if jenkins user lookup is expensive, requesting changelogs can place undue burden on the master
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35484 Re: if jenkins user lookup is expensive, requesting changelogs can place undue burden on the master Code changed in jenkins User: Sam Van Oort Path: rest-api/src/main/java/com/cloudbees/workflow/rest/external/ChangeSetExt.java http://jenkins-ci.org/commit/pipeline-stage-view-plugin/647f03fc8cdb7422af259d78e96173491df7dad1 Log: Add system config option to avoid doing user lookup for changelog entries to resolve JENKINS-35484 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-organization-folder-plugin] (JENKINS-35251) Provide different strategies for repositories and branches / pull request
Title: Message Title Sorin Sbarnea reopened an issue Sorry but this bug was closed without giving an explanation for the reported problem. Currently, the list of sub-projects (branches) is growing indefinitely and we were not able to find any option for removal of the old ones. Git flow does state that branches are supposed to be removed after they are merged and we are doing this but it seems that Jenkins never removes them and now we have hundreds of them for each repository. Jenkins / JENKINS-35251 Provide different strategies for repositories and branches / pull request Change By: Sorin Sbarnea Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [core] (JENKINS-35508) Invoking Config.xml through REST returns BOM
Title: Message Title Shawn Cole created an issue Jenkins / JENKINS-35508 Invoking Config.xml through REST returns BOM Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Jun/09 4:46 PM Environment: Windows Server 2008 R2 Jenkins v 1.651 Powershell 3.0 Labels: rest Priority: Minor Reporter: Shawn Cole When invoking the Jenkins rest api for Freestyle jobs, the response began returning a BOM appended to the beginning:  This is causing malformed XML. I know this script was working in my last known jenkins ver : 1.627 Also, interestingly enough, this seems to only be a problem with freestyle jobs, retrieving the config.xml for my Maven jobs return normal XML data. Powershell : $url = "" class="code-quote"
[JIRA] [role-strategy-plugin] (JENKINS-18377) Improve the performance when listing many jobs
Title: Message Title Croesus Kall commented on JENKINS-18377 Re: Improve the performance when listing many jobs With the new release, 2.3.0, the performance is worse than ever (Using jenkins 2.8) After downgrading to 2.2.0, things were ok. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-34246) Deleting Jenkinsfile does not remove a repository from an organization folder
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-34246 Deleting Jenkinsfile does not remove a repository from an organization folder Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-34246) Deleting Jenkinsfile does not remove a repository from an organization folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34246 Re: Deleting Jenkinsfile does not remove a repository from an organization folder Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/multibranch/AbstractWorkflowMultiBranchProjectFactory.java src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/a7d63ecf3fc97a4657514c1b0495dd039aeafbc0 Log: [FIXED JENKINS-34246] Make AbstractWorkflowMultiBranchProjectFactory handle deletion or update of existing children. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-34246) Deleting Jenkinsfile does not remove a repository from an organization folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34246 Re: Deleting Jenkinsfile does not remove a repository from an organization folder Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/multibranch/AbstractWorkflowMultiBranchProjectFactory.java src/test/java/org/jenkinsci/plugins/workflow/multibranch/WorkflowMultiBranchProjectFactoryTest.java http://jenkins-ci.org/commit/workflow-multibranch-plugin/c0d0368994973cc3d6d2d542c36304b4acd71de3 Log: Merge pull request #15 from jglick/MultiBranchProjectFactory-update- JENKINS-34246 JENKINS-34246 Make AbstractWorkflowMultiBranchProjectFactory handle deletion or update of existing children Compare: https://github.com/jenkinsci/workflow-multibranch-plugin/compare/04d93559028b...c0d036899497 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-27216) "remoting.Channel" can not garbage collect
Title: Message Title Oleg Nenashev commented on JENKINS-27216 Re: "remoting.Channel" can not garbage collect I think it can be closed as a duplicate of JENKINS-26855 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-27216) "remoting.Channel" can not garbage collect
Title: Message Title Oleg Nenashev resolved as Duplicate Please reopen the issue if it is not correct Jenkins / JENKINS-27216 "remoting.Channel" can not garbage collect Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-26855) Unreachable objects "remoting.Channel" can not garbage collect
Title: Message Title Oleg Nenashev commented on JENKINS-26855 Re: Unreachable objects "remoting.Channel" can not garbage collect Another related issue is JENKINS-34213 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-28667) Memory usage of jnlp slave
Title: Message Title Oleg Nenashev commented on JENKINS-28667 Re: Memory usage of jnlp slave Needs to be retested with newest remoting versions. There were related fixes in Jenkins core and remoting Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-33524) Windows slave fails to connect to Jenkins via HTTPS
Title: Message Title Oleg Nenashev commented on JENKINS-33524 Re: Windows slave fails to connect to Jenkins via HTTPS It would be great to have server logs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-35247) Move git/svn steps out of workflow-scm-steps
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35247 Re: Move git/svn steps out of workflow-scm-steps Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/steps/scm/GitStep.java src/main/java/org/jenkinsci/plugins/workflow/steps/scm/SubversionStep.java http://jenkins-ci.org/commit/workflow-scm-step-plugin/ff3e0b937a5ff9e62754af2080bef89bd0b82aab Log: JENKINS-35247 Delegate to Git and Subversion plugins via reflection. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-35247) Move git/svn steps out of workflow-scm-steps
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35247 Re: Move git/svn steps out of workflow-scm-steps Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/steps/scm/GitStep.java src/main/java/org/jenkinsci/plugins/workflow/steps/scm/SubversionStep.java http://jenkins-ci.org/commit/workflow-scm-step-plugin/58237d3ca4f72fa102234910018286d9898cfcc4 Log: Merge pull request #3 from jglick/SCMStep-JENKINS-35247-reflection JENKINS-35247 Delegate to Git and Subversion plugins via reflection Compare: https://github.com/jenkinsci/workflow-scm-step-plugin/compare/edc5c6262d9f...58237d3ca4f7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-34322) Graceful error reporting if build agent runs unsupported version of Java
Title: Message Title Oleg Nenashev commented on JENKINS-34322 Re: Graceful error reporting if build agent runs unsupported version of Java I suppose Java should have built-in version requirement specification engine. .NET has it (even if it's crappy) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-35507) Paging not usable with large number of historical builds
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-35507 Paging not usable with large number of historical builds Issue Type: Bug Assignee: Patrik Boström Attachments: pipeline-view-with-paging.png, pipeline-view-without-paging.png Components: delivery-pipeline-plugin Created: 2016/Jun/09 4:12 PM Environment: Jenkins 1.642.3, delivery-pipeline-plugin 0.9.11 Priority: Critical Reporter: Marcin Zajączkowski It seems that paging mechanism ( JENKINS-28918 ) introduced regression in the situation where the first job in the pipeline has many historical builds. With paging enabled `Pipeline.createPipelineLatest()` creates a `Pipeline` instance for [every](https://github.com/Diabol/delivery-pipeline-plugin/commit/072343839463fe97a5b09e3ac47ef9f9433b239b#diff-abd99f83e18e7913a8ea3929339bc3a2R228) historical build (even if just a few will be displayed in the
[JIRA] [buildgraph-view-plugin] (JENKINS-35502) Build description misplaced on the same line with build status
Title: Message Title Suresh Kumar resolved as Fixed Jenkins / JENKINS-35502 Build description misplaced on the same line with build status Change By: Suresh Kumar Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-35506) Add a Pipeline step to the hpi Maven archetype
Title: Message Title Andrew Bayer created an issue Jenkins / JENKINS-35506 Add a Pipeline step to the hpi Maven archetype Issue Type: Improvement Assignee: Andrew Bayer Components: core, workflow-plugin Created: 2016/Jun/09 4:08 PM Labels: maven-hpi Priority: Minor Reporter: Andrew Bayer Note - there's no component I could find specifically for maven-hpi-plugin. It'd be good to have a Pipeline step for the HelloWorldBuilder in the sample project generated by maven-hpi-plugin's archetype. Add Comment
