[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev Labels: remoting winsw Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev commented on JENKINS-22692 Re: Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Created https://github.com/kohsuke/winsw/pull/172 The issue needs some reviews. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev updated JENKINS-22692 Jenkins / JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Title: Message Title Oleg Nenashev started work on JENKINS-22692 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39621) Pipeline job loop after polling always find changes
Title: Message Title Leibo commented on JENKINS-39621 Re: Pipeline job loop after polling always find changes Hi, Not sure it is related but - Is there a way to clean Jenkins SCM cache or something alike? We moved from our current Git server to a new one and once creating a new job with the new SCM details it started finding changes on every poll Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title
Patrick Wolf edited a comment on JENKINS-27295
Re: Boolean parameters injected as String
I would say that it is a best practice to always use the {{params}} object if you want the ensure that the type is consistent. Referencing the parameter as either {{foo}} or {{env.foo}} returns the value as it was injected into an environment variable and will always be of type {{String}}.{code:java}properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])])echo "foo: " + foo.getClass().toString()echo "env.foo: " + env.foo.getClass().toString()echo "params.foo: " + params.foo.getClass().toString(){code}returns:{code:java}[Pipeline] echofoo: class java.lang.String[Pipeline] echoenv.foo: class java.lang.String[Pipeline] echoparams.foo: class java.lang.Boolean[Pipeline] } {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title Patrick Wolf commented on JENKINS-27295 Re: Boolean parameters injected as String I would say that it is a best practice to always use the params object if you want the ensure that the type is consistent. Referencing the parameter as either foo or env.foo returns the value as it was injected into an environment variable and will always be of type String. properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])]) echo "foo: " + foo.getClass().toString() echo "env.foo: " + env.foo.getClass().toString() echo "params.foo: " + params.foo.getClass().toString() returns: [Pipeline] echo foo: class java.lang.String [Pipeline] echo env.foo: class java.lang.String [Pipeline] echo params.foo: class java.lang.Boolean [Pipeline] } Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title David Karr commented on JENKINS-27295 Re: Boolean parameters injected as String So then, in general, if the name of a pipeline parameter specified in the job configuration is "foo", then referencing it in the body of the pipeline script as "foo" will get a variable of a type equivalent to what is specified in the job configuration, EXCEPT if the type in the job configuration is "Boolean Parameter", which will result in a String type. In that case, referencing it as "params.foo" will always guarantee that it will be provisioned as a type that is equivalent to what is specified in the job configuration, including a "Boolean Parameter". Under those circumstances, would you conclude that it would be reasonable to document this understanding in the pipeline documentation? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title
Patrick Wolf edited a comment on JENKINS-27295
Re: Boolean parameters injected as String
[~dkarr] This is my understanding based on the comments above and the the release notes of the [Pipeline Groovy Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Groovy+Plugin] Parameters are passed into the run as environment variables and are captured in a {{params}} object. This means there are three references to that parameter value:{code:java}env.foofooparams.foo{code}The first two return that environment variable that was set. This has to be a string because it is an environment variable. The third method retains the parameter type set because it is not used in the environment. In this case:This functions as expected because it is a boolean param{code:java}properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])])if (params.foo) {echo "true: $foo"}else echo "false: $foo"{code}But this will not because it is a string from environment variable:{code:java}properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])])if (foo) {echo "true: $foo"}else echo "false: $foo"{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title
Patrick Wolf commented on JENKINS-27295
Re: Boolean parameters injected as String
David Karr This is my understanding based on the comments above the the release notes of the Pipeline Groovy Plugin Parameters are passed into the run as environment variables and are captured in a params object. This means there are three references to that parameter value:
env.foo
foo
params.foo
The first two return that environment variable that was set. This has to be a string because it is an environment variable. The third method retains the parameter type set because it is not used in the environment. In this case: This functions as expected because it is a boolean param
properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])])
if (params.foo) {
echo "true: $foo"
}
else echo "false: $foo"
But this will not because it is a string from environment variable:
properties([parameters([booleanParam(defaultValue: false, description: '', name: 'foo')])])
if (foo) {
echo "true: $foo"
}
else echo "false: $foo"
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-27295) Boolean parameters injected as String
Title: Message Title David Karr commented on JENKINS-27295 Re: Boolean parameters injected as String I would appreciate a clear summary of the current and desired state for this situation. The context is a pipeline job with a parameter clearly defined as a "Boolean Parameter". In my experience, this is provisioned as a string, which with no other information, is just confusing. So, is this going to be fixed, or is this considered to be acceptable? I'm having trouble discerning a clear message on this. If this isn't going to change, at the least, the job configuration page should make it clear that it will be provisioned as a String type. Otherwise, every single person who discovers this for the first time is going to assume this is a bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40665) Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-40665 Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs Change By: Cyrille Le Clerc Assignee: Cyrille Le Clerc Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40665) Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-40665 Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs Change By: Cyrille Le Clerc Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40665) Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-40665 Maven SettingsProvider and GlobalSettingsProvider should support Pipeline jobs Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Dec/24 4:47 PM Priority: Minor Reporter: Cyrille Le Clerc Maven SettingsProvider and GlobalSettingsProvider are designed for 'classic' Jenkins jobs relying on "AbstractBuild" and are NOT compatible with pipeline jobs that rely on "WorkflowRun" and "Run" (see jenkins.mvn.SettingsProvider#supplySettings(AbstractBuild build, TaskListener listener))". Maven SettingsProvider and GlobalSettingsProvider should be able to supply Maven settings.xml and global settings.xml to "Run". Add Comment
[JIRA] (JENKINS-35370) Workflow shell step ERROR: script returned exit code -1
Title: Message Title Ben Mathews commented on JENKINS-35370 Re: Workflow shell step ERROR: script returned exit code -1 The production server is running the builds on a centos 7 slave. My test environment is running jenkins in a docker container that is mounting /var/run/docker.sock from my laptop. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-39977 Support for bitbucket-branch-source-plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39713) java.io.IOException: Failed to dynamically deploy this plugin for job-dsl plugin
Title: Message Title Daniel Spilker closed an issue as Not A Defect Jenkins / JENKINS-39713 java.io.IOException: Failed to dynamically deploy this plugin for job-dsl plugin Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40091) Require support for ZAProxy Plugin using DSL
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40091 Require support for ZAProxy Plugin using DSL Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40099) Job creation takes awhile
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-40099 Job creation takes awhile Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39917) project update with dsl-script does not update "rootPom" settings for maven job
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-39917 project update with dsl-script does not update "rootPom" settings for maven job Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40102) job dsl does not respect pipeline withEnv
Title: Message Title Daniel Spilker closed an issue as Duplicate Jenkins / JENKINS-40102 job dsl does not respect pipeline withEnv Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40191 job created by multibranch pipeline created by job dsl script uses wrong github URL Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40636) Maven steps enable deprecated injectBuildVariables option
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40636 Maven steps enable deprecated injectBuildVariables option Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40205) job-dsl-api-viewer need internet connection for access css and js file
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40205 job-dsl-api-viewer need internet connection for access css and js file Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40601) Cannot create pipelineView with job-dsl 1.53
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40601 Cannot create pipelineView with job-dsl 1.53 Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title squalou jenkins commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) I'm running Jenkins 2.19.4 on a redhat 7.2 and java8 The slaves on which I ran the job are either redhat 7.2, or 6.4, no idea if it could affect the result. (yet note that the slave is not on the same host as the master) build is triggered manually for now Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25333) Jenkins 1.586 not starting up using Java8
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25333 Re: Jenkins 1.586 not starting up using Java8 Code changed in jenkins User: Jesse Glick Path: war/pom.xml http://jenkins-ci.org/commit/jenkins/4f814c0a9f8e72384046015975f201f4f693abaf Log: [FIXED JENKINS-25333] Update to Winstone 3.2. (#2673) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40636) Maven steps enable deprecated injectBuildVariables option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40636 Re: Maven steps enable deprecated injectBuildVariables option Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/RequiresCore.java job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/MavenContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/CoreVersionASTTransformationSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/InterruptibleJobManagement.groovy job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java http://jenkins-ci.org/commit/job-dsl-plugin/384c836962582d3bd2654e0e589016b3e284cbf1 Log: enhanced support for the Maven build step [FIXES JENKINS-40636] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40636) Maven steps enable deprecated injectBuildVariables option
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40636 Maven steps enable deprecated injectBuildVariables option Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40636) Maven steps enable deprecated injectBuildVariables option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40636 Re: Maven steps enable deprecated injectBuildVariables option Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/JobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/RequiresCore.java job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/MavenContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/CoreVersionASTTransformationSpec.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/InterruptibleJobManagement.groovy job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JenkinsJobManagement.java http://jenkins-ci.org/commit/job-dsl-plugin/ab0748a0b08c86b9519ebca2f5c6aefe6aa7820a Log: Merge pull request #975 from daspilker/JENKINS-40636 JENKINS-40636 enhanced support for the Maven build step Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/86131780161c...ab0748a0b08c Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
