[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46715  
 
 
  Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 
 
Attachment: 
 TK-Branch-am-selben-Tag.png  
 
 
Attachment: 
 TK-Branch-am-selben-Tag-ClassicUI.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46715  
 
 
  Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 
 
Attachment: 
 TK-Branch-am-nächsten-Tag-BUG.png  
 
 
Attachment: 
 TK-Branch-am-nächsten-Tag-Stage-mit-Fehler-BUG.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder commented on  JENKINS-46715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
 Thorsten Scherler Yesterday I provoked an artifical reproducer by adding an error step at around the same point in the pipeline stage and while it looked OK immediately (or maybe ~1h) afterwards, this morning it is NOT anymore! 
 
Initially it is still OK: 
 
BO:  
Classic "Steps" view:  
  
Today it is broken: 
 
BO for pipeline:  
BO when selecting broken stage in pipeline:  
  
  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46715  
 
 
  Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 
 
Attachment: 
 TK-Branch-am-selben-Tag-ClassicUI.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46715  
 
 
  Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
Change By: 
 Reinhold Füreder  
 
 
Attachment: 
 TK-Branch-am-selben-Tag-ClassicUI.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51606) OTA Connectivity Issue with Jenkins 2.125 and HP ALM12.21 OTA (4848)

2018-10-31 Thread daniel.gr...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Gront assigned an issue to Tamas Florin  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-51606  
 
 
  OTA Connectivity Issue with Jenkins 2.125 and HP ALM12.21 OTA (4848)   
 

  
 
 
 
 

 
Change By: 
 Daniel Gront  
 
 
Assignee: 
 Roy Lu Tamas Florin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46715) Error steps may change to show up as errors in pipeline view

2018-10-31 Thread r.fuere...@xortex.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Reinhold Füreder edited a comment on  JENKINS-46715  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error steps may change to show up as errors in pipeline view   
 

  
 
 
 
 

 
 [~tscherler] Yesterday I provoked an artifical  new/up-to-date  reproducer  (version information: Jenkins Core 2.147, Jenkins Blue Ocean Plugin 1.9.0)  by adding an {{error}} step at around the same point in the pipeline stage and {color:#00875a}while it looked OK immediately (or maybe ~1h) afterwards{color}, {color:#de350b}this morning it is NOT anymore!{color} # Initially it is still OK: ## BO: !TK-Branch-am-selben-Tag.png|thumbnail! ## Classic "Steps" view:  !TK-Branch-am-selben-Tag-ClassicUI.png|thumbnail! # Today it is broken: ## BO for pipeline:  !TK-Branch-am-nächsten-Tag-BUG.png|thumbnail! ## BO when selecting broken stage in pipeline:  !TK-Branch-am-nächsten-Tag-Stage-mit-Fehler-BUG.png|thumbnail!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number

2018-10-31 Thread artem.fedo...@blazemeter.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Artem Fedorov commented on  JENKINS-54181  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number   
 

  
 
 
 
 

 
 Hi Liu Wang  I working on this issue now. I hope that I'll finished it today/tomorrow   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54361) Plugin name doesn't match UI, docs stale

2018-10-31 Thread cr...@2ndquadrant.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Ringer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54361  
 
 
  Plugin name doesn't match UI, docs stale   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 antisamy-markup-formatter-plugin  
 
 
Created: 
 2018-10-31 08:20  
 
 
Environment: 
 Jenkins 2.138.2, OWASP Markup Formatter Plugin 1.5  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Craig Ringer  
 

  
 
 
 
 

 
 The Jenkins UI and docs refer to the "Safe HTML" markup formatter. But there is really no such thing. It is implemented by the "OWASP Markup Formatter Plugin" (which links to "plugins.jenkins.io/antisamy-markup-formatter"). The "jenkinsci/antisamy-markup-formatter project has a 1.5 tag", and appears to be what Jenkins bundles. The plugin site mentions that policies are configurable, but there's no UI to configure policies. The "file with the extension in it, confusingly named RawHtmlMarkupFormatter" appears to have had any pluggability cut out, but the comment still reflects the old support: {{ // Use the policy defined above to sanitize the HTML. HtmlSanitizer.sanitize(markup, MyspacePolicy.POLICY_DEFINITION.apply(renderer)); }} so in practice it looks like you can only use the copy of the MyspacePolicy embedded in the plugin code. Hopefully this helps the next person who is utterly confused by this, when trying to figure out how to configure the "Safe HTML" formatter policy, allow additional tags in the "Safe HTML" markup formatter in Jenkins, etc.  
 

  
 
 
 
 

 

[JIRA] (JENKINS-54361) Plugin name doesn't match UI, docs stale

2018-10-31 Thread cr...@2ndquadrant.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Ringer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54361  
 
 
  Plugin name doesn't match UI, docs stale   
 

  
 
 
 
 

 
Change By: 
 Craig Ringer  
 

  
 
 
 
 

 
 The Jenkins UI and docs refer to the "Safe HTML" markup formatter. But there is really no such thing.It is implemented by the ["OWASP Markup Formatter Plugin"|http://wiki.jenkins-ci.org/display/JENKINS/OWASP+Markup+Formatter+Plugin] (which links to ["plugins.jenkins.io/antisamy-markup-formatter"|https://plugins.jenkins.io/antisamy-markup-formatter]).The ["jenkinsci/antisamy-markup-formatter project has a 1.5 tag"|https://github.com/jenkinsci/antisamy-markup-formatter-plugin/tree/antisamy-markup-formatter-1.5], and appears to be what Jenkins bundles.The plugin site mentions that policies are configurable, but there's no UI to configure policies. The ["file with the extension in it, confusingly named RawHtmlMarkupFormatter"|https://github.com/jenkinsci/antisamy-markup-formatter-plugin/blob/antisamy-markup-formatter-1.5/src/main/java/hudson/markup/RawHtmlMarkupFormatter.java] appears to have had any pluggability cut out, but the comment still reflects the old support:  {{  // Use the policy defined above to sanitize the HTML. }}  {{ HtmlSanitizer.sanitize(markup, MyspacePolicy.POLICY_DEFINITION.apply(renderer));  }}so in practice it looks like you can only use the copy of the MyspacePolicy embedded in the plugin code.Hopefully this helps the next person who is utterly confused by this, when trying to figure out how to configure the "Safe HTML" formatter policy, allow additional tags in the "Safe HTML" markup formatter in Jenkins, etc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
 

[JIRA] (JENKINS-54362) java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild

2018-10-31 Thread j...@newcombe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Newcombe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54362  
 
 
  java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Kohsuke Kawaguchi  
 
 
Components: 
 matrix-project-plugin  
 
 
Created: 
 2018-10-31 08:25  
 
 
Labels: 
 JEP-200  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Jack Newcombe  
 

  
 
 
 
 

 
 

 

23:19:07 FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild
23:19:07 java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; see https://jenkins.io/redirect/class-filter/
23:19:07 	at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546)
23:19:07 	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)
23:19:07 	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
23:19:07 	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)
23:19:07 	at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)
23:19:07 	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)
23:19:07 Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log for class org.jenkinsci.plugins.EnvironmentVarSetter
23:19:07 	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256)
23:19:07 	at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConv

[JIRA] (JENKINS-54362) java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild

2018-10-31 Thread j...@newcombe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Newcombe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54362  
 
 
  java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild   
 

  
 
 
 
 

 
Change By: 
 Jack Newcombe  
 

  
 
 
 
 

 
 {code:java}23:19:07 FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild23:19:07 java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; see https://jenkins.io/redirect/class-filter/23:19:07  at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)23:19:07  at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)23:19:07  at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)23:19:07  at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)23:19:07 Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.EnvironmentVarSetter#log for class org.jenkinsci.plugins.EnvironmentVarSetter23:19:07  at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256)23:19:07  at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224)23:19:07  at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138)23:19:07  at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209)23:19:07  at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)23:19:07  at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)23:19:07  at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88)23:19:07  at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64)23:19:07  at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69)23:19:07  at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)23:19:07  at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84)23:19:07  at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265)23:19:07  at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)

[JIRA] (JENKINS-54361) Plugin name doesn't match UI, docs stale

2018-10-31 Thread cr...@2ndquadrant.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Craig Ringer commented on  JENKINS-54361  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin name doesn't match UI, docs stale   
 

  
 
 
 
 

 
 I updated the wiki page. I don't have the access to update the plugins page, or the github repository's descriptive text. Both should really be changed to mention the three names it gets referred to, and the fact it's not configurable (anymore?).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive

2018-10-31 Thread re...@crisostomo.me (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Renzo Crisóstomo commented on  JENKINS-54187  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: EC2 Plugin deadlock leaving Jenkins unresponsive   
 

  
 
 
 
 

 
 I can confirm that we haven't experienced deadlocks since we downgrade to a version build on top of revision 67aba04d0c60e8db1134d068ea2c10bc3e961c90 (1.40.0).  FABRIZIO MANFREDI We're not using spot instances.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54354) Jenkins Window slave can not fetch from bitbucket

2018-10-31 Thread xavier.fust...@clarivate.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Xavier Fustero commented on  JENKINS-54354  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Window slave can not fetch from bitbucket   
 

  
 
 
 
 

 
 Hi Mark Waite,   thanks for looking at it. I looked for an answer to the mailing list first but I couldn't find an answer. Similar problems but different.  I have removed the GIT_SSH from Windows but getting the same error. I set it as I saw the Jenkins Job said: 

 
 Fetching upstream changes from ssh://g...@git.clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance.git
 > C:\Program Files\Git\bin\git.exe --version # timeout=10
 using GIT_SSH to set credentials rsa / deploy keys 

 and probably I read someone suggesting to set it in Windows to that value. I see you close it but just wanted to note I am using Jenkins 2.138.2 in case someone else is reading it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-54330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
 Oleg Nenashev there is zero point in assigning issues like this to me. My work current assignments since the past year mean that I only have time to provide API oversight on these plugins. When you assign issues to me it gives others a false sense of engagement.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54330  
 
 
  While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-54330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
 Oleg Nenashev in any case if you follow the stack trace the root cause seems to be `Caused by: java.lang.UnsupportedClassVersionError: jenkins/branch/MultiBranchProject ` That indicates that the reporter is likely not using the correct version of Java for the version of Jenkins they are using. Also seems strange that they are running such a really old version of Jenkins (i.e. 2.3) as indicated by jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.3.jar!/lib/hudson/actions.jelly:39:70 In summary. This isn't even an issue with branch-api  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54330  
 
 
  While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Component/s: 
 core  
 
 
Component/s: 
 branch-api-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Oleg Nenashev  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54330  
 
 
  While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54362) java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild

2018-10-31 Thread j...@newcombe.io (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jack Newcombe commented on  JENKINS-54362  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild   
 

  
 
 
 
 

 
 This feels like it might be a major or critical, but I'll leave that to the discretion of someone more familiar with JEP-200 related issues.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53940) Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly

2018-10-31 Thread michael.sel...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin started work on  JENKINS-53940  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53940) Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly

2018-10-31 Thread michael.sel...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin updated  JENKINS-53940  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53940  
 
 
  Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo commented on  JENKINS-16163  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: NullPointerException when sending post build emails - all triggers appear to be impacted   
 

  
 
 
 
 

 
 I had the same issues Email was triggered for: Always Sending email for trigger: Always ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Some error occured trying to send the email...check the Jenkins log  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53940) Octane UFT test integration - uft test discovery - localized tests name in Octane not shown correctly

2018-10-31 Thread michael.sel...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin stopped work on  JENKINS-53940  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53478) error 504 connecting Octane with Jenkins - Micro Focus Application Automation Tools

2018-10-31 Thread michael.sel...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Client input required to confirm and verify the bug.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53478  
 
 
  error 504 connecting Octane with Jenkins - Micro Focus Application Automation Tools   
 

  
 
 
 
 

 
Change By: 
 Michael Seldin  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54363  
 
 
  ERROR: Could not send email as a part of the post-build publishers.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 David van Laatum  
 
 
Components: 
 email-ext-plugin  
 
 
Created: 
 2018-10-31 09:17  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Huang Echo  
 

  
 
 
 
 

 
 Sending email for trigger: Always ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Some error occured trying to send the email...check the Jenkins log Finished: SUCCESS  
 

  
 
 
 
 

 
 
 

[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54363  
 
 
  ERROR: Could not send email as a part of the post-build publishers.   
 

  
 
 
 
 

 
Change By: 
 Huang Echo  
 

  
 
 
 
 

 
 |[Email Extension Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin] |Version: 2.63  Sending email for trigger: AlwaysERROR: Could not send email as a part of the post-build publishers.java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Some error occured trying to send the email...check the Jenkins logFinished: SUCCESS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atl

[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54363  
 
 
  ERROR: Could not send email as a part of the post-build publishers.   
 

  
 
 
 
 

 
Change By: 
 Huang Echo  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54363  
 
 
  ERROR: Could not send email as a part of the post-build publishers.   
 

  
 
 
 
 

 
Change By: 
 Huang Echo  
 

  
 
 
 
 

 
 |[Email Extension Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin] |Version: 2.63  Jenkin version: 2.121.2  Sending email for trigger: Always ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Some error occured trying to send the email...check the Jenkins log Finished: SUCCESS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 

[JIRA] (JENKINS-53402) Connection to ALM Octane server failed

2018-10-31 Thread michael.sel...@hpe.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Seldin commented on  JENKINS-53402  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Connection to ALM Octane server failed   
 

  
 
 
 
 

 
 From the logs you have provided, Jenkins could not connect to the Octane server. When you hit the test connection button in Octane Configuration in the Configurations page. Do you get connection successful message?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54206) Merged PRs not being removed from multibranch

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 If you say keep orphaned items forever then they will be kept forever  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54206  
 
 
  Merged PRs not being removed from multibranch   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53912  
 
 
  Unable to use SSHCheckoutTrait   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Component/s: 
 configuration-as-code-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54330  
 
 
  While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Assignee: 
 Oleg Nenashev  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-54330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
 Stephen Connolly maybe you want to remove yourself from the default assignee then. I am using "Automatic" assignee selection when I change components    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54330) While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.

2018-10-31 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev edited a comment on  JENKINS-54330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: While updating jenkins from 2.3 gets OOPS A problem occurred while processing the request.
 

  
 
 
 
 

 
 [~stephenconnolly] maybe you want to remove yourself from the default assignee then. I am using "Automatic" assignee selection when I change components  during triage.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53798) Add ability to suppress multibranch scan on build

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-53798  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add ability to suppress multibranch scan on build   
 

  
 
 
 
 

 
 Sounds like either the gerrit plugin is not implementing the event api support in scm-api and instead is triggering a full scan. This https://github.com/jenkinsci/scm-api-plugin/blob/master/docs/implementation.adoc#implementing-event-support details how that should be implemente. If the gerrit plugin was implementing event support, then only the affected branches would be scanned rather than a full scan. There is no requirement to add the feature you request to branch-api, rather the gerrit plugin needs to implement event support. Can you please change the component to reflect the gerrit plugin you are using  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53798) Add ability to suppress multibranch scan on build

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly resolved as Incomplete  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopen when you know the gerrit plugin that needs to add scm-api event support  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53798  
 
 
  Add ability to suppress multibranch scan on build   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Incomplete  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53719) No way to disable lightweight checkout for Multibranch projects

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-53719  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No way to disable lightweight checkout for Multibranch projects   
 

  
 
 
 
 

 
 Correct fix would be for the subversion plugin to implement traits support and then a trait could be added to suppress the lightweight checkout, e.g. https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/jenkins/scm/impl/subversion/SubversionSCMFileSystem.java#L84 could be something like: 

 

		@Override
		public boolean supports(SCMSource source) {
			return source instanceof SubversionSCMSource 
 && ((SubversionSCMSource)source).getTraits().get(SuppressLightweightCheckout.class) == null;
		}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53719) No way to disable lightweight checkout for Multibranch projects

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53719  
 
 
  No way to disable lightweight checkout for Multibranch projects   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Component/s: 
 subversion-plugin  
 
 
Component/s: 
 branch-api-plugin  
 
 
Component/s: 
 workflow-multibranch-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly commented on  JENKINS-53624  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Branch indexing schedules builds for other branches and repos   
 

  
 
 
 
 

 
 Sounds like you want to configure the Branch Build Strategies (and possibly install some of the branch build strategy plugins)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.

2018-10-31 Thread sar...@126.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Huang Echo updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54363  
 
 
  ERROR: Could not send email as a part of the post-build publishers.   
 

  
 
 
 
 

 
Change By: 
 Huang Echo  
 

  
 
 
 
 

 
 |[Email Extension Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin] |Version: 2.63  Win10 X86 Jenkin version: 2.121.2 Sending email for trigger: Always ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisherDescriptor.createSession(ExtendedEmailPublisherDescriptor.java:244) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:726) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:451) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:441) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:349) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.cleanUp(Build.java:196) at hudson.model.Run.execute(Run.java:1845) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Some error occured trying to send the email...check the Jenkins log Finished: SUCCESS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
   

[JIRA] (JENKINS-52179) Wrong data mapping on serialization

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52179  
 
 
  Wrong data mapping on serialization   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25412) Update JSch to 0.1.49

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-25412  
 
 
  Update JSch to 0.1.49   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-44611) Any way to restrict build for non-whitelisted users?

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-44611  
 
 
  Any way to restrict build for non-whitelisted users?
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48564) SCMSource.id should be part of out of the box API jelly

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48564  
 
 
  SCMSource.id should be part of out of the box API jelly   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53152) MultiBranch Pipeline repository scan broken

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53152  
 
 
  MultiBranch Pipeline repository scan broken   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53335) CHANGE_BRANCH for pull-request should return source branch, not pull-request pseudo-branch

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53335  
 
 
  CHANGE_BRANCH for pull-request should return source branch, not pull-request pseudo-branch   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47675) Events are not processed correctly, no builds until you hit scan.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47675  
 
 
  Events are not processed correctly, no builds until you hit scan.   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51051) Trying to start new docker container and get credential error on login

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51051  
 
 
  Trying to start new docker container and get credential error on login   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50160) Can't add credentials through https

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50160  
 
 
  Can't add credentials through https   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48385) Migrate from SCMHead to concrete subclass

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48385  
 
 
  Migrate from SCMHead to concrete subclass   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48241) Credentials being masked when passed to a shell script

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48241  
 
 
  Credentials being masked when passed to a shell script   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50998) Credentials selector "Add" button doesn't work in a repeatable property

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50998  
 
 
  Credentials selector "Add" button doesn't work in a repeatable property   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49566) credentials-plugin 2.1.16 breaks ssh-private-key connection to docker slaves

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49566  
 
 
  credentials-plugin 2.1.16 breaks ssh-private-key connection to docker slaves   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41895) Branch API support for Favourite Plugin

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41895  
 
 
  Branch API support for Favourite Plugin   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-20967) Cloud provisioning called when Jenkins is quieting Down

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-20967  
 
 
  Cloud provisioning called when Jenkins is quieting Down   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-16502) Permission to see an executor/slave

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-16502  
 
 
  Permission to see an executor/slave   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52683) Allow flexible source definition in WorkflowBranchProjectFactories

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52683  
 
 
  Allow flexible source definition in WorkflowBranchProjectFactories   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49645) Dynamically added credentials Add button doesn't work

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49645  
 
 
  Dynamically added credentials Add button doesn't work   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50037) Can't trigger a build remotrly

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50037  
 
 
  Can't trigger a build remotrly   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-36147) Expose a thread pool / queue for polling related tasks

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-36147  
 
 
  Expose a thread pool / queue for polling related tasks   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51912) Unable to add user scope credentials in jenkins 2.74 version

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51912  
 
 
  Unable to add user scope credentials in jenkins 2.74 version   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48536) Organization folder does not call afterSave on child multibranch projects

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48536  
 
 
  Organization folder does not call afterSave on child multibranch projects   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-33704) Multiple calls to the CloudRetentionStrategy when removing a node

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33704  
 
 
  Multiple calls to the CloudRetentionStrategy when removing a node   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51763) Hide credentials given to the dockerfile

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51763  
 
 
  Hide credentials given to the dockerfile   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49706) User should be able to configure the Credentials Plugin to store data in AWS KMS

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49706  
 
 
  User should be able to configure the Credentials Plugin to store data in AWS KMS   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-51240) Add option to block until completion of remote job

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-51240  
 
 
  Add option to block until completion of remote job   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-19817) JCE cannot authenticate the provider BC for Windows 7 Slave

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-19817  
 
 
  JCE cannot authenticate the provider BC for Windows 7 Slave   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52041) can't use docker-compose - minimized workspace name start with underscore

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52041  
 
 
  can't use docker-compose - minimized workspace name start with underscore
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-37570) Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-37570  
 
 
  Jenkins starts to response super slow after creating 400 branch jobs from Multi-branch-project   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-30513) multiple slaves spin up from multiple clouds

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-30513  
 
 
  multiple slaves spin up from multiple clouds   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52127) Connecting Jenkins and JIRA using Jenkins

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52127  
 
 
  Connecting Jenkins and JIRA using Jenkins
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52634) Job configuration screen stuck on LOADING after upgrade.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52634  
 
 
  Job configuration screen stuck on LOADING after upgrade.   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-30469) expose NodeMonitoring API for cloud slaves

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-30469  
 
 
  expose NodeMonitoring API for cloud slaves   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53049) Execute Jenkins Powershell job using another domain account

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53049  
 
 
  Execute Jenkins Powershell job using another domain account   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48775) Proxy authentication error 407 even if 'check proxy' works

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48775  
 
 
  Proxy authentication error 407 even if 'check proxy' works   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45478) Add support for utm_ query parameters

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45478  
 
 
  Add support for utm_ query parameters   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52291) Plug-ins should define their credential type. This type should be pre-selected.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52291  
 
 
  Plug-ins should define their credential type. This type should be pre-selected.   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-39785) Error in "Folder Computation" - any possibility to be notified?

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-39785  
 
 
  Error in "Folder Computation" - any possibility to be notified?   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-50000) Finish user and consumer guide for branch-api

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-5  
 
 
  Finish user and consumer guide for branch-api   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-31916) Broken Serializable structure for Slave class

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-31916  
 
 
  Broken Serializable structure for Slave class   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49999) Write user and consumer guide for metrics plugin

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-4  
 
 
  Write user and consumer guide for metrics plugin   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-46536) A pollSCM property in a multibranch pipeline should ignore checking the primary SCM

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-46536  
 
 
  A pollSCM property in a multibranch pipeline should ignore checking the primary SCM   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45771) Disable shallow clone when we know a merge will take place

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45771  
 
 
  Disable shallow clone when we know a merge will take place   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-52386) credentials() parameter does not support HTML in description

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52386  
 
 
  credentials() parameter does not support HTML in description   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45254) credential ID accepts a too narrow set of characters

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45254  
 
 
  credential ID accepts a too narrow set of characters   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-25863) Jenkins tries to build jobs on nodes that are removed

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-25863  
 
 
  Jenkins tries to build jobs on nodes that are removed   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-41073) MultiBranch projects should veto SCM Polling

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41073  
 
 
  MultiBranch projects should veto SCM Polling   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-40293) "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40293  
 
 
  "Add" button should allow opening the dialogue with a specific "Kind" of credential pre-selected   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-49717) no token field in Openshift OAuth token credential type

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-49717  
 
 
  no token field in Openshift OAuth token credential type   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45540) Refactor id-and-description tear-off

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45540  
 
 
  Refactor id-and-description tear-off   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-45235) UpdateCenter fails to find newer plugin versions from additional sites

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-45235  
 
 
  UpdateCenter fails to find newer plugin versions from additional sites   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-20075) Support moving credentials between credential stores

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-20075  
 
 
  Support moving credentials between credential stores   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-29647) java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path.

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-29647  
 
 
  java.lang.NoClassDefFoundError thrown by jenkins slave while the class is in the class path.   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-42280) Nullpointer on BasicSSHUserPrivateKey passphrase

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-42280  
 
 
  Nullpointer on BasicSSHUserPrivateKey passphrase   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47226) Provide easy access to git branch name in (single branch) Pipeline build

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47226  
 
 
  Provide easy access to git branch name in (single branch) Pipeline build   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-47699) Cannot use user-scoped credentials from pipeline input step parameters

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47699  
 
 
  Cannot use user-scoped credentials from pipeline input step parameters   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48772) Overescaped description of credentials

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48772  
 
 
  Overescaped description of credentials   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-48226) MultiBranch doesn't distinguish Branches and PRs

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-48226  
 
 
  MultiBranch doesn't distinguish Branches and PRs   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  1   2   3   >