[JIRA] (JENKINS-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title Janis Balodis commented on JENKINS-40432 Re: writeMavenPom throws class cast exception when creating a new pom file The workaround works. Thank you. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34121) IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3
Title: Message Title Mallikarjuna Manoj Kandala commented on JENKINS-34121 Re: IBM Java doesn't support AES/CTR/PKCS5Padding, required for JNLP3 Can someone please provide instructions to upgrade to JNLP4 ? We prefer to use IBM JRE. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42831) Enable StartTls is always TRUE in the UI
Title: Message Title Cristian Uroz commented on JENKINS-42831 Re: Enable StartTls is always TRUE in the UI Same issue with version activedirectory 2.3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42732) Unable to push file into slack with Slack file upload plugin
Title: Message Title Shitij Goyal commented on JENKINS-42732 Re: Unable to push file into slack with Slack file upload plugin Hi, Please post a screenshot of the build process and a screenshot of plugin configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Michael Neale Problem: The pipeline creation wizard in BO does not check for special characters and does not redirect to the activity page of jobs with special characters. Disclaimer: I don’t think we should support jobs with special characters. I think we should filter them out. The same constraints/rules should apply as in classic Care must be taken to ensure valid unicode is allowed and not inadvertently blocked. ATH test coverage is a pre-req for this. Steps to reproduce: # Create a new pipeline using the BO UI # In the pipeline name field enter any of these: # [file:/etc/hosts|file:///etc/hosts] # Or any of the unicode special characters from here: [https://github.com/minimaxir/big-list-of-naughty-strings/blob/master/blns.txt] # Save the pipeline. # At this point I got a 404 # Next I saw that the job was in the main UI but which I clicked on it, I got another 404. # After I restated the jobs with the special characters disappeared from the UI. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Michael Neale Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Michael Neale Problem: The pipeline creation wizard in BO does not check for special characters and does not redirect to the activity page of jobs with special characters. Disclaimer: I don’t think we should support jobs with special characters. I think we should filter them out. The same constraints/rules should apply as in classic Steps to reproduce: # Create a new pipeline using the BO UI # In the pipeline name field enter any of these: # [ file:/etc/hosts |file:///etc/hosts] # Or any of the unicode special characters from here: [https://github.com/minimaxir/big-list-of-naughty-strings/blob/master/blns.txt] # Save the pipeline. # At this point I got a 404 # Next I saw that the job was in the main UI but which I clicked on it, I got another 404. # After I restated the jobs with the special characters disappeared from the UI. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale edited a comment on JENKINS-42990 Re: Pipelines will misbehave if some special symbols are given in the name Needs more investigation * firstly the validation should be the same as Jenkins classic * with valid characters allowed by classic, pipeline creation should still work This may end up as 2 tickets EDIT: I checked some different languages that are legitimate and it works correctly, so this ticked is valid in requiring more validation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Michael Neale Labels: techical-debt Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: Michael Neale Environment: The jenkins server is the BO Exploratory Testing server here: http://ec2-52-200-141-179.compute-1.amazonaws.com:8080/ \ My client is a Manjaro Linux install, kernel version 4.4.54-1. The browsers I tested this with are: Firefox 52.0 (64-bit), and Chromium 57.0.2987.110 (64-bit) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title Michael Neale commented on JENKINS-42990 Re: Pipelines will misbehave if some special symbols are given in the name Needs more investigation firstly the validation should be the same as Jenkins classic with valid characters allowed by classic, pipeline creation should still work This may end up as 2 tickets Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title James Dumay commented on JENKINS-43039 Re: Blue Ocean Test Results fail to load over https Assigning to myself while we investigate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43056) Error while building code over kallithea repository
Title: Message Title kd medhe created an issue Jenkins / JENKINS-43056 Error while building code over kallithea repository Issue Type: Task Assignee: Unassigned Attachments: Invalid_Username_JenkinsMavenProject_20_Console_Jenkins_.png Components: maven-plugin, mercurial-plugin Created: 2017/Mar/23 5:07 AM Environment: Windows 8 64 bit Java 1.8 jdk jenkins 2.32.3 Labels: windows jenkins mercurial Priority: Minor Reporter: kd medhe Hii, I am facing problem while building a project from kallithea repository , i get following error Started by user Kd [EnvInject] - Loading node environment variables. Building in workspace C:\Users\Kd\.jenkins\jobs\JenkinsMavenProject\workspace $ hg clone --rev default --noupdate [repo url] C:\Users\Kd\.jenkins\jobs\JenkinsMavenProject\workspace ignoring invalid [auth] key 'default' ignoring invalid [auth] key 'username' ignoring invalid [auth] key 'password' ignoring invalid [auth] key 'default' ignoring invalid [auth] key 'username' ignoring invalid [auth] key 'password' abort: http authorization required for [repo url] ERROR: Failed to clone [repo url] ERROR: Failed to clone [repo url] Finished: FAILURE Even though I mentioned username and password in mercurial.ini file or in .hgrc file , it failing to clone. Please suggest the needful aspect while using jenkins with kallithea. Thanks in advance.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43039 Blue Ocean Test Results fail to load over https Change By: James Dumay Sprint: Blue Ocean 1.0-rc2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-43039 Blue Ocean Test Results fail to load over https Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43039) Blue Ocean Test Results fail to load over https
Title: Message Title James Dumay commented on JENKINS-43039 Re: Blue Ocean Test Results fail to load over https Jonathan Brito If you don't mind capturing a HAR file of the Test page load in Blue Ocean, that could help us diagnose this quicker. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43030) Naming Step sections in Blue Ocean
Title: Message Title James Dumay resolved as Duplicate Sean Whyte we want this too Our approach is to have steps produce better names. If that does not solve most users problems we can look into custom step names but it is a much bigger change. See JENKINS-37324 for more info Jenkins / JENKINS-43030 Naming Step sections in Blue Ocean Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-43046) declarative pipeline with long list choice parameters have incorrect display
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-43046 declarative pipeline with long list choice parameters have incorrect display Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42990) Pipelines will misbehave if some special symbols are given in the name
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42990 Pipelines will misbehave if some special symbols are given in the name Change By: James Dumay Sprint: Blue Ocean 1. 0-rc2 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43014) Branches saved off of non-master cause false "duplicate name" error, don't save content
Title: Message Title Michael Neale updated JENKINS-43014 Jenkins / JENKINS-43014 Branches saved off of non-master cause false "duplicate name" error, don't save content Change By: Michael Neale Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Misa Travel commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent Hello! I also want to join my case: I have Jenkins running in a Windows 10 machine, no cygwin, and after the upgrade I get these messages: [03/23/17 11:46:57] [SSH] Opening SSH connection to fedora1.misatravel.org:22. C:\Users\dev\.ssh\known_hosts [SSH] No Known Hosts file was found at C:\Users\dev\.ssh\known_hosts. Please ensure one is created at this path and that Jenkins can read it. Key exchange was not finished, connection is closed. java.io.IOException: There was a problem while connecting to fedora1.misatravel.org:22 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:601) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1265) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:790) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:785) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Key exchange was not finished, connection is closed. at com.trilead.ssh2.transport.KexManager.getOrWaitForConnectionInfo(KexManager.java:93) at com.trilead.ssh2.transport.TransportManager.getConnectionInfo(TransportManager.java:230) at com.trilead.ssh2.Connection.connect(Connection.java:770) ... 9 more Caused by: java.io.IOException: The server hostkey was not accepted by the verifier callback at com.trilead.ssh2.transport.KexManager.handleMessage(KexManager.java:591) at com.trilead.ssh2.transport.TransportManager.receiveLoop(TransportManager.java:777) at com.trilead.ssh2.transport.TransportManager$1.run(TransportManager.java:489) ... 1 more [03/23/17 11:46:57] Launch failed - cleaning up connection [03/23/17 11:46:57] [SSH] Connection closed. Again, it is a Windows machine and it doesn't need to follow the architecture of a Linux machine. Why is the SSH know relying in what the system may have instead of Jenkins' configuration? After of all, the manager of Jenkins doesn't need to be the same manager than the manager for the system account where Jenkins is running. Add Comment
[JIRA] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Title: Message Title
jothibasu k edited a comment on JENKINS-17514
Re: NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
we are using maven plugin and slave is connected as Windows Slave, in the middle of the maven execution build got aborted due to same error, Could you please check and let me know this error is related to this issue or different.{code:java}ERROR: Build step failed with exceptionjava.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[Maventest-01] which is computer hudson.slaves.SlaveComputer@3c2ce65f and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:74) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Build step 'Execute Windows batch command' marked build as failureERROR: Maventest-01 is offline; cannot locate Maven 3.0.4ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4ERROR: Failed to parse POMsjava.io.IOException: Backing channel is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at com.sun.proxy.$Proxy114.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur.Finished: FAILURE{code}our Jenkins Version is : Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)
Add Comment
[JIRA] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Title: Message Title jothibasu k commented on JENKINS-17514 Re: NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510 we are using maven plugin and slave is connected as Windows Slave, in the middle of the maven execution build got aborted due to same error, Could you please check and let me know this error is related to this issue or different. ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[Maventest-01] which is computer hudson.slaves.SlaveComputer@3c2ce65f and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:74) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:906) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:857) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Build step 'Execute Windows batch command' marked build as failure ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4 ERROR: Maventest-01 is offline; cannot locate Maven 3.0.4 ERROR: Failed to parse POMs java.io.IOException: Backing channel is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:184) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:249) at com.sun.proxy.$Proxy114.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:996) at hudson.maven.ProcessCache$MavenProcess.call(ProcessCache.java:166) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:840) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur. Finished: FAILURE our Jenkins Version is : Jenkins ver. 1.651.3.1 (CloudBees Jenkins Enterprise 16.06)
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title James Dumay commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step Tomasz Śniatowski we certainly plan for it to be a link of some kind. We will upload a design on this issue when we get to this one so you can give us feedback Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: James Dumay Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43014) Branches saved off of non-master cause false "duplicate name" error, don't save content
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43014 Re: Branches saved off of non-master cause false "duplicate name" error, don't save content Code changed in jenkins User: Keith Zantow Path: src/main/js/EditorPage.jsx src/main/js/SaveApi.js http://jenkins-ci.org/commit/blueocean-pipeline-editor-plugin/d2e6795aa60bbcd62d11c38df30939d65d07fd69 Log: JENKINS-43014 save to/from branches properly, use optimized indexing (#35) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42872) Inputs with multiple approvers do not work
Title: Message Title Ivan Meredith started work on JENKINS-42872 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42702) Applying the branch filter should set active the activity tab
Title: Message Title Ivan Meredith updated JENKINS-42702 Jenkins / JENKINS-42702 Applying the branch filter should set active the activity tab Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Andrew Bayer assigned an issue to Jesse Glick Jesse Glick - I've been seeing this lately too. Not sure if it's a problem or what. Jenkins / JENKINS-43055 "List of flow heads unset for CpsFlowExecution[null]" Warning Change By: Andrew Bayer Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43041) Cannot create a new instance of a pipeline shared library class
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-43041 Cannot create a new instance of a pipeline shared library class Change By: Andrew Bayer Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-43055 "List of flow heads unset for CpsFlowExecution[null]" Warning Change By: Andrew Bayer Component/s: workflow-cps-global-lib-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-43055 "List of flow heads unset for CpsFlowExecution[null]" Warning Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: workflow-cps-global-lib-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40885) Environment variables are not exposed in pipeline script
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-40885 Re: Environment variables are not exposed in pipeline script The latest version of P4 plugin is 1.5.1 and I am not able to reproduce the issue with that version. This seems fixed no ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Waite commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work That's a good suggestion, though I really intend that the plugin will never prompt for a passphrase, where run with a controlling terminal or not. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Sergey Serebryakov commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work Tip: if running Jenkins inside of Docker container, don't provide -it flags, otherwise Jenkins will think it's run from a terminal and start asking for passphrase instead of using the one provided in Credentials settings. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36486) httpRequest executes from Jenkins Master node
Title: Message Title Janario Oliveira started work on JENKINS-36486 Change By: Janario Oliveira Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26046) Wiki 'open issues' link brings to component 'http_request-plugin' instead of 'http_request'
Title: Message Title Janario Oliveira closed an issue as Not A Defect Jenkins / JENKINS-26046 Wiki 'open issues' link brings to component 'http_request-plugin' instead of 'http_request' Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32263) Workflow support for http-request-plugin
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-32263 Workflow support for http-request-plugin Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29261) Jenkins Proxy error: Server redirected too many times
Title: Message Title Janario Oliveira closed an issue as Not A Defect Jenkins / JENKINS-29261 Jenkins Proxy error: Server redirected too many times Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41934) HTTPS/TLS Cert check bypassed
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-41934 HTTPS/TLS Cert check bypassed Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42303) handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin
Title: Message Title Janario Oliveira closed an issue as Fixed Jenkins / JENKINS-42303 handshake_failure for (AWS) HTTPS/SSL urls with the HTTP Request plugin Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title Janario Oliveira closed an issue as Cannot Reproduce Jenkins / JENKINS-39680 httpRequest method in Pipeline causes weird behavior Change By: Janario Oliveira Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43055) "List of flow heads unset for CpsFlowExecution[null]" Warning
Title: Message Title Kenny N created an issue Jenkins / JENKINS-43055 "List of flow heads unset for CpsFlowExecution[null]" Warning Issue Type: Bug Assignee: Unassigned Components: core, pipeline Created: 2017/Mar/23 12:38 AM Environment: # defaults for jenkins continuous integration server # pulled in from the init script; makes things easier. NAME=jenkins # location of java JAVA=/usr/bin/java # arguments to pass to java JAVA_ARGS="-Djava.awt.headless=true" # Allow graphs etc. to work even when an X server is present #JAVA_ARGS="-Xmx256m" JAVA_ARGS="-Djava.net.preferIPv4Stack=true" # make jenkins listen on IPv4 address PIDFILE=/var/run/$NAME/$NAME.pid # user and group to be invoked as (default to jenkins) JENKINS_USER=$NAME JENKINS_GROUP="$NAME docker" # location of the jenkins war file JENKINS_WAR=/usr/share/$NAME/$NAME.war # jenkins home location JENKINS_HOME=/data/jenkins # set this to false if you don't want Hudson to run by itself # in this set up, you are expected to provide a servlet container # to host jenkins. RUN_STANDALONE=true # log location. this may be a syslog facility.priority JENKINS_LOG=/var/log/$NAME/$NAME.log #JENKINS_LOG=daemon.info # OS LIMITS SETUP # comment this out to observe /etc/security/limits.conf # this is on by default because http://github.com/jenkinsci/jenkins/commit/2fb288474e980d0e7ff9c4a3b768874835a3e92e # reported that Ubuntu's PAM configuration doesn't include pam_limits.so, and as a result the # of file # descriptors are forced to 1024 regardless of /etc/security/limits.conf MAXOPENFILES=8192 # set the umask to control permission bits of files that Jenkins creates. # 027 makes files read-only for group and inaccessible for others, which some security sensitive users # might consider benefitial, especially if Jenkins runs in a box that's used for multiple purposes. # Beware that 027 permission would interfere with sudo scripts that run on the master ( JENKINS-25065 .) # # Note also that the particularly sensitive part of $JENKINS_HOME (such as credentials) are always # written without 'others' access. So the umask values only affect job configuration, build records, # that sort of things. # # If commented out, the value from the OS is inherited, which is normally 022 (as of Ubuntu 12.04, # by default umask comes from pam_umask(8) and /etc/login.defs # UMASK=027 # port for HTTP connector (default 8080; disable with -1) HTTP_PORT=8080 # port
[JIRA] (JENKINS-43033) Suppress Sleep Step Output
Title: Message Title Marc Benstein updated an issue Jenkins / JENKINS-43033 Suppress Sleep Step Output Change By: Marc Benstein Summary: Suppress Sleep logging Step Output Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title James Dumay commented on JENKINS-43053 Re: Allow user to document their pipeline in model friendly way Liam Newman I'd like to call out that nesting stages isn't an appropriate solution for this problem. It's a huge, nuanced problem on its own - just read JENKINS-38442 to get a sense of that. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title Liam Newman commented on JENKINS-43053 Re: Allow user to document their pipeline in model friendly way James Dumay Andrew Bayer I'm okay with that too. My only strong feeling is that whatever we do should: 1. not require changes to the way existing Scripted Pipeline steps are used 2. be consistent and usable throughout Declarative with reasonable liimitation. For example, it might be reasonable to say comments can't be added inside the environment directive due to technical limitations. I'm open to discussing. 3. (optional) flexible enough to cover the labelling concept you mentioned or a reasonable parallel example of how the labeling might also be done. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row
Title: Message Title Swathi Gangisetty updated JENKINS-43048 Jenkins / JENKINS-43048 Anchore report triggers datatables error if gate output contains only one row Change By: Swathi Gangisetty Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title
Mark Waite edited a comment on JENKINS-43052
Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
I believe your concern is that when using the UI to define the top level pipeline project (in a pipeline project that gets its Jenkinsfile from a git repository, or in a multi-branch pipeline), there are options displayed which will prevent the pipeline code from finding Jenkinsfile in the {{...@script}} directory. I think you're right that we should disable presenting those options to the user when they are defining the top level pipeline project.I think your statement:bq. As far as I can see, Additional Behaviors > Check out to a sub-directory is never appropriate with Pipeline.is too broad, at least for my use case. I use checkout to a subdirectory to allow me to bring multiple repositories into a single workspace with simple calls to checkout. I could certainly replace those calls to checkout by nesting them inside a dir(), but I don't see why we should disallow my use of checkout to a subdirectory from inside a Jenkinsfile. I don't see how that would help users who (like me) can use "Pipeline Syntax" to show the options in that context, and use them.Refer to the [35475 verification check Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-35475/Jenkinsfile] for an example of how I use checkout to a subdirectory inside a Jenkinsfile.However, I'm certainly open to further knowledge from @ [~ jglick ] . I would rather not break compatibility with existing uses of the checkout command, unless there is a compelling reason to do so.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43054) Command line access to pipeline retry
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-43054 Command line access to pipeline retry Issue Type: New Feature Assignee: Unassigned Components: workflow-api-plugin Created: 2017/Mar/22 11:12 PM Priority: Major Reporter: Michael Neale To aid development of Jenkinsfiles, it would be advantagous if the CLI allowed access to the "retry" feature of pipeline. You could edit a Jenkinsfile locally, run the retry with its content (against an appropriate build run number) and see the results, repeat. Add Comment
[JIRA] (JENKINS-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein edited a comment on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround \ { \{ code:java} writeFile file: 'pom.xml', text: '4.0.0' def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip'writeMavenPom model: pom {code } }
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein edited a comment on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround \ { \ { }} writeFile file: 'pom.xml', text: '4.0.0'def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip'writeMavenPom model: pom }}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay commented on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Alternative - allow a comment {} block anywhere?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title James Dumay commented on JENKINS-43053 Re: Allow user to document their pipeline in model friendly way Liam Newman annotations don't really fit the style we are promoting in declarative. I believe Libraries used annotations and we ended up going a different route for them in declarative. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40432) writeMavenPom throws class cast exception when creating a new pom file
Title: Message Title
Marc Benstein commented on JENKINS-40432
Re: writeMavenPom throws class cast exception when creating a new pom file
Here's a workaround {{}} writeFile file: 'pom.xml', text: '4.0.0' def pom = readMavenPom() pom.artifactId = 'some.id' pom.groupId = 'org.something' pom.version = '1.0.0-SNAPSHOT' pom.packaging = 'zip' writeMavenPom model: pom
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Mark Waite commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects I believe your concern is that when using the UI to define the top level pipeline project (in a pipeline project that gets its Jenkinsfile from a git repository, or in a multi-branch pipeline), there are options displayed which will prevent the pipeline code from finding Jenkinsfile in the ...@script directory. I think you're right that we should disable presenting those options to the user when they are defining the top level pipeline project. I think your statement: As far as I can see, Additional Behaviors > Check out to a sub-directory is never appropriate with Pipeline. is too broad, at least for my use case. I use checkout to a subdirectory to allow me to bring multiple repositories into a single workspace with simple calls to checkout. I could certainly replace those calls to checkout by nesting them inside a dir(), but I don't see why we should disallow my use of checkout to a subdirectory from inside a Jenkinsfile. I don't see how that would help users who (like me) can use "Pipeline Syntax" to show the options in that context, and use them. Refer to the 35475 verification check Jenkinsfile for an example of how I use checkout to a subdirectory inside a Jenkinsfile. However, I'm certainly open to further knowledge from @jglick. I would rather not break compatibility with existing uses of the checkout command, unless there is a compelling reason to do so. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-40456) First time builds are not reporting to Bitbucket
Title: Message Title
Adrian Carriger commented on JENKINS-40456
Re: First time builds are not reporting to Bitbucket
Hi Antonio Mansilla, thanks for the awesome plugin! I'm also experiencing the issue and have created a minimal repo to demonstrate what I'm experiencing. Steps to reproduce
Create a mutlibranch Jenkins (v2.51) project with a Jenkinsfile like this
This does post to Bitbucket
Create a branch, publish it, make a commit
This does not post to Bitbucket
Make another change on the branch
This does post to Bitbucket
No Error Message In the Jenkins log for the build that does not post to Bitbucket there is no error message and there is no success message. Log Here is the log for the build that does not post to Bitbucket Branch indexing > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 using GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ Seen branch in repository origin/issue-example Seen branch in repository origin/master Seen 2 remote branches Obtained Jenkinsfile from be3deb74d3c0f1f489c64e76827606ece518131b [Pipeline] node Running on master in /Users/acarriger/.jenkins/workspace/tifier-plugin_issue-example-7CIO4G3WKWGDSZ73ZRBWZTTA265YQQSKAEKGOJOPCLK5RW635WYQ [Pipeline] { [Pipeline] checkout Cloning the remote Git repository Cloning repository g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git init /Users/acarriger/.jenkins/workspace/tifier-plugin_issue-example-7CIO4G3WKWGDSZ73ZRBWZTTA265YQQSKAEKGOJOPCLK5RW635WYQ # timeout=10 Fetching upstream changes from g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git > git --version # timeout=10 using GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git +refs/heads/:refs/remotes/origin/ > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10 > git config remote.origin.url g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git # timeout=10 Fetching upstream changes from g...@bitbucket.org:dt-acarriger/bitbucket-build-status-notifier-plugin-issue.git using GIT_ASKPASS to set credentials Bitbucket Notify > git fetch --tags --progress g...@bitbucket.org:dt-acarriger/bitbu
[JIRA] (JENKINS-38233) Enable review builds with pipeline scripts
Title: Message Title Joel Brown reopened an issue reopening since broken in 1.5.1 Jenkins / JENKINS-38233 Enable review builds with pipeline scripts Change By: Joel Brown Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38233) Enable review builds with pipeline scripts
Title: Message Title Joel Brown commented on JENKINS-38233 Re: Enable review builds with pipeline scripts Broken in 1.5.1, worked in 1.4.9 Repro: in browser, navigate to pipeline job (http://jenkinsHost/job/PIPELINE-JOB) and append /review/build to the address. actual: 404 not found expected: build triggered Swarm log: 2017-03-22T15:42:44-07:00 ERR (3): Failed to trigger automated tests: http://jbrown-p4.das.perforce.com:8080/job/piper/review/build?status=shelved&review=751&change=753&pass=http%3 A%2F%2Fjbrown-swarm.das.perforce.com%2Freviews%2F751%2Ftests%2Fpass%2F7A3CA388-112E-42DE-F37A-9237B49285D0.v2%2F&fail=http%3A%2F%2Fjbrown-swarm.das.perforce.com%2Freviews%2F751%2Ft ests%2Ffail%2F7A3CA388-112E-42DE-F37A-9237B49285D0.v2%2F (404 - ). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42813) Discard old items to be removed from multi-branch UI config
Title: Message Title Christoph Schwarz edited a comment on JENKINS-42813 Re: Discard old items to be removed from multi-branch UI config Invalid as "discard old items" in this context refers to "branches". Documenting it would be helpful and avoid confusion . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42813) Discard old items to be removed from multi-branch UI config
Title: Message Title Christoph Schwarz resolved as Not A Defect Invalid as "discard old items" in this context refers to "branches". Documenting it would be helpful. Jenkins / JENKINS-42813 Discard old items to be removed from multi-branch UI config Change By: Christoph Schwarz Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsu
[JIRA] (JENKINS-43049) Jobs for deleted branches are no longer pruned
Title: Message Title Christoph Schwarz resolved as Not A Defect Just figured out that there is a way to have deleted branches removed. In the configuration under "Orphaned Item Strategy" click "Discard old items" (the term items in this context refers to branches). Then enter "Days to keep old items" or "Max # of old items to keep". "Days to keep old items" with value 1 worked for us. That being said, this configuration item lacks documentation and that was the case why we did not understand how to use it. Jenkins / JENKINS-43049 Jobs for deleted branches are no longer pruned Change By: Christoph Schwarz Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
Liam Newman edited a comment on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
The problem is that steps aren't allowed in some places you'd want to put documenting comments. [~jamesdumay]Stages and nested-stages seem like they'd address the `label` scenario. Having a way to give individual steps more meaningful display names is also good, and if we can have consistent way do both documenting and step labeling, that'd be great. But they may not line up perfectly. The annotation route (if I understand it correctly) might look something like:{code}@Comment('This is a comment helps someone editing this pipeline understand the intent.')@Description('This a description that is visible to the end user when they look at the details of this stage.')stage ('Build') { steps { @Title('Resolve Maven Dependencies') @Description('This a description that is visible to the end user when they look at the details of this step.') sh 'mvn dependencies:resolve' @Title('Maven Clean and Install') sh 'mvn clean install'} }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title Liam Newman commented on JENKINS-43053 Re: Allow user to document their pipeline in model friendly way The problem is that steps aren't allowed in some places you'd want to put documenting comments. James Dumay Stages and nested-stages seem like they'd address the `label` scenario. Having a way to give individual steps more meaningful display names is also good, and if we can have consistent way do both documenting and step labeling, that'd be great. But they may not line up perfectly. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay edited a comment on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Could this also serve the purpose of defining step names etc for the editor? Perhaps we should bring back the idea of {{label}}?{code}stage ('Build') { steps {label( title name : 'Run maven', description:'Run Maven before packaging') { sh 'mvn dependencies:resolve' sh 'mvn clean install'} }}{code}Then the visualization could collapse both shell script steps into a single step called 'Run Maven' and we could even use the description as extra information on hover etc.Making it step based would allow documenting within the editor. Perhaps we could even go as far as:{code}stage (name: 'Build', description: 'cool description for this stage') { ...}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay edited a comment on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Could this also serve the purpose of defining step names etc for the editor? Perhaps we should bring back the idea of {{label}}?{code}stage ('Build') { steps {label(name: 'Run maven', description:'Run Maven before packaging') { sh 'mvn dependencies:resolve' sh 'mvn clean install'} }}{code}Then the visualization could collapse both shell script steps into a single step called 'Run Maven' and we could even use the description as extra information on hover etc.Making it step based would allow documenting within the editor.Perhaps we could even go as far as add this to the {{stage}} too :{code}stage (name: 'Build', description: 'cool description for this stage') { ...}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay edited a comment on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Could this also serve the purpose of defining step names etc for the editor? Perhaps we should bring back the idea of {{label}}?{code}stage ('Build') { steps {label(title: 'Run maven', description:'Run Maven before packaging') { sh 'mvn dependencies:resolve' sh 'mvn clean install'} }}{code}Then the visualization could collapse both shell script steps into a single step called 'Run Maven' and we could even use the description as extra information on hover etc.Making it step based would also make it work perfectly with allow documenting within the editor.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay edited a comment on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Could this also serve the purpose of defining step names etc for the editor? Perhaps we should bring back the idea of {{label}}?{code}stage ('Build') { steps {label(title: 'Run maven', description:'Run Maven before packaging') { sh 'mvn dependencies:resolve' sh 'mvn clean install'} }}{code} Then the visualization could collapse both shell script steps into a single step called 'Run Maven' and we could even use the description as extra information on hover etc.Making it step based would also make it work perfectly with the editor.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title
James Dumay commented on JENKINS-43053
Re: Allow user to document their pipeline in model friendly way
Could this also serve the purpose of defining step names etc for the editor? Perhaps we should bring back the idea of label?
stage ('Build') {
steps {
label(title: 'Run maven', description:'Run Maven before packaging') {
sh 'mvn dependencies:resolve'
sh 'mvn clean install'
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Stephen McCants commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Jesse Glick, fair enough. I wasn't sure what the long term plan was. I'm okay with this being marked as a duplicate of JENKINS-32167. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40267) Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory
Title: Message Title John McGehee closed an issue as Won't Fix This is a git-plugin issue, not a Pipeline issue. Created Check out to a sub-directory" for Pipeline projects" class="issue-link" data-issue-key="JENKINS-43052" style="color: #3b73af; text-decoration: none">JENKINS-43052 per Jesse Glick's suggestion. Jenkins / JENKINS-40267 Multibranch pipeline cannot find Jenkinsfile with Check out to a sub-directory Change By: John McGehee Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.go
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title Michael Neale commented on JENKINS-43053 Re: Allow user to document their pipeline in model friendly way For your consideration Andrew Bayer and Patrick Wolf Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38864) Add support for preserving comments and formatting for Jenkinsfile roundtrip
Title: Message Title Michael Neale commented on JENKINS-38864 Re: Add support for preserving comments and formatting for Jenkinsfile roundtrip I have opened https://issues.jenkins-ci.org/browse/JENKINS-43053 to see if a neater and simpler alternative is possible Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43053) Allow user to document their pipeline in model friendly way
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-43053 Allow user to document their pipeline in model friendly way Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2017/Mar/22 10:23 PM Priority: Major Reporter: Michael Neale As https://issues.jenkins-ci.org/browse/JENKINS-38864 is likely to be a bit of rocket science, there is still a need to allow users to document their pipelines in a model friendly way, that the blue ocean editor (for example) can read, and allow users to edit. The comments may also be useful for people diagnosing broken steps etc If there was a way to annotate or have a meta data field for parts of the pipeline declarative model, this could be really helpful. In terms of syntax, I don't have concrete ideas - it could be an attribute, an annotation, or someting. Anything really. Add Comment
[JIRA] (JENKINS-43052) Disallow *Additional Behaviors > Check out to a sub-directory* for Pipeline projects
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-43052 Disallow *Additional Behaviors > Check out to a sub-directory* for Pipeline projects Change By: John McGehee Summary: Allow Disallow * Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject * for Pipeline projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title John McGehee updated an issue Jenkins / JENKINS-43052 Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Change By: John McGehee Summary: Disallow * " Additional Behaviors > Check out to a sub-directory * " for Pipeline projects Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-43052 Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43052) Allow Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject
Title: Message Title
John McGehee created an issue
Jenkins / JENKINS-43052
Allow Additional Behaviors > Check out to a sub-directory only if the AncestorInPath is an AbstractProject
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2017/Mar/22 10:19 PM
Environment:
Jenkins ver. 2.19.2 Pipeline 2.4 Pipeline: Multibranch 2.9 Ubuntu 16 LTS
Priority:
Minor
Reporter:
John McGehee
Additional Behaviors > Check out to a sub-directory clones Jenkinsfile in the specified directory. Meanwhile, Jenkins itself continues to look for Jenkinsfile at the top of the workspace. This is very confusing. As far as I can see, Additional Behaviors > Check out to a sub-directory is never appropriate with Pipeline. This should be handled in Jenkinsfile using dir():
dir('subDir') {
checkout scm
}
In JENKINS-40267, Jesse Glick suggested that git-plugin should conditionally display the Additional Behaviors > Check out to a sub-directory option only if the AncestorInPath is an AbstractProject.
[JIRA] (JENKINS-41345) P4 Plugin does not read credentials from folders
Title: Message Title Clifford Holden closed an issue as Duplicate This was a duplicate of JENKINS-34825 Jenkins / JENKINS-41345 P4 Plugin does not read credentials from folders Change By: Clifford Holden Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/op
[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row
Title: Message Title Swathi Gangisetty updated JENKINS-43048 Jenkins / JENKINS-43048 Anchore report triggers datatables error if gate output contains only one row Change By: Swathi Gangisetty Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43051) Jenkins Parameters/Variables are not expanded during Polling
Title: Message Title
Emory Penney created an issue
Jenkins / JENKINS-43051
Jenkins Parameters/Variables are not expanded during Polling
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2017/Mar/22 10:15 PM
Environment:
Jenkins: 2.32.2 p4-plugin: 1.5.1
Priority:
Major
Reporter:
Emory Penney
Steps to reproduce:
Create a job with P4 Plugin
Add two parameters to the job
changelist (leave default blank)
depot_path //depot/some/path
Set Manual View Mappings:
${depot_path}/... //${P4_CLIENT}/...
Set pin build at perforce label:
${changelist}
Check "Poll SCM":
EG: H/2 * * * *
[JIRA] (JENKINS-43048) Anchore report triggers datatables error if gate output contains only one row
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43048 Re: Anchore report triggers datatables error if gate output contains only one row Code changed in jenkins User: Swathi Gangisetty Path: src/main/java/com/anchore/jenkins/plugins/anchore/BuildWorker.java http://jenkins-ci.org/commit/anchore-container-scanner-plugin/a069e51feab8671cdae813b8c3991558ab66bb4b Log: Fix data generation for policy evaluation summary table Fixes JENKINS-43048 Signed-off-by: Swathi Gangisetty Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41345) P4 Plugin does not read credentials from folders
Title: Message Title Clifford Holden commented on JENKINS-41345 Re: P4 Plugin does not read credentials from folders Thanks for the update, I'll close this one as a duplicate. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38864) Add support for preserving comments and formatting for Jenkinsfile roundtrip
Title: Message Title Michael Neale edited a comment on JENKINS-38864 Re: Add support for preserving comments and formatting for Jenkinsfile roundtrip Yes I agree this is possibly quite important - if you think about comments as pipeline documentation. some other options are to have first class elements somewere that store documentation, but that isn't groovy comments. The effort/reward ratio here isn't high clear to me yet , but documentation in pipeline will become VERY important I think, just don't know how to solve it with the groovy tax being paid. It's a very expensive tax. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40477) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild
Title: Message Title Jesse Glick commented on JENKINS-40477 Re: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowRun cannot be cast to hudson.model.AbstractBuild Zee Maqbool see discussion above. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37800) Incorrect PATH over pipeline nodes
Title: Message Title Jesse Glick commented on JENKINS-37800 Re: Incorrect PATH over pipeline nodes Not really following, but sounds like a user list question. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38864) Add support for preserving comments and formatting for Jenkinsfile roundtrip
Title: Message Title Michael Neale commented on JENKINS-38864 Re: Add support for preserving comments and formatting for Jenkinsfile roundtrip Yes I agree this is possibly quite important - if you think about comments as pipeline documentation. some other options are to have first class elements somewere that store documentation, but that isn't groovy comments. The effort/reward ratio here isn't high, but documentation in pipeline will become VERY important I think, just don't know how to solve it with the groovy tax being paid. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42637) Jenkins stuck UI does not open at all
Title: Message Title Jesse Glick commented on JENKINS-42637 Re: Jenkins stuck UI does not open at all No idea offhand. Reproducible from scratch? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43046) declarative pipeline with long list choice parameters have incorrect display
Title: Message Title James Dumay commented on JENKINS-43046 Re: declarative pipeline with long list choice parameters have incorrect display Boudoux Etienne no worries about the duplicate! Theres a lot of content in this issue tracker and its even difficult for me to find duplicates I've marked this ticket as a duplicate of both JENKINS-42131 and JENKINS-43009 since your example both exhibits the issue with Dropdowns in Firefox (scheduled) and a general styling issue that made the parameterised form appear in the top left (this one has been fixed). I really appreciate you taking the time to report this issue so thank you! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43050) SSH Agent plugin doesn't work well with docker pipelines
Title: Message Title
Erik Lattimore created an issue
Jenkins / JENKINS-43050
SSH Agent plugin doesn't work well with docker pipelines
Issue Type:
Bug
Assignee:
Unassigned
Components:
ssh-agent-plugin
Created:
2017/Mar/22 10:05 PM
Priority:
Minor
Reporter:
Erik Lattimore
I've tried
dockerImage.inside {
sshagent([...]) {
sh '...'
}
}
and this appears to fail because the ssh-agent gets launched but then the next command appears to be ssh-agent -k which kills the process before the sh step has a chance to run despite the sh command being inside the sshagent block. And also
sshagent([...]){
dockerImage.inside {
sh '...'
}
}
fails (I think) for a more predictable reason: the ssh-agent stays running and the env variables get set correctly inside the container, however the socket is in /tmp on the container server which is not visible to the container (by default).
[JIRA] (JENKINS-38837) Mutibranch project plugin does not respect "Workspace Root Directory" global configuration
Title: Message Title Jesse Glick commented on JENKINS-38837 Re: Mutibranch project plugin does not respect "Workspace Root Directory" global configuration will still retrieve the entire repository into the master's workspace directories for each Jenkinsfile it wants to read Not if you update workflow-multibranch and meet the conditions mentioned in its release notes. Anyway that is off topic here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43049) Jobs for deleted branches are no longer pruned
Title: Message Title Christoph Schwarz updated an issue Jenkins / JENKINS-43049 Jobs for deleted branches are no longer pruned Change By: Christoph Schwarz This is the third regression we found after upgrading the "Pipeline: Multibranch" plugin from 2.9.2 to 2.14In version 2.9.2, jobs got automatically deleted once the remote branch got deleted and thus disappear from the branch list .Since version 2.14 those jobs are not deleted but rather changed to "disabled" and stay on the branch list .We would like the have the option to configure the original behavior. We did not find any such option on the configuration page. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43049) Jobs for deleted branches are no longer pruned
Title: Message Title Christoph Schwarz created an issue Jenkins / JENKINS-43049 Jobs for deleted branches are no longer pruned Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2017/Mar/22 9:59 PM Environment: Pipeline: Multibranch 2.14 GIT client plugin 2.3.0 GIT plugin 3.1.0 Priority: Major Reporter: Christoph Schwarz This is the third regression we found after upgrading the "Pipeline: Multibranch" plugin from 2.9.2 to 2.14 In version 2.9.2, jobs got automatically deleted once the remote branch got deleted. Since version 2.14 those jobs are not deleted but rather changed to "disabled". We would like the have the option to configure the original behavior. We did not find any such option on the configuration page. Add Comment
[JIRA] (JENKINS-42729) Remove bare parameters from pipeline binding context
Title: Message Title Jesse Glick commented on JENKINS-42729 Re: Remove bare parameters from pipeline binding context we should make bare access obsolete and move toward removing it Other than updating documentation, which we are already doing, I suppose CpsScript.getProperty could print a warning to the log before returning a value from EnvActionImpl, if it can determine that this property came from a build parameter. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42729) Remove bare parameters from pipeline binding context
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-42729 Remove bare parameters from pipeline binding context Change By: Jesse Glick Labels: usability Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35102) Xvfb is not stopped
Title: Message Title Chris Giddings edited a comment on JENKINS-35102 Re: Xvfb is not stopped Also experiencing this issue. * Jenkins master only, no slaves * No parallelism * Maven jobThings to know: * Jenkins 2.51 * Xvfb plugin 1.1.3 * Ubuntu Linux Restarting Jenkins (and consequently the plugin) tends to fix this issue. Restarting the server is not required. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35102) Xvfb is not stopped
Title: Message Title Chris Giddings commented on JENKINS-35102 Re: Xvfb is not stopped Also experiencing this issue. Jenkins master only, no slaves No parallelism Maven job Things to know: Jenkins 2.51 Xvfb plugin 1.1.3 Ubuntu Linux Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37220) Job DSL analogue of multibranch projects & organization folders
Title: Message Title Jesse Glick commented on JENKINS-37220 Re: Job DSL analogue of multibranch projects & organization folders Christian Höltje your use case is solvable in various ways in organization folders as they stand, since you “only” need to adjust the behavior of the build. Now it happens that currently scm is not “editable” but that could be addressed I think. Really you can checkout any GitSCM you like, you just lose the feature of picking up the exact commit (including a PR merge with base branch) that the Jenkinsfile comes from. This issue was more about allowing users to programmatically customize things which are inherently aspects of the job, not any individual build. Or even decide when to create a job for a given repo/branch, or create multiple such jobs, etc. Michael Neale for years now, plenty of Job DSL users already iterate over the GitHub API (via github-api plugin, or roll-your-own), or something along those lines, so as to get a DIY version of multibranch. This proposal would (if it is feasible) bring some of the polish of branch-api and some of the features of branch source plugins to this usage style, while retaining its flexibility. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43046) declarative pipeline with long list choice parameters have incorrect display
Title: Message Title Boudoux Etienne commented on JENKINS-43046 Re: declarative pipeline with long list choice parameters have incorrect display firefox 52.0.1 (64 bits) on linux sorry about the duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43005) Warn if there are comment strings in declarative pipeline when opened in editor
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-43005 Warn if there are comment strings in declarative pipeline when opened in editor Change By: Michael Neale Summary: Support retaining/adding comments Warn if there are comment strings in BlueOcean Editor declarative pipeline when opened in editor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43005) Support retaining/adding comments in BlueOcean Editor
Title: Message Title Michael Neale commented on JENKINS-43005 Re: Support retaining/adding comments in BlueOcean Editor If comments can't be round tripped, yes I think a warning - on load perhaps? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
