[JIRA] (JENKINS-50863) list.empty broken in pipeline scripts
Title: Message Title
Daniel Sobral commented on JENKINS-50863
Re: list.empty broken in pipeline scripts
I think you are right, Andrew Bayer, because I've noticed calls that do not end with parenthesis are just returning the object's value:
def ald = []
print "ald: " + ald
print "ald.getClass: " + ald.getClass
print "ald.class: " + ald.class
print "ald.isEmpty: " + ald.isEmpty
print "ald.empty: " + ald.empty
echo "ald: ${ald}"
echo "ald.getClass(): ${ald.getClass()}"
echo "ald.class: ${ald.class}"
echo "ald.isEmpty(): ${ald.isEmpty()}"
echo "ald.empty: ${ald.empty}"
ald: []
[Pipeline] echo
ald.getClass: []
[Pipeline] echo
ald.class: class java.util.ArrayList
[Pipeline] echo
ald.isEmpty: []
[Pipeline] echo
ald.empty: []
[Pipeline] echo
ald: []
[Pipeline] echo
ald.getClass(): class java.util.ArrayList
[Pipeline] echo
ald.class: class java.util.ArrayList
[Pipeline] echo
ald.isEmpty(): true
[Pipeline] echo
ald.empty: []
If I had to guess, I'd say "empty" is not treating "isEmpty" as a getter (is vs get), and the failure case (no method or property) is doing some weird thing.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title Daniel Sobral commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" My maven builds were plagued by this, so it's not pipeline-related. I don't see it much with pipelines, though I wrote my pipelines with retry from the start, because I expected that very problem to persist. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40844) Config File Provider Plugin fails to load due to Guice issue
Title: Message Title Daniel Sobral commented on JENKINS-40844 Re: Config File Provider Plugin fails to load due to Guice issue During startup, I get this: Failed to instantiate Key[type=org.jenkinsci.plugins.configfiles.GlobalConfigFiles, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.IllegalArgumentException: providerId can NOT be null at org.jenkinsci.plugins.configfiles.GlobalConfigFiles.(GlobalConfigFiles.java:38) 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:424) 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:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:472) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1506) at hudson.plugins.sonar.SonarPlugin.postInitialize(SonarPlugin.java:44) at hudson.PluginManager$2$1$2.run(PluginManager.java:542) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:1051) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalArgumentException: providerId can NOT be null at org.jenkinsci.lib.configprovider.model.Config.(Config.java:93) at org.jenkinsci.lib.configprovider.model.Config.(Config.java:85) at org.jenkinsci.plugins.configfiles.custom.CustomConfig.(CustomConfig.java:51) at org.jenkinsci.plugins.configfiles.custom.CustomConfig$CustomConfigProvider.convert(CustomConfig.java:78) at org.jenkinsci.lib.configprovider.AbstractConfigProviderImpl.getConfigs(AbstractConfigProviderImpl.java:50) at org.jenkinsci.plugins.configfiles.GlobalConfigFiles.(GlobalConfigFiles.java:42) at org.jenkinsci.plugins.configfiles.GlobalConfigFiles$$FastClassByGuice$$32984daf.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61) 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.ProviderToInternalFactoryA
[JIRA] (JENKINS-40844) Config File Provider Plugin fails to load due to Guice issue
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-40844 Config File Provider Plugin fails to load due to Guice issue Issue Type: Bug Assignee: Dominik Bartholdi Components: config-file-provider-plugin Created: 2017/Jan/05 7:00 PM Environment: Jenkins 2.26, Config File Provider 2.15.1 Priority: Blocker Reporter: Daniel Sobral I've got this on my log: Failed to instantiate Key[type=org.jenkinsci.plugins.configfiles.ConfigFilesManagement, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.lang.IllegalStateException at org.jenkinsci.plugins.configfiles.ConfigFilesManagement.(ConfigFilesManagement.java:60) 1 error
[JIRA] (JENKINS-39232) unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave
Title: Message Title Daniel Sobral commented on JENKINS-39232 Re: unable to start slave after installing version 2.27 on master + new 3.0 slave.jar on slave I'm seeing a similar log with mesos-launched slaves 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-38945) Pipeline script doesn't find method with explicit parameter type
Title: Message Title Daniel Sobral commented on JENKINS-38945 Re: Pipeline script doesn't find method with explicit parameter type Just checked, and the error stays the same. 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-38945) Pipeline script doesn't find method with explicit parameter type
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-38945
Pipeline script doesn't find method with explicit parameter type
Issue Type:
Bug
Assignee:
Unassigned
Components:
script-security-plugin, workflow-cps-plugin
Created:
2016/Oct/13 1:13 AM
Environment:
Jenkins 2.23 Pipeline 2.4 Pipeline: Groovy 2.19 Script Security 1.23
Priority:
Minor
Reporter:
Daniel Sobral
Pipeline scripts fail to find method declaring parameter type. The script below will fail to execute "doStuff", with NoSuchMethodError. This used to work, but rolling back security and groovy didn't help, and utility steps (which defines readMavenPom) wasn't available for rollback. On a simple test, "Integer n" works as a type parameter, so this might well be specific to the object returned by readMavenPom().
import org.apache.maven.model.Model
stage ("initial") {
node ('mesos') {
git url: 'https://github.com/jglick/simple-maven-project-with-tests.git'
Model pom = readMavenPom()
echo "Class of pom is ${pom.class}"
doThings(pom)
doStuff(pom)
}
}
def doThings(pom) {
echo "Got something"
}
def doStuff(Model pom) {
echo "Got pom"
}
[JIRA] (JENKINS-31396) Access to submitter ID from return value of input step
Title: Message Title Daniel Sobral commented on JENKINS-31396 Re: Access to submitter ID from return value of input step I record relevant information from the build on Bitbucket and JIRA. Who clicked on the input button is rather relevant. 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Daniel Sobral commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Mind you, it doesn't work for submodules. Submodules have a fundamental flaw: they are repos on their own, so the credentials for the module that include them does not apply, but you can't set local credentials for them before they are fetched. Catch-22. For submodules, either use relative paths, SSH keys, or run a sed on the URL of .gitmodules. 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Daniel Sobral commented on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Workaround:
withCredentials([[$class : 'FileBinding', credentialsId: 'your-credential-id',
variable: 'CREDENTIALS']]) {
sh 'git config --local credential.username RepoUserName'
sh "git config --local credential.helper 'store --file=${env.CREDENTIALS}'"
sh "git do-your-stuff"
sh 'git config --local --remove-section credential'
}
See git man page for the git store credential for information on the file format.
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-37426) FileBinding not working
Title: Message Title Daniel Sobral closed an issue as Not A Defect File isn't visible outside the credential scope. Jenkins / JENKINS-37426 FileBinding not working Change By: Daniel Sobral Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37426) FileBinding not working
Title: Message Title Daniel Sobral commented on JENKINS-37426 Re: FileBinding not working This is a false report. The credentials plugin rightfully removes the file after the wrapped closure executes, so of course it isn't visible outside it. My mistake, sorry. 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-37527) String.join won't accept iterables (vararg vs iterable overload issue?)
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37527
String.join won't accept iterables (vararg vs iterable overload issue?)
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
script-security-plugin
Created:
2016/Aug/18 9:25 PM
Environment:
Script Security 1.21, Jenkins 2.18
Priority:
Minor
Reporter:
Daniel Sobral
Pipeline fails if I pass an iterable parameter to String.join, with an error message suggesting it tried to use the vararg overload. Jenkinsfile:
def lst = ['a', 'bc', 'def']
echo "Lst: $lst"
// Works
def str = String.join('\n', lst.toArray(new String[lst.size()]))
echo "Str: $str"
// Doesn't work
def str2 = String.join('\n', lst)
echo "Str2: ${str2}"
Console text:
Started by user dsobral
DatadogBuildListener.java: Started build!
DatadogBuildListener.java: Using unix hostname found via `/bin/hostname -f`. Hostname: sfdev-061.richrelevance.com
DatadogBuildListener.java: Sending event
DatadogBuildListener.java: API call of type 'v1/events' was sent successfully!
DatadogBuildListener.java: Payload: {"alert_type":"info","title":"string_join_test build #5 started on sfdev-061.richrelevance.com","text":"%%% \n [Follow build #5 progress](https://jenkins.richrelevance.com/job/string_join_test/5/) \n %%%","date_happened":1471555196,"event_type":"build start","ho
[JIRA] (JENKINS-37484) Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result
Title: Message Title Daniel Sobral commented on JENKINS-37484 Re: Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result https://github.com/jenkinsci/pipeline-build-step-plugin/pull/6 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-37484) Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37484 Pipeline Build Step incorrectly documents FAILED instead of FAILURE as a result Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/17 9:12 PM Priority: Minor Reporter: Daniel Sobral The documentation for the Build step presently states this: result typically SUCCESS, UNSTABLE, or FAILED (may be null for an ongoing build) However, the actual state is FAILURE, not FAILED. Add Comment
[JIRA] (JENKINS-37433) findFiles doesn't get dot directories
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37433
findFiles doesn't get dot directories
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2016/Aug/16 4:59 AM
Priority:
Minor
Reporter:
Daniel Sobral
Looking at the code, this seems to be more of a general Jenkins issue than a plugin one, but I had to pick a place to file it, and this is where I'm seeing it. If I use dot (.) to represent the current directory, findFiles fails to find anything. Here's sample pipeline script and output.
node {
touch file: 'oneFile.txt'
sh 'test -d dir/target || mkdir -p dir/target'
touch file: 'dir/anotherFile.txt'
touch file: 'dir/target/targetFile.txt'
def period_star = findFiles glob: './*'
def star = findFiles glob: '*'
def period_doublestar = findFiles glob: './**'
def doublestar = findFiles glob: '**'
def dir_doublestar = findFiles glob: 'dir/**'
def period_doublestar_target_doublestar = findFiles glob: './**/target/**'
def doublestar_target_doublestar = findFiles glob: '**/target/**'
echo "*: ${period_star.length} ${star.length}"
echo "**: ${period_doublestar.length} ${doublestar.length} ${dir_doublestar.length}"
echo "**/target/**: ${period_doublestar_target_doublestar.length} ${doublestar_target_doublestar.length}"
}
Output:
[Pipeline] node
Running on mesos-jenkins-260e7dcce7044a1b90d183a388efed99-mesos in /jenkins/workspace/findfiles_test_pipeline
[Pipeline] {
[Pipeline] touch
[Pipeline
[JIRA] (JENKINS-37398) unclassified field groovy.util.Node xxx
Title: Message Title Daniel Sobral commented on JENKINS-37398 Re: unclassified field groovy.util.Node xxx It is working for me, as long as I use map syntax instead of property syntax, fwiw. 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-37426) FileBinding not working
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37426
FileBinding not working
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
credentials-binding-plugin
Created:
2016/Aug/16 12:16 AM
Environment:
Credentials Binding Plugin 1.8, Jenkins 2.17
Priority:
Major
Reporter:
Daniel Sobral
It seems FileBinding is not working. I've tried this on master and slaves, with the same result:
Jenkinsfile
node {
def tmp = pwd tmp: true
echo "TMP: $tmp"
withCredentials([[$class: 'FileBinding', credentialsId: 'bitbucket-rrbuild-store-helper-credential',
variable: 'CREDENTIALS']]) {
sh "echo '${env.CREDENTIALS}' > file.txt"
}
sh 'cat file.txt'
sh 'ls -laR $(dirname $(dirname $(dirname $(cat file.txt'
sh 'ls -la $(dirname $(dirname $(cat file.txt)))'
sh 'ls -la $(dirname $(cat file.txt))'
sh 'cat $(cat file.txt)'
}
And get this:
Started by user dsobral
DatadogBuildListener.java: Started build!
DatadogBuildListener.java: Using unix hostname found via `/bin/hostname -f`. Hostname: sfdev-061.richrelevance.com
DatadogBuildListener.java: Sending event
Dat
[JIRA] (JENKINS-37181) Multibranch Pipeline Jenkinsfile job script not seeing Credentials
Title: Message Title
Daniel Sobral commented on JENKINS-37181
Re: Multibranch Pipeline Jenkinsfile job script not seeing Credentials
It's an environment variable binding, so you should use $ {env.SECRET_FILE} .
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-37398) unclassified field groovy.util.Node xxx
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37398
unclassified field groovy.util.Node xxx
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
script-security-plugin
Created:
2016/Aug/13 10:36 PM
Priority:
Minor
Reporter:
Daniel Sobral
I'm trying to use one of Groovy's XML libraries, but I keep stumbling on errors. XMLSlurper gives me an Object getProperty String which I'm not supposed to accept. When I use XMLParser, I get this:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified field groovy.util.Node testcase
This one does not appear on approval list. It comes from this piece of code:
def result = new XmlParser().parseText(xml)
result.testcase.'*'.findAll { node -> node.name() == 'failure' || node.name() == 'error' }*.text()
Using result['testcase'] gets me past this error, up to '*', which I haven't tried using the map syntax for yet. Still, it doesn't appear on the security list for approval/denial.
[JIRA] (JENKINS-28467) With concurrent builds, Flaky Test Handler blocks later builds from finishing first
Title: Message Title Daniel Sobral commented on JENKINS-28467 Re: With concurrent builds, Flaky Test Handler blocks later builds from finishing first I've seen this too. A weird build had over a thousand failed tests, which were being processed VERY SLOWLY, and all subsequent builds were blocked on that. Very bad. I'm also using JUnit Flaky Tests. 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-37357) Allow messaging users
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37357 Allow messaging users Issue Type: Improvement Assignee: Unassigned Components: hipchat-plugin Created: 2016/Aug/11 6:05 PM Priority: Minor Reporter: Daniel Sobral Allow messages to be sent to users instead of rooms. Particularly useful for Pipeline configurations, where information such as committer, pull request author or reviewers can be used. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526
[JIRA] (JENKINS-37327) Allow stashing/unstashing empty sets
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37327 Allow stashing/unstashing empty sets Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/11 5:10 AM Priority: Minor Reporter: Daniel Sobral The stash step fails if there's no files are selected to be stashed. Allowing that to optionally work would make it easier to make Jenkinsfile more generic, by stashing files that might not get generated on some repositories, instead of passing information around with fields, or catching failure when unstashing (which still leaves the corresponding log marked as Failure in the build). Add Comment
[JIRA] (JENKINS-37325) Make static analysis results visible from a Pipeline
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37325 Make static analysis results visible from a Pipeline Issue Type: Improvement Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2016/Aug/11 1:41 AM Priority: Minor Reporter: Daniel Sobral I'd like to be able to tell if the static analysis publisher I executed failed the build. That is easy on serial pipelines by checking the currentBuild.result, but when executing tasks in parallel, I cannot rely on that. It would be even better if the actual data was made available, in which case I could drop the thresholds and use more complex logic. Add Comment
[JIRA] (JENKINS-32556) Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin
Title: Message Title Daniel Sobral commented on JENKINS-32556 Re: Workflow plugin now Pipeline crashes with GitHub Pull Request Builder plugin I got the same problem with Stack Pull Request Builder. javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:249) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176) at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145) at org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92) at com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:87) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilt
[JIRA] (JENKINS-37224) Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Title: Message Title
Daniel Sobral created an issue
Jenkins / JENKINS-37224
Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
2016/Aug/05 6:39 PM
Environment:
Jenkins 2.16, Git 2.53, Pipeline SCM Step 2.2
Priority:
Major
Reporter:
Daniel Sobral
When adding the additional behavior of "Merge before build", the "Merge strategy" is generated like this: {{ mergeStrategy: }} This is related to JENKINS-26753 (dup), JENKINS-26619, but that one is resolved and the problem is happening.
Add Comment
[JIRA] (JENKINS-36956) Pipeline hangs on JUnitResultArchiver step
Title: Message Title Daniel Sobral commented on JENKINS-36956 Re: Pipeline hangs on JUnitResultArchiver step It stops hanging if you remove test stability. 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-37134) Add @NonCPS to Jenkinsfile GDSL
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-37134 Add @NonCPS to Jenkinsfile GDSL Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 2016/Aug/02 10:54 PM Environment: IntelliJ 2016.2, Pipeline plugin 2.2 Labels: workflow Priority: Minor Reporter: Daniel Sobral The current IntelliJ IDEA GDSL provides no support for @NonCPS, so it gets highlighted as an error. Add support for it. Add Comment
[JIRA] [stash-pullrequest-builder-plugin] (JENKINS-33917) Add support for token-macro plugin
Title: Message Title Daniel Sobral created an issue Jenkins / JENKINS-33917 Add support for token-macro plugin Issue Type: New Feature Assignee: nathan m Components: stash-pullrequest-builder-plugin Created: 2016/Mar/30 11:54 PM Priority: Minor Reporter: Daniel Sobral When posting a post-build comment on Stash, support expansion of variables provided through the token macro plugin. This would make it possible to include information from the various static analysis or build failure analysis plugins, for example. Add Comment
[JIRA] (JENKINS-14036) Sonar jobs not appering after upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163668#comment-163668 ] Daniel Sobral commented on JENKINS-14036: - In fact, it was tagged won't fix. > Sonar jobs not appering after upgrade > - > > Key: JENKINS-14036 > URL: https://issues.jenkins-ci.org/browse/JENKINS-14036 > Project: Jenkins > Issue Type: Bug > Components: sonar >Affects Versions: current > Environment: Jenkins: 1.467 > Sonar: 3.0.1 (Sonar Jenkins plugin-1.8) > openSUSE 12.1 (Asparagus) (x86_64) >Reporter: Michel Drenthe >Assignee: sonarteam > Labels: jenkins, job, plugin, sonar, update > > After updating Jenkins 1.466 -> 1.467 > All Jobs where Sonar is included are removed from the job list. > Log shows: > INFO | jvm 1| 2012/06/07 09:44:51 | Jun 07, 2012 9:44:51 AM > jenkins.InitReactorRunner$1 onTaskFailed > INFO | jvm 1| 2012/06/07 09:44:51 | SEVERE: Failed Loading job Name > SONAR > INFO | jvm 1| 2012/06/07 09:44:51 | java.lang.NoSuchMethodError: > hudson.maven.MavenModuleSet.getRootPOM()Ljava/lang/String; > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.plugins.sonar.SonarPublisher.getPomName(SonarPublisher.java:278) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.plugins.sonar.SonarPublisher.getSonarUrl(SonarPublisher.java:340) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.plugins.sonar.SonarPublisher.getProjectAction(SonarPublisher.java:358) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.tasks.BuildStepCompatibilityLayer.getProjectActions(BuildStepCompatibilityLayer.java:73) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:376) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:624) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:363) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.model.AbstractProject.onLoad(AbstractProject.java:279) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:669) > INFO | jvm 1| 2012/06/07 09:44:51 | at > hudson.model.Items.load(Items.java:115) > INFO | jvm 1| 2012/06/07 09:44:51 | at > jenkins.model.Jenkins$15.run(Jenkins.java:2472) > INFO | jvm 1| 2012/06/07 09:44:51 | at > org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) > INFO | jvm 1| 2012/06/07 09:44:51 | at > org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > INFO | jvm 1| 2012/06/07 09:44:51 | at > jenkins.model.Jenkins$6.runTask(Jenkins.java:865) > INFO | jvm 1| 2012/06/07 09:44:51 | at > org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) > INFO | jvm 1| 2012/06/07 09:44:51 | at > org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) > INFO | jvm 1| 2012/06/07 09:44:51 | at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > INFO | jvm 1| 2012/06/07 09:44:51 | at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > INFO | jvm 1| 2012/06/07 09:44:51 | at > java.lang.Thread.run(Thread.java:722) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
