[JIRA] [core] (JENKINS-3195) Cannot update from 1.286 to 1.287 with update center
Title: Message Title SCM/JIRA link daemon commented on JENKINS-3195 Re: Cannot update from 1.286 to 1.287 with update center Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/67c13dab316130468f101a300a3f0f388b8d6736 Log: Noting JENKINS-30304 and JENKINS-3195 from https://github.com/jenkinsci/jenkins/pull/1908 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30304) Footer hides trend graph links
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30304 Re: Footer hides trend graph links Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/67c13dab316130468f101a300a3f0f388b8d6736 Log: Noting JENKINS-30304 and JENKINS-3195 from https://github.com/jenkinsci/jenkins/pull/1908 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29059) Always display example build times in Build Periodically section
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29059 Re: Always display example build times in Build Periodically section Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/1fa120197155be439f72f765fca49d3cc8f6d7a1 Log: Noting JENKINS-29059 from https://github.com/jenkinsci/jenkins/pull/1941 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-31776) Extract online-node CLI command from Core to CLI
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31776 Re: Extract online-node CLI command from Core to CLI Code changed in jenkins User: Oleg Nenashev Path: changelog.html http://jenkins-ci.org/commit/jenkins/d3e3c57af098ad337ef7fc26aa45ce99372f10bc Log: Noting JENKINS-31776 from https://github.com/jenkinsci/jenkins/pull/1938 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31954) Fail to set GIT Source Code Management
Title: Message Title Nico Bollen updated an issue Jenkins / JENKINS-31954 Fail to set GIT Source Code Management Change By: Nico Bollen Environment: Debian, Jenkins 1.640 , gitlab-plugin 1.1.28, git-plugin 2.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing), an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose reusing throwing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title Jon Cairns commented on JENKINS-31943 Re: Meme generator plugin is broken Thanks for reporting this. It's been a long time since I've done anything on the plugin, so I'll familiarise myself with the code again and try and get the API call fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31321) Renaming a node over another is possible and destroys both configurations
Title: Message Title Christopher Simons edited a comment on JENKINS-31321 Re: Renaming a node over another is possible and destroys both configurations When attempting to create a new node with the same name as an existing node (rather than editing) , an error page is rendered with the message "Error: Slave called ‘foo’ already exists" and HTTP status 400. I'd propose rendering the reusing this same error message upon trying to rename a node over another existing node.Fixed in [PR #1949|https://github.com/jenkinsci/jenkins/pull/1949]. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-31954) Fail to set GIT Source Code Management
Title: Message Title Nico Bollen created an issue Jenkins / JENKINS-31954 Fail to set GIT Source Code Management Issue Type: Bug Assignee: Mark Waite Components: git-plugin, gitlab-plugin Created: 08/Dec/15 7:55 AM Environment: Debian, Jenkins 1.640 Labels: exception Priority: Minor Reporter: Nico Bollen After upgrading to v1.640 I get error reports after enabling the GIT Source Code Management and trying to save a job. Add Comment
[JIRA] [git-parameter-plugin] (JENKINS-31939) The top value is better to be chosed by default of to have such option
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-31939 The top value is better to be chosed by default of to have such option Issue Type: Improvement Assignee: Niklaus Giger Components: git-parameter-plugin Created: 07/Dec/15 1:36 PM Priority: Major Reporter: Viachaslau Kabak It would be good to have an option or setting the most top of results to be chosen by default. Add Comment This message was sent by Atlassian JIRA
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Jesse Glick commented on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds I do not think the user should be forced to pick a number, it should just show information from builds in the currently displayed time window. If you do not scroll, no more work is performed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Félix Belzunce Arcos edited a comment on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds [~jglick] If auto refresh is enabled, then it will be all the time doing the costly operation all the time , right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Andrew Bayer commented on JENKINS-29881 Re: WorkflowRun.getChangeSets should skip empty changesets Gotcha. That should be pretty simple. I'll try to bang that out today. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" On the unstash side - what seems, again at first glance, most reasonable is to actually add it as an option to stash, which probably means either adding options for flatten to DirScanner.Glob (and therefore DirScanner.Full for the optimization case?) first, or I guess writing a new DirScanner implementation extending DirScanner.Glob? Not sure. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title
Jesse Glick commented on JENKINS-29780
Re: unarchive should support "Flatten directories"
I do not think you need API changes to ArtifactManager. archive already takes a map of source path vs. target path. You need merely prepend something here such as:
if (isFlatten()) {
Map flattened = new LinkedHashMap<>();
for (Map.Entry deep : files.entrySet()) {
if (flattened.put(deep.getKey().replaceFirst(".+/", "")) != null) {
throw new AbortException("not unique");
}
}
files = flattened;
}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2-plugin] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Title: Message Title Kanstantsin Shautsou stopped work on JENKINS-17957 Change By: Kanstantsin Shautsou Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-31941) Got a 503/cancel when Jenkins sends a message to Google Hangout
Title: Message Title Julien Palard created an issue Jenkins / JENKINS-31941 Got a 503/cancel when Jenkins sends a message to Google Hangout Issue Type: Bug Assignee: Unassigned Components: jabber-plugin Created: 07/Dec/15 1:45 PM Environment: Jenkins 1.639, jabber notifier plugin 1.35 Priority: Minor Reporter: Julien Palard XMPP connection seems up and running, but messages can't be sent. Here are some redacted logs for readability: SENT: RECV: RCV PKT: RECV: 41187abf8d69378ae881bd8e45839878553fdbbf RCV PKT: 41187abf8d69378ae881bd8e45839878553fdbbf RECV: SENT: RECV: RCV PKT: RECV: SENT: RECV: RCV PKT: SENT: Working: 1 out of 5 executors are busy.1awayjenkins.42 RECV: SENT: Project p build #71: SUCCESS in 3 min 6 sec: https://jenkins.example.com/job/p/71/ samuel: Player: enable groupredacted RECV: Project p build #71: SUCCESS in 3 min 6 sec: https://jenkins.example.com/job/p/71/ samuel: Player: enable groupredacted Obviously I accpeted the Jenkins account in my google account, and already chatted between jenkins (logged on a browser) and me to test them. I suspect that it's just Google refusing messages without telling us why, but why...
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-31769 Re: sh steps on slaves randomly hang when complete And this does not reproduce consistently enough to inspect logs during a workday I suppose? You could either create a custom build of support-core that makes this and/or this larger (or determined by configurable system property—if so, please submit a PR), or configure your servlet container to capture logs if that is possible (depends on the container I think). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-29780 unarchive should support "Flatten directories" Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Félix Belzunce Arcos commented on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds Jesse Glick If auto refresh is enabled, then it will be all the time doing the costly operation all the time , right? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-31940) Ability to sort on "All Tags" or at least they come presorted.
Title: Message Title Marsel Tadjer created an issue Jenkins / JENKINS-31940 Ability to sort on "All Tags" or at least they come presorted. Issue Type: Improvement Assignee: James Nord Attachments: Screen Shot 2015-11-30 at 10.36.23 AM.png Components: cucumber-testresult-plugin Created: 07/Dec/15 1:37 PM Priority: Minor Reporter: Marsel Tadjer It seems that they come in whatever the json format reports it in, while I have some control over the feature execution the tags appear in not a very organized order. If there is a way to sort these this would greatly help the feature, and help us discover discrepancies earlier. Thank you. Add Comment
[JIRA] [publish-over-ssh-plugin] (JENKINS-29360) Bump jsch to fix "Algorithm negotiation failed"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29360 Re: Bump jsch to fix "Algorithm negotiation failed" Code changed in jenkins User: Alex Earl Path: pom.xml http://jenkins-ci.org/commit/publish-over-ssh-plugin/906b3de4552396778a6b0b5cb2ea0b637e19b3a0 Log: Merge pull request #11 from rwegmann/ JENKINS-29360 [FIXED JENKINS-29360] Updated jsch to 0.1.53 Compare: https://github.com/jenkinsci/publish-over-ssh-plugin/compare/b0bcd4f7a60a...906b3de45523 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Ok, once https://github.com/jenkinsci/workflow-plugin/pull/266 is done, I'll get on this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Gotcha. Will look for that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title hannes schluchtmann commented on JENKINS-29077 Re: No selector is shown for installing NodeJS from nodejs.org Hm, thx Daniel Beck. I tried, but I get an error. I'll focus on something else for now I guess. Error: Result: ERROR: Signature verification failed in downloadable hudson.plugins.nodejs.tools.NodeJSInstaller (show details)java.security.cert.CertPathValidatorException: algorithm constraints check failed at sun.security.provider.certpath.PKIXMasterCertPathValidator.validate(PKIXMasterCertPathValidator.java:135) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:219) at sun.security.provider.certpath.PKIXCertPathValidator.validate(PKIXCertPathValidator.java:140) at sun.security.provider.certpath.PKIXCertPathValidator.engineValidate(PKIXCertPathValidator.java:79) at java.security.cert.CertPathValidator.validate(CertPathValidator.java:292) at org.jvnet.hudson.crypto.CertificateUtil.validatePath(CertificateUtil.java:93) at jenkins.util.JSONSignatureValidator.verifySignature(JSONSignatureValidator.java:76) at hudson.model.DownloadService$Downloadable.load(DownloadService.java:370) at hudson.model.DownloadService$Downloadable.updateNow(DownloadService.java:385) at hudson.model.DownloadService$Downloadable$updateNow.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:112) at Script1.run(Script1.groovy:1) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618) at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:142) at hudson.util.RemotingDiagnostics$Script.call(RemotingDiagnostics.java:114) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.util.RemotingDiagnostics.executeGroovy(RemotingDiagnostics.java:111) at jenkins.model.Jenkins._doScript(Jenkins.java:3599) at jenkins.model.Jenkins.doScript(Jenkins.java:3571) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) 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:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at
[JIRA] [xtrigger-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Jesse Glick assigned an issue to Gregory Boissinot Tips Jenkins / JENKINS-31933 Workflow can't be triggered with BuildResultTrigger Change By: Jesse Glick Component/s: xtrigger-plugin Component/s: workflow-plugin Labels: workflow Assignee: Jesse Glick Gregory Boissinot Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message
[JIRA] [subversion-plugin] (JENKINS-27248) List Subversion Tags parameter not available in workflow
Title: Message Title
Christoph Vogtländer commented on JENKINS-27248
Re: List Subversion Tags parameter not available in workflow
It seems that parameters of type ListSubversionTagsParameterValue are not recorded as a groovy variable in a workflow run automatically. But it is possible to get access to the two embedded values "tag" and "tagsDir" using the following code inside a workflow run (assuming the parameter is named "BASE_TAG"):
def BASE_TAG = currentBuild.rawBuild.getAction(hudson.model.ParametersAction).getParameter("BASE_TAG")
println("Tag: ${BASE_TAG.tag}, URL: ${BASE_TAG.tagsDir}")
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Félix Belzunce Arcos commented on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds Manuel Jesús Recena Soto Do you plan to customize the number of builds of buildTimeTrend as well? '0' would mean that you don't want to use the graph so you are sure you don't face any Lazyloading issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-ssh-plugin] (JENKINS-29360) Bump jsch to fix "Algorithm negotiation failed"
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29360 Bump jsch to fix "Algorithm negotiation failed" Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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-29360) Bump jsch to fix "Algorithm negotiation failed"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29360 Re: Bump jsch to fix "Algorithm negotiation failed" Code changed in jenkins User: Raúl Wegmann Path: pom.xml http://jenkins-ci.org/commit/publish-over-ssh-plugin/d849fa71693276ab299276445b9794e17ab115e6 Log: [FIXED JENKINS-29360] Updated jsch to 0.1.53 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-ssh-plugin] (JENKINS-25122) Permanent error message "Either Source files, Exec command or both must be supplied"
Title: Message Title Brian Kotek commented on JENKINS-25122 Re: Permanent error message "Either Source files, Exec command or both must be supplied" Any idea if/when this will be fixed? It's been a problem for over a year, and it's very easy for folks to get confused when they see error messages on every build artifact being transferred. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Durr. I was overthinking. =) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-31751) JaCoCo 2.0.0 plugin shows html instead of coverage report chart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31751 Re: JaCoCo 2.0.0 plugin shows html instead of coverage report chart Code changed in jenkins User: Dominik Stadler Path: src/main/resources/hudson/plugins/jacoco/tags/breakdownMethodsTable.jelly src/main/resources/hudson/plugins/jacoco/tags/breakdownTable.jelly src/main/resources/hudson/plugins/jacoco/tags/summaryMethod.jelly src/main/resources/hudson/plugins/jacoco/tags/summaryTable.jelly http://jenkins-ci.org/commit/jacoco-plugin/c5edf40d484ec11a2ccbc20f73b2c482dbf8c261 Log: Merge pull request #62 from calin-iorgulescu/master JENKINS-31751 : Fix HTML rendering by correctly escaping it in jelly files. Compare: https://github.com/jenkinsci/jacoco-plugin/compare/5c79c7896ba9...c5edf40d484e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-31751) JaCoCo 2.0.0 plugin shows html instead of coverage report chart
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31751 Re: JaCoCo 2.0.0 plugin shows html instead of coverage report chart Code changed in jenkins User: Calin Iorgulescu Path: src/main/resources/hudson/plugins/jacoco/tags/breakdownMethodsTable.jelly src/main/resources/hudson/plugins/jacoco/tags/breakdownTable.jelly src/main/resources/hudson/plugins/jacoco/tags/summaryMethod.jelly src/main/resources/hudson/plugins/jacoco/tags/summaryTable.jelly http://jenkins-ci.org/commit/jacoco-plugin/8651004c738ea37f43932cea0de244d20b16d52f Log: [FIXED JENKINS-31751]: Correctly escape HTML in jelly files. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-31751) JaCoCo 2.0.0 plugin shows html instead of coverage report chart
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31751 JaCoCo 2.0.0 plugin shows html instead of coverage report chart Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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] [cli] (JENKINS-31776) Extract online-node CLI command from Core to CLI
Title: Message Title dogfood commented on JENKINS-31776 Re: Extract online-node CLI command from Core to CLI Integrated in jenkins_main_trunk #4386 JENKINS-31776 CLI command online-node extracted from core to CLI (Revision 809a3c6a61845e1938c0ed0979438af7cf265e97) Result = SUCCESS pjanouse : 809a3c6a61845e1938c0ed0979438af7cf265e97 Files : core/src/main/resources/hudson/model/Messages_it.properties core/src/main/resources/hudson/cli/Messages.properties core/src/main/java/hudson/model/Computer.java core/src/main/resources/hudson/cli/Messages_de.properties core/src/main/resources/hudson/cli/Messages_pt_BR.properties core/src/main/resources/hudson/model/Messages_de.properties core/src/main/resources/hudson/model/Messages_pt_BR.properties core/src/main/resources/hudson/model/Messages_es.properties core/src/main/resources/hudson/cli/Messages_it.properties core/src/main/resources/hudson/cli/Messages_ja.properties core/src/main/resources/hudson/cli/Messages_da.properties core/src/main/resources/hudson/model/Messages.properties test/src/test/java/hudson/cli/OnlineNodeCommandTest.java core/src/main/resources/hudson/model/Messages_da.properties core/src/main/resources/hudson/cli/Messages_es.properties core/src/main/resources/hudson/model/Messages_ja.properties
[JIRA] [core] (JENKINS-31395) On the jenkins homepage the footer scrolls up with the rest of the page
Title: Message Title dogfood commented on JENKINS-31395 Re: On the jenkins homepage the footer scrolls up with the rest of the page Integrated in jenkins_main_trunk #4386 JENKINS-31395 Footer does not work fine in IE11 (Revision 0fc3176a9219133e7c50b6865751a54654a11d76) JENKINS-31395 Footer will be at the bottom of the page (Revision 1219bd1790a9c4864695c649cfa1cc05e7906479) JENKINS-31395 Footer more robust (Revision 9013b290b75d3638203c3b112b2ef2a2cfb31dc4) Result = SUCCESS mrecena : 0fc3176a9219133e7c50b6865751a54654a11d76 Files : war/src/main/webapp/css/style.css mrecena : 1219bd1790a9c4864695c649cfa1cc05e7906479 Files : war/src/main/webapp/css/style.css recena : 9013b290b75d3638203c3b112b2ef2a2cfb31dc4 Files : core/src/main/resources/lib/layout/layout.jelly war/src/main/webapp/css/style.css Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Jesse Glick commented on JENKINS-29780 Re: unarchive should support "Flatten directories" I recall there being some RFE for ArtifactArchiver to flatten directories, but I cannot find it now. Anyway that would address the issue for archive users, since you could just use the step metastep instead with the new option. Then we would only need a flatten option for stash. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27248) List Subversion Tags parameter not available in workflow
Title: Message Title
Christoph Vogtländer edited a comment on JENKINS-27248
Re: List Subversion Tags parameter not available in workflow
It seems that parameters of type ListSubversionTagsParameterValue are not recorded as a groovy variable in a workflow run automatically. But it is possible to get access to the two embedded values "tag" and "tagsDir" using the following code inside a workflow run (assuming the parameter is named " BASE_TAG SVNTAG "):{code}def BASE_TAG SVNTAG = currentBuild.rawBuild.getAction(hudson.model.ParametersAction).getParameter(" BASE_TAG SVNTAG ")println("Tag: ${ BASE_TAG SVNTAG .tag}, URL: ${ BASE_TAG SVNTAG .tagsDir}"){code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-29881 WorkflowRun.getChangeSets should skip empty changesets Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-28946) JIRA support for Workflow jobs
Title: Message Title Christoph Vogtländer commented on JENKINS-28946 Re: JIRA support for Workflow jobs This is a stack trace for version 2.1 of the JIRA plugin plug in: Caught exception evaluating: it.versions in /job/TestWorkflow/build. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:94) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title Jesse Glick commented on JENKINS-31769 Re: sh steps on slaves randomly hang when complete No working hypothesis. Still need to either get logs from the time of the hang, or a way to reproduce from scratch. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" So I see two ways to add this to ArtifactArchiver - one that's more in-depth but, well, more in-depth - adding a flatten option to FilePath.copyRecursiveTo, ArtifactManager.archive and its implementations, etc... It'd be more thorough, but I'm wary of breaking APIs on ArtifactManager.archive. The simpler approach, I think, would be to add a flatten option to ArtifactArchiver.ListFiles. My instincts are the latter - does that sound reasonable? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title Sébastien Barthélémy commented on JENKINS-31769 Re: sh steps on slaves randomly hang when complete No working hypothesis. Still need to either get logs from the time of the hang, or a way to reproduce from scratch. ok. The good news is that my logger was mis-configured, my logs now cover a longer timespan: I see 3 to 4 logs per seconds: either 2015-12-07 15:10:30.671+ [id=52]FINEo.j.p.d.FileMonitoringTask$FileMonitoringController#writeLog: copied 89 bytes from /home/jenkins/jenkins/workspace/test_workflow/.a7304ceb/jenkins-log.txt 2015-12-07 15:10:30.962+ [id=53]FINEo.j.p.d.FileMonitoringTask$FileMonitoringController#writeLog: copied 89 bytes from /home/jenkins/jenkins/workspace/test_workflow/.3bb38477/jenkins-log.txt or 2015-12-07 10:12:26.691+ [id=59]FINEo.j.p.w.s.d.DurableTaskStep$Execution#check: still running in /home/jenkins/jenkins/workspace/team_romeo_dev on qisrc 2015-12-07 10:12:27.003+ [id=59]FINEo.j.p.w.s.d.DurableTaskStep$Execution#check: still running in /home/jenkins/jenkins/workspace/team_romeo_dev on qisrc which means a file (1 lines) covers 40 to 55 minutes. However, with only 10 of them I cannot cover the whole week-end. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to
[JIRA] [core] (JENKINS-22008) buildTimeTrend only shows the last 20 builds
Title: Message Title Jesse Glick commented on JENKINS-22008 Re: buildTimeTrend only shows the last 20 builds Félix Belzunce Arcos JENKINS-19828 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-31942) Add option to restore latest snapshot
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-31942 Add option to restore latest snapshot Issue Type: New Feature Assignee: Unassigned Components: vsphere-cloud-plugin Created: 07/Dec/15 2:53 PM Priority: Minor Reporter: Kevin Phillips I couldn't help but notice the vSphere cloud plugin has options for restoring snapshots as a build operation, but this feature only works with named snapshots at the moment. I'd like to see this functionality enhanced such that one could restore a VM back to the "last" snapshot (ie: the one used to launch the current instance of the VM). The vSphere client and all other vSphere tools have this option, so I suspect there must be a remote API call exposing this exact behavior. That being the case I'd hope it would be a trivial amount of work to implement this feature. NOTE: The rationale for this request is, we'd like to have VM cleanup logic done automatically as part of our Jenkins jobs, which would essentially shut down a running VM, restore it back to the 'last' snapshot, then restart it, thus ensuring CI operations that use the VM always start in a consistent state. Further, as the number of VMs increases it becomes difficult to ensure the names of snapshots stays consistent over time so it would be helpful to be able to restore the VM back to the last snapshot without needing to refer to it's name explicitly in the job.
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Jesse Glick commented on JENKINS-29881 Re: WorkflowRun.getChangeSets should skip empty changesets I think WorkflowRun.getChangeSets should behave analogously to the implementation in AbstractBuild: any ChangeLogSet in the result should be nonempty. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Jesse Glick commented on JENKINS-29780 Re: unarchive should support "Flatten directories" For StashManager I think you would indeed need a custom DirScanner, inspired by Glob but stripping any directory prefix before calling scanSingle. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Oleg Nenashev commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release +1 for handling it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title
Daniel Beck commented on JENKINS-29077
Re: No selector is shown for installing NodeJS from nodejs.org
hannes schluchtmann In the mean time, try this in the script console: DownloadService.Downloadable.get('hudson.plugins.nodejs.tools.NodeJSInstaller').updateNow()
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-31930) Jenkins job hangs up
Title: Message Title Martin Stolle commented on JENKINS-31930 Re: Jenkins job hangs up Details missing - Job Configuration, logs, the flow scripts. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-27248) List Subversion Tags parameter not available in workflow
Title: Message Title Christoph Vogtländer updated an issue Jenkins / JENKINS-27248 List Subversion Tags parameter not available in workflow Change By: Christoph Vogtländer Labels: workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jesse Glick commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator You are missing the essential point which is that Snippet Generator only ever offers to specify parameters which are configured with a nondefault value. Thus if the user enters a nonparameterized job ds, depending on which checkboxes are ticked the possible snippets that could be generated are build 'ds' build job: 'ds', propagate: false build job: 'ds', wait: false build job: 'ds', propagate: false, wait: false Of these, #1, #2, and #3 are all sensible choices¹. #4 is senseless, since the runtime behavior is identical to #3, so explicitly specifying propagate: false in your script is just misleading—that value is unused. propagate: true, wait: false would be just as silly, but Snippet Generator will never offer this, so there is no need for a form validation warning about it. (It would be possible for the runtime to print a warning to the build log if propagate were specified either way when wait were off, but this could be an annoyance to scripts which determine these options dynamically.) ¹#1 means wait for the downstream build to completely successfully and return a representation of it, otherwise fail. #2 means wait for it to complete and return a representation from which you can use the result field to inspect status, or fail if the queue item was cancelled before the build started. #3 means schedule the build and immediately return (void), failing only if the queue rejected the submission, which is possible but rare. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [conditional-buildstep-plugin] (JENKINS-20292) Option to specify an else-block
Title: Message Title Michał Stasiak commented on JENKINS-20292 Re: Option to specify an else-block I'd like to vote for this feature. It would be nice to have bash-like "if" options - not only 'if-else', but if --> step x else if --> step y else if --> step z [..] else --> final step Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2-plugin] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Title: Message Title Kanstantsin Shautsou commented on JENKINS-17957 Re: Crowd plugin - "remember me" doesn't work Will be glad for somebody's help, refactored state in PR and requires only single SSO resolution, also described how to test. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title
Andrew a created an issue
Jenkins / JENKINS-31943
Meme generator plugin is broken
Issue Type:
Bug
Assignee:
Jon Cairns
Components:
memegen-plugin
Created:
07/Dec/15 4:57 PM
Priority:
Minor
Reporter:
Andrew a
Something changed in memegenerator API, no meme is generated and you can see the following in the jenkins log:
Memegenerator API failure: Procedure or function 'Instance_Create' expects parameter '@Created', which was not supplied., full response: {"errorMessage":"Procedure or function 'Instance_Create' expects parameter '@Created', which was not supplied.","success":false}
Add Comment
[JIRA] [memegen-plugin] (JENKINS-31943) Meme generator plugin is broken
Title: Message Title Andrew a updated an issue Jenkins / JENKINS-31943 Meme generator plugin is broken Change By: Andrew a Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Rob Winch commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release I'm very glad to see this issue getting traction! I'd like to formally extend an offer to provide any support with the migration from a Spring Security perspective. Please let me know if you have any questions. Regards, Rob Winch (Spring Security Lead) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-29881 WorkflowRun.getChangeSets should skip empty changesets Change By: Andrew Bayer Labels: community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31086) 'stash' step applies default ant exclude patterns, no way to disable this
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-31086 'stash' step applies default ant exclude patterns, no way to disable this Change By: Andrew Bayer Labels: community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Debating whether to put that `DirScanner` in core - that feels right to me, since it could be useful elsewhere... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Title: Message Title Kevin Chen commented on JENKINS-23345 Re: Git Plugin should have an option to use clone instead of init/fetch Our situation is almost identical to the others reported. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-9346) Improve layout of help text for parameters of git tokens
Title: Message Title Andrew Bayer assigned an issue to Oleg Nenashev Jenkins / JENKINS-9346 Improve layout of help text for parameters of git tokens Change By: Andrew Bayer Assignee: Andrew Bayer Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title
Andrew Bayer edited a comment on JENKINS-29780
Re: unarchive should support "Flatten directories"
Debating whether to put that ` {{ DirScanner ` }} in core - that feels right to me, since it could be useful elsewhere...
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-custom-build-environment-plugin] (JENKINS-31944) Docker commandline passed wrong user id when executing.
Title: Message Title Stephen Leary created an issue Jenkins / JENKINS-31944 Docker commandline passed wrong user id when executing. Issue Type: Bug Assignee: Nicolas De Loof Components: docker-custom-build-environment-plugin Created: 07/Dec/15 5:44 PM Priority: Minor Reporter: Stephen Leary When docker is invoked it is passed the userid of the jenkins user on the host machine. This breaks things because the local user doesnt actually exist (PAM module checks fail for example) and doesnt match the environment variables for the username. It would be better to use the username (easymode) or explicitly create the jenkins user with the userid of the host. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title
Andrew Bayer commented on JENKINS-29780
Re: unarchive should support "Flatten directories"
PR up - https://github.com/jenkinsci/jenkins/pull/1948 - as I said on the PR, I'm a bit wary of the DirScanner.FlattenGlob logic - more specifically, I'm not sure how best to test it. The {{relativePath}}s are definitely coming in right, though.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-31801) Using Throttle Concurrent Builds in a WorkFlow
Title: Message Title Andrew Bayer commented on JENKINS-31801 Re: Using Throttle Concurrent Builds in a WorkFlow Ping? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-27092 create a step to abort the build with a NOT_BUILT status Change By: Andrew Bayer Labels: community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27396) Elastic timeout
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-27396 Elastic timeout Change By: Andrew Bayer Labels: community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: Andrew Bayer Labels: api community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Kanstantsin Shautsou commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release Rob Winch will it be possible to create Proxy or backward compatible migration? If not, could provide some PR to core (there is a spring-security branch but with 0 work). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Kanstantsin Shautsou edited a comment on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release [~rwinch] will it be possible to create Proxy or backward compatible migration? If not, could you provide some PR to core (there is a spring-security branch but with 0 work). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves-plugin] (JENKINS-31928) Little/No documentation on windows slave "No tty allocated failure"
Title: Message Title
Amrish R updated an issue
Jenkins / JENKINS-31928
Little/No documentation on windows slave "No tty allocated failure"
Change By:
Amrish R
I am not able to find much documentation/help on resolving an issue with building a Jenkins job on a windows slave. I am not sure what needs to be done to fix the following issue. Here are the logs. It will be nice if the wiki is updated with some information on solving this issue{code:java}Building remotely on Windows Slave (windows) in workspacec:\Builds\workspace\windows-nuget-push> C:\Git\cmd\git.exe rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository> C:\Git\cmd\git.exe config remote.origin.url g...@github.com:SDK-NewGen/sdk.git # timeout=10Fetching upstream changes from g...@github.com:NewGen/sdk.git> C:\Git\cmd\git.exe --version # timeout=10using GIT_SSH to set credentials > C:\Git\cmd\git.exe -c core.askpass=true fetch --tags --progress g...@github.com:NewGen/sdk.git +refs/heads/*:refs/remotes/origin/*> C:\Git\cmd\git.exe rev-parse "refs/remotes/origin/develop^{commit}" # timeout=10> C:\Git\cmd\git.exe rev-parse "refs/remotes/origin/origin/develop^{commit}" # timeout=10Checking out Revision e1feb68bcc21e8801a5bcaf087bda5041370fbf7 (refs/remotes/origin/develop)> C:\Git\cmd\git.exe config core.sparsecheckout # timeout=10> C:\Git\cmd\git.exe checkout -f e1feb68bcc21e8801a5bcaf087bda5041370fbf7> C:\Git\cmd\git.exe rev-list e1feb68bcc21e8801a5bcaf087bda5041370fbf7 # timeout=10[windows-nuget-push] $ sh -xe C:\WINDOWS\TEMP\hudson8489555376979916245.sh 2 [main] sh 140924 tty_list::allocate_tty: No tty allocated+ ./update-repo.shC:\WINDOWS\TEMP\hudson8489555376979916245.sh: ./update-repo.sh: not foundBuild step 'Execute shell' marked build as failureFinished: FAILURE{code}I think the failure is indicated by the following log message and I am not sure how to fix it.2 [main] sh 140924 tty_list::allocate_tty: No tty allocated, A quick google search pointed me to this [link][https://git.wiki.kernel.org/index.php/GitFaq#Why_does_gitk_on_Cygwin_display_.22git_1316_tty_list::allocate:_No_tty_allocated.22.3F], but I am not able to resolve this issue by removing tty from the CYGWIN environmental variable. Here is the shell command that is configured to be executed{code:java}./update-repo.sh./node_modules/.bin/gulp dev{code}
Add Comment
[JIRA] [crowd2-plugin] (JENKINS-17957) Crowd plugin - "remember me" doesn't work
Title: Message Title Nathan Neulinger commented on JENKINS-17957 Re: Crowd plugin - "remember me" doesn't work FYI, I am no longer using Crowd. I'm sure there is value in fixing this issue, but I'm not in a position to test/validate/etc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-29780 unarchive should support "Flatten directories" Change By: Andrew Bayer Labels: community-bee Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title Daniel Beck commented on JENKINS-29077 Re: No selector is shown for installing NodeJS from nodejs.org Sorry about that, looks like all files are signed and not just Maven's. Which is a good thing, I suppose, just not right now Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-29077) No selector is shown for installing NodeJS from nodejs.org
Title: Message Title hannes schluchtmann commented on JENKINS-29077 Re: No selector is shown for installing NodeJS from nodejs.org Haha, all fine with me. I can wait for now. But all your replies helped me a lot to understand the general situation. Thanks for that! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy commented on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
This week-end I had another hang, on a toy workflow I created for the occasion.
Here is is code:
class Config implements Serializable {
String branch
String source
String build
}
def runme(Config c)
{
echo "runme"
stage name: 'run_stage', concurrency: 1
node("qisrc") {
for (int i = 0; i < 1000; ++i) {
echo("i: ${i}");
try {
sh "file ${c.source}/.qi" // will throw if .qi is missing
} catch (all) {
sh "ls ${c.source}"
}
}
}
}
def c = new Config(
branch: "team/romeo/dev",
source: "/home/jenkins/w/team_romeo_dev",
build: "/home/jenkins/w/team_romeo_dev-build")
runme(c)
class Config implements Serializable {
String branch
String source
String build
}
def runme(Config c)
{
echo "runme"
stage name: 'run_stage', concurrency: 1
node("qisrc") {
for (int i = 0; i < 1000; ++i) {
echo("i: ${i}");
try {
sh "file ${c.source}/.qi" // will throw if .qi is missing
} catch (all) {
sh "ls ${c.source}"
}
}
}
}
def c = new Config(
branch: "team/romeo/dev",
source: "/home/jenkins/w/team_romeo_dev",
build: "/home/jenkins/w/team_romeo_dev-build")
runme(c)
I found it hung at iteration 530 http://agility-test.local/job/test_workflow/19/console
Started by upstream project "nightly" build number 6
originally caused by:
Started by timer
Running: Print Message
runme
Running: run_stage
Entering stage run_stage
Proceeding
Running: Allocate node : Start
Running on qisrc in /home/jenkins/jenkins/workspace/test_workflow
Running: Allocate node : Body : Start
Running: Print Message
i: 0
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
Running: Print Message
i: 1
Running: Shell Script
...
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
Running: Print Message
i: 530
Running: Shell Script
[test_workflow] Running shell script
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
Nothing unexpected in the control directory seems
$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`
$ ls -la jenkins/workspace/test_workflow/
total 24
drwxrwxr-x 3 jenkins jenkins 4096 Dec 6 02:39 .
drwxrwxr-x 4 jenkins jenkins 4096 Dec 2 13:20 ..
drwxrwxr-x 2 jenkins jenkins 4096 Dec 6 02:39 .ac553e58
-rw-rw-r-- 1 jenkins jenkins 10130 Dec 4 02:14 snapshot.json
jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt
+ file /home/jenkins/w/team_romeo_dev/.qi
/home/jenkins/w/team_romeo_dev/.qi: directory
jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/
jenkins-log.txt jenkins-result.txt pid script.sh
jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt
0
[JIRA] [core] (JENKINS-31932) Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292)
Title: Message Title Lukasz Karnasiewicz started work on JENKINS-31932 Change By: Lukasz Karnasiewicz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28292) Setting JDK installations not thread-safe
Title: Message Title Lukasz Karnasiewicz commented on JENKINS-28292 Re: Setting JDK installations not thread-safe Caused JENKINS-31932 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy edited a comment on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
This week-end I had another hang, on a toy workflow I created for the occasion.Here is is code:{code}class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c)class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c){code}I found it hung at iteration 530http://agility-test.local/job/test_workflow/19/console{noformat}Started by upstream project "nightly" build number 6originally caused by: Started by timerRunning: Print MessagerunmeRunning: run_stageEntering stage run_stageProceedingRunning: Allocate node : StartRunning on qisrc in /home/jenkins/jenkins/workspace/test_workflowRunning: Allocate node : Body : StartRunning: Print Messagei: 0Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 1Running: Shell Script...Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 530Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory {noformat}Nothing unexpected in the control directory {code}$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`$ ls -la jenkins/workspace/test_workflow/total 24drwxrwxr-x 3 jenkins jenkins 4096 Dec 6 02:39 .drwxrwxr-x 4 jenkins jenkins 4096 Dec 2 13:20 ..drwxrwxr-x 2 jenkins jenkins 4096 Dec 6 02:39 .ac553e58-rw-rw-r-- 1 jenkins jenkins 10130 Dec 4 02:14 snapshot.json$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt + file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory $ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt jenkins-result.txt pid script.sh $ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt 0$ cat jenkins/workspace/test_workflow/.ac553e58/ jenkins-log.txt jenkins-result.txt pid script.sh $ cat jenkins/workspace/test_workflow/.ac553e58/pid 17882$ cat jenkins/workspace/test_workflow/.ac553e58/script.sh #!/bin/sh -xefile /home/jenkins/w/team_romeo_dev/.qi{code}The jobs usually runs for 5 minutes and started Dec 6, 2015 2:35 AM.Sadly, my older log is 2015-12-06 21:31:54.875+.I tried this in http://agility-test.local/script{code}Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt').exists(){code}I got {noformat}Result: true{noformat}But nothing happened. The job is still hanged.
[JIRA] [build-flow-plugin] (JENKINS-31930) Jenkins job hangs up
Title: Message Title Sri Ramanjaneyulu Lingala created an issue Jenkins / JENKINS-31930 Jenkins job hangs up Issue Type: Bug Assignee: Nicolas De Loof Attachments: jenkins-hang.PNG Components: build-flow-plugin Created: 07/Dec/15 8:25 AM Environment: jenkins version 1.614 Priority: Critical Reporter: Sri Ramanjaneyulu Lingala Jenkins job hangs up . Job was running since 1 day 11 hours but the actual time for the job is 2.5 hrs. I had to restart jenkins to stop the job and have started it again.
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.
Title: Message Title Dominik Bartholdi resolved as Fixed Jenkins / JENKINS-22185 Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label. Change By: Dominik Bartholdi Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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] [nodelabelparameter-plugin] (JENKINS-22185) Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.
Title: Message Title Dominik Bartholdi commented on JENKINS-22185 Re: Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label. released with version 1.7 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy edited a comment on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
This week-end I had another hang, on a toy workflow I created for the occasion.Here is is code:{code}class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c)class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c){code}I found it hung at iteration 530http://agility-test.local/job/test_workflow/19/console{noformat}Started by upstream project "nightly" build number 6originally caused by: Started by timerRunning: Print MessagerunmeRunning: run_stageEntering stage run_stageProceedingRunning: Allocate node : StartRunning on qisrc in /home/jenkins/jenkins/workspace/test_workflowRunning: Allocate node : Body : StartRunning: Print Messagei: 0Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 1Running: Shell Script...Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 530Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory {noformat}Nothing unexpected in the control directory seems {code}$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`$ ls -la jenkins/workspace/test_workflow/total 24drwxrwxr-x 3 jenkins jenkins 4096 Dec 6 02:39 .drwxrwxr-x 4 jenkins jenkins 4096 Dec 2 13:20 ..drwxrwxr-x 2 jenkins jenkins 4096 Dec 6 02:39 .ac553e58-rw-rw-r-- 1 jenkins jenkins 10130 Dec 4 02:14 snapshot.jsonjenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt + file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt 0jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/ jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/pid 17882jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/script.sh #!/bin/sh -xefile /home/jenkins/w/team_romeo_dev/.qijenkins@036123a0bf25:~${code}The jobs usually runs for 5 minutes and started Dec 6, 2015 2:35 AM.Sadly, my older log is 2015-12-06 21:31:54.875+.I tried this in http://agility-test.local/script{code}Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt').exists(){code}I got {noformat}Result: true{noformat}But nothing happened. The job is still hanged.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy edited a comment on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
This week-end I had another hang, on a toy workflow I created for the occasion.Here is is code:{code}class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c)class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c){code}I found it hung at iteration 530http://agility-test.local/job/test_workflow/19/console{noformat}Started by upstream project "nightly" build number 6originally caused by: Started by timerRunning: Print MessagerunmeRunning: run_stageEntering stage run_stageProceedingRunning: Allocate node : StartRunning on qisrc in /home/jenkins/jenkins/workspace/test_workflowRunning: Allocate node : Body : StartRunning: Print Messagei: 0Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 1Running: Shell Script...Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 530Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory {noformat}Nothing unexpected in the control directory seems {code}$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`$ ls -la jenkins/workspace/test_workflow/total 24drwxrwxr-x 3 jenkins jenkins 4096 Dec 6 02:39 .drwxrwxr-x 4 jenkins jenkins 4096 Dec 2 13:20 ..drwxrwxr-x 2 jenkins jenkins 4096 Dec 6 02:39 .ac553e58-rw-rw-r-- 1 jenkins jenkins 10130 Dec 4 02:14 snapshot.jsonjenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt + file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt 0jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/ jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/pid 17882jenkins@036123a0bf25:~$ cat jenkins/workspace/test_workflow/.ac553e58/script.sh #!/bin/sh -xefile /home/jenkins/w/team_romeo_dev/.qijenkins@036123a0bf25:~${code}The jobs usually runs for 5 minutes and started Dec 6, 2015 2:35 AM.Sadly, my older log is 2015-12-06 21:31:54.875+.I tried this in http://agility-test.local/script{code}Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt').exists(){code}I got {noformat} Result: true{noformat}But nothing happened. The job is still hanged.
[JIRA] [core] (JENKINS-31871) Jenkins improperly handles single quotes in item names
Title: Message Title Félix Belzunce Arcos commented on JENKINS-31871 Re: Jenkins improperly handles single quotes in item names I was not able to re-produce the fact that the item with singles quotes cannot be opened within a folder. However, the Field verification is really an issue as Daniel Beck said. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31871) Jenkins improperly handles single quotes in item names
Title: Message Title Félix Belzunce Arcos edited a comment on JENKINS-31871 Re: Jenkins improperly handles single quotes in item names I was not able to re-produce the fact that the item with singles quotes cannot be opened within a folder. However, the Field verification is really an issue as Daniel Beck said. [~oleg_nenashev] What Jenkins version were you using? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31932) Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292)
Title: Message Title Lukasz Karnasiewicz updated an issue Jenkins / JENKINS-31932 Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292) Change By: Lukasz Karnasiewicz Environment: Ubuntu 14.04.1 LTS 64bitJenkins ver. 1.625.2Java(TM) SE Runtime Environment (build 1.7.0_76-b13) The fix for JENKINS-28292 included in 1.618 is causing performance issues - requests are hanging on Jenkins.getJDKs for a very long time (sometimes minutes). This does happen on 2 of our Jenkins instances and can be observed at least a few times per day for every user by different users . I don't have a thread dump available but I'll try to get it for reference. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31931) archive step sets result to FAILURE but does not fail the job
Title: Message Title
Christoph Vogtländer created an issue
Jenkins / JENKINS-31931
archive step sets result to FAILURE but does not fail the job
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
07/Dec/15 8:26 AM
Environment:
Jenkins 1.625.2 LTS
Labels:
workflow
Priority:
Major
Reporter:
Christoph Vogtländer
When no files matching the file mask are found, the archive workflow step as well as the general build step will set the result of the workflow to FAILURE but the build continues. The Step is not marked as failed in the "Workflow Steps" graph
node('master') {
archive "nonexistingdir/"
step([$class: 'ArtifactArchiver', artifacts: 'nonexistingdir/', excludes: null])
}
Both steps are marked as SUCCESS, the
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22185 Re: Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label. Code changed in jenkins User: Antonio Muñiz Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterDefinition.java src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterValue.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/24cc8f069fd274ea1ad19465d0290fcbe189ad63 Log: JENKINS-22185 Run the build on all matching nodes Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31769) sh steps on slaves randomly hang when complete
Title: Message Title
Sébastien Barthélémy edited a comment on JENKINS-31769
Re: sh steps on slaves randomly hang when complete
This week-end I had another hang, on a toy workflow I created for the occasion.Here is is code:{code}class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c)class Config implements Serializable { String branch String source String build}def runme(Config c){ echo "runme" stage name: 'run_stage', concurrency: 1 node("qisrc") {for (int i = 0; i < 1000; ++i) { echo("i: ${i}"); try {sh "file ${c.source}/.qi" // will throw if .qi is missing } catch (all) {sh "ls ${c.source}" }} }}def c = new Config( branch: "team/romeo/dev", source: "/home/jenkins/w/team_romeo_dev", build: "/home/jenkins/w/team_romeo_dev-build")runme(c){code}I found it hung at iteration 530http://agility-test.local/job/test_workflow/19/console{noformat}Started by upstream project "nightly" build number 6originally caused by: Started by timerRunning: Print MessagerunmeRunning: run_stageEntering stage run_stageProceedingRunning: Allocate node : StartRunning on qisrc in /home/jenkins/jenkins/workspace/test_workflowRunning: Allocate node : Body : StartRunning: Print Messagei: 0Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 1Running: Shell Script...Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory Running: Print Messagei: 530Running: Shell Script[test_workflow] Running shell script+ file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory {noformat}Nothing unexpected in the control directory {code}$ ssh jenkins@`sudo docker inspect --format '{{.NetworkSettings.IPAddress}}' qisrc`$ ls -la jenkins/workspace/test_workflow/total 24drwxrwxr-x 3 jenkins jenkins 4096 Dec 6 02:39 .drwxrwxr-x 4 jenkins jenkins 4096 Dec 2 13:20 ..drwxrwxr-x 2 jenkins jenkins 4096 Dec 6 02:39 .ac553e58-rw-rw-r-- 1 jenkins jenkins 10130 Dec 4 02:14 snapshot.json jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt + file /home/jenkins/w/team_romeo_dev/.qi/home/jenkins/w/team_romeo_dev/.qi: directory jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt 0 jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/ jenkins-log.txt jenkins-result.txt pid script.sh jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/pid 17882 jenkins@036123a0bf25:~ $ cat jenkins/workspace/test_workflow/.ac553e58/script.sh #!/bin/sh -xefile /home/jenkins/w/team_romeo_dev/. qijenkins@036123a0bf25:~$ qi {code}The jobs usually runs for 5 minutes and started Dec 6, 2015 2:35 AM.Sadly, my older log is 2015-12-06 21:31:54.875+.I tried this in http://agility-test.local/script{code}Jenkins.instance.getNode('qisrc').createPath('/home/jenkins/jenkins/workspace/test_workflow/.ac553e58/jenkins-result.txt').exists(){code}I got {noformat}Result: true{noformat}But nothing happened. The job is still hanged.
[JIRA] [sqlplus-script-runner-plugin] (JENKINS-31597) SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level
Title: Message Title Fernando Boaglio commented on JENKINS-31597 Re: SQLPlus Script Runner Plugin: ORACLE_HOME at job or slave level Hi Raphaël, I am having a hard time trying to make it work on slaves properly, but I am getting closer Anyway, I've added localization support to this plugin to translate it to my native language (pt_BR). Assuming that you are not native American, do you want to help translate it to another language ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31932) Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292)
Title: Message Title Lukasz Karnasiewicz created an issue Jenkins / JENKINS-31932 Performance regression after fixing synchronization issue when setting JDK installations. (issue 28292) Issue Type: Bug Assignee: Lukasz Karnasiewicz Components: core Created: 07/Dec/15 9:28 AM Priority: Major Reporter: Lukasz Karnasiewicz The fix for JENKINS-28292 included in 1.618 is causing performance issues - requests are hanging on Jenkins.getJDKs for a very long time (sometimes minutes). This does happen at least a few times per day for every user. I don't have a thread dump available but I'll try to get it for reference. Add Comment
[JIRA] [scoverage-plugin] (JENKINS-31929) No trend graph in job overview
Title: Message Title Sascha Kolberg created an issue Jenkins / JENKINS-31929 No trend graph in job overview Issue Type: Bug Assignee: Unassigned Components: scoverage-plugin Created: 07/Dec/15 8:14 AM Priority: Minor Reporter: Sascha Kolberg Coverage is displayed for last successful job but now trend graph. Jenkins version: 1.639 Scoverage-Plugin version: 1.3.0 WARNING: Error while serving http:scoverage/trendGraph/png java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1079.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) 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$13.dispatch(MetaClass.java:411) 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
[JIRA] [scoverage-plugin] (JENKINS-31929) No trend graph in job overview
Title: Message Title
Sascha Kolberg updated an issue
Jenkins / JENKINS-31929
No trend graph in job overview
Change By:
Sascha Kolberg
Coverage is displayed for last successful job but now no trend graph.Jenkins version: 1.639Scoverage-Plugin version: 1.3.0{code}WARNING: Error while serving http:scoverage/trendGraph/pngjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1079.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) 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$13.dispatch(MetaClass.java:411) 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:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:92) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [nodelabelparameter-plugin] (JENKINS-22185) Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22185 Re: Job with "NodeLabel Parameter Plugin" does not build in parallel on all nodes which share a label. Code changed in jenkins User: Antonio Muñiz Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/wrapper/TriggerNextBuildWrapper.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/b235b9e86cc7f1f9cdfc08b9c01550b78e1b0506 Log: JENKINS-22185 Avoid to run twice in the same node Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31933) Workflow can't be triggered with BuildResultTrigger
Title: Message Title Przemek Hejman created an issue Jenkins / JENKINS-31933 Workflow can't be triggered with BuildResultTrigger Issue Type: Bug Assignee: Jesse Glick Attachments: workflow2.jpg Components: workflow-plugin Created: 07/Dec/15 9:37 AM Environment: Jenkins ver. 1.638, BuildResultTrigger Plug-in 0.17 Priority: Major Reporter: Przemek Hejman I would like to have my workflow triggered by BuildResultTrigger. When I configure this in 'Build Triggers' section and click "Save", I end up with following page (screenshot attached). Here's pasted stack trace: javax.servlet.ServletException: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] [job-dsl-plugin] (JENKINS-31911) Add support for Mantis Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31911 Re: Add support for Mantis Plugin Code changed in jenkins User: Victor Martinez Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/mantis.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/MantisContext.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/443b9098fd2b4b1698b51d8f23e522da5fe65bd9 Log: JENKINS-31911 Added support for Mantis plugin Added TestCases and Docs for Mantis plugin JENKINS-31911 Added support for Mantis plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Привет вам моего хорошего друга,
Привет вам моего хорошего друга, Я очень рад быть в контакте с вами, Меня зовут Ури Талла Rajiha и я связаться с Вами из Сирии, у меня есть бизнес-инвестиций Я хочу, чтобы установить в Ваша страна, и я хотел, чтобы вы быть помощь мне, я хочу переехать в Ваша страна за эту войну, что в настоящее время происходит в моей стране Сирии. Если вы поможете мне достичь успеха этих инвестиций, пожалуйста, свяжитесь мне для более подробной информации. (allaur...@gmail.com) Ури -- 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.
