[JIRA] (JENKINS-41442) Configuring Pipeline Global Library injects History into Job.
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-41442 Configuring Pipeline Global Library injects History into Job. Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2017/Jan/25 5:11 PM Environment: Jenkins 2.19.4 workflow-global-lib-plugin Priority: Trivial Reporter: Mark Bidewell I have a global library in an external Git (Modern SCM). When I make changes to my groovy scripts, the change history of the scripts is intermixed with the change history of the build. The script history should not appear in the job. Add Comment
[JIRA] (JENKINS-41955) MaskPaswordsBuildWrapper no longer hiding Passwords
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-41955 MaskPaswordsBuildWrapper no longer hiding Passwords Issue Type: Bug Assignee: Oleg Nenashev Components: mask-passwords-plugin Created: 2017/Feb/12 1:11 AM Environment: Jenkins 2.19.4 and 2.32.4 and Mask Passwords 2.9 Priority: Minor Reporter: Mark Bidewell The MaskPasswordsBuildWrapper for Pipeline is no longer hiding passwords in Mask Passwords 2.9. Freestyle jobs appear to work. Version 2.8 works correctly. Add Comment
[JIRA] (JENKINS-41955) MaskPaswordsBuildWrapper no longer hiding Passwords
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-41955 MaskPaswordsBuildWrapper no longer hiding Passwords Change By: Mark Bidewell Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37687) Exception when attempting to save filter branches.
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-37687 Exception when attempting to save filter branches. Issue Type: Bug Assignee: Robin Müller Components: gitlab-plugin Created: 2016/Aug/25 3:09 PM Environment: Jenkins 1.651.3 gitlab-plugin 1.3.0 Priority: Minor Reporter: Mark Bidewell When I attempt to specify a branch name filter for the build trigger. I receive the following exception: javax.servlet.ServletException: com.google.common.util.concurrent.UncheckedExecutionException: javax.ws.rs.client.ResponseProcessingException: javax.ws.rs.ProcessingException: RESTEASY003145: Unable to find a MessageBodyReader of content-type text/html;charset=utf-8 and type interface java.util.List at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at
[JIRA] (JENKINS-36673) MissingMethodException When Calling Pipeline Library Function
Title: Message Title Mark Bidewell commented on JENKINS-36673 Re: MissingMethodException When Calling Pipeline Library Function Steps: 1) Create a file under vars which has a function other than "call" 2) Call that function from a workflow. If you use the attached "SingletonTest.groovy" and call SingletonTest.checkSingleton, you will get the error. SingletonTest.groovy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36673) MissingMethodException When Calling Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 MissingMethodException When Calling Pipeline Library Function Change By: Mark Bidewell Attachment: SingletonTest.groovy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38709) withMaven Disables Containing MaskPasswordsBuildWrapper
Title: Message Title
Mark Bidewell created an issue
Jenkins / JENKINS-38709
withMaven Disables Containing MaskPasswordsBuildWrapper
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2016/Oct/04 6:02 PM
Environment:
Jenkins 2.7.4
Priority:
Critical
Reporter:
Mark Bidewell
If a withMaven block is placed inside a MaskPasswordsBuildWrapper, passwords are displayed in clear text. i.e. node { wrap([$class: 'MaskPasswordsBuildWrapper']) { //Password masked here. withMaven(...) { //Password printed in Clear Text } } } Placing the wrapper inside the withMaven works correctly.
Add Comment
[JIRA] (JENKINS-36673) Cannot Call Pipeline Library Function
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-36673 Cannot Call Pipeline Library Function Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Jul/14 1:13 AM Environment: Jenkins 1.651.3 and 2.7.1 Priority: Minor Reporter: Mark Bidewell I updated to the latest Pipeline plugins. I had some library functions taking closures created using the directions here: https://github.com/jenkinsci/workflow-cps-global-lib-plugin/blob/master/README.md Prior to the update the scripts worked perfectly. after updating I get the error: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: static Maven.svnRelease() is applicable for argument types: (org.jenkinsci.plugins.workflow.cps.CpsClosure2) values: [org.jenkinsci.plugins.workflow.cps.CpsClosure2@3a07d220] Possible solutions: svnRelease(groovy.lang.Closure) at groovy.lang.MetaClassImpl.invokeStaticMissingMethod(MetaClassImpl.java:1367) at groovy.lang.MetaClassImpl.invokeStaticMethod(MetaClassImpl.java:1353) at org.codehaus.groovy.runtime.callsite.StaticMetaClassSite.call(StaticMetaClassSite.java:50) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:15) at WorkflowScript.run(WorkflowScript:1) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.N
[JIRA] (JENKINS-36673) Cannot Call Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 Cannot Call Pipeline Library Function Change By: Mark Bidewell Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36673) MissingMethodException When Calling Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 MissingMethodException When Calling Pipeline Library Function Change By: Mark Bidewell Summary: Cannot Call MissingMethodException When Calling Pipeline Library Function Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36673) MissingMethodException When Calling Pipeline Library Function
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-36673 MissingMethodException When Calling Pipeline Library Function Change By: Mark Bidewell Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34416) workflow-cps-global-lib: global variables are not global singletons
Title: Message Title Mark Bidewell commented on JENKINS-34416 Re: workflow-cps-global-lib: global variables are not global singletons I believe this issue may also be the root cause of JENKINS-36673 as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 2016/Aug/17 2:12 PM Environment: Jenkins 1.651.3 build-pipeline-plugin 1.5.3.1 Priority: Critical Reporter: Mark Bidewell I am trying to organize jobs in jenkins using the folders plugin. When trying to manually trigger a build in the pipeline between two jobs in the folder I receive an exception similar to the following: SEVERE: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deploy Aug 16, 2016 4:50:17 PM se.diabol.jenkins.pipeline.DeliveryPipelineView triggerManual WARNING: Could not trigger manual build ACE/service-ace-tracker-api-devacetrack01-deploy for upstream ACE/service-ace-tracker-api-ci id: 5. Did you mean to specify service-ace-tracker-api-devacetrack01-deploy? se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger at se.diabol.jenkins.pipeline.trigger.BPPManualTrigger.triggerManual(BPPManualTrigger.java:38) at se.diabol.jenkins.pipeline.DeliveryPipelineView.triggerManual(DeliveryPipelineView.java:419) at se.diabol.jenkins.pipeline.PipelineApi.doManualStep(PipelineApi.java:50) at sun.reflect.GeneratedMethodAccessor2261.invoke(Unknown Source) 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:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124) at
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell I am trying to organize jobs in jenkins using the folders plugin. When trying to manually trigger a build in the pipeline between two jobs in the folder I receive an exception similar to the following: Aug 16, 2016 4:52:51 PM au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView triggerBuild SEVERE: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deployAug 16, 2016 4: 50 52 : 17 51 PM se org . diabol kohsuke . jenkins stapler . pipeline.DeliveryPipelineView triggerManual HttpResponseRenderer$Default handleJavaScriptProxyMethodCall WARNING: Could not trigger manual build ACE call to / service-ace-tracker-api-devacetrack01-deploy for upstream ACE $stapler / service bound/6c2ef2bd - ace 4b56 - tracker 4307 - api 9b6b - ci id: 5 8407f34bfbf1/triggerManualBuild failedjava . Did you mean to specify lang.IllegalStateException: No upstream trigger found for this projectAccelerated Client Experience » service-ace-tracker-api-devacetrack01-deploy ? se.diabol.jenkins.pipeline.trigger.TriggerException: Could not trigger at se au . diabol com . jenkins centrumsystems . pipeline hudson . trigger plugin . BPPManualTrigger buildpipeline . triggerManual BuildPipelineView.triggerBuild ( BPPManualTrigger BuildPipelineView .java: 38 496 ) at se au . diabol com . jenkins centrumsystems . pipeline hudson . DeliveryPipelineView plugin . triggerManual buildpipeline.BuildPipelineView.triggerManualBuild ( DeliveryPipelineView BuildPipelineView .java: 419 405 ) at se sun . diabol reflect . jenkins NativeMethodAccessorImpl . pipeline.PipelineApi.doManualStep invoke0 ( PipelineApi.java:50 Native Method ) at sun.reflect. GeneratedMethodAccessor2261 NativeMethodAccessorImpl .invoke( Unknown Source 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:320) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:163) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$ 1 _javascript_ProxyMethodDispatcher .doDispatch(MetaClass.java: 124 474 ) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$ 3 11 . doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher. dispatch( NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler. MetaClass $5 . doDispatch(MetaClass. java: 233 380 ) at org.kohsuke.stapler. NameBasedDispatcher.dis
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell resolved as Not A Defect This issue is caused by not specifying the full project name (including folder path). Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com
[JIRA] (JENKINS-37471) Build Pipeline Plugin Maunal Trigger not working in Folders
Title: Message Title Mark Bidewell closed an issue as Not A Defect Jenkins / JENKINS-37471 Build Pipeline Plugin Maunal Trigger not working in Folders Change By: Mark Bidewell Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38132) Pipeline support
Title: Message Title Mark Bidewell commented on JENKINS-38132 Re: Pipeline support In a pipeline you can accomplish this by setting currentBuild.description in you groovy script. 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] [workflow-plugin] (JENKINS-34862) Input step Proceed/Abort like do not work
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-34862 Input step Proceed/Abort like do not work Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/May/16 8:01 PM Environment: Jenkins 1.651.1, Java 1.8 RHEL 6 Labels: workflow Priority: Minor Reporter: Mark Bidewell When an input step is given only a message, The step prints links for Proceed and Abort into the console log. These links, however, are not functional. Add C
[JIRA] [workflow-plugin] (JENKINS-34862) Input step Proceed/Abort like do not work
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-34862 Input step Proceed/Abort like do not work Change By: Mark Bidewell Attachment: screenshot-1.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] [workflow-plugin] (JENKINS-34862) Input step Proceed/Abort links do not work
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-34862 Input step Proceed/Abort links do not work Change By: Mark Bidewell Summary: Input step Proceed/Abort like links do not work 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-34862) Input step Proceed/Abort like do not work
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-34862 Input step Proceed/Abort like do not work Change By: Mark Bidewell When an input step is given only a message, The step prints links for Proceed and Abort into the console log. These links, however, are not functional. The "Input Requested" link works correctly. 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] (JENKINS-35989) Allow for Restartable Pipeline Step
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-35989 Allow for Restartable Pipeline Step Issue Type: Improvement Assignee: Antonio Muñiz Components: pipeline-milestone-step-plugin Created: 2016/Jun/16 1:02 AM Environment: Jenkins 1.651.2 Labels: pipeline Priority: Minor Reporter: Mark Bidewell Often in Pipeline examples I see something like: "Deploy" -> "Deploy Again" ->"Deploy Yet Again" Should pipeline milestones or stages have a way to mark them as restartable? Add Comment
[JIRA] [mask-passwords-plugin] (JENKINS-31033) Passwords from Workflow "input" step not masked
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-31033 Passwords from Workflow "input" step not masked Issue Type: Bug Assignee: Oleg Nenashev Components: mask-passwords-plugin Created: 19/Oct/15 4:28 PM Labels: workflow Priority: Minor Reporter: Mark Bidewell The Mask passwords build step will only mask password parameters known before the Workflow starts. Passwords obtained via the Workflow "input" step are not masked. Add Comment
[JIRA] [git-client-plugin] (JENKINS-20879) SSH Credentials (private key with passphrase) do not work
Title: Message Title Mark Bidewell commented on JENKINS-20879 Re: SSH Credentials (private key with passphrase) do not work If I have an SSH key with a passphrase, I get a request for the passphrase using the Git or SSH-Agent plugin on a slave. JGit works fine and the key works fine on the master. 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-27039) Option for input or stage step to cancel older executions
Title: Message Title Mark Bidewell commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions While we are thinking about this, would it make sense to allow for the final status of the canceled step to reflect the status of the last executed stage? For example, Assume I have a two stage workflow with stage 1 being CI and stage 2 being production build. There will be many stage 1 builds that do not make stage 2, but they could still be successful builds. 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-32163) Allow Jenkins to Archive Artifacts from a Stage
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-32163 Allow Jenkins to Archive Artifacts from a Stage Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 21/Dec/15 8:46 PM Priority: Minor Reporter: Mark Bidewell When using the current archive step, the files archived will be made available at the end of the complete job run. In many cases however it would also make sense to allow artifacts to be archived and made available per stage. For example after running a "CI" stage a workflow could archive a -SNAPSHOT version for testers to use before advancing to the "Test" stage of the same workflow. Add Comment
[JIRA] (JENKINS-60271) Allow selection of field(s) for Issue selector display
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-60271 Allow selection of field(s) for Issue selector display Issue Type: New Feature Assignee: Unassigned Components: jira-plugin Created: 2019-11-25 17:30 Priority: Minor Reporter: Mark Bidewell Sometimes it would be useful to use a different Jira issue field or fields and the title in the issue selector dropdown. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61948) SSH Remote not Populated on Manual Build
Title: Message Title Mark Bidewell created an issue Jenkins / JENKINS-61948 SSH Remote not Populated on Manual Build Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-17 13:45 Priority: Minor Reporter: Mark Bidewell When a build is triggered by a webhook, the git remote origin is set to the ssh url for the project. However on a manual build only the http link is included. This makes interacting with the git repo from a manual job difficult. Add Comment
[JIRA] (JENKINS-62057) Webhook triggering job with no SCM
Title: Message Title Mark Bidewell commented on JENKINS-62057 Re: Webhook triggering job with no SCM Getting something similar. It appears that webhook triggers to pipeline jobs are broken and do not work. Increasing priority as critical functionality is broken. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205955.1587878967000.23142.1588853100384%40Atlassian.JIRA.
[JIRA] (JENKINS-62057) Webhook triggering job with no SCM
Title: Message Title Mark Bidewell updated an issue Jenkins / JENKINS-62057 Webhook triggering job with no SCM Change By: Mark Bidewell Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205955.1587878967000.23145.1588853100498%40Atlassian.JIRA.
[JIRA] (JENKINS-62057) Webhook triggering job with no SCM
Title: Message Title Mark Bidewell commented on JENKINS-62057 Re: Webhook triggering job with no SCM It appears that webhooks only work with Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205955.1587878967000.23202.1588863240272%40Atlassian.JIRA.
