[JIRA] (JENKINS-38122) Intermittent error when using withMaven
Title: Message Title Dan Jasek closed an issue as Cannot Reproduce My mistake. Error is in different plugin. Jenkins / JENKINS-38122 Intermittent error when using withMaven Change By: Dan Jasek Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-38122) Intermittent error when using withMaven
Title: Message Title
Dan Jasek created an issue
Jenkins / JENKINS-38122
Intermittent error when using withMaven
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2016/Sep/12 3:17 AM
Environment:
Jenkins v2.3 pipeline-maven-plugin v0.2
Priority:
Major
Reporter:
Dan Jasek
My build scripts fail intermittently on the withMaven step. This configuration did work correctly when I first added it. It will still work occasionally, but usually produces the below error. I have not yet found a pattern as to when it does or doesn't work. The call in the Jenkinsfile: withMaven(maven: 'maven-3', mavenSettingsConfig: 'global-settings') I turned on logging for the plugin: Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Maven: maven-3 Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Jdk: null Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution MavenOpts: null Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Settings Config: global-settings Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Settings FilePath: null Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Computer: Sep 12, 2016 2:53:08 AM FINE org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution Env: {GRADLE_HOME=/usr/local/gradle, HOME=, JAVA_HOME=/usr/lib/jvm/java, JAVA_OPTS=, JENKINS_HOME=/var/jenkins, M2=/usr/local/apache-maven/bin, M2_HOME=/usr/local/apache-maven, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin, PORT=5000, SUPERVISOR_ENABLED=1, SUPERVISOR_GROUP_NAME=application,
[JIRA] (JENKINS-37731) syntax for SCMTrigger in pipelineTriggers
Title: Message Title
Dan Jasek updated an issue
Jenkins / JENKINS-37731
syntax for SCMTrigger in pipelineTriggers
Change By:
Dan Jasek
From what I can tell this syntax should work for defining an SCMTrigger within Jenkinsfile:{code}properties([pipelineTriggers([scm('H/5 * * * *')])]){code}For comparison, this works for the TimerTrigger:{code}properties([pipelineTriggers([cron('H/5 * * * *')])]){code}As a workaround, this does work correctly:{code}properties([pipelineTriggers([[$class: "SCMTrigger", spec scmpoll_spec : "H/5 * * * *"],])]){code}This is the error I get when using scm:hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: hudson.plugins.git.GitSCM.call() is applicable for argument types: (java.lang.String) values: [H/5 * * * *]Possible solutions: all(), wait(), any(), wait(long), each(groovy.lang.Closure), any(groovy.lang.Closure) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:58) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:64) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:12) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:48) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor275.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
[JIRA] (JENKINS-37731) syntax for SCMTrigger in pipelineTriggers
Title: Message Title
Dan Jasek created an issue
Jenkins / JENKINS-37731
syntax for SCMTrigger in pipelineTriggers
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Aug/27 12:03 AM
Priority:
Minor
Reporter:
Dan Jasek
From what I can tell this syntax should work for defining an SCMTrigger within Jenkinsfile:
properties([
pipelineTriggers([
scm('H/5 * * * *')
])
])
For comparison, this works for the TimerTrigger:
properties([
pipelineTriggers([
cron('H/5 * * * *')
])
])
As a workaround, this does work correctly:
properties([
pipelineTriggers([
[$class: "SCMTrigger", spec: "H/5 * * * *"],
])
])
This is the error I get when using scm: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: hudson.plugins.git.GitSCM.call() is applicable for argument types: (java.lang.String) values: [H/5 * * * *] Possible solutions: all(), wait(), any(), wait(long), each(groovy.lang.Closure), any(groovy.lang.Closure) at
[JIRA] (JENKINS-34779) configurable scm polling for github organization folder jobs
Title: Message Title Dan Jasek edited a comment on JENKINS-34779 Re: configurable scm polling for github organization folder jobs I currently get around this by setting a property in the Jenkinsfiles.It is not ideal, and I would prefer this setting at the organization level, but it works (with the latest pipeline plugin version).I have the following in all my Jenkinsfiles: bq. properties([ bq. pipelineTriggers([[$class: 'SCMTrigger', scmpoll_spec: 'H/5 * * * *']]) bq. ]) 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-34779) configurable scm polling for github organization folder jobs
Title: Message Title
Dan Jasek edited a comment on JENKINS-34779
Re: configurable scm polling for github organization folder jobs
I currently get around this by setting a property in the Jenkinsfiles.It is not ideal, and I would prefer this setting at the organization level, but it works (with the latest pipeline plugin version).I have the following in all my Jenkinsfiles:{ quote} { properties([pipelineTriggers([[$class: 'SCMTrigger', scmpoll_spec: 'H/5 * * * *']])]) {quote } }
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-34779) configurable scm polling for github organization folder jobs
Title: Message Title
Dan Jasek edited a comment on JENKINS-34779
Re: configurable scm polling for github organization folder jobs
I currently get around this by setting a property in the Jenkinsfiles.It is not ideal, and I would prefer this setting at the organization level, but it works (with the latest pipeline plugin version).I have the following in all my Jenkinsfiles: {{ bq. properties([ bq. pipelineTriggers([[$class: 'SCMTrigger', scmpoll_spec: 'H/5 * * * *']]) bq. ]) }}
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-34779) configurable scm polling for github organization folder jobs
Title: Message Title Dan Jasek commented on JENKINS-34779 Re: configurable scm polling for github organization folder jobs I currently get around this by setting a property in the Jenkinsfiles. It is not ideal, and I would prefer this setting at the organization level, but it works (with the latest pipeline plugin version). I have the following in all my Jenkinsfiles: properties([ pipelineTriggers([[$class: 'SCMTrigger', scmpoll_spec: 'H/5 * * * *']]) ]) 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-3345) Dependency analyzer plugin support for free-style-projects that execute maven goals
Title: Message Title Dan Jasek commented on JENKINS-3345 Re: Dependency analyzer plugin support for free-style-projects that execute maven goals Now, 4 years later. With the release of Pipeline projects, it would be nice if this plugin supported these projects as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Dan Jasek edited a comment on JENKINS-34005 Re: Make WorkflowJob.triggers into a JobProperty I implemented a solution to this, for the reason Greg describes.This is the step: https://gist.github.com/oillio/14cb6621877ecfb3a1d711e0f31ace90It is not the same solution as you describe. It is a new step which allows setting the scmTrigger for the job, instead of rewriting the job to use JobProperty for the triggers.If this is an acceptable fix, I would be happy to flesh this out and generalize it to other triggers , and submit it as a pull request . 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-34005) Make WorkflowJob.triggers into a JobProperty
Title: Message Title Dan Jasek commented on JENKINS-34005 Re: Make WorkflowJob.triggers into a JobProperty I implemented a solution to this, for the reason Greg describes. This is the step: https://gist.github.com/oillio/14cb6621877ecfb3a1d711e0f31ace90 It is not the same solution as you describe. It is a new step which allows setting the scmTrigger for the job, instead of rewriting the job to use JobProperty for the triggers. If this is an acceptable fix, I would be happy to flesh this out and generalize it to other triggers. 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] [github-organization-folder-plugin] (JENKINS-34779) repo polling
Title: Message Title Dan Jasek created an issue Jenkins / JENKINS-34779 repo polling Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2016/May/12 11:27 PM Priority: Trivial Reporter: Dan Jasek I would like to be able to configure my github organization folder to use scm polling for jobs it creates. My Jenkins server is behind a firewall and cannot be accessed by Github. The current web hook functionality doesn't work. I need some other way to trigger builds. Add Comment
