[JIRA] [build-blocker-plugin] (JENKINS-29924) Items with non-AbstractProjects tasks block the build queue
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-29924
Items with non-AbstractProjects tasks block the build queue
Change By:
Félix Belzunce Arcos
When an item which doesn't have an AbstractProject task stayed in stay on the queue blocking blocks the build queue. This happen happens specifically with CloudBees proprietary plugin long-running-builds. However, it is in my opinion a bug.It might be perfect not to use Abstractproject and better use Job instead so Workflow plugin is integrated. I might work on this, but for the moment my intention is just to fix this bug more than integrate with Workflow. {code:java}2015-08-08 13:50:48.211+0200 [id=62]SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@423e2af8 failedjava.lang.ClassCastException: com.cloudbees.jenkins.plugins.longrunning.BackgroundTask cannot be cast to hudson.model.AbstractProjectat hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199)at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:108)at hudson.model.Queue$JobOffer.canTake(Queue.java:281)at hudson.model.Queue.maintain(Queue.java:1049)at hudson.model.Queue$MaintainTask.doRun(Queue.java:2033)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745){code}
Add Comment
[JIRA] [build-blocker-plugin] (JENKINS-29924) Items with non-AbstractProjects tasks block the build queue
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-29924
Items with non-AbstractProjects tasks block the build queue
Change By:
Félix Belzunce Arcos
When an item which doesn't have an AbstractProject task is stayed in the queue block blocking the build queue. This happen specifically with CloudBees proprietary plugin long-running-builds. However, it is in my opinion a bug.It might be perfect not to use Abstractproject and better use Job instead so Workflow plugin is integrated. I might work on this, but for the moment my intention is just to fix this bug more than integrate with Workflow. {code:java}2015-08-08 13:50:48.211+0200 [id=62]SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@423e2af8 failedjava.lang.ClassCastException: com.cloudbees.jenkins.plugins.longrunning.BackgroundTask cannot be cast to hudson.model.AbstractProjectat hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199)at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.canTake(BuildBlockerQueueTaskDispatcher.java:108)at hudson.model.Queue$JobOffer.canTake(Queue.java:281)at hudson.model.Queue.maintain(Queue.java:1049)at hudson.model.Queue$MaintainTask.doRun(Queue.java:2033)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745){code}
Add Comment
T
[JIRA] [jdk_parameter_plugin] (JENKINS-29925) CLI parameter submission is not supported for the class com.datalex.jdkparameter.JavaParameterDefinition
Title: Message Title Olga Jdanov assigned an issue to Baris Batiege Jenkins / JENKINS-29925 CLI parameter submission is not supported for the class com.datalex.jdkparameter.JavaParameterDefinition Change By: Olga Jdanov Assignee: Baris Batiege 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] [jdk_parameter_plugin] (JENKINS-29925) CLI parameter submission is not supported for the class com.datalex.jdkparameter.JavaParameterDefinition
Title: Message Title Olga Jdanov created an issue Jenkins / JENKINS-29925 CLI parameter submission is not supported for the class com.datalex.jdkparameter.JavaParameterDefinition Issue Type: Bug Assignee: Unassigned Components: jdk_parameter_plugin Created: 13/Aug/15 6:31 AM Environment: Linux Ubuntu Priority: Blocker Reporter: Olga Jdanov When trying to run job in CLI and need to provide baseline name parameter, got the following error: CLI parameter submission is not supported for the class com.datalex.jdkparameter.JavaParameterDefinition type. Please file a bug report for this Command I use: java -jar jenkins-cli.jar -s http://vjl-01:8080/ build test -p JDK=JDK_1.7 Add Comment
[JIRA] [build-blocker-plugin] (JENKINS-29924) Items with non-AbstractProjects tasks block the build queue
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-29924 Items with non-AbstractProjects tasks block the build queue Issue Type: Bug Assignee: Félix Belzunce Arcos Components: build-blocker-plugin Created: 13/Aug/15 6:28 AM Environment: build-blocker-plugin-1.7.1 Priority: Major Reporter: Félix Belzunce Arcos When an item which doesn't have an AbstractProject task is in the queue block the build queue. This happen specifically with CloudBees proprietary plugin long-running-builds. However, it is in my opinion a bug. It might be perfect not to use Abstractproject and better use Job instead so Workflow plugin is integrated. I might work on this, but for the moment my intention is just to fix this bug more than integrate with Workflow. 2015-08-08 13:50:48.211+0200 [id=62]SEVERE hudson.triggers.SafeTimerTask#run: Timer task hudson.model.Queue$MaintainTask@423e2af8 failed java.lang.ClassCastException: com.cloudbees.jenkins.plugins.longrunning.BackgroundTask cannot be cast to hudson.model.AbstractProject at hudson.plugins.buildblocker.BuildBlockerQueueTaskDispatcher.getBuildBlockerProperty(BuildBlockerQueueTaskDispatcher.java:199) at hudson.plugins.buildblock
[JIRA] [svn-tag-plugin] (JENKINS-2924) Svn Tagging As a Promoted Build Action
Title: Message Title Peter Ettinger commented on JENKINS-2924 Re: Svn Tagging As a Promoted Build Action mhmm. currently i'm running version 1.5.90. but the drop-down box "add action" does not show an option to svn tag that build 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] [thinBackup] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title Swapnil Kotwal edited a comment on JENKINS-12096 Re: ThinBackup Worker Thread thread is still running. Execution aborted. I have restarted Jenkins but still "Creating backup..." thread not yet stooped stopped . :(!Capture.PNG|thumbnail! 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] [thinBackup] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title Swapnil Kotwal commented on JENKINS-12096 Re: ThinBackup Worker Thread thread is still running. Execution aborted. I have restarted Jenkins but still "Creating backup..." thread not yet stooped. 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] [thinBackup] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title Swapnil Kotwal updated an issue Jenkins / JENKINS-12096 ThinBackup Worker Thread thread is still running. Execution aborted. Change By: Swapnil Kotwal Attachment: Capture.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] [tfs-plugin] (JENKINS-29006) Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}
Title: Message Title
Olga Jdanov updated an issue
Jenkins / JENKINS-29006
Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}
Change By:
Olga Jdanov
Summary:
TFS Team Foundation Server Plugin "Local workfolder" variable setting can't use job variables like ${VAR}
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] [rhnpush-plugin] (JENKINS-23738) Error when expanding parameters
Title: Message Title Nils-Helge Hegvik commented on JENKINS-23738 Re: Error when expanding parameters This would certainly be a very useful feature. Any progress on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
Title: Message Title Dominik Bartholdi commented on JENKINS-18629 Re: Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single). Donald Eytel this plugin does not support Hudson Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-timeout-plugin] (JENKINS-26778) Build-timeout+Plugin global timeout setting
Title: Message Title ikedam commented on JENKINS-26778 Re: Build-timeout+Plugin global timeout setting I don't know about changing configurations automatically. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on "console" icon doesn't work
Title: Message Title Vikas Kumar updated JENKINS-25430 Jenkins / JENKINS-25430 Clicking on "console" icon doesn't work Change By: Vikas Kumar Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on "console" icon doesn't work
Title: Message Title Vikas Kumar commented on JENKINS-25430 Re: Clicking on "console" icon doesn't work The solution by Nicolas did not worked for me on Jenkins v1.621-1.1 and Build Pipeline v1.4.7. The console icon is clickable now, but does not show any output. I even tried to copy+paste the two files in vain. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29345) Unable to login after modifying permissions
Title: Message Title Bryan Alexander commented on JENKINS-29345 Re: Unable to login after modifying permissions Update: I forgot to select the 'Security Realm' upon first security configuration. That appears to be what threw it into a funk. After reinstalling Jenkins and setting it up correctly, it appears to be good. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29345) Unable to login after modifying permissions
Title: Message Title Bryan Alexander updated an issue Jenkins / JENKINS-29345 Unable to login after modifying permissions Hit this bug today as well. Jenkins ver. 1.624 Running on Ubuntu 14.04 Fresh install, had just configured nginx reverse proxy with ssl on the subdomain I wanted to run jenkins on. From the first time I hit the 'Manage Jenkins' screen I only had time to do a few things. First I installed some of the additional packages I wanted to use: Git xcode testflight android - gradle android - emulator Then, went to secure Jenkins with Matrix-based security and checked the Anonymous Read right under the View group per the Digital Ocean tutorial I was following. Then, upon clicking 'Save' Got the attached screen and following Stack Trace. Will likely reinstall Jenkins or uninstall packages to try workaround. Stack Trace: hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission at hudson.security.ACL.checkPermission(ACL.java:63) at hudson.model.Node.checkPermission(Node.java:441) at jenkins.model.Jenkins.getTarget(Jenkins.java:3825) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:674) 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 org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHan
[JIRA] [workflow-plugin] (JENKINS-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title
Flávio Augusto Valones edited a comment on JENKINS-28510
Re: DescribableHelper error with @DataBoundSetter on Map
Thanks for the reply, I use the {{Map}} only as a workflow-step param, the conventional UI {{Builder}} uses only supported databinds compatible with {{/lib/form}} controls. Here's the code:{code:java}public class SCTMStep extends AbstractStepImpl {private final int projectId; private final List execDefIds;@DataBoundSetter public Map params; @DataBoundSetter public String buildNumber; @DataBoundSetter public int delay; @DataBoundSetter public boolean continueOnError; @DataBoundSetter public boolean collectResults = true; @DataBoundSetter public boolean ignoreSetupCleanup; @DataBoundConstructor public SCTMStep(final int projectId, final List execDefIds) {this.projectId = projectId;this.execDefIds = execDefIds; }//getters for private fields@Extension(optional = true) public static final class DescriptorImpl extends AbstractStepDescriptorImpl {public DescriptorImpl() { super(Execution.class); }@Override public String getFunctionName() { return "sctm"; }@Override public String getDisplayName() { return Messages.getString("SCTMExecutorDescriptor.plugin.title"); } }public static final class Execution extends AbstractSynchronousStepExecution {private static final long serialVersionUID = 1L;@Inject private transient SCTMStep step;@StepContextParameter private transient TaskListener listener;@StepContextParameter private transient FilePath workspace;@StepContextParameter private transient Run run;@Overrideprotected Boolean run() throws Exception { SCTMExe sctmExe = new SCTMExe(workspace, listener); sctmExe.execute(step.projectId, step.execDefIds, step.params, step.buildNumber, step.delay, step.collectResults, step.ignoreSetupCleanup, step.continueOnError, false);if (step.collectResults) {sctmExe.publish(run); } return true;} } }{code}The databind of the {{Map}} is done correctly and in the workflow Job this works like a charm:{code:java}...sctm projectId: 123, execDefIds: [456, 789], params: [NAME: 'Flávio Augusto Valones', ADDR: 'Some Street']...{code}The {{sctm}} step is listed in the Snippet Generator (I have not yet implemented the jelly form for it), and everything goes as expected. The exception only occurs if I do this in the {{SCTMStep}}:{code:java}...private Map params;@DataBoundSetter public void setParams( Map getParams( params ) { ... }...{code}
Add Comment
This message was sent by Atlassian JIRA
[JIRA] [workflow-plugin] (JENKINS-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title Flávio Augusto Valones commented on JENKINS-28510 Re: DescribableHelper error with @DataBoundSetter on Map Oops, my fault, the error occurs in the setter, I erroneously transcribed manually on getter, fixed previous comment. Thanks for the tips, I'll think of a way to refactor the parameters to make them practical as the Map, but data-bound supported. 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-tag-cloud] (JENKINS-29923) Internal error in Jenkins log
Title: Message Title J John assigned an issue to Unassigned Jenkins / JENKINS-29923 Internal error in Jenkins log Change By: J John Component/s: jenkins-tag-cloud Component/s: m2release-plugin Environment: Linux hudson-ci 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/LinuxApache Tomcat/6.0.24 Windows java version " Jenkins 1. 6.0_21"Java(TM) SE Runtime Environment (build 1.6.0_21-b06)Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode)Hudson ver. 1.376Hudson Maven Release Plug-in Plug-in v0.6.0 623 Assignee: James Nord 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 r
[JIRA] [m2release-plugin] (JENKINS-29923) Internal error in Jenkins log
Title: Message Title J John created an issue Jenkins / JENKINS-29923 Internal error in Jenkins log Issue Type: Bug Affects Versions: current Assignee: James Nord Components: m2release-plugin Created: 13/Aug/15 2:06 AM Environment: Linux hudson-ci 2.6.27.19-5-default #1 SMP 2009-02-28 04:40:21 +0100 x86_64 x86_64 x86_64 GNU/Linux Apache Tomcat/6.0.24 java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b06) Java HotSpot(TM) 64-Bit Server VM (build 17.0-b16, mixed mode) Hudson ver. 1.376 Hudson Maven Release Plug-in Plug-in v0.6.0 Priority: Major Reporter: J John Settings of perform release: Maven will decide the version Specify SCM login/password
[JIRA] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Title: Message Title Kanstantsin Shautsou commented on JENKINS-23301 Re: Support unix protocol for connection Ok, will keep open until verify myself (hope to get some time someday). 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation
Title: Message Title Jesse DeRose commented on JENKINS-29921 Re: "Failed to get git executable" During Git Installation JGit did not work either. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-commons-plugin] (JENKINS-28702) Clean up registry credentials
Title: Message Title Nicolas De Loof commented on JENKINS-28702 Re: Clean up registry credentials Docker 1.8 do support DOCKER_CONFIG that plugin should use so it can have distinct config dir per build, and fully delete it after build completion. Main issue I can see is KeyMaterialFactory usage. API is designed to 1.create 2.contextualize 3.materialize, which would be OK. But usage actually do run 1+2 together (1), which prevent combining KeyMaterialFactory using KeyMaterialFactory.plus() with a shared context. Changing this would require some incompatible API changes afaik. (1) https://github.com/jenkinsci/docker-commons-plugin/blob/master/src/main/java/org/jenkinsci/plugins/docker/commons/credentials/DockerServerEndpoint.java#L142 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29922) Promote delegates of metasteps to top-level functions
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-29922 Promote delegates of metasteps to top-level functions Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 12/Aug/15 10:38 PM Labels: usability api Priority: Major Reporter: Jesse Glick Currently you must write e.g. step([$class: 'JUnitResultArchiver', testResults: 'target/surefire-reports/*.xml']) which is awkward. Also in Snippet Generator you need to look under General Build Step for what to a user is logically a distinct step. Metasteps (step, wrap, checkout) should have an API by which they can declare that their delegate (scm in the last case) ought to be treated as a top-level step as far as DSL and Snippetizer are concerned, via some kind of syntactic sugar. In the absence of any Jenkins core API which would allow a Descriptor to specify a short name (yaml-project tries to define one of its own), this would have to be constructed somehow from the $class, perhaps simply:
[JIRA] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Title: Message Title Jesse Glick commented on JENKINS-23301 Re: Support unix protocol for connection Sorry, no time. If you think it works, close as fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title Jesse Glick commented on JENKINS-28510 Re: DescribableHelper error with @DataBoundSetter on Map Well @DataBoundSetter is supposed to be on the setter, not the getter of course. Creating Step implementations with parameter types that cannot be data-bound is possible, but not easy and not recommended if you can possibly avoid it. StepDescriptor.newInstance (and potentially .defineArguments) overrides are needed to bypass DescribableHelper, and config.jelly would need to omit that parameter while documenting its syntax in help.html. BuildTriggerStep is the only example I can think of. 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] [subversion-plugin] (JENKINS-29492) Fix several findbugs issues
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29492 Re: Fix several findbugs issues Code changed in jenkins User: Steven Christou Path: src/main/java/hudson/scm/RevisionParameterAction.java src/main/java/hudson/scm/SubversionChangeLogBuilder.java http://jenkins-ci.org/commit/subversion-plugin/0c52b546082dafbced41feaf7f74ad3158b96efb Log: Merge pull request #123 from christ66/findbugs-1 JENKINS-29492 Fix some findbugs issues Compare: https://github.com/jenkinsci/subversion-plugin/compare/8e1e0aeefb97...0c52b546082d 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation
Title: Message Title Mark Waite commented on JENKINS-29921 Re: "Failed to get git executable" During Git Installation In the master Jenkins configuration screen there is a section for Git. In that section, I believe there is a pull down menu that will allow you to add another implementation. JGit is one of the choices from that menu. Once you've added JGit globally, it becomes available on all your slaves. 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-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title
Flávio Augusto Valones commented on JENKINS-28510
Re: DescribableHelper error with @DataBoundSetter on Map
Thanks for the reply, I use the Map only as a workflow-step param, the conventional UI Builder uses only supported databinds compatible with /lib/form controls. Here's the code:
public class SCTMStep extends AbstractStepImpl {
private final int projectId;
private final List execDefIds;
@DataBoundSetter public Map params;
@DataBoundSetter public String buildNumber;
@DataBoundSetter public int delay;
@DataBoundSetter public boolean continueOnError;
@DataBoundSetter public boolean collectResults = true;
@DataBoundSetter public boolean ignoreSetupCleanup;
@DataBoundConstructor
public SCTMStep(final int projectId, final List execDefIds) {
this.projectId = projectId;
this.execDefIds = execDefIds;
}
//getters for private fields
@Extension(optional = true)
public static final class DescriptorImpl extends AbstractStepDescriptorImpl {
public DescriptorImpl() { super(Execution.class); }
@Override public String getFunctionName() { return "sctm"; }
@Override public String getDisplayName() { return Messages.getString("SCTMExecutorDescriptor.plugin.title"); }
}
public static final class Execution extends AbstractSynchronousStepExecution {
private static final long serialVersionUID = 1L;
@Inject private transient SCTMStep step;
@StepContextParameter private transient TaskListener listener;
@StepContextParameter private transient FilePath workspace;
@StepContextParameter private transient Run run;
@Override
protected Boolean run() throws Exception {
SCTMExe sctmExe = new SCTMExe(workspace, listener);
sctmExe.execute(step.projectId, step.execDefIds, step.params, step.buildNumber,
step.delay, step.collectResults, step.ignoreSetupCleanup, step.continueOnError, false);
if (step.collectResults) {
sctmExe.publish(run);
}
return true;
}
}
}
The databind of the Map is done correctly and in the workflow Job this works like a charm:
...
sctm projectId: 123, execDefIds: [456, 789], params: [NAME: 'Flávio Augusto Valones', ADDR: 'Some Street']
...
The sctm step is listed in the Snippet Generator (I have not yet implemented the jelly form for it), and everything goes as expected.
The exception only occurs if I do this in the SCTMStep:
...
private Map params;
@DataBoundSetter public Map getParams() { ... }
...
[JIRA] [job-dsl-plugin] (JENKINS-29662) Job DSL downstreamParameterized blockingThresholds 'never' option not available
Title: Message Title Daniel Spilker commented on JENKINS-29662 Re: Job DSL downstreamParameterized blockingThresholds 'never' option not available Will be fixed as part of https://github.com/jenkinsci/job-dsl-plugin/pull/572 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation
Title: Message Title Jesse DeRose commented on JENKINS-29921 Re: "Failed to get git executable" During Git Installation Git has not been configured elsewhere in the global configuration. I looked for a JGit plugin but did not find it - is this something that comes pre-installed with Jenkins core? 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 Jesse Glick started work on JENKINS-27039 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation
Title: Message Title Mark Waite commented on JENKINS-29921 Re: "Failed to get git executable" During Git Installation You might consider enabling JGit on your master server, then you could use the JGit (pure Java) implementation rather than depending on command line git. Any chance you've defined the location of your git executable as something other than "git" in the global configuration? Particularly, have you defined it as a Windows specific path? I think this is a configuration issue, not a plugin bug. 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-29676) Workflow: executing bat through Groovy can loop infinitely.
Title: Message Title Martin Bédard commented on JENKINS-29676 Re: Workflow: executing bat through Groovy can loop infinitely. You're right, it does work with 1.9. I don't know what I did wrong last time. Thanks a lot for all your help and patience. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-29840) when workflow uses multiple git repos the "git build data" and "tags" become next to useless.
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-29840 when workflow uses multiple git repos the "git build data" and "tags" become next to useless. Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-29908) Male OWASP Dependency-Check Plug-in compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29908 Re: Male OWASP Dependency-Check Plug-in compatible with Workflow Steve Springett, I'm using the master branch without modifications from my side. I was running mvn hpi:run and I found this problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title Jesse Glick assigned an issue to Antonio Muñiz Jenkins / JENKINS-25977 Make publishers of analysis-core a SimpleBuildStep Change By: Jesse Glick Assignee: Jesse Glick Antonio Muñiz 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] [analysis-core-plugin] (JENKINS-25977) Make publishers of analysis-core a SimpleBuildStep
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-25977 Make publishers of analysis-core a SimpleBuildStep Change By: Jesse Glick Assignee: Antonio Muñiz Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-29920) E-mail Notification Settings: Could not connect to SMTP host
Title: Message Title Alex Earl commented on JENKINS-29920 Re: E-mail Notification Settings: Could not connect to SMTP host Sounds like your system can't connect, this is not an issue with email-ext. 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation
Title: Message Title Jesse DeRose created an issue Jenkins / JENKINS-29921 "Failed to get git executable" During Git Installation Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin, git-client-plugin Created: 12/Aug/15 8:42 PM Environment: Jenkins v1.620, Git client plugin v1.18.0 Priority: Minor Reporter: Jesse DeRose Setup: I use the ec2 plugin to spin up slave instances (running Amazon Linux) then install Git via the Git plugin (using the command "sudo yum -y install git"). Problem: When Jenkins attempts to install Git on the EC2 slave via the Git plugin, it returns the error "Failed to get git executable". I cannot find anyone else with this error online or in these tickets. I triple-checked the executable path (/usr/bin/git) and tool home (/usr/bin). I can successfully run the command manually on the slave (via the CLI) and I can successfully run the command via the "Init script" portion of the ec2 plugin.
[JIRA] [mercurial-plugin] (JENKINS-29311) Deprecated call to Run.getEnvironment
Title: Message Title Jesse Glick started work on JENKINS-29311 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Jesse Glick commented on JENKINS-26100 Re: SCM steps should return revision state Robert Jay if you use a multibranch flow ( JENKINS-26129 ) you get this out of the box, assuming the logic is all in one job. 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] [kubernetes-plugin] (JENKINS-29342) to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29342 to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC Change By: Jesse Glick Labels: docker kubernetes 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] [kubernetes-plugin] (JENKINS-29342) to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29342 to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC Change By: Jesse Glick Component/s: kubernetes-plugin Component/s: docker-workflow-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [kubernetes-plugin] (JENKINS-29342) to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29342 to use docker workflow nicely on kubernetes we should turn a docker workflow into a Pod/RC Change By: Jesse Glick Labels: docker workflow 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] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title Jesse Glick commented on JENKINS-29425 Re: Multiple SCM + Mercurial + Git (Multiple checkouts are supported from a Workflow build. Freestyle projects were never designed to support this, hence the hacks in Multiple SCMs.) 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] [mercurial-plugin] (JENKINS-29425) Multiple SCM + Mercurial + Git
Title: Message Title Jesse Glick commented on JENKINS-29425 Re: Multiple SCM + Mercurial + Git Sounds similar to JENKINS-27638 , supposedly fixed in 0.5. In general, the Mercurial plugin does not claim to support Multiple SCMs and does not test with it. Your mileage may vary. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-29860) SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider
Title: Message Title Jesse Glick assigned an issue to Unassigned Not sure why this was assigned to me. Jenkins / JENKINS-29860 SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider Change By: Jesse Glick Component/s: core Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-29617) Activating Project-based Matrix Authorization Strategy without configuring it avoids Jenkins to restart
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-29617 Activating Project-based Matrix Authorization Strategy without configuring it avoids Jenkins to restart Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29611) Snippetizer does not call overriden newInstance
Title: Message Title Jesse Glick commented on JENKINS-29611 Re: Snippetizer does not call overriden newInstance Not that I know of. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-workflow-plugin] (JENKINS-29046) NPE when using withDockerRegistry
Title: Message Title Jesse Glick commented on JENKINS-29046 Re: NPE when using withDockerRegistry docker.withRegistry is not “advanced”, it is an advertised feature under the docker global variable, the entry point for all functionality in this plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-29920) E-mail Notification Settings: Could not connect to SMTP host
Title: Message Title
JDA JDA updated an issue
Jenkins / JENKINS-29920
E-mail Notification Settings: Could not connect to SMTP host
Change By:
JDA JDA
I am unable to connect to a SMTP host using the E-mail Notification abilities in Jenkins. I believe I have everything set up correctly. This is my configuration:SMTP Server: smtp.gmail.comDefault user e-mail suffix: @gmail.comUse SMTP Authentication: checkedUser Name: myusern...@gmail.comPassword: myGmailPasswordUse SSL: checkedSMTP Port: 465Reply-To Address: nore...@gmail.comCharset: UTF-8This is the error I am running into: {{ Failed to send out e-mailjavax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465; nested exception is: java.net.ConnectException: Connection timed out: connect at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:317) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:522) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compressio
[JIRA] [email-ext-plugin] (JENKINS-29920) E-mail Notification Settings: Could not connect to SMTP host
Title: Message Title
JDA JDA created an issue
Jenkins / JENKINS-29920
E-mail Notification Settings: Could not connect to SMTP host
Issue Type:
Bug
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
12/Aug/15 8:09 PM
Environment:
Jenkins Version: 1.547 Email Extension Plugin Version: 2.39.2 Jenkins Mailer Plugin Version: 1.11
Priority:
Major
Reporter:
JDA JDA
I am unable to connect to a SMTP host using the E-mail Notification abilities in Jenkins. I believe I have everything set up correctly. This is my configuration:
SMTP Server: smtp.gmail.com Default user e-mail suffix: @gmail.com Use SMTP Authentication: checked User Name: myusern...@gmail.com Password: myGmailPassword Use SSL: checked SMTP Port: 465 Reply-To Address: nore...@gmail.com Charset: UTF-8
This is the error I am running into:
{{Failed to send out e-mail javax.mail.MessagingException: Could not connect to SMTP host: smtp.gmail.com, port: 465; nested exception is: java.net.ConnectException: Connection timed out: connect
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638)
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title Jesse Glick commented on JENKINS-29548 Re: don't group both advanced and deprecated together - its not possible to know which is which. Well either or both could apply to the steps in this section. You need to read the description of the step to judge for yourself. 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] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
Title: Message Title Boaz Brudner updated an issue Jenkins / JENKINS-27456 Emulator can't connect to adb server!? Change By: Boaz Brudner Priority: Minor Critical 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] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?
Title: Message Title Boaz Brudner commented on JENKINS-27456 Re: Emulator can't connect to adb server!? Is there a resolution for this issue? This is now is significantly impacting us. 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-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title Jesse Glick commented on JENKINS-28510 Re: DescribableHelper error with @DataBoundSetter on Map (You could override StepDescriptor.newInstance and manually parse out content coming in from a Groovy script, but Snippet Generator will not work, so this is not a good idea.) 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-28510) DescribableHelper error with @DataBoundSetter on Map
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-28510 DescribableHelper error with @DataBoundSetter on Map A bug in DescribableHelper that it throws this low-level exception, but I doubt it could work in any case. Jenkins has no databinding support for Map. You must choose a type for which an actual /lib/form control exists. Change By: Jesse Glick Summary: Reflection Error Defining Step Param DescribableHelper error with @DataBoundSetter on Map 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-28510) Reflection Error Defining Step Param
Title: Message Title Jesse Glick reopened an issue Jenkins / JENKINS-28510 Reflection Error Defining Step Param Change By: Jesse Glick Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29676) Workflow: executing bat through Groovy can loop infinitely.
Title: Message Title
Jesse Glick commented on JENKINS-29676
Re: Workflow: executing bat through Groovy can loop infinitely.
1.9 includes all the changes in 1.9-beta-1 and then some.
This is working for me in Workflow 1.9 on Jenkins 1.609.1:
Started by user anonymous
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 2: expecting ''', found '' @ line 2, column 22.
{ bat ''echo ON ''' }
^
1 error
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:302)
at org.codehaus.groovy.control.ErrorCollector.addFatalError(ErrorCollector.java:149)
at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:119)
at org.codehaus.groovy.control.ErrorCollector.addError(ErrorCollector.java:131)
at org.codehaus.groovy.control.SourceUnit.addError(SourceUnit.java:359)
at org.codehaus.groovy.antlr.AntlrParserPlugin.transformCSTIntoAST(AntlrParserPlugin.java:137)
at org.codehaus.groovy.antlr.AntlrParserPlugin.parseCST(AntlrParserPlugin.java:108)
at org.codehaus.groovy.control.SourceUnit.parse(SourceUnit.java:236)
at org.codehaus.groovy.control.CompilationUnit$1.call(CompilationUnit.java:161)
at org.codehaus.groovy.control.CompilationUnit.applyToSourceUnits(CompilationUnit.java:846)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:550)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:526)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:503)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:302)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:281)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:731)
at groovy.lang.GroovyShell.parse(GroovyShell.java:743)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:100)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:361)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:328)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:188)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:374)
Finished: FAILURE
Add Comment
[JIRA] [conditional-buildstep-plugin] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
Title: Message Title Alex Earl commented on JENKINS-18629 Re: Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single). You'll want to contact the Hudson developers. This is specific to Jenkins. Hudson and Jenkins have diverged a great deal since the split. 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] [dependency-check-jenkins-plugin] (JENKINS-29908) Male OWASP Dependency-Check Plug-in compatible with Workflow
Title: Message Title Steve Springett commented on JENKINS-29908 Re: Male OWASP Dependency-Check Plug-in compatible with Workflow I guess I'm failing to understand how the plugin is being executed. If you're using workflow, wouldn't it just be easier to update with the command line? It's a one liner. 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-29676) Workflow: executing bat through Groovy can loop infinitely.
Title: Message Title Martin Bédard commented on JENKINS-29676 Re: Workflow: executing bat through Groovy can loop infinitely. Works in beta 1.9-beta-1 (Thanks for the experimental update center information, proven really useful). However doesn't work in the latest 1.9 compiled few days ago, long after 1.9-beta-1 Should I reopen the report since it was not implemented in latest release or leave it like that? Either way thanks for everything!! 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] [conditional-buildstep-plugin] (JENKINS-18629) Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single).
Title: Message Title Donald Eytel commented on JENKINS-18629 Re: Jenkins fails to save configuration when using Invoke Gradle script in Conditional Step (single). It appears that this might still be an issue. I have installed Gradle Plugin 1.24 and I am getting this error in Hudson Build 3.3.0. Any suggestion. I see this is for Jenkin's but Hudson link takes me here. Don. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [bitbucket-pullrequest-builder-plugin] (JENKINS-29919) Pull Requests with double quotes cause build failures
Title: Message Title
David Stockton created an issue
Jenkins / JENKINS-29919
Pull Requests with double quotes cause build failures
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-pullrequest-builder-plugin
Created:
12/Aug/15 5:59 PM
Labels:
security plugin
Priority:
Major
Reporter:
David Stockton
Pull requests with double quotes in the title of the PR are not properly escaped when used in invoking shell commands. The description is sent as part of the commands to the shell which causes the command to fail. This may be a possible command injection vulnerability for projects that are using this plugin and allow public pull requests.
A chunk of the relevant log file:
[workspace] $ hg --config log --template "{desc|xmlescape}{file_adds|stringify|xmlescape}{file_dels|stringify|xmlescape}{files|stringify|xmlescape}{parents}\n" --rev BAL-3134:0 --follow --prune ae1822f7c61eab5bb14ef7cfb725d134ac4c893f --encoding UTF-8 --encodingmode replace
[workspace] $ /var/lib/jenkins/tools/hudson.tasks.Ant_AntInstallation/redant/bin/ant -DsourceBranch=BAL-3134 -DdestinationRepositoryName=*** -DpullRequestId=1369 -DdestinationRepositoryOwner=*** -Dre
[JIRA] [workflow-plugin] (JENKINS-28510) Reflection Error Defining Step Param
Title: Message Title
Flávio Augusto Valones edited a comment on JENKINS-28510
Re: Reflection Error Defining Step Param
Hi Jesse, wildcards are not used in this case, it is a {{Map}}.In the implementation of the {{AbstractStepImpl}}, if the map param is annotated in the field it works correctly, but if it is annotated in setter the error occurs.There are other parameters of type types {{String}}, {{int}} and {{boolean}}, but these work normally whether annotated in the field or setter.
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-28510) Reflection Error Defining Step Param
Title: Message Title Flávio Augusto Valones commented on JENKINS-28510 Re: Reflection Error Defining Step Param Hi Jesse, wildcards are not used in this case, it is a Map. In the implementation of the AbstractStepImpl, if the map param is annotated in the field it works correctly, but if it is annotated in setter the error occurs. There are other parameters of type String, int and boolean, but these work normally whether annotated in the field or setter. 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-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord edited a comment on JENKINS-29548 Re: don't group both advanced and deprecated together - its not possible to know which is which. if there is no distinction then this section title is completely wrong.Deprecated means shouldn't use an and may be removed in a future version. Advanced means - normal users may not need this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29548) don't group both advanced and deprecated together - its not possible to know which is which.
Title: Message Title James Nord reopened an issue if there is no distinction then this section title is completely wrong. Deprecated means shouldn't use an may be removed in a future version. Advanced means - normal users may not need this. Jenkins / JENKINS-29548 don't group both advanced and deprecated together - its not possible to know which is which. Change By: James Nord Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ivytrigger-plugin] (JENKINS-24950) IvyTrigger not triggering when new snapshot is posted in same version
Title: Message Title Andrew January commented on JENKINS-24950 Re: IvyTrigger not triggering when new snapshot is posted in same version Looking through the code, it seems like checking artifact changes relies on the repository being local so it can look at the file's last modified date. I think it should fallback to artifact.getPublicationDate(), which should be available even when not downloading the artefacts. 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] [subversion-plugin] (JENKINS-29897) Failed to record SCM polling Error
Title: Message Title k2nakamura commented on JENKINS-29897 Re: Failed to record SCM polling Error I hope you can guess the correct plugin version from the History section in the page. Please identify the release date of the Jenkins version you're using, and pick up the plugin version before or after. https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Tagging+Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svn-tag-plugin] (JENKINS-2924) Svn Tagging As a Promoted Build Action
Title: Message Title k2nakamura commented on JENKINS-2924 Re: Svn Tagging As a Promoted Build Action https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Installingthenewestversion 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] [svn-tag-plugin] (JENKINS-2924) Svn Tagging As a Promoted Build Action
Title: Message Title k2nakamura commented on JENKINS-2924 Re: Svn Tagging As a Promoted Build Action The patch was incorporated in ver.1.10. Please follow the instruction and you should get the feature. Please contact the contributor if you have questions on the feature. 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] [dependency-check-jenkins-plugin] (JENKINS-29908) Male OWASP Dependency-Check Plug-in compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29908 Re: Male OWASP Dependency-Check Plug-in compatible with Workflow Steve Springett, I hope to send a PR soon. Now, I'm trying to resolve some problems. One of them is: I find this using the master branch: INFO: Loaded all jobs Aug 12, 2015 6:53:51 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.DependencyCheck.DependencyCheckUpdateOnlyBuilder$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Tried proxying org.jenkinsci.plugins.DependencyCheck.DependencyCheckUpdateOnlyBuilder$DescriptorImpl to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382) at hudson.ExtensionFinder._find(ExtensionFinder.java:151) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:316) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptor(Jenkins.java:1163) at org.jenkinsci.plugins.DependencyCheck.DependencyCheckUpdateOnlyBuilder$DescriptorImpl.(DependencyCheckUpdateOnlyBuilder.java:139) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinde
[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College updated an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Change By:
Tim College
I have jobs that monitor the status of external projects. These look for the latest version, and compare it to a known version. The known version is tracked in a file in the workspace.Unfortunately, sometime between July 11 (the last successful build) and August 9 (when I *noticed* it didn't work) the $WORKSPACE variable has stopped being available in the environment when the ScriptTrigger script is run. This ends up meaning my jobs are now looking in the wrong place. Since looking in the wrong place wound up exiting non-zero, the result was "don't run", which meant I didn't notice something was wrong until the team noticed that an external project had been updated and our Jenkins jobs didn't trigger.I'm able to use a combination of {{' ${JENKINS_HOME}/workspace/${JOB_NAME} '}} to re-create the path, but that's a lot less clear, contains a hard-coded value, and I'd rather not have to update dozens of jobs manually.If this was changed on purpose, can you explain why, or link to documentation that explains it? I wasn't able to determine.
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] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College updated an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Change By:
Tim College
I have jobs that monitor the status of external projects. These look for the latest version, and compare it to a known version. The known version is tracked in a file in the workspace.Unfortunately, sometime between July 11 (the last successful build) and August 9 (when I *noticed* it didn't work) the $WORKSPACE variable has stopped being available in the environment when the ScriptTrigger script is run. This ends up meaning my jobs are now looking in the wrong place. Since looking in the wrong place wound up exiting non-zero, the result was "don't run", which meant I didn't notice something was wrong until the team noticed that an external project had been updated and our Jenkins jobs didn't trigger.I'm able to use a combination of {{'$ { JENKINS_HOME } /workspace/$ { JOB_NAME } '}}to re-create the path, but that's a lot less clear, contains a hard-coded value, and I'd rather not have to update dozens of jobs manually.If this was changed on purpose, can you explain why, or link to documentation that explains it? I wasn't able to determine.
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] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script
Title: Message Title
Tim College created an issue
Jenkins / JENKINS-29918
$WORKSPACE has stopped working in ScriptTrigger shell script
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
scripttrigger-plugin
Created:
12/Aug/15 4:20 PM
Environment:
Jenkins 1.624
Priority:
Major
Reporter:
Tim College
I have jobs that monitor the status of external projects. These look for the latest version, and compare it to a known version. The known version is tracked in a file in the workspace.
Unfortunately, sometime between July 11 (the last successful build) and August 9 (when I noticed it didn't work) the $WORKSPACE variable has stopped being available in the environment when the ScriptTrigger script is run. This ends up meaning my jobs are now looking in the wrong place. Since looking in the wrong place wound up exiting non-zero, the result was "don't run", which meant I didn't notice something was wrong until the team noticed that an external project had been updated and our Jenkins jobs didn't trigger.
I'm able to use a combination of $ {JENKINS_HOME}
/workspace/$ {JOB_NAME}
to re-create the path, but that's a lot less clear, contains a hard-coded value, and I'd rather not have to update dozens of jobs manuall
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Gilad Baruchian commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master Update : it works if I delete and create the slaves again but that is a real pain. currently i just add an inject variable stage and i add path=;%path% Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Oded Arbel commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master I have the same problem with EC2 on demand Windows slaves. The slaves are installed and launched through WinRM ( I believe as a standard Java process). 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] [subversion-plugin] (JENKINS-29897) Failed to record SCM polling Error
Title: Message Title Srinivas Jajou closed an issue as Fixed I had to disable Subversion tagging plugin in order to get away from the error. Will figure out later when the plug in is needed. Anyway we are on a very older version Jenkins and might need to upgrade the core to be able to compatible with latest plugins. Thanks for the quick response and I really appreciate. Jenkins / JENKINS-29897 Failed to record SCM polling Error Change By: Srinivas Jajou Status: Open Closed Assignee: k2nakamura Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" g
[JIRA] [publish-over-ssh-plugin] (JENKINS-29917) SocketException: Network is unreachable on ipv6-only environment
Title: Message Title Kirill Merkushev created an issue Jenkins / JENKINS-29917 SocketException: Network is unreachable on ipv6-only environment Issue Type: Bug Assignee: bap Components: publish-over-ssh-plugin Created: 12/Aug/15 3:57 PM Environment: jenkins-1.609.1, java6, java7 publish-over-ssh-1.13 Priority: Major Reporter: Kirill Merkushev Full stack trace: [java.net.SocketException: Network is unreachable]] jenkins.plugins.publish_over.BapPublisherException: Failed to connect session for config [serv]. Message [java.net.SocketException: Network is unreachable] at jenkins.plugins.publish_over_ssh.BapSshHostConfiguration.connect(BapSshHostConfiguration.java:228) at jenkins.plugins.publish_over_ssh.BapSshHostConfiguration.createClient(BapSshHostConfiguration.java:138) at jenkins.plugins.publish_over_ssh.BapSshHostConfiguration.createClient(BapSshHostConfiguration.java:115) at jenkins.plugins.publish_over_ssh.BapSshHostConfiguration.createClient(BapSshHostConfiguration.java:51) at jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:229) at jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205) at jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158) at je
[JIRA] [gradle-plugin] (JENKINS-29916) Gradle 2.7 Automatic installation
Title: Message Title Emile Darroch-Davies created an issue Jenkins / JENKINS-29916 Gradle 2.7 Automatic installation Issue Type: Bug Assignee: Gregory Boissinot Attachments: Gradle.PNG Components: gradle-plugin Created: 12/Aug/15 3:54 PM Environment: Jenkins 1.624, Linux Red Hat Enterprise Linux Server release 6.6 Labels: Gradle automatic-install plugins CI HELP Priority: Blocker Reporter: Emile Darroch-Davies Hi So I'm trying to get Gradle up and running, but I can not choose a version when selecting install automatically. I have tried installing manually and setting the Gradle home, and although it works through the command line, Jenkins fail
[JIRA] [doxygen-plugin] (JENKINS-29681) Variable in in "Doxyfile path" for publish is not resolved
Title: Message Title
Jesper Jensen edited a comment on JENKINS-29681
Re: Variable in in "Doxyfile path" for publish is not resolved
I just saw it in 1.624 on windows 2008 server running Java 1.8_40 and 1.8_51I don't have a variable path! {noformat}Publishing Doxygen HTML results.11:41:17 FATAL: error11:41:17 java.io.IOException: remote file operation failed: C:\Jenkins\workspace\MC4-All-Doc at hudson.remoting.Channel@ac46659:wcjenkins01: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7f0c341011:41:17 at hudson.FilePath.act(FilePath.java:987)11:41:17 at hudson.FilePath.act(FilePath.java:969)11:41:17 at hudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:223)11:41:17 at hudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:177)11:41:17 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)11:41:17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)11:41:17 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)11:41:17 at hudson.model.Build$BuildExecution.post2(Build.java:185)11:41:17 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)11:41:17 at hudson.model.Run.execute(Run.java:1766)11:41:17 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)11:41:17 at hudson.model.ResourceController.execute(ResourceController.java:98)11:41:17 at hudson.model.Executor.run(Executor.java:381)11:41:17 Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7f0c341011:41:17 at hudson.remoting.UserRequest.serialize(UserRequest.java:169)11:41:17 at hudson.remoting.UserRequest.(UserRequest.java:63)11:41:17 at hudson.remoting.Channel.call(Channel.java:776)11:41:17 at hudson.FilePath.act(FilePath.java:980)11:41:17 ... 12 more11:41:17 Caused by: java.io.NotSerializableException: hudson.plugins.doxygen.DoxygenEnvironmentVariableExpander11:41:17 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184)11:41:17 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)11:41:17 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)11:41:17 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)11:41:17 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)11:41:17 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1548)11:41:17 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1509)11:41:17 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1432)11:41:17 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1178)11:41:17 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348)11:41:17 at hudson.remoting.UserRequest._serialize(UserRequest.java:158)11:41:17 at hudson.remoting.UserRequest.serialize(UserRequest.java:167)11:41:17 ... 15 more11:41:17 Build step 'Publish Doxygen' changed build result to FAILURE{noformat}
Add Comment
[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-25249
Re: Post-commit hook for P4 plugin
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java src/main/java/org/jenkinsci/plugins/p4/trigger/P4Trigger.java src/main/java/org/jenkinsci/plugins/p4/workflow/P4PublishStep.java src/main/java/org/jenkinsci/plugins/p4/workflow/P4TaggingStep.java src/main/resources/org/jenkinsci/plugins/p4/trigger/P4Trigger/P4TriggerAction/index.jelly src/main/webapp/script.js src/main/webapp/style.css http://jenkins-ci.org/commit/p4-plugin/7bc19f9ca1b79a630af99c2332c8769954687e21 Log: Perforce triggered polling BETA.
Perforce triggers on a change-submit and sends a POST to the endpoint http://$ {JENKINS}
/p4/change with the data: {"change":"12345","p4port":"localhost:1666"}
Note: ‘change’ is not used (yet), but ‘p4port’ MUST match the credential in the Jenkins Job.
JENKINS-25249
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] [pmd-plugin] (JENKINS-29799) pmdResult links doesnt work from the trendDetails graph
Title: Message Title Ulli Hafner resolved as Duplicate Jenkins / JENKINS-29799 pmdResult links doesnt work from the trendDetails graph Change By: Ulli Hafner Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29681) Variable in in "Doxyfile path" for publish is not resolved
Title: Message Title Jesper Jensen updated an issue Jenkins / JENKINS-29681 Variable in in "Doxyfile path" for publish is not resolved Change By: Jesper Jensen Environment: LTS jenkins master 1.609.1 and 1.624 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] [doxygen-plugin] (JENKINS-29681) Variable in in "Doxyfile path" for publish is not resolved
Title: Message Title Jesper Jensen updated an issue Jenkins / JENKINS-29681 Variable in in "Doxyfile path" for publish is not resolved Change By: Jesper Jensen Priority: Minor Critical 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] [doxygen-plugin] (JENKINS-29681) Variable in in "Doxyfile path" for publish is not resolved
Title: Message Title Jesper Jensen edited a comment on JENKINS-29681 Re: Variable in in "Doxyfile path" for publish is not resolved I just saw it in 1.624 on windows 2008 server running Java 1.8_40 and 1.8_51 I don't have a variable path! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [doxygen-plugin] (JENKINS-29681) Variable in in "Doxyfile path" for publish is not resolved
Title: Message Title Jesper Jensen commented on JENKINS-29681 Re: Variable in in "Doxyfile path" for publish is not resolved I just saw it in 1.624 on windows 2008 server running Java 1.8_40 and 1.8_51 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title Paul Allen commented on JENKINS-25249 Re: Post-commit hook for P4 plugin I have been experimenting with a trigger based endpoint in Jenkins. I have seen a few plugins take this approach (https://github.com/jenkinsci/bitbucket-plugin). I have submitted a change, if you are interested in trying it out let me know and I can send you the details. 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] [jclouds-jenkins] (JENKINS-29915) Copy artifact from cloud
Title: Message Title Jonathan Langevin created an issue Jenkins / JENKINS-29915 Copy artifact from cloud Issue Type: Improvement Assignee: Marat Mavlyutov Components: jclouds-jenkins, jclouds-plugin Created: 12/Aug/15 3:32 PM Labels: cloud storage artifact-download artifacts jclouds Priority: Major Reporter: Jonathan Langevin I run Jenkins on a small master instance that doesn't have a ton of storage, but I need to save large artifacts from the slaves. I also need to be able to run a build using artifacts from an upstream. When this is immediate, then storage isn't really an issue as the artifact is available still, but for a downstream build that I want to re-execute a week or two later, I no longer have the artifact locally, and if I saved the artifact to S3 using jclouds, I'm unable to retrieve it using jclouds for the downstream build to use. Please add a build step or pre-build step that allows us to fetch artifacts from S3. Thanks!
[JIRA] [subversion-plugin] (JENKINS-29914) Subversion working copy is slow (low resolution timestamps?)
Title: Message Title Josh Kelley created an issue Jenkins / JENKINS-29914 Subversion working copy is slow (low resolution timestamps?) Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 12/Aug/15 3:18 PM Environment: Jenkins 1.609.2, Subversion plugin 2.5, OpenJDK 7u79-2.5.6 (as provided by Ubuntu 14.04) Labels: performance subversion Priority: Major Reporter: Josh Kelley Working copies created by the Jenkins Subversion plugin are very slow to work with. I think that the problem is that the plugin and its Subversion libraries don't maintain enough precision in file timestamps. Details: One of the steps in our build process runs svnversion on a large working copy. We noticed that this operation took over 30 times longer in a working copy created by Jenkins' Subversion plugin, compared to a working copy checked out in the standard svn command-line (CLI) client.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-29808) cve xml-files in $JENKINS_HOME/temp
Title: Message Title Steve Springett commented on JENKINS-29808 Re: cve xml-files in $JENKINS_HOME/temp The location of the temp directory can be changed in the plugin's global configuration. Moving it somewhere else may make monitoring a bit easier. Need to investigate to see if this is an issue with the core, or with the Jenkins plugin specifically. 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] [jclouds-jenkins] (JENKINS-21864) Rename jclouds plugin to better reflect what it does
Title: Message Title Jonathan Langevin commented on JENKINS-21864 Re: Rename jclouds plugin to better reflect what it does As it provides blob storage, it's not limited to slaves, so perhaps "Multi-Cloud Plugin" Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-29808) cve xml-files in $JENKINS_HOME/temp
Title: Message Title Steve Springett assigned an issue to Steve Springett Jenkins / JENKINS-29808 cve xml-files in $JENKINS_HOME/temp Change By: Steve Springett Assignee: Steve Springett Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29913) Generalize DependencyGraph to Job (or ParameterizedJobMixIn)
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-29913 Generalize DependencyGraph to Job (or ParameterizedJobMixIn) Issue Type: Task Assignee: Unassigned Components: core Created: 12/Aug/15 3:17 PM Labels: workflow Priority: Major Reporter: Jesse Glick Currently DependencyGraph is limited to AbstractProject, making it impossible for Workflows to participate in upstream/downstream relationships (in cases where job chaining is required, for example due to security constraints). Add Comment
[JIRA] [parameterized-trigger-plugin] (JENKINS-26050) Workflow integration for Parameterized Trigger
Title: Message Title Jesse Glick commented on JENKINS-26050 Re: Workflow integration for Parameterized Trigger the upstream/downstream relationships is not visible in the web browser/API This is not possible from the plugin currently since DependencyGraph is currently limited to AbstractProject. I filed JENKINS-29913 to track it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins-plugin] (JENKINS-29908) Male OWASP Dependency-Check Plug-in compatible with Workflow
Title: Message Title Steve Springett commented on JENKINS-29908 Re: Male OWASP Dependency-Check Plug-in compatible with Workflow Manuel, What is the expected behavior you're trying to achieve? Any presentations or code you can share? 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] [parameterized-trigger-plugin] (JENKINS-26050) Workflow integration for Parameterized Trigger
Title: Message Title Vegard Endresen commented on JENKINS-26050 Re: Workflow integration for Parameterized Trigger Version 2.28 works, nice! As a comment the upstream/downstream relationships is not visible in the web browser/API. I think this would be nice to have. 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.
