[JIRA] [active-directory-plugin] (JENKINS-13058) E-mail to individuals who broke the build is sent to wrong address
nir h commented on JENKINS-13058 E-mail to individuals who broke the build is sent to wrong address I'm having the same issue with TFS source control plugin. My Jenkins version is 1.599. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Tommy Tynjä commented on JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) It's been a while now since we requested some more details regarding this issue (see PR). Are you able to provide a reproducing unit test? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27917) Stack Trace when Checking for Updates
Daniel Beck commented on JENKINS-27917 Stack Trace when Checking for Updates The best option would be to enforce a connection check similar to what the update center does before installing, IF that check is enhanced to include a check for the returned page contents, similar to what Windows does (http://www.msftncsi.com/ncsi.txt). Unfortunately, that will not work with self-hosted update centers and Jenkins instances not meant to access the internet, even breaking them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [fitnesse-plugin] (JENKINS-25010) NullPointerException running FitNesse-tests
Antoine Aumjaud resolved JENKINS-25010 as Fixed NullPointerException running FitNesse-tests fixed in v1.10 Change By: Antoine Aumjaud (14/Apr/15 7:04 AM) Status: Open Resolved Assignee: AntoineAumjaud Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
dan tran commented on JENKINS-27722 upgrade to the release plugin has left the plugin broken @Daniel, I am very new to Jenkins development, could you confirm if Glen's changes at https://github.com/glenritchie/release-plugin/tree/JENKINS-27722-1609 are correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27917) Stack Trace when Checking for Updates
Daniel Beck commented on JENKINS-27917 Stack Trace when Checking for Updates And my point is, how do you expect a user to know the issue is their proxy setup when you have a vague, misspelled error message that doesn't in any way indicate this? I read 're-opening' to mean reading and reopening this specific issue, which contains the solution in the comments. Please change the error message to something along the lines of, "Jenkins received an unexpected response. Please check your proxy/network configuration." The problem here is that this requires an assumption such as 'all invalid JSON responses are due to no proxy being set up', something I doubt is reasonably accurate. There can be any number of reasons. (In fact, the redirect seems to be fairly braindead to me, as it'll break all kinds of tools not used interactively. It should at least set some HTTP error code in the response so automated tools know to fail.) Do you think it would it help to wrap the error in a more generic 'failed to parse JSON update center metadata', and maybe show an excerpt of the data? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27924) Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin
Tadej Lasic created JENKINS-27924 Concurrent jobs dont queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 7:00 AM Description: After Jenkins version 1.607 jobs that run on the same SVN directory/repository and are throttled with using Throttle Concurrent Builds Plugin (Multi-Project Throttle Category is setup for these jobs, all are part of the same throttle category) are being executed at the same time and not queued correctly. This leads to SVN locks (one project detects the lock, wants to clean and re-checkout SVN repository, others fail etc.). This started happening with 1.607 and is still present in 1.609. Reverting back to 1.606 fixes the problem. Not sure, if an update to the Throttle Concurrent Builds Plugin is needed or if this is a core issue. Environment: Jenkins 1.606 - 1.609, Throttle Concurrent Builds Plugin 1.8.4 Project: Jenkins Priority: Major Reporter: Tadej Lasic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27921) Multijob generation failed when upgrading from 1.29 to 1.32
Daniel Spilker commented on JENKINS-27921 Multijob generation failed when upgrading from 1.29 to 1.32 Yes, it's a regression, but one that is probably not going to be fixed. It's a thing you have to be aware of when using loop closures. It also happens for other parts of the DSL, see JENKINS-27492. If you use a for loop, you do not need the workaround because for loops are not implemented by closures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27921) Multijob generation failed when upgrading from 1.29 to 1.32
Daniel Spilker updated JENKINS-27921 Multijob generation failed when upgrading from 1.29 to 1.32 Change By: Daniel Spilker (14/Apr/15 7:46 AM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
dan tran commented on JENKINS-27009 Default versioning mode maven release plugin issue looks like you report to the wrong plugin, there is no such jenkins maven-release-plugin. There are 2 known release plugin that works with Maven, release-plugin and m2-release This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26854) EC2 slave launch stops working after a while with AmazonServiceException Request has expired
Ximon Eighteen commented on JENKINS-26854 EC2 slave launch stops working after a while with AmazonServiceException Request has expired Unfortunately https://github.com/jenkinsci/ec2-plugin/pull/131 has now been closed without merging because the closer thought that ec2-1.27 fixed the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
dan tran commented on JENKINS-27722 upgrade to the release plugin has left the plugin broken @Glen, thanks for the hint by running the release directly via url xxx/release, when I run the scheduler release build, it complains about "missing the Release/Release permission". It is working now since I configure the user with release access. Finally, thank you and thank you. Next is to wait for Daniel to confirm your changes, then you can merge. But I also notice, I dont need configure matrix-plugin with optional=false, i also need to add mailer so here is my list dependency groupIdorg.jenkins-ci.main/groupId artifactIdmaven-plugin/artifactId version2.9/version optionaltrue/optional /dependency dependency groupIdorg.jenkins-ci.plugins/groupId artifactIddashboard-view/artifactId version2.9.4/version optionaltrue/optional /dependency dependency groupIdorg.jenkins-ci.plugins/groupId artifactIdpromoted-builds/artifactId version2.21/version optionaltrue/optional /dependency dependency groupIdorg.jenkins-ci.plugins/groupId artifactIdmatrix-project/artifactId version1.4.1/version optionaltrue/optional /dependency dependency groupIdorg.jenkins-ci.plugins/groupId artifactIdmailer/artifactId version1.9/version optionaltrue/optional /dependency This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [m2release-plugin] (JENKINS-12736) m2release with scm-git seems to ignore username:password in repository URL on release:perform
dan tran updated JENKINS-12736 m2release with scm-git seems to ignore username:password in repository URL on release:perform Change By: dan tran (14/Apr/15 8:14 AM) Component/s: m2release-plugin Component/s: release-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-parameter-plugin] (JENKINS-16290) git parameter plugin doesn't support Jenkins slave setup with git repos checked out only on slaves
Yaron Knochen commented on JENKINS-16290 git parameter plugin doesnt support Jenkins slave setup with git repos checked out only on slaves Any update on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27921) Multijob generation failed when upgrading from 1.29 to 1.32
Geoffroy Jabouley commented on JENKINS-27921 Multijob generation failed when upgrading from 1.29 to 1.32 Hi Daniel Thanks a lot for the explanation. Is this still a regression in the job-dsl plugin, as it was doing fine in prior versions without the "delegate.job" call? Or is this behavior the correct one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Daniel Beck commented on JENKINS-27722 upgrade to the release plugin has left the plugin broken They don't look obviously wrong, but I have no time to dig deeper into this. Just saw the comment I quoted and thought I'd clarify why that is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27722) upgrade to the release plugin has left the plugin broken
Daniel Beck commented on JENKINS-27722 upgrade to the release plugin has left the plugin broken Next is to wait for Daniel to confirm your changes, then you can merge. Sorry, but no. I'm not working on this plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [m2release-plugin] (JENKINS-22339) Enable environment variables for M2 Release Plugin
dan tran updated JENKINS-22339 Enable environment variables for M2 Release Plugin Change By: dan tran (14/Apr/15 8:15 AM) Assignee: PeterHayes Component/s: m2release-plugin Component/s: release-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27926) Allow slash character in login
Jean-Yves CRONIER created JENKINS-27926 Allow slash character in login Issue Type: New Feature Assignee: Unassigned Components: core Created: 14/Apr/15 8:31 AM Description: After following instruction of Jenkins WIKI page "Apache frontend for security", the user's login becomes the Subject Distinguished Name (DN) of the Client X509 Certificate. For ex.: /CN=John DOE/OU=Development Unit/O=ACME/C=US But we can't create the user with this login in Jenkins. User login is transformed into: _CN=John DOE_OU=Development Unit_O=ACME_C=US Project: Jenkins Priority: Major Reporter: Jean-Yves CRONIER This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27709) Release button must honor project auth matrix
dan tran resolved JENKINS-27709 as Not A Defect Release button must honor project auth matrix The latest snapshot does honor release role Change By: dan tran (14/Apr/15 8:05 AM) Status: Open Resolved Assignee: PeterHayes Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27709) Release button must honor project auth matrix
dan tran closed JENKINS-27709 as Not A Defect Release button must honor project auth matrix Change By: dan tran (14/Apr/15 8:05 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [m2release-plugin] (JENKINS-27009) Default versioning mode maven release plugin issue
dan tran updated JENKINS-27009 Default versioning mode maven release plugin issue Change By: dan tran (14/Apr/15 8:10 AM) Component/s: m2release-plugin Component/s: release-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Rasmus Pedersen created JENKINS-27925 Build step is not always saved Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 8:30 AM Description: When changing a build step from a Windows batch command to a Shell command and at the same time puts two hyphens, --, in the shell command, the content of the shell command is not always saved. Steps to reproduce: Create two Windows batch command build steps. Click Save Delete one of the build steps Create a Shell command build step and enter some text in it containing two hyphens, e.g. some text -- some thing Move the just created build step to the top. Click Save What I expected to happen: The content of the Shell command build step is saved. What actually happens: The content isn't saved. I've tried the above method in both Firefox (with addons disabled), IE and Chrome and I've only successfully reproduced it in Firefox (is it a bug in Firefox?). Environment: Jenkins 1.609 Firefox 37.0.1 (started with --safe-mode) Windows 7 Project: Jenkins Priority: Major Reporter: Rasmus Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27927) Use of interface in workflow scripts wont compile
Thomas Dalton
created JENKINS-27927
Use of interface in workflow scripts wont compile
Issue Type:
New Feature
Assignee:
Jesse Glick
Components:
workflow-plugin
Created:
14/Apr/15 12:09 PM
Description:
Since class inheritance is not available to groovy workflow scripts, I thought I'd try some alternatives, so I gave "interfaces" a go instead. I want to specify an interface that provides the templating for a common behavior I want to achieve.
e.g. MyFoo.groovy could implement an interface specified in Foo.groovy. Other scripts e.g. Bar.groovy could then invoke a common interface specified in YourFoo.groovy, MyFoo.groovy, RonaldsFoo.groovy and so on.
In trying out a very simple example of an interface to achieve what I want, the groovy-cps compiler errors.
Here is the valid groovy code that I tried (and works) under a groovy console:
interface Foo {
String name()
}
b = [name: {return "Ronald"}]
a = b as Foo
println a.name()
return
This prints "Ronald" as you'd expect.
The code that I tried in an example workflow, I was hoping could do the same, but does not:
node {
b = [name: {return "Ronald"}]
a = b as Foo
echo a.name()
}
interface Foo {
String name()
}
The error that is thrown when I hit "Apply" after entering the code in the Groovy CPS DSL box is:
javax.servlet.ServletException: java.lang.NullPointerException: Cannot invoke method visit() on null object
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at 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:123)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
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:168)
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
[JIRA] [copyartifact-plugin] (JENKINS-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Paul Holmberg commented on JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) See JENKINS-25111 for a workaround if you are currently blocked by this issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27828) Module Detection
SCM/JIRA link daemon commented on JENKINS-27828 Module Detection Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/util/ModuleDetector.java src/test/java/hudson/plugins/analysis/util/ModuleDetectorTest.java src/test/resources/hudson/plugins/analysis/util/no-name-pom.xml http://jenkins-ci.org/commit/analysis-core-plugin/e7a42b2e48ec27fa0eb4d7d4f743a6f20fd8aaa1 Log: FIXED JENKINS-27828 Use artifact ID as module name if pom defines no name. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27828) Module Detection
Ulli Hafner commented on JENKINS-27828 Module Detection Thanks for checking that. I thought that the ID is used as fallback but seems that I missed that part up to now... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-21886) Push notifications don't work if JOB_NAME variable is in repository URL
Rouke de Jong
commented on JENKINS-21886
Push notifications dont work if JOB_NAME variable is in repository URL
Still applicable, push/merge etc notifications are not working. Changing the repository url to a hard-coded entry works immediately but swapping it back to contain ${JOB_NAME} (which makes templating jobs way easier) fails silently.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Sebastian Schuberth commented on JENKINS-25111 Ability to Copy Artifacts from a Phase Job FYI, for me the patch is working (except that it did not support build filters until 1 was merged just today). You can look at the job config at 2 to see how we're using it. 1 https://github.com/jenkinsci/tikal-multijob-plugin/pull/64 2 https://dscho.cloudapp.net/job/gfw-msys1-test-git-multi-node/configure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [cvs-plugin] (JENKINS-20354) Change log crashes due to -S option not supported by CVS
Nicolas Staelens commented on JENKINS-20354 Change log crashes due to -S option not supported by CVS Is there any update on this issue? I'm also facing the problem with the -S option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Rasmus Pedersen
updated JENKINS-27925
Build step is not always saved
Change By:
Rasmus Pedersen
(14/Apr/15 11:15 AM)
Description:
Whenchangingabuildstepfroma{{Windowsbatchcommand}}toa{{Shellcommand}}andatthesametimeputstwohyphens,{{--}},intheshellcommand,thecontentoftheshellcommandisnotalwayssaved.*Stepstoreproduce:*#Createtwo{{Windowsbatchcommand}}buildsteps.#Click{{Save}}#
Click{{Configure}}#
Deleteoneofthebuildsteps#Createa{{Shellcommand}}buildstepandentersometextinitcontainingtwohyphens,e.g.{noformat}sometext--something{noformat}#Movethejustcreatedbuildsteptothetop.#Click{{Save}}*WhatIexpectedtohappen:*Thecontentofthe{{Shellcommand}}buildstepissaved.*Whatactuallyhappens:*Thecontentisntsaved.IvetriedtheabovemethodinbothFirefox(withaddonsdisabled),IEandChromeandIveonlysuccessfullyreproduceditinFirefox(isitabuginFirefox?).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [multijob-plugin] (JENKINS-25111) Ability to Copy Artifacts from a Phase Job
Paul Holmberg
commented on JENKINS-25111
Ability to Copy Artifacts from a Phase Job
We pulled the change above and rebuilt the plugin but still got 'unable to find job to copy artifact from' errors. We are trying to copy junit test result files from child phases up to the parent job so as to collate build results in one place.
In case someone else is currently blocked by this there is a workaround using the EnvInject plugin. After your build phases have run execute a python build step with the following code. It uses the Jenkins JSON API to create a new file called propsfile containing the build numbers and success/failures of all the child phases that have executed so far as JOB_NAME_BUILD_NUMBER and JOB_NAME_BUILD_SUCCESS (note it replaces hyphens with underscores to avoid invalid environment variables).
#!/usr/bin/env python
import os
import json
import urllib2
url = ""
req = urllib2.Request('%s/api/json' % url, headers = {'Accept' : 'application/json'})
res = urllib2.urlopen(req)
res = json.loads(res.read())
f = open('propsfile', 'w')
try:
buildNumbers = {}
for subbuild in res['subBuilds']:
name = subbuild['jobName'].upper()
name = name.replace('-', '_')
f.write('%s_BUILD_NUMBER=%s\n' % (name, subbuild['buildNumber']))
f.write('%s_BUILD_SUCCESS=%d\n' % (name, subbuild['result'].lower() == 'success'))
finally:
f.close()
Then add a subsequent envinject step to pull the contents of that propsfile in and you can use the resulting environment variables to copy artifacts from the correct triggered child builds. You can also use the build success environment variables and the ConditionalJob plugin to optionally run steps (in the case where you have an early smoke test phase that prevents the lengthy subsequent phases from executing if it fails).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27925) Build step is not always saved
Daniel Beck commented on JENKINS-27925 Build step is not always saved If you press the 'Back' button between step 2 and 3, that's the problem. Don't ever 'Go Back' to a config form in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved I didn't I clicked Configure (I've updated the description). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms updated JENKINS-27929 Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Description: ExtendparametersupportonarchiveArtifactstocover allowEmptyArchive fingerprintonlyIfSuccessful This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms assigned JENKINS-27929 to Mark Syms Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Assignee: DanielSpilker MarkSyms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-27930) Consider plugins's dependencies as triggers for building a maven project
Victor Noël created JENKINS-27930 Consider pluginss dependencies as triggers for building a maven project Issue Type: Improvement Assignee: Unassigned Components: maven-plugin Created: 14/Apr/15 1:32 PM Description: Hi, When using the option to trigger builds of jobs when one of its dependency has been rebuilt, the dependencies of the plugins are not used. For example I have one project A that uses the antrun maven plugin, and in the plugins dependency section we refer to project B. When a new SNAPSHOT version of project B is built, project A is not triggered for building as one would expect. Thank you Environment: maven 3.2.2 and jenkins 1.606 Project: Jenkins Priority: Major Reporter: Victor Noël This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [junit-plugin] (JENKINS-27931) stdout/stderr are truncated even on failing test
Alex V
updated JENKINS-27931
stdout/stderr are truncated even on failing test
Change By:
Alex V
(14/Apr/15 1:49 PM)
Description:
Atestclasswithmanytestsinitmayproducelargelogsonstdout.Inthatcase,ifthereisatestfailingwithinthistestclass,Iwouldhaveexpectedthattheentirestdoutoutputiskeptbyjunitplugin.Butitistruncated.{code}...[truncated1051034chars]...{code}Thisseemstobevoluntary:https://github.com/jenkinsci/junit-plugin/commit/5f7513baff89516cd7217ea39101ad67116cd059Itotallyunderstandtheneedofdiscarddatafortestssucceed.Howeverforfailingtests,itmakesalmostimpossibletofindthecauseoffailure.Besides,itcontradictsthedocumentationoftheoption{{Retainlongstandardoutput/error}}whichstates:{panel}Ifchecked,anystandardoutputorerrorfromatestsuitewillberetainedinthetestresultsafterthebuildcompletes.(Thisrefersonlytoadditionalmessagesprintedtoconsole,nottoafailurestacktrace.){color:red}Suchoutputisalwayskeptifthetestfailed{color},butbydefaultlengthyoutputfrompassingtestsistruncatedtosavespace.Checkthisoptionifyouneedtoseeeverylogmessagefromevenpassingtests,butbewarethatJenkinssmemoryconsumptioncansubstantiallyincreaseasaresult,evenifyouneverlookatthetestresults!{panel}Isthatpossibletoatleastmakethisconfigurable
.
?
Inmyworkflow,theidealwouldbetocompletelydiscardpassingtestslogs,andkeepalloffailingones.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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] [maven-plugin] (JENKINS-27686) Password Paramater in Maven project is sent build as stars instead real value
João Luís commented on JENKINS-27686 Password Paramater in Maven project is sent build as stars instead real value In Freestyle project, did you used a shell script step to invoke mvn or an Invoke top level maven target step? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [junit-plugin] (JENKINS-27931) stdout/stderr are truncated even on failing test
Alex V created JENKINS-27931 stdout/stderr are truncated even on failing test Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 14/Apr/15 1:48 PM Description: A test class with many tests in it may produce "large" logs on stdout. In that case, if there is a test failing within this test class, I would have expected that the entire stdout output is kept by junit plugin. But it is truncated. ...[truncated 1051034 chars]... This seems to be voluntary: https://github.com/jenkinsci/junit-plugin/commit/5f7513baff89516cd7217ea39101ad67116cd059 I totally understand the need of discard data for tests succeed. However for failing tests, it makes almost impossible to find the cause of failure. Besides, it contradicts the documentation of the option Retain long standard output/error which states: If checked, any standard output or error from a test suite will be retained in the test results after the build completes. (This refers only to additional messages printed to console, not to a failure stack trace.) Such output is always kept if the test failed, but by default lengthy output from passing tests is truncated to save space. Check this option if you need to see every log message from even passing tests, but beware that Jenkins's memory consumption can substantially increase as a result, even if you never look at the test results! Is that possible to at least make this configurable. In my workflow, the ideal would be to completely discard passing tests logs, and keep all of failing ones. Environment: Jenkins 1.609 Junit plugin 1.5 Project: Jenkins Labels: stdout truncation Priority: Major Reporter: Alex V This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27927) Some interface idioms do not work in Groovy CPS
Jesse Glick updated JENKINS-27927 Some interface idioms do not work in Groovy CPS Yet another exotic Groovy syntax which is apparently not yet supported by groovy-cps. I would suggest sticking to more conservative Java-like idioms which are more likely to work. Change By: Jesse Glick (14/Apr/15 1:46 PM) Summary: Useof Some interface idiomsdonotwork in workflowscriptswontcompile GroovyCPS Issue Type: NewFeature Bug Assignee: JesseGlick KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27929) Allow archiveArtifacts to specify all parameters
Mark Syms started work on JENKINS-27929 Allow archiveArtifacts to specify all parameters Change By: Mark Syms (14/Apr/15 1:31 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-27932) Pull Request Publisher
Victor Cabello created JENKINS-27932 Pull Request Publisher Issue Type: New Feature Assignee: Victor Cabello Components: job-dsl-plugin Created: 14/Apr/15 1:52 PM Description: The pull request builder plugin has a nice feature that allows to merge the branch in GitHub if the build was successful, unfortunately the job dsl plugin does not have the syntax to can configure the merge process. I could be a useful feature to configure the Pull Request Merge publish from job dsl. Project: Jenkins Priority: Minor Reporter: Victor Cabello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26158) Active Directory authentication for Subversion plugin fails
Benny Prange
commented on JENKINS-26158
Active Directory authentication for Subversion plugin fails
I'm having the same issue. My workaround is to use exec in ant and call svn directly from commandline. Eg:
exec executable="svn"
arg line="checkout --non-interactive --trust-server-cert --username ${svn.user} --password ${svn.psw} ${svn.url} ${param.dep.dest}" /
/exec
Nevertheless I would love to see this bug fixed.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27937) Archives of Workspaces / Artifacts don't preserve extended attributes (like 'executable') although the Zip format supports it
Andreas Kotes created JENKINS-27937 Archives of Workspaces / Artifacts dont preserve extended attributes (like executable) although the Zip format supports it Issue Type: Improvement Assignee: Unassigned Components: core Created: 14/Apr/15 4:38 PM Description: Zips would support including extended attributes like the executable bit of files - this currently isn't done, so when a zipfile of a folder is downloaded, shell scripts stop being executable after unzipping Project: Jenkins Labels: archive workspace artifact artifact-download zip zipfile Priority: Minor Reporter: Andreas Kotes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [fitnesse-plugin] (JENKINS-27938) Unable to expand collapsed SLIM tables
Serge Zukov created JENKINS-27938 Unable to expand collapsed SLIM tables Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:41 PM Description: New styling added in the latest FitNesse plugin makes SLIM tables appear as collapsed inside captured details, however there is no way to expand them. It seems like FitNesse plugin is missing some essential java-script to allow those tables behave same way they do in FitNesse. Another option is that java-script is included but unable to interact with elements inside Jenkins page. Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27939) DefaultJnlpSlaveReceiver should return true when rejecting a takeover.
David Hoover created JENKINS-27939 DefaultJnlpSlaveReceiver should return true when rejecting a takeover. Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Apr/15 4:48 PM Description: See https://github.com/jenkinsci/jenkins/pull/1649 In summary: JnlpAgentReceiver is documented as returning true after calling handshake.error() in case of failure to indicate that the receiver DID claim this node but had issues, but DefaultJnlpSlaveReceiver returns false. https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/slaves/JnlpSlaveAgentProtocol2.java#L56-61 loops over all receivers until one claims it, so this is giving other receivers a chance at a node they shouldn't grab since the receiver wanted it but couldn't grab it. Assuming no others do, it also then continues on and gives the erroneous log message about not recognizing the node's name. Project: Jenkins Priority: Minor Reporter: David Hoover This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [clearcase-ucm-plugin] (JENKINS-26985) Poll rebase functionality (case 12578)
Mads Nielsen resolved JENKINS-26985 as Fixed Poll rebase functionality (case 12578) Change By: Mads Nielsen (14/Apr/15 2:44 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Daniel Beck commented on JENKINS-27925 Build step is not always saved Interesting. Does this work for newly created projects? Are they freestyle projects? Are any errors shown in the JS console of your browser? In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? Is this reproducible 100% of the time, or only sometimes? Are the two original Windows batch commands empty, or do they contain text? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s commented on JENKINS-23958 Pipe Broken It's not clear to me how this is different from JENKINS-22492 since they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Anyway, we are having the broken pipe issue as well. Details: Linux master (Ubuntu) Unity builds occur on remote Mac OSX slaves Jenkins v1.607 Unity3d plugin v0.7 I'm here today because I feel like after our recent Jenkins update to 1.607 this error has started occurring more frequently, however I can't say for certain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [fitnesse-plugin] (JENKINS-27940) Consider using jUnit output from FitNesse
Serge Zukov created JENKINS-27940 Consider using jUnit output from FitNesse Issue Type: New Feature Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:54 PM Description: In addition to XML format current version of FitNesse supports jUnit format output. It is very basic at this point (but could expended). Environment: FitNesse plugin 1.12 Jenkins 1.600 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken Ben, It's not clear to me how this is different from JENKINS-22492 since they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Let's fix both then Do you happen to have a reliable way to reproduce this ? If not, have you tried to create one ? Is your job long running ? Do you use the -logFile option ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s commented on JENKINS-23958 Pipe Broken Unfortunately I don't have any specific way to reproduce it. Most of our jobs are rather long, however. In fact when a job undergoes a fresh import into a new workspace, the likelihood of this error occurring seems to increase. The larger the project (the more assets) the more frequent. It often happens after Unity lists "Used Assets, sorted by uncompressed size:" 0.0 kb 0.0% Assets/Resources/path/to/some/file1 0.0 kb 0.0% Assets/Resources/path/to/some/file2 Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) But it also occurs in other points in time: Unloading 0 unused Assets to reduce memory usage. Loaded Objects now: 488. Total: 1.677543 ms (FindLiveObjects: 0.061794 ms CreateObjectMapping: 0.023056 ms MarkObjects: 1.508662 ms DeleteObjects: 0.005961 ms) Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) And: DisplayProgressbar: Android build DisplayProgressbar: Fetching assembly references DisplayProgressbar: Creating staging area DisplayProgressbar: Rebuilding resources DisplayProgressbar: Compiling resources DisplayProgressbar: Creating streaming package DisplayProgressbar: Creating asset package DisplayProgressbar: Creating APK package Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(PipedInputStream.java:322) at java.io.PipedInputStream.read(PipedInputStream.java:378) at java.io.InputStream.read(InputStream.java:101) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) All of the above are taken from completely separate projects. And yes, all of our jobs use the -logFile option -batchmode -quit -logFile "$WORKSPACE/unity.log" -projectPath $WORKSPACE -executeMethod Foo.bar I've never seen the error occur more than once per build, and it never seems to cause the build to fail, but if something else causes the build to fail it can be a serious red herring. After the "pipe broken" error, the Jenkins log picks up with the next immediate build step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27917) Stack Trace when Checking for Updates
Mark Nejman commented on JENKINS-27917 Stack Trace when Checking for Updates The problem here is that this requires an assumption such as 'all invalid JSON responses are due to no proxy being set up', something I doubt is reasonably accurate. There can be any number of reasons. (In fact, the redirect seems to be fairly braindead to me, as it'll break all kinds of tools not used interactively. It should at least set some HTTP error code in the response so automated tools know to fail.) Do you think it would it help to wrap the error in a more generic 'failed to parse JSON update center metadata', and maybe show an excerpt of the data? Yes, I understand, you don't want to write error messages that are guessing what the issue is. I do think your proposed error message would be clear though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [publish-over-ssh-plugin] (JENKINS-27703) Failure to connect - jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: TheKey]
Chadwick Bushnell commented on JENKINS-27703 Failure to connect - jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: TheKey] Worked perfectly. Thank you so much. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [repo-plugin] (JENKINS-23262) Permission denied when using repo plugin with ssh-agent plugin
Geert Pante commented on JENKINS-23262 Permission denied when using repo plugin with ssh-agent plugin I have the same issue, even when my passphrase is empty. I think it's got to do with how ssh-agent works: http://www.snailbook.com/faq/about-agent.auto.html The ssh-agent injects variables into the environment, which can be picked up by other processes within the same session. The repo plugin probably does not run in the same session as the SSH Agent plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [fitnesse-plugin] (JENKINS-27936) When few FitNesse test results being published in a single job they renamed into Summary
Serge Zukov created JENKINS-27936 When few FitNesse test results being published in a single job they renamed into Summary Issue Type: Bug Assignee: Unassigned Components: fitnesse-plugin Created: 14/Apr/15 4:33 PM Description: Expected: Test name for published test results to always match content of rootPath. Actual: When job contains more than one FitNesse test results published then test name appears as "Summary". Steps to reproduce: Given you have two test suites: TestSuite1 and TestSuite2 In a single job run TestSuite1 and produce TestSuite1.xml Run TestSuite2 and produce TestSuite2.xml Publish FitNesse tests using *.xml as a mask Upon execution FitNesse test results (and test history) will contain Summary as test name. P.S. Same would occur if you use copy artifacts plugin to collect all FitNesse XML files into a single job and publish them simultaneously. Environment: Jenkins ver. 1.608; FitNesse Plugin 1.12 Project: Jenkins Priority: Minor Reporter: Serge Zukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-19752) Download build artifacts as zip generates a corrupted file
Andreas Kotes commented on JENKINS-19752 Download build artifacts as zip generates a corrupted file btw: I also noticed that extended attributes (like an executable bit) are not preserved in those archives This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-19752) Download build artifacts as zip generates a corrupted file
Andreas Kotes edited a comment on JENKINS-19752 Download build artifacts as zip generates a corrupted file btw: I also noticed that extended attributes (like an executable bit) are not preserved in those archives (created JENKINS-27937) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED
Peter Buckley commented on JENKINS-10406 Maven Jobs with build modules in parallel always ABORTED I see (I think related?) issues with the "build modules in parallel" using 1.580.1. Symptoms can vary as any of the following: 1. sub-module builds don't report back (some sub-modules show up as "didn't run" but they did run) 2. overall build status is UNSTABLE and shows "No test failures" but sub-modules have test failures 3. a few sub-module builds are from build #2160 (a non-existent build) but the overall build was #2159 It would be great to get this "build modules in parallel" feature working well, it would be a more useful feature if it were stable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [urltrigger-plugin] (JENKINS-27941) Proxy user cannot be empty even if the proxy does not require authentication
Dave Hunt created JENKINS-27941 Proxy user cannot be empty even if the proxy does not require authentication Issue Type: Bug Assignee: Gregory Boissinot Components: urltrigger-plugin Created: 14/Apr/15 6:08 PM Description: When checking the box to use the Jenkins proxy, polling fails if a username is not defined, even if the proxy does not require authentication. Project: Jenkins Priority: Minor Reporter: Dave Hunt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. won't I lose the ability to specify env variables if I uninstall that plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [envinject-plugin] (JENKINS-27496) NPE during submission of EnvInject JobProperty when the formis empty
Oleg Nenashev resolved JENKINS-27496 as Fixed NPE during submission of EnvInject JobProperty when the formis empty 1.91.2 has been released today. Marking as fixed Change By: Oleg Nenashev (14/Apr/15 3:13 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
ben s edited a comment on JENKINS-23958 Pipe Broken It's not clear to me how this is different from JENKINS-22492 since they both appear to be identical according to the descriptions. I'm not sure which one I should watch, so I'm watching both Anyway, we are having the broken pipe issue as well. Details: Linux master (Ubuntu) Unity builds occur on remote Mac OSX slaves Jenkins v1.607 Unity3d plugin v0.7 Various Unity versions: 3.5.7, 4.5.4, 4.6.4. Doesn't seem to make a difference. I'm here today because I feel like after our recent Jenkins update to 1.607 this error has started occurring more frequently, however I can't say for certain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon created JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Issue Type: Bug Assignee: Unassigned Components: slack-plugin Created: 14/Apr/15 4:15 PM Description: For some reason, on a few of our Jenkins servers, the Slack 1.7 plugin fails to post messages to the slack channel. We have had to revert to version 1.2 of the plugin. In comparing the project configs and the console logs, there is no apparent reason for this. This is with projects we have imported onto these machines from older machines. New projects created after the 1.7 plugin was installed seem to post just fine. The new machines are all behind a proxy server. Not sure if that makes a difference. However, since newly created jobs seem to use the Slack 1.7 plugin just fine, it is probably a red herring. Environment: Ubuntu 14.04.2 Jenkins 1.596.1 Slack Plugin 1.7 Project: Jenkins Priority: Minor Reporter: M Chon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27928) environment variable changes are not applied.
marlene cote updated JENKINS-27928 environment variable changes are not applied. Change By: marlene cote (14/Apr/15 2:42 PM) Environment: jenkinsserver- windows server2008R2SP164bitjenkinsclient - windowsserver2008R2SP164bit jenkins server version1.608 recentlyupgradedfrom1.598Ihavenottriedtodowngradebecausetheteamswerenotchangingthisvariablebeforenoweither.multiplebrowserstried,noeffect.firefoxv-37.0.1,IEv10windowsinstallerusedslavesinstalledviwebpage-windowsserviceinstalled-startedviajavawebstartjavaonserver-standardedition7_6732bitjavaonclient-standardedition7_6732bitsysteminfopagedatabelow. Description: Whenchanginganexistingnodeenvironmentvariable (%JENKINS_BUILD_REPOSITORY%) valueinthenodesconfigurationdialog,thechangeisnotapplied.LookingatthesystemInfoofthenodeshows,thatthevariablestillhasgottheoldvalue.AlsoreloadingtheJenkinsconfigurationfromdiskdidnothelp.Theonlythingthatseemstohelpisarebootofthejenkinsserver.Restartingtheslaveisntenough.
[JIRA] [core] (JENKINS-27928) environment variable changes are not applied.
marlene cote edited a comment on JENKINS-27928 environment variable changes are not applied. won't I lose the ability to specify and use env variables if I uninstall that plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton
commented on JENKINS-27927
Some interface idioms do not work in Groovy CPS
I'm glad the intention is aligned with the desire to have these groovy language features available and understand that support for interface will require work in the groovy CPS.
In the short term though, is there a recommended workaround that could provide some interface like equivalent? Or is it just not possible to do anything like this at this stage?
Perhaps pass HashMaps of Closures between the top level "classes" as per
https://github.com/jenkinsci/workflow-plugin/blob/master/cps-global-lib/README.md#writing-shared-code
e.g.
org/foo/Zot.groovy
package org.foo
// Closures define the interface for Zot
Closure show
Closure name
def specify_interface (Hashmap hm) {
this.show = hm["show"]
this.name = hm["name"]
}
flow.groovy
node {
def z = new org.foo.Zot()
z.specify_interface(["show": { echo "Hello" }, "name": { return "Bernard" }])
// you can then pass z around beyond the scope of flow.groovy
z.show()
echo z.name()
}
Or is there a more elegant way within the constraints of what is and what is not possible today?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27928) environment variable changes are not applied.
marlene cote commented on JENKINS-27928 environment variable changes are not applied. I need to schedule the restart of jenkins to finish the uninstall of the plugin.. I will get back to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27928) environment variable changes are not applied.
Daniel Beck commented on JENKINS-27928 environment variable changes are not applied. Does the same issue occur without envinject? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Dwane Pottratz commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I am currently seeing this issue. Jenkins 1.609 with Throttle 1.8.4 I have read that 'Priority Sort Plugin' can cause issues with Throttle. I have Priority 2.9. I have tried several different configurations. I don't see anything that is working. I think that throttling per project is working but have not been able to confirm it. I have tired setting the max per label. I have tried without setting a max per label. Nothing seems to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon updated JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Change By: M Chon (14/Apr/15 4:18 PM) Description: Forsomereason,onafewofourJenkinsservers,theSlack1.7pluginfailstopostmessagestotheslackchannel.Wehavehadtoreverttoversion1.2oftheplugin.Incomparingtheprojectconfigsandtheconsolelogs,thereisnoapparentreasonforthis.Thisiswithprojectswehaveimportedontothesemachinesfromoldermachines.Newprojectscreatedafterthe1.7pluginwasinstalledseemtopostjustfine.Thenewmachinesareallbehindaproxyserver.Notsureifthatmakesadifference.However,sincenewlycreatedjobsseemtousetheSlack1.7pluginjustfine,itisprobablyaredherring. Imhappytocollectdebugdataifyoucanprovideanysuggestions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [slack-plugin] (JENKINS-27935) Slack plugin 1.7 fails to post to channel; had to revert to 1.2
M Chon updated JENKINS-27935 Slack plugin 1.7 fails to post to channel; had to revert to 1.2 Change By: M Chon (14/Apr/15 4:18 PM) Description: Forsomereason,onafewofourJenkinsservers,theSlack1.7pluginfailstopostmessagestotheslackchannel.Wehavehadtoreverttoversion1.2oftheplugin.Incomparingtheprojectconfigsandtheconsolelogs,thereisnoapparentreasonforthis.Thisiswithprojectswehaveimportedontothesemachinesfromoldermachines.Newprojectscreatedafterthe1.7pluginwasinstalledseemtopostjustfine.Thenewmachinesareallbehindaproxyserver.Notsureifthatmakesadifference.However,sincenewlycreatedjobsseemtousetheSlack1.7pluginjustfine,itisprobablyaredherring.Imhappytocollectdebugdataifyoucanprovideanysuggestions fordoingso . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27905) stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
Thomas Dalton
commented on JENKINS-27905
stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
A stage within parallel could be a common use-case for CI. For example, a given workflow may need multiple builds as well as multiple independent tests, all of which could run in parallel on the same server - each of these flows could easily benefit from having stages.
You could work around this by defining flows for each of the parallel builds, and then kicking these off e.g.
parallel([build_1: {build job: "FooFlow"}, build_2: {build job: "BarFlow"}])
Where FooFlow and BarFlow could identify their own stages, but this would require further setup on the jenkins server, more jobs to configure, and detract from the usefulness of the workflow-plugin to do this programmatically.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27928) environment variable changes are not applied.
Daniel Beck
commented on JENKINS-27928
environment variable changes are not applied.
Node specific env vars ("environment variables, list of key-value pairs") are a core feature.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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-27927) Some interface idioms do not work in Groovy CPS
Jesse Glick commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS Sure, the intention is to support all Groovy language features, but there is a way to go before we get there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [_test] (JENKINS-27934) Can not add promotion process named 'Closed Beta'
Andrei Petrov created JENKINS-27934 Can not add promotion process named Closed Beta Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 14/Apr/15 4:10 PM Description: 1. Create new Multi-Configurational project from the template 2. Add promotion process called 'Closed beta' 3. You will get an exception as described below A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.IllegalArgumentException: Job Closed beta already exists at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) Project: Jenkins Priority: Critical Reporter: Andrei Petrov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Alex Earl commented on JENKINS-23271 Intermittent Invalid Object ID in remoting module This happens intermittently for me. Jenkins 1.596.2 Windows 2012 R2 (64-bit) master Windows 7 (32bit) slave Java: Oracle 1.8 java.lang.IllegalStateException: Invalid object ID 182 iota=183 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:354) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:604) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:317) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ..remote call to vme-sv-exe-d12(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:179) at com.sun.proxy.$Proxy73.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.Launcher$ProcStarter.join(Launcher.java:388) at org.jenkinsci.plugins.managedscripts.ScriptBuildStep.perform(ScriptBuildStep.java:177) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: java.lang.Exception: Object was recently deallocated #182 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.init(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:600) at hudson.remoting.Channel.export(Channel.java:591) at hudson.remoting.Channel.export(Channel.java:561) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) Released at Tue Apr 14 17:19:36 MST 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:382) at hudson.remoting.Channel.unexport(Channel.java:612) at hudson.remoting.UnexportCommand.execute(UnexportCommand.java:43) at hudson.remoting.Channel$2.handle(Channel.java:483) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command hudson.remoting.UnexportCommand@17b6a6d created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at
[JIRA] [tfs-plugin] (JENKINS-23033) TFS Password visible in view source
Olivier Dagenais closed JENKINS-23033 as Fixed TFS Password visible in view source Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-10629) Tar implimentation can't handle 8GB and doesn't error out.
dogfood commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. Integrated in jenkins_main_trunk #4082 Result = SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-23344) TFS plugin does not create label as trigger value is not saved in config
Olivier Dagenais closed JENKINS-23344 as Fixed TFS plugin does not create label as trigger value is not saved in config Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:22 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-3002) TFS Support to get labels
Olivier Dagenais closed JENKINS-3002 as Fixed TFS Support to get labels Fixed in version 3.2.0 Change By: Olivier Dagenais (15/Apr/15 2:23 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27928) environment variable changes are not applied.
Daniel Beck resolved JENKINS-27928 as Duplicate environment variable changes are not applied. It looks like you're using a plugin (Tikal Multijob) with a hard dependency on env-inject. That was unexpected, sorry about that. That said, this looks a lot like JENKINS-27739, so resolving as duplicate. Feel free to help investigate the cause over there. Change By: Daniel Beck (15/Apr/15 4:23 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Daniel Beck commented on JENKINS-27925 Build step is not always saved The json argument looks fine, first the shell, then the batch. And after submitting that, the job still contains two batch build steps? There have been no warnings logged in /log/all? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8
Daniel Beck commented on JENKINS-27947 JDK 1.6 maven builds fail when running on Tomcat 8 JENKINS-25272? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Daniel Beck commented on JENKINS-27944 Auto-installer list not populating on Ubuntu Server Force an update of the update center metadata by clicking 'Update Now' in the Advanced tab of Manage Plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [unity3d-plugin] (JENKINS-23958) Pipe Broken
lacostej commented on JENKINS-23958 Pipe Broken As indicated earlier, I posted a message on the dev list: https://groups.google.com/d/msg/jenkinsci-dev/LjHaBd6yUW8/LstWtVCaOHwJ But I didn't get feedback. I am considering to start patching the remoting lib to get more debugging. I don't understand why the pipe gets broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Daniel Beck commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value If BUILD_TIMESTAMP is a Jenkins variable, why can't it be used directly (without using the Zentimestamp plugin). That variable is not provided by Jenkins core. It's not defined without Zentimestamp. Jenkins core changed the storage format and therefore the format of the BUILD_ID variable contents. If you were using it for something other than a reference to the build folder name (e.g. to indicate start date and time of a build), you now need to switch to using BUILD_TIMESTAMP provided by Zentimestamp, or determine the date on your own (some solutions provided in comments above). The recent change in core was a documentation fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [release-plugin] (JENKINS-27942) MAven release build from jenkins using release plugin + Accurev as source code
Karthic Bala updated JENKINS-27942 MAven release build from jenkins using release plugin + Accurev as source code Change By: Karthic Bala (14/Apr/15 6:23 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27928) environment variable changes are not applied.
Daniel Beck commented on JENKINS-27928 environment variable changes are not applied. Please include the information requested in the wiki at https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue as I wrote in JENKINS-14801. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27905) stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
Jesse Glick resolved JENKINS-27905 as Not A Defect stage concurrency allows 1 thread to be blocked at a time, others fail and hang job Change By: Jesse Glick (14/Apr/15 1:58 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [freestyle-multibranch-plugin] (JENKINS-27915) Oops and stack trace configuring a new freestyle multibranch job with Jenkins 1.609
Jesse Glick resolved JENKINS-27915 as Not A Defect Oops and stack trace configuring a new freestyle multibranch job with Jenkins 1.609 Wrong plugin. You are looking for: https://github.com/mjdetullio/multi-branch-project-plugin/issues Change By: Jesse Glick (14/Apr/15 1:58 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27916) GString not flattened to String by DSL inside a map
Jesse Glick updated JENKINS-27916 GString not flattened to String by DSL inside a map Workaround (untested): unarchive mapping: ['' + requiredFile: '.'] Change By: Jesse Glick (14/Apr/15 2:01 PM) Summary: Unable GStringnotflattened to passvariabletofilepathelementofunarchive StringbyDSLinsidea map Labels: groovy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27905) stage concurrency allows 1 thread to be blocked at a time, others fail and hang job
Jesse Glick commented on JENKINS-27905 stage concurrency allows 1 thread to be blocked at a time, others fail and hang job stage is not supported inside parallel. Or rather it is legal but pointless, since the list of stages is global to a build, and does not take into account threads. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [mailer-plugin] (JENKINS-27933) mailer-plugin does not support mail adresses without an @-sign anymore
Patric Rufflar created JENKINS-27933 mailer-plugin does not support mail adresses without an @-sign anymore Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 14/Apr/15 2:08 PM Description: The mailer-plugin does not support mail adresses without an '@' anymore (assuming that a default mail suffix has not been configured). While this is reasonable for internet email traffic, internal/local mail adresses like 'jenkins-ci' might be perfectly valid. This is caused by jenkins.plugins.mailer.tasks.MimeMessageBuilder.toNormalizedAddress(String) which returns null in such cases. Project: Jenkins Priority: Major Reporter: Patric Rufflar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko commented on JENKINS-26726 java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Sorry for a delay. I was trying to reproduce this one again with no luck. It seems like a 3rd party plugin caused this behaviour originally and probably it has been fixed on their side. Closing this issue for now, will reopen in case of luck with reproducing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton commented on JENKINS-27927 Some interface idioms do not work in Groovy CPS Hi Jesse, Thanks for getting back to me again. The reason I'm looking at the workflow-plugin is because it allows a programmatic interface, and it is potentially a very powerful means to share jenkins job setups across multiple teams and engineers, and even more so if it can work in a way that provides the extensibility and reuse that the groovy language can offer. This means things like class inheritance, interfaces and other OO techniques are desirable and of particular interest to me. Moreover, the flows I'm looking at are inherently quite complex and I would ideally like to generate infra for them that could be used by a number of people/teams - not just copy/pasted. If I go with conservative, I fear I will end up with multiple copies of the same rehashed code for each instance where it is actually used - and that means more places for it to go wrong and maintain. So what would really set the workflow-plugin apart from e.g. a typical multijob setup is the ability to do some of the less "conservative", more "groovy" things Regards, Tom. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [delivery-pipeline-plugin] (JENKINS-26726) java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70)
Dmytro Kryvenko closed JENKINS-26726 as Cannot Reproduce java.lang.StackOverflowError at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:70) Change By: Dmytro Kryvenko (14/Apr/15 2:15 PM) Status: Open Closed Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27925) Build step is not always saved
Rasmus Pedersen commented on JENKINS-27925 Build step is not always saved Q: In the developer tools of your browser, what is the request sent on clicking 'Send' in step 7? A: The request-body: Content-Type: application/x-www-form-urlencoded Content-Length: 5363
[JIRA] [workflow-plugin] (JENKINS-27927) Some interface idioms do not work in Groovy CPS
Thomas Dalton
commented on JENKINS-27927
Some interface idioms do not work in Groovy CPS
Ahh.. in which case I apologies for the miscommunication on my part, I actually tried the Java syntax first - I then reduced the problem to simpler forms to post the issue.
Here is what I tried originally:
interface Foo {
String name()
}
class Bar implements Foo {
def String name() {
return "Ronald"
}
}
node {
b = new Bar()
a = b as Foo
echo a.name()
}
This doesn't work either and the same exception Cannot invoke method visit() on null object is thrown.
Yet under a groovy console:
interface Foo {
String name()
}
class Bar implements Foo {
def String name() {
return "Ronald"
}
}
b = new Bar()
a = b as Foo
println a.name()
It works fine. Hence I think it is likely a problem with all uses of interface and why I'm on the lookout for a decent workaround
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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.
