[JIRA] (JENKINS-38054) Handle pagination for tests
Title: Message Title James Dumay created an issue Jenkins / JENKINS-38054 Handle pagination for tests Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/08 7:05 AM Priority: Minor Reporter: James Dumay Context In JENKINS-37202 we enabled pagination across all the REST APIs. The test page is not handling pagination yet. At the moment we limit to 100 items in a collection returned from the API. In Scope Make sure the tests page handles pagination for large amounts of tests (say 150 failures). A "more" button should suffice. Add Comment
[JIRA] (JENKINS-37202) Turn on paging by default
Title: Message Title James Dumay updated JENKINS-37202 Jenkins / JENKINS-37202 Turn on paging by default Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37202) Turn on paging by default
Title: Message Title James Dumay commented on JENKINS-37202 Re: Turn on paging by default PR https://github.com/jenkinsci/blueocean-plugin/pull/486 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16456) Manage launch order of jobs into a phase
Title: Message Title hagzag commented on JENKINS-16456 Re: Manage launch order of jobs into a phase Mohammad Shalabi AFAIK Items within a phase can be dragged in order to order. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38022) Create a verbose logging option for Nuget trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38022 Re: Create a verbose logging option for Nuget trigger Code changed in jenkins User: Arnaud TAMAILLON Path: src/main/java/org/jenkinsci/plugins/nuget/triggers/NugetTrigger.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/InfoTriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/TriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/VerboseTriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetGetLatestPackageVersionCommand.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetPackageCheckerVisitor.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetPackagesCheckerCallable.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetUpdater.java src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.jelly src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.properties src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config_fr.properties http://jenkins-ci.org/commit/nuget-plugin/3ac6d67dff3d8916d63b188f726fada34891be23 Log: Merge pull request #9 from Greybird/master [FIXED JENKINS-38022] Create a verbose logging option for Nuget trigger Compare: https://github.com/jenkinsci/nuget-plugin/compare/57d1ec4d096c...3ac6d67dff3d Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visi
[JIRA] (JENKINS-38022) Create a verbose logging option for Nuget trigger
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38022 Create a verbose logging option for Nuget trigger Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38022) Create a verbose logging option for Nuget trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38022 Re: Create a verbose logging option for Nuget trigger Code changed in jenkins User: Arnaud Path: src/main/java/org/jenkinsci/plugins/nuget/triggers/NugetTrigger.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/InfoTriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/TriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/triggers/logs/VerboseTriggerLog.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetGetLatestPackageVersionCommand.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetPackageCheckerVisitor.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetPackagesCheckerCallable.java src/main/java/org/jenkinsci/plugins/nuget/utils/NugetUpdater.java src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.jelly src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config.properties src/main/resources/org/jenkinsci/plugins/nuget/triggers/NugetTrigger/config_fr.properties http://jenkins-ci.org/commit/nuget-plugin/731e3592919f658d86963d59b1cc5ea88c8ad9b2 Log: [FIXED JENKINS-38022] Create a verbose logging option for Nuget trigger Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38055) Set default pagination size per API
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-38055 Set default pagination size per API Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/08 7:21 AM Priority: Minor Reporter: Vivek Pandey JENKINS-37202 sets value of default pagination limit size to 100, its applied to all APIs. What we need is per API default limit, for example 100 for search, 50 for pipelines etc. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:252
[JIRA] (JENKINS-38021) Accessing unset global variable cause master to hang
Title: Message Title
Marcus Philip commented on JENKINS-38021
Re: Accessing unset global variable cause master to hang
Even more strange behavior found... These two calls are not identical, the second does not call the setter as one would expected
globalConfig.setFoo('bar')
globalConfig.foo = 'bar'
So it does not behave like groovy properties: http://groovy-lang.org/objectorientation.html#properties . And indeed globalConfig.properties.keySet() does not contain these so called 'properties'. This means that code like this could behave 'interesting' if you do something more than just set and return field in getter and setter:
globalConfig.setFoo('bar')
globalConfig.foo('beep')
echo globalConfig.scmFoo
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.go
[JIRA] (JENKINS-37202) Turn on paging by default
Title: Message Title Vivek Pandey updated JENKINS-37202 Jenkins / JENKINS-37202 Turn on paging by default Change By: Vivek Pandey Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37707) Saving SecretBuildWrapper for the first time fails due to duplicated credentialsId field unless git also installed
Title: Message Title Thomas de Grenier de Latour updated an issue Jenkins / JENKINS-37707 Saving SecretBuildWrapper for the first time fails due to duplicated credentialsId field unless git also installed Change By: Thomas de Grenier de Latour Component/s: credentials-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38056) Duration of running Pipeline is not live
Title: Message Title James Dumay created an issue Jenkins / JENKINS-38056 Duration of running Pipeline is not live Issue Type: Bug Assignee: Thorsten Scherler Attachments: Jenkins Blue Ocean 2016-09-08 17-32-30.png Components: blueocean-plugin Created: 2016/Sep/08 7:34 AM Priority: Trivial Reporter: James Dumay Not sure if this ever worked but I noticed the duration for a running pipeline never updates itself. Thorsten Scherler if this is not trivial feel free to remove it from the sprint and we can address it later (but if it is trivial - smash it ) Add Comment
[JIRA] (JENKINS-36558) Sort the dashboard alphabetically
Title: Message Title James Dumay resolved as Won't Fix This works on the dashboard already. Ivan is doing the branches and pr tabs in another ticket. Jenkins / JENKINS-36558 Sort the dashboard alphabetically Change By: James Dumay Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit h
[JIRA] (JENKINS-37338) Pipeline scripts that should appear in /queue are returned in /runs API
Title: Message Title James Dumay commented on JENKINS-37338 Re: Pipeline scripts that should appear in /queue are returned in /runs API Cliff Meyers Vivek Pandey if this requires extensive frontend work lets punt this to the next sprint Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37337) Pipeline scripts that appear as "queued" in classic UI are not returned from /queue API
Title: Message Title James Dumay commented on JENKINS-37337 Re: Pipeline scripts that appear as "queued" in classic UI are not returned from /queue API Cliff Meyers is this a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-37338? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26578) Adjuncts do not include CSS correctly for removable dom fragments
Title: Message Title Thomas de Grenier de Latour commented on JENKINS-26578 Re: Adjuncts do not include CSS correctly for removable dom fragments stephenconnolly: I think there is an issue with the JS hack introduced in select.js in your last commit, for applying new behaviours to existing DOM elements. You should call Behaviour.applySubtree with includeSelf=true, otherwise it will not apply one of the specified behaviours (the one for "DIV.credentials-select-control" itself). I opened a PR which does that (PR-67), referring to JENKINS-37707 (which is an issue with credentials-binding-plugin when trying to bind credentials to a project and the credentials selection code is loaded for the first time in the job configuration page). Tell me if you need me to edit the PR to refer to this issue instead, it's just that I've only found it afterward. To reproduce the issue and test the fix, here is what I did: get master sources for credentials-binding-plugin bump jenkins.version to 1.609 and credentials version to 2.1.4 hpi:run, create a login/password credentials, create a freestyle job, try to bind the secret to a combined variable (for instance) => it should give you the error reported in JENKINS-37707 build credentials 2.1.5-SNAPSHOT with my fix, bump dependency in credentials-binding-plugin, and repeat previous step => it should work fine Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36569) Add 'Slaves' axis is broken
Title: Message Title Tom Ghyselinck commented on JENKINS-36569 Re: Add 'Slaves' axis is broken Hi, Any update on this? We see this issue after upgrading to 1.7.1 and downgrading to 1.6 again. It is quite blocking since we have a few 100 of jobs which have slave selection. We didn't notice it with the initial 1.6 installation... With best regards, Tom. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36569) Add 'Slaves' axis is broken
Title: Message Title Tom Ghyselinck updated an issue Jenkins / JENKINS-36569 Add 'Slaves' axis is broken Change By: Tom Ghyselinck Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36569) Add 'Slaves' axis is broken
Title: Message Title Tom Ghyselinck commented on JENKINS-36569 Re: Add 'Slaves' axis is broken Hi, Actually we get a 404 error with message: Apache Tomcat/6.0.35 - Error reportHTTP Status 404 - "1" noshade="noshade">type Status reportmessage description The requested resource () is not available."1" noshade="noshade">Apache Tomcat/6.0.35 "empty" POST is done to /$stapler/bound/19883ddb-a5aa-4945-b8fd-7ea68e6ce6dd/render Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To un
[JIRA] (JENKINS-37542) Jenkins is not scheduling jobs for offline nodes
Title: Message Title Giuseppe Landolfi resolved as Not A Defect Closing the issue as "Not A Defect" and improving the plugin documentation to cover the topic, as the situation looks fairly common. Jenkins / JENKINS-37542 Jenkins is not scheduling jobs for offline nodes Change By: Giuseppe Landolfi Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-36569) Add 'Slaves' axis is broken
Title: Message Title
Tom Ghyselinck edited a comment on JENKINS-36569
Re: Add 'Slaves' axis is broken
Hi,Actually we get a 404 error with message SyntaxError : unterminated string literal (hudson-behavior.js:425:108): {code :html } Apache Tomcat/6.0.35 geval()hudson - Error report behavior.js:372evalInnerHtmlScripts/ title> < style> ()hudson - -H1 {font-family behavior.js : Tahoma,Arial,sans 579next()hudson - serif;color behavior.js : white;background 597sequencer()hudson - color behavior.js : #525D76;font 600evalInnerHtmlScripts()hudson - size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A behavior . name {color js : black;}HR {color : #525D76;}-->< 585renderOnDemand / style> < /head>HTTP Status 404 ()hudson - < behavior.js:556makeStaplerProxy / h1>type< genMethod / b> Status report< proxy[methodName] / p> < p>message description The requested resource .onSuccess () is not available bind . js:57Ajax.Request < /u>Apache Tomcat/6 . 0 respondToReadyState()prototype . 35 js:1655Ajax.Request < .onStateChange()prototype.js:1600bind / h3> < /body> () prototype.js:414 {code} "_empty_" POST is done to {{/$stapler/bound/19883ddb We have:Jenkins 1.609.3matrix - a5aa project - 4945-b8fd-7ea68e6ce6dd/render}} plugin 1.6
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34805) Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade
Title: Message Title Tommy Tynjä commented on JENKINS-34805 Re: Delivery Pipeline plugin doesn't create the environment variable PIPELINE_VERSION since upgrade Mattias Jiderhamn Can you possibly create a new ticket with a reproducing test case / description? Thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37542) Jenkins is not scheduling jobs for offline nodes
Title: Message Title Giuseppe Landolfi commented on JENKINS-37542 Re: Jenkins is not scheduling jobs for offline nodes Ricky Cormier please have a look on how to report issues on Jenkins Jira: if you don't follow the issues after creating them, they may be closed as 'Incomplete'. Best regards. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38057) Opening "Global Tool Configuration" or "Global Security" fails
Title: Message Title Peter Schütt created an issue Jenkins / JENKINS-38057 Opening "Global Tool Configuration" or "Global Security" fails Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Sep/08 9:12 AM Environment: Windows Server 2008 R2 Running in Tomcat 8.0.21 Priority: Critical Reporter: Peter Schütt When I want to open "Global Tool Configuration" or "Global Security" I get a StackTrace: Stack trace javax.servlet.ServletException: java.lang.AssertionError: InstanceIdentity is missing its singleton at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) 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:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security
[JIRA] (JENKINS-38057) Opening "Global Tool Configuration" or "Global Security" fails
Title: Message Title Peter Schütt commented on JENKINS-38057 Re: Opening "Global Tool Configuration" or "Global Security" fails Some additional infos from the apache-Log-file: 08-Sep-2016 10:46:02.002 WARNING [Handling GET /jenkins/configureTools from 10.3.21.40 : http-apr-8080-exec-10] hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.error Failed to instantiate Key[type=org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Error injecting constructor, java.io.IOException: Invalid DER: length field too big (186) at org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.(PageDecoratorImpl.java:21) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:478) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.ExtensionList.get(ExtensionList.java:147) at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:131) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getKeyPair(InstanceIdentityRSAProvider.java:23) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.get(InstanceIdentityProvider.java:161) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getKeyPair(InstanceIdentityProvider.java:210) at jenkins.model.identity.IdentityRootAction.getUrlName(IdentityRootAction.java:42) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3472) at sun.reflect.GeneratedMethodAccessor380.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:378) 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:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginSe
[JIRA] (JENKINS-38057) Opening "Global Tool Configuration" or "Global Security" fails
Title: Message Title Peter Schütt edited a comment on JENKINS-38057 Re: Opening "Global Tool Configuration" or "Global Security" fails Some additional infos from the apache-Log-file:08-Sep-2016 10:46:02.002 WARNING [Handling GET /jenkins/configureTools from 10.3.21.40 : http-apr-8080-exec-10] hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.error Failed to instantiate Key[type=org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors:1) Error injecting constructor, java.io.IOException: Invalid DER: length field too big (186) at org.jenkinsci.main.modules.instance_identity.PageDecoratorImpl.(PageDecoratorImpl.java:21)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:478) at hudson.ExtensionList.load(ExtensionList.java:349) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:287) at hudson.ExtensionList.iterator(ExtensionList.java:156) at hudson.ExtensionList.get(ExtensionList.java:147) at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:131) at org.jenkinsci.main.modules.instance_identity.InstanceIdentityRSAProvider.getKeyPair(InstanceIdentityRSAProvider.java:23) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.get(InstanceIdentityProvider.java:161) at jenkins.model.identity.InstanceIdentityProvider$KeyTypes.getKeyPair(InstanceIdentityProvider.java:210) at jenkins.model.identity.IdentityRootAction.getUrlName(IdentityRootAction.java:42) at jenkins.model.Jenkins.getDynamic(Jenkins.java:3472) at sun.reflect.GeneratedMethodAccessor380.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:167) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:378) 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:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(Plu
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title
Manuel Franco updated an issue
Jenkins / JENKINS-38058
Properly pass context in folder's page objects
Change By:
Manuel Franco
Let's describe the issue with a test. Assumming we already have an injector and a JenkinsController, the following test will fail:{code:java}Jenkins j1 = new Jenkins(injector, jenkinsController);Assert.assertSame(j1, j1.jobs.getJenkins()); Jenkins j1 = new Jenkins(injector, jc);Assert.assertSame(j1, j1.jobs.getJenkins());FolderItem f = j1.jobs.create(FolderItem.class);Assert.assertSame(j1, f.jobs.getJenkins()); {code}The problem is that the jenkins instance returned by the {{getJenkins()}} method in the {{JobsMixIn}} object (actually inherited from {{PageObject}}) is not the instance that was passed as a context in the construction of this last one, but an instance that is looked up (and built if needed) using guice.This leads to potential inconsistencies for some operations (e.g. {{jobs.create}}) that rely on querying its jenkins instance, for example for the version number.Sometimes as an [external user|https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/EXTERNAL.md] of the ATH I may need to create several instances with different versions, and want each jobs mixin to know exactly to which jenkins they belong to and behave consistently.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title Manuel Franco created an issue Jenkins / JENKINS-38058 Properly pass context in folder's page objects Issue Type: Bug Assignee: Manuel Franco Components: acceptance-test-harness Created: 2016/Sep/08 9:50 AM Environment: ATH 1.38 Labels: test Priority: Minor Reporter: Manuel Franco Let's describe the issue with a test. Assumming we already have an injector and a JenkinsController, the following test will fail: Jenkins j1 = new Jenkins(injector, jenkinsController); Assert.assertSame(j1, j1.jobs.getJenkins()); The problem is that the jenkins instance returned by the getJenkins() method in the JobsMixIn object (actually inherited from PageObject) is not the instance that was passed as a context in the construction of this last one, but an instance that is looked up (and built if needed) using guice. This leads to potential inconsistencies for some operations (e.g. jobs.create) that rely on querying its jenkins instance, for example for the version number. Sometimes as an external user of the ATH I may need to create several instances with different versions, and want each jobs mixin to know exactly to which jenkins they belong to and behave consistently.
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Kanstantsin Shautsou Basic pipeline visualization in delivery pipeline view based on the workflow/pipeline plugin configuration with appropriate pipeline status (green/red). This currently works but has some minor details left. I think we could possibly release a first version soon and then just iterate and improve as we move along. It won't have as many configuration options (initially at least), but since it is a fundamentally different model configuration options will most likely diverge. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title
Manuel Franco updated an issue
Jenkins / JENKINS-38058
Properly pass context in folder's page objects
Change By:
Manuel Franco
Let's describe the issue with a test. Assumming we already have an injector and a JenkinsController, the following test will fail:{code:java}Jenkins j1 = new Jenkins(injector, jenkinsController); Assert.assertSame(j1, j1.jobs.getJenkins());Jenkins j1 = new Jenkins(injector, jc);Assert.assertSame(j1, j1.jobs.getJenkins()); FolderItem f = j1.jobs.create(FolderItem.class);Assert.assertSame(j1, f.jobs.getJenkins());{code}The problem reproduced is that the jenkins instance returned by the {{getJenkins()}} method same described in the {{JobsMixIn}} object (actually inherited from {{PageObject}}) is not the instance that was passed as a context in the construction of this last one JENKINS-XXX , but an instance that is looked up (and built if needed) using guice.This leads specific to potential inconsistencies for some operations (e.g. {{ jobs.create FolderItem }} ) that rely on querying its jenkins instance s , for example for the version number.Sometimes as an [external user|https://github.com/jenkinsci/acceptance-test-harness/blob/master/docs/EXTERNAL.md] of the ATH I may need to create several instances with different versions, and want each jobs mixin to know exactly to which jenkins since they belong to and behave consistently are not properly receiving their context when created .
Add Comment
This message was sent by Atla
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title
Manuel Franco updated an issue
Jenkins / JENKINS-38058
Properly pass context in folder's page objects
Change By:
Manuel Franco
Let's describe the issue with a test. Assumming we already have an injector and a {{ JenkinsController }} , the following test will fail:{code:java}Jenkins j1 = new Jenkins(injector, jenkinsController);FolderItem f = j1.jobs.create(FolderItem.class);Assert.assertSame(j1, f.jobs.getJenkins());{code}The problem reproduced is the same described in JENKINS-XXX, but specific to {{FolderItem}}s, since they are not properly receiving their context when created.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title
Manuel Franco updated an issue
Jenkins / JENKINS-38058
Properly pass context in folder's page objects
Change By:
Manuel Franco
Let's describe the issue with a test. Assumming we already have an injector and a {{JenkinsController}}, the following test will fail:{code:java}Jenkins j1 = new Jenkins(injector, jenkinsController);FolderItem f = j1.jobs.create(FolderItem.class);Assert.assertSame(j1, f.jobs.getJenkins());{code}The problem reproduced is the same described in JENKINS- XXX 37615 , but specific to {{FolderItem}}s, since they are not properly receiving their context when created.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title Manuel Franco started work on JENKINS-38058 Change By: Manuel Franco Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Kanstantsin Shautsou commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Maybe you would be interested in https://github.com/jenkinsci/pipeline-view-plugin that has modern behaviours? It on top of pipeline but maybe it could be useful to refresh something. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37993) Can't load main dashboard - hudson model view
Title: Message Title Luiz Pereira commented on JENKINS-37993 Re: Can't load main dashboard - hudson model view Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.21.jar!/hudson/model/View/index.jelly:42:43: JSONObject["displayStrategy"] not found. at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:813) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at org.jenkinsci.plugins.modernstatus.ModernStatusFilter.doFilter(ModernStatusFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.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 org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.compression
[JIRA] (JENKINS-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38006 Re: REGRESSION: logs not tailing with freestyle Code changed in jenkins User: Thorsten Scherler Path: .gitignore pom.xml http://jenkins-ci.org/commit/blueocean-acceptance-test/389743210de4d200d41d2840869cb8ec0941863f Log: Merge remote-tracking branch 'origin/master' into JENKINS-38006 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38006 Re: REGRESSION: logs not tailing with freestyle Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js src/test/js/failing.js src/test/js/log-karaoke/freestyle.js src/test/js/log-karaoke/freestylePing.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/stages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/5add1af48dc3917187d13944f1ce279b29c1fcec Log: JENKINS-38006 Drop passing browser object to page methods. Add comments to bluePipelineRunDetail and the failing.js. Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/9ceca9da323e...5add1af48dc3 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36307) "Can not read hook payload" exception whenever a hook is received
Title: Message Title Tom Bamford commented on JENKINS-36307 Re: "Can not read hook payload" exception whenever a hook is received Im seeing this too now; is this PR in the release? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38006 Re: REGRESSION: logs not tailing with freestyle Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js src/test/js/failing.js src/test/js/log-karaoke/freestyle.js src/test/js/log-karaoke/freestylePing.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/freestylePing.sh http://jenkins-ci.org/commit/blueocean-acceptance-test/3a3f8d8086ff124d5a0625da34682098a7bfc3ff Log: FIX Jenkins 38006 Fix condition which had been implemented wrong (#35) JENKINS-38006 first working version to test whethe we have scrolled to bottom JENKINS-38006 move method to the page object JENKINS-38006 Drop passing browser object to page methods. Add comments to bluePipelineRunDetail and the failing.js. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it
[JIRA] (JENKINS-38006) REGRESSION: logs not tailing with freestyle
Title: Message Title Thorsten Scherler updated JENKINS-38006 Jenkins / JENKINS-38006 REGRESSION: logs not tailing with freestyle Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco commented on JENKINS-33698 Re: NodeJS plugin npm install without root permissions The same here, issue happends wtith NodeJS >= 6.0. Debugging a bit the issue it's clear is in the NodeJS because since 6.x it's changed the prefix value from the local NodeJS installation folder to new one in the (/usr in linux) that obvious only root have access there. I found a workaround to keept global modules separated per Node version. Following this documentation after the tar.gz is installed if we put an npmrc file into lib/node_modules/npm with right prefix value works. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Raphaël PINSON commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Slawa Giterman the Jenkins Pipeline GUI is great, but it still doesn't show steps inside each parallel branch, even though the syntax is accepted. Do you know if that is planned? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title Manuel Franco updated an issue Jenkins / JENKINS-38058 Properly pass context in folder's page objects Change By: Manuel Franco Environment: ATH 1. 38 39 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title Manuel Franco updated JENKINS-38058 Jenkins / JENKINS-38058 Properly pass context in folder's page objects Change By: Manuel Franco Status: In Review Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38058) Properly pass context in folder's page objects
Title: Message Title Manuel Franco updated JENKINS-38058 Jenkins / JENKINS-38058 Properly pass context in folder's page objects Change By: Manuel Franco Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Tomasz Śniatowski commented on JENKINS-33168 Re: Junit plugin took 7 hours to complete recording test failures We're also seeing this problem on Jenkins ver. 2.7.2, junit plugin 1.18, Ubuntu 14.04 and it's causing a significant disruption because the slow parsing cannot be aborted. We're seeing threads in states like "Executor #0 for aa-01 : executing foo #141" Id=3787231 Group=main RUNNABLE at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:122) - locked com.thoughtworks.xstream.converters.reflection.FieldDictionary@4e6649e2 at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldOrNull(FieldDictionary.java:113) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.getFieldOrNull(PureJavaReflectionProvider.java:194) at hudson.util.RobustReflectionConverter.fieldDefinedInClass(RobustReflectionConverter.java:347) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:284) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:229) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:352) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:290) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:229) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.RobustCollectionConverter.populateCollection(RobustCollectionConverter.java:85) at com.thoughtworks.xstream.converters.collections.CollectionConverter.unmarshal(CollectionConverter.java:80) at hudson.util.RobustCollectionConverter.unmarshal(RobustCollectionConverter.java:76) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmar
[JIRA] (JENKINS-38007) 504 gateway timeout in sse-gateway/configure https://ci.blueocean.io
Title: Message Title Tom FENNELLY started work on JENKINS-38007 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37921) SSE failures and deadlocking with github auth plugin installed (needs investigation)
Title: Message Title Tom FENNELLY started work on JENKINS-37921 Change By: Tom FENNELLY Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33168) Junit plugin took 7 hours to complete recording test failures
Title: Message Title Tomasz Śniatowski commented on JENKINS-33168 Re: Junit plugin took 7 hours to complete recording test failures The problem does not reliably reproduce when we take a "bad" output xml and try to process it with the junit plugin on an idle test instance of Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32349) Entering a newline in a Label description makes "slave" matrix axis unavailable
Title: Message Title Tom Ghyselinck commented on JENKINS-32349 Re: Entering a newline in a Label description makes "slave" matrix axis unavailable Hi all, Any update on this? Not a major issues, but it makes our label descriptions hard to edit... With best regards, Tom. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Code changed in jenkins User: Thorsten Scherler Path: .gitignore pom.xml src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/edgeCases/folder.js src/test/js/failing.js src/test/js/log-karaoke/freestyle.js src/test/js/log-karaoke/freestylePing.js src/test/js/log-karaoke/noStages.js src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/freestylePing.sh http://jenkins-ci.org/commit/blueocean-acceptance-test/d3547caa37af515fcb1174bbd22265106aebc828 Log: Merge remote-tracking branch 'origin/master' into JENKINS-37323 Compare: https://github.com/jenkinsci/blueocean-acceptance-test/compare/5afc5f5bd859...d3547caa37af Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/log-karaoke/stages.js http://jenkins-ci.org/commit/blueocean-acceptance-test/b1ec3e1f137cd328d0ee83d5b0e56287b14a86b7 Log: JENKINS-37323 fix merge problem and make sure we returning always self and not coditional Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37831) Favoriting on Matrix style project broken
Title: Message Title Cliff Meyers commented on JENKINS-37831 Re: Favoriting on Matrix style project broken Ok that makes sense. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38059) Script editor should remember size
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-38059 Script editor should remember size Issue Type: Improvement Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2016/Sep/08 12:58 PM Priority: Minor Reporter: Max Wahler Everytime I configure a pipeline job, the script editor window gets its initial size even if I resized it on the last time. That's annoying if you want to edit a script that's longer than a few lines. In comparison, the "Execute shell" step remembers the editor's size. Add Comment
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-37519 Enhance "fetch" library to augment REST API responses with "Capabilities" metadata Pulling this forward because in order to fix JENKINS-37831 we need more capabilities logic, and we need to handle this more cleanly. Change By: Cliff Meyers Sprint: 1.0-beta- 2 1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38017) Better AT coverage for JENKINS-37323 - multiple syntaxed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38017 Re: Better AT coverage for JENKINS-37323 - multiple syntaxed Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/stages-with-wait-block-syntax.groovy src/test/resources/test_scripts/stages-with-wait-pipelineModel-syntax.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/9f546a028e30a1b1c46282c9c55be028414cf57a Log: [FIX JENKINS-38017 JENKINS-37323] Implement test cases with new syntax (#30) JENKINS-37323 Implement test cases with new syntax JENKINS-37323 adding all known pipeline syntax as test case JENKINS-37323 fix merge problem and make sure we returning always self and not coditional Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issu
[JIRA] (JENKINS-37519) Enhance "fetch" library to augment REST API responses with "Capabilities" metadata
Title: Message Title Cliff Meyers started work on JENKINS-37519 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37323) Ensure that Pipeline Graph can handle stage blocks
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37323 Re: Ensure that Pipeline Graph can handle stage blocks Code changed in jenkins User: Thorsten Scherler Path: src/main/js/page_objects/blueocean/bluePipelineActivity.js src/main/js/page_objects/blueocean/bluePipelineRunDetail.js src/test/js/log-karaoke/stages.js src/test/resources/test_scripts/stages-with-wait-block-syntax.groovy src/test/resources/test_scripts/stages-with-wait-pipelineModel-syntax.groovy http://jenkins-ci.org/commit/blueocean-acceptance-test/9f546a028e30a1b1c46282c9c55be028414cf57a Log: [FIX JENKINS-38017 JENKINS-37323] Implement test cases with new syntax (#30) JENKINS-37323 Implement test cases with new syntax JENKINS-37323 adding all known pipeline syntax as test case JENKINS-37323 fix merge problem and make sure we returning always self and not coditional Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+uns
[JIRA] (JENKINS-38060) Does not work with pipeline job
Title: Message Title Patrick Ruckstuhl created an issue Jenkins / JENKINS-38060 Does not work with pipeline job Issue Type: Bug Assignee: Unassigned Components: tracking-svn-plugin Created: 2016/Sep/08 1:06 PM Priority: Major Reporter: Patrick Ruckstuhl On a pipeline job, the track svn appears but is not actually used. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37835) Developer can remove items from the queue
Title: Message Title Cliff Meyers stopped work on JENKINS-37835 Change By: Cliff Meyers Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36569) Add 'Slaves' axis is broken
Title: Message Title Tom Ghyselinck commented on JENKINS-36569 Re: Add 'Slaves' axis is broken Please ignore my previous comments, It was due to issue JENKINS-32349. With best regards, Tom. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38017) Better AT coverage for JENKINS-37323 - multiple syntaxed
Title: Message Title Thorsten Scherler updated JENKINS-38017 Jenkins / JENKINS-38017 Better AT coverage for JENKINS-37323 - multiple syntaxed Change By: Thorsten Scherler Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: credentials id dropdown not populated I suppose you are talking about a global library, rather than a folder-scoped library? So the lack of credentialsId is a bug in the git plugin, in UserRemoteConfig.DescriptorImpl.doFillCredentialsIdItems. If project == null, it should offer global credentials, assuming you have Jenkins.ADMINISTER (I suppose). To make that easier, in credentials, includeMatchingAs should accept context == null. Unable to find nearby scm/id looks like a bug in this plugin, though it does not appear to break anything. TypeError: Cannot read property 'firstChild' of undefined I need to analyze. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38061) Please support the pipeline API and Jenkinsfile to the S3 plugin
Title: Message Title Oded Arbel created an issue Jenkins / JENKINS-38061 Please support the pipeline API and Jenkinsfile to the S3 plugin Issue Type: Bug Assignee: Alexander A Components: s3-plugin Created: 2016/Sep/08 1:27 PM Priority: Trivial Reporter: Oded Arbel The README for the s3-plugin mentions support for pipeline, but: there are no examples the snippet generator mentioned does not actually have the option to generate S3 publish steps Google came up empty when looking for examples of pipeline use with the S3 plugin So it doesn't look like its implemented. Because I've moved all of our builds to run through the Github integration with the automatic Jenkinsfile detection, I can't use any plugin that has no support for Jenkins file and I'd really like to be able to publish to S3. TIA Add Comment
[JIRA] (JENKINS-38061) Please support the pipeline API and Jenkinsfile to the S3 plugin
Title: Message Title Alexander A resolved as Fixed https://github.com/jenkinsci/s3-plugin/pull/91 Jenkins / JENKINS-38061 Please support the pipeline API and Jenkinsfile to the S3 plugin Change By: Alexander A Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: credentials id dropdown not populated Same applies to GitSCMSource, which you would be using if my PR to the git plugin were merged. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick started work on JENKINS-38048 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 credentials id dropdown not populated Change By: Jesse Glick Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 credentials id dropdown not populated Same applies in the subversion plugin and probably others as well. Change By: Jesse Glick Component/s: subversion-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: credentials id dropdown not populated In another context I get TypeError: Cannot read property 'value' of undefined from select.js:46 but I am not sure if it is related to global libraries. Unfortunately the Jenkins form _javascript_ does no sanity checking whatsoever and so freely throws errors with no diagnostic information whenever anything is amiss. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33632) docker.inside broken
Title: Message Title Danny Waite commented on JENKINS-33632 Re: docker.inside broken This very simple project (derived from Google's Jenkins/Kubernetes example) appears to be working: https://github.com/danny-waite/jenkins-sample-pipeline-app Great work, many thanks, will continue to more detailed testing, I realise this isn't done 'by the book', ie. the use of `sh` blocks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title
Christopher Shannon created an issue
Jenkins / JENKINS-38062
"Create Delivery Pipeline version" errors
Issue Type:
Improvement
Assignee:
Patrik Boström
Components:
delivery-pipeline-plugin, matrix-project-plugin
Created:
2016/Sep/08 2:27 PM
Environment:
Jenkins 2.7.2 Delivery Pipeline Plugin 0.9.12 Matrix Project Plugin 1.7.1
Labels:
delivery matrix
Priority:
Major
Reporter:
Christopher Shannon
Steps to reproduce:
Create freestyle job and select the "Create Delivery Pipeline version" option (providing something like foo.$ {BUILD_NUMBER} in the Template field.
Create a matrix build, with one user-defined axis and one input string parameter.
Trigger the matrix build as a post-build step from the freestyle job, passing in the single parameter.
Although everything runs okay, jenkins.err.log will show several errors about skipping parameters. {{Sep 08, 2016 9:03:26 AM hudson.model.ParametersAction filter WARNING: Skipped parameter `INPUT` as it is undefined on `Sandbox/Matrix/Downstream/AXIS=64`. Set `-Dhudson.model.ParametersAction.keepUndefinedParameters`=true to allow undefined parameters to be injected as environment variables or `-Dhudson.model.ParametersAction.safeParameters=[comma-separated list]` to whitelist specific parameter names, even tho
[JIRA] (JENKINS-38062) "Create Delivery Pipeline version" errors
Title: Message Title Christopher Shannon updated an issue Jenkins / JENKINS-38062 "Create Delivery Pipeline version" errors Change By: Christopher Shannon Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38063) An attempt to send an e-mail to empty list of recipients, ignored.
Title: Message Title Ajay Patil created an issue Jenkins / JENKINS-38063 An attempt to send an e-mail to empty list of recipients, ignored. Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2016/Sep/08 2:31 PM Priority: Critical Reporter: Ajay Patil I'm not able to send build notification email from my jenkin server. getting following error: "Checking if email needs to be generated Email was triggered for: Success Sending email for trigger: Success messageContentType = text/plain; charset=UTF-8 Collecting change authors... build: 49 Adding recipients from trigger recipient list Successfully created MimeMessage An attempt to send an e-mail to empty list of recipients, ignored. Some error occured trying to send the email...check the Jenkins log Finished: SUCCESS" Jenkins is installed on Mac OS . Current Jenkins version is 1.653 and Email Extension Plugin version is 2.47 I'm using smtp.gmail.com with port number 587 into email-ext config. Please help to resolve this issue. Add Comment
[JIRA] (JENKINS-38064) Jenkins - Dead locked
Title: Message Title NAVEEN SRINIVASAN created an issue Jenkins / JENKINS-38064 Jenkins - Dead locked Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2016/Sep/08 2:34 PM Priority: Minor Reporter: NAVEEN SRINIVASAN We are running jenkins and it is getting dead locked. Here is the thread dump. What can we do? "Jenkins initialization thread" #12 prio=5 os_prio=0 tid=0x7f94f8ae1800 nid=0x1a in Object.wait() [0x7f94e0163000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:267) locked <0x83561630> (a jenkins.model.Jenkins$8) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:937) at jenkins.model.Jenkins.(Jenkins.java:818) at hudson.model.Hudson.(Hudson.java:83) at hudson.model.Hudson.(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) "Java2D Disposer" #11 daemon prio=10 os_prio=0 tid=0x7f94f8a06000 nid=0x19 in Object.wait() [0x7f94e8109000] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) waiting on <0x8355e6b8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:143) locked <0x8355e6b8> (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:164) at sun.java2d.Disposer.run(Disposer.java:148) at java.lang.Thread.run(Thread.java:745) "HashSessionScavenger-0" #10 dae
[JIRA] (JENKINS-37726) Publish Over SSH plugin: shebang is fully ignored
Title: Message Title Alex Domoradov commented on JENKINS-37726 Re: Publish Over SSH plugin: shebang is fully ignored Any updates? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick updated JENKINS-38048 Jenkins / JENKINS-38048 credentials id dropdown not populated Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) credentials id dropdown not populated
Title: Message Title Jesse Glick commented on JENKINS-38048 Re: credentials id dropdown not populated Until maintainers of SCM plugins merge and release my PRs, workarounds would include: using folder-scoped (untrusted) libraries, rather than global using repositories that can be checked out anonymously, or using credentials stored at the OS level on the Jenkins master editing $JENKINS_HOME/org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml to include the desired credentialsId, then restarting Jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37917) Review permissions API for multi-branch pipeline
Title: Message Title Vivek Pandey started work on JENKINS-37917 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Jesse Glick Summary: credentials id dropdown not populated Credentials dropdowns empty when configuring external libraries at the global level Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38048 Credentials dropdowns empty when configuring external libraries at the global level Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32112) NullPointerExceptions about templates in various places
Title: Message Title pjdarton started work on JENKINS-32112 Change By: pjdarton Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32112) NullPointerExceptions about templates in various places
Title: Message Title pjdarton assigned an issue to pjdarton Jenkins / JENKINS-32112 NullPointerExceptions about templates in various places Change By: pjdarton Assignee: pjdarton Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26192) Add support for Grape (@Grab) in workflow scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26192 Re: Add support for Grape (@Grab) in workflow scripts Code changed in jenkins User: Jesse Glick Path: src/test/java/plugins/WorkflowPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/0a43987a7dfad296b0521a7e242bcb6e090dc0f1 Log: JENKINS-26192 workflow-cps-global-lib 2.3 was released. Amends #176. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Stephen Hassard commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
The following code does a good job of capturing the pwd without writing any files which causes issues when running inside the Groovy sandbox.
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
node {
env.WORKSPACE = sh(returnStdout: true, script: 'pwd').trim()
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Stephen Hassard edited a comment on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
The following code does a good job of capturing the pwd without writing any files which causes issues when running inside the Groovy sandbox.{code: groovy java }node {env.WORKSPACE = sh(returnStdout: true, script: 'pwd').trim()}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38026) Error while creating jira issue
Title: Message Title
Radek Antoniuk commented on JENKINS-38026
Re: Error while creating jira issue
WARNING: JIRA REST createIssue error: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={issuetype=valid issue type is required}, errorMessages=[]}]}
What issue types do you have defined in JIRA? Can you check the names and IDs that get returned from REST API?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32112) NullPointerExceptions about templates in various places
Title: Message Title pjdarton commented on JENKINS-32112 Re: NullPointerExceptions about templates in various places This is caused by a failure to check that the list of templates isn't null before attempting to iterate over them. If there's at least one template defined (in each vSphere cloud) then the bug won't appear (which is why that works as a workaround) but for users who aren't using templates that's not ideal... I've got a fix for this as part of JENKINS-36878 - if the code changes for that are accepted, this one will be fixed too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20743) How to obtain the secret to use when starting a slave with java from a scheduled task?
Title: Message Title pjdarton started work on JENKINS-20743 Change By: pjdarton Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20743) How to obtain the secret to use when starting a slave with java from a scheduled task?
Title: Message Title pjdarton assigned an issue to pjdarton Jenkins / JENKINS-20743 How to obtain the secret to use when starting a slave with java from a scheduled task? Change By: pjdarton Assignee: pjdarton Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title davidkarlsen commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Any progress on this? We´re a paying support customer with CB and have an issue open there as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-36121 Github Branch Source plugin trips api rate limit Change By: Jesse Glick Labels: github performance Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36121) Github Branch Source plugin trips api rate limit
Title: Message Title Jesse Glick commented on JENKINS-36121 Re: Github Branch Source plugin trips api rate limit I don't understand the use-case for not having a secret in place. Only that the github plugin does not support secret validation on webhooks, at least last I checked. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38049) FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script
Title: Message Title Andrew Bayer commented on JENKINS-38049 Re: FlowExecution.getResult() and FlowExecution.getCauseOfFailure() regression with Pipeline script So I'm not entirely clear on what's happening - we're using catchError extensively, so I assume that's swallowing failures? Sam Van Oort, Jesse Glick - do you have any ideas on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38065) "Recent Changes" link takes more than 10 minutes to display the results
Title: Message Title JayaPavanKumar Bhattiprolu created an issue Jenkins / JENKINS-38065 "Recent Changes" link takes more than 10 minutes to display the results Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Sep/08 3:49 PM Environment: Jenkins Version: 2.7.1 Installed Plugins and their versions: Email Extension Plugin -- 2.44 External Monitor Job Type Plugin -- 1.5 Git client plugin -- 1.19.6 Git plugin -- 2.5.2 JUnit Plugin -- 1.15 Mailer Plugin -- 1.17 Pipeline: Step API -- 2.2 SCM API Plugin -- 1.2 Script Security Plugin -- 1.21 Structs Plugin -- 1.2 Timestamper -- 1.8.4 Windows Slaves Plugin -- 1.1 Workspace Cleanup Plugin -- 0.29 Operating System -- Centos 6 Browser -- Google Chrome Priority: Minor Reporter: JayaPavanKumar Bhattiprolu We have installed Jenkins LTS version 2.7.1 on the new machine and created few jobs. And we are git-plugin to clone the git repo. After few builds generated (around 10 builds), If we click on "Recent Changes" link under the job it takes more than 10 minutes to display the consolidated changes. Please point me what went wrong for this issue? Thanks, Pavan
[JIRA] (JENKINS-38066) Fail to get selected Node, ${NODE_NODE} is empty
Title: Message Title
Yang Li created an issue
Jenkins / JENKINS-38066
Fail to get selected Node, ${NODE_NODE} is empty
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
nodelabelparameter-plugin
Created:
2016/Sep/08 3:51 PM
Priority:
Major
Reporter:
Yang Li
We use the node label parameter plugin to pass the name of the node selected to another plugin "Active Choices Plugin" that's replying on UI elements change, but when I use $ {NODE_NAME} as reference parameters, it didn't work, looks like it didn't response the value selected from Node drop down list. ${NODE_NAME} is empty before build, the value filled until it start to build. I can find $ {NODE_NAME} in environment variable. is it possible to auto response the value of drop down list dynamically? or am I using wrong UI element as reference parameters, but I did try with name "nodes" of Node definition. it didn't work neither. BTW, I was using "Disallow multi node selection when triggering build manually" to get single DDL.
Add Comment
[JIRA] (JENKINS-34433) pipeline lock does not retry
Title: Message Title recampbell updated an issue Jenkins / JENKINS-34433 pipeline lock does not retry Change By: recampbell Component/s: pipeline-utility-steps-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34433) pipeline lock does not retry
Title: Message Title recampbell assigned an issue to Unassigned Jenkins / JENKINS-34433 pipeline lock does not retry Change By: recampbell Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38066) Fail to get selected Node, ${NODE_NODE} is empty
Title: Message Title
Yang Li updated an issue
Jenkins / JENKINS-38066
Fail to get selected Node, ${NODE_NODE} is empty
Change By:
Yang Li
Attachment:
ACR_b02_param.gif
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38067) Failure to call Util.encode
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-38067 Failure to call Util.encode Issue Type: Bug Assignee: James Dumay Components: display-url-api-plugin Created: 2016/Sep/08 3:55 PM Labels: encoding Priority: Minor Reporter: Jesse Glick AbstractItem.getAbsoluteUrl calls Util.encode to deal with non-ASCII project names. (I suppose; not sure the exact motivation, but perhaps to allow URLs to be embedded in non-Unicode-safe content.) Yet ClassicDisplayURLProvider does not do this. Probably it should. Add Comment
