[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent

2017-03-29 Thread srl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Loomis commented on  JENKINS-42959  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed known_hosts verification for SSH agent   
 

  
 
 
 
 

 
 I needed this workaround from the mailing list: > ssh -o HostKeyAlgorithms=ssh-rsa slave2.example.com   The implication below is that Jenkins is using weaker encryption. https://groups.google.com/d/msgid/jenkinsci-users/7006ab93-7ca4-4063-baf6-7c844be60165%40googlegroups.com  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-36335) support regex for issue id pattern

2016-06-29 Thread srl...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Steven Loomis created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36335  
 
 
  support regex for issue id pattern   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 trac-publisher-plugin  
 
 
Created: 
 2016/Jun/29 10:03 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Steven Loomis  
 

  
 
 
 
 

 
 Just as in JENKINS-3665 - would like to be able to modify the regex used for the publisher.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
   

[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-10-14 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29816 
 
 
 
  $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Loomis 
 
 
 

Labels:
 
 plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-10-14 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis edited a comment on  JENKINS-29816 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 
 Q, any updates on this? We are mystified at how to emit a literal $  - not sure if this is a token issue [~slide_o_mix] 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-10-14 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis commented on  JENKINS-29816 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 
 
Q, any updates on this? We are mystified at how to emit a literal $ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [token-macro-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-10-14 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis edited a comment on  JENKINS-29816 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 
 [~williamg] That's a lot of dollar signs.. 2^3^  .. this has got to be the best workaround ever, and a smile of the day. And more importantly, thanks for the investigation and reply. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [token-macro-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-10-14 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis commented on  JENKINS-29816 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 
 
William Gautier That's a lot of dollar signs.. 2^3^ .. this has got to be the best workaround ever, and a smile of the day.  
And more importantly, thanks for the investigation and reply. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-29816) Document that $$ emits a literal $ in token-macro and thus cloudfoundry

2015-08-05 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29816 
 
 
 
  Document that $$ emits a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 William Gautier 
 
 
 

Components:
 

 cloudfoundry-plugin, token-macro-plugin 
 
 
 

Created:
 

 05/Aug/15 8:55 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Steven Loomis 
 
 
 
 
 
 
 
 
 
 
according to  
 https://github.com/jenkinsci/token-macro-plugin/blob/master/src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java#L72 
$$FOO expands to $FOO ( where $$ is a literal). Please document this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 

[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-08-05 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29816 
 
 
 
  $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Loomis 
 
 
 

Issue Type:
 
 Improvement Bug 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-08-05 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29816 
 
 
 
  $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Loomis 
 
 
 

Summary:
 
 Documentthat $$ emits shouldemit aliteral$intoken-macroandthuscloudfoundry 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-29816) $$ should emit a literal $ in token-macro and thus cloudfoundry

2015-08-05 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29816 
 
 
 
  $$ should emit a literal $ in token-macro and thus cloudfoundry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Steven Loomis 
 
 
 
 
 
 
 
 
 
 accordingtohttps://github.com/jenkinsci/token-macro-plugin/blob/master/src/main/java/org/jenkinsci/plugins/tokenmacro/Tokenizer.java#L72 onemightthinkthat $$FOOexpandsto$FOO(where$$isaliteral). Pleasedocumentthis …butitdoesn't,atleastnotinthecloudfoundryplugin . ERROR:Couldnotparsetokenmacro:Unrecognizedmacro'FOO'in'$FOO'tokenmacro1.10,cloudfoundry1.4.2(builtfromgit) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-28885) NPE when deploying w/o any services

2015-07-23 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis commented on  JENKINS-28885 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: NPE when deploying w/o any services  
 
 
 
 
 
 
 
 
 
 
Thanks! I'm unblocked, but it would be great to fix it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


[JIRA] [cloudfoundry-plugin] (JENKINS-28885) NPE when deploying w/o any services

2015-07-22 Thread srl...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steven Loomis commented on  JENKINS-28885 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: NPE when deploying w/o any services  
 
 
 
 
 
 
 
 
 
 
Filed here. The constructor's not being called. https://github.com/ActiveState/cloudfoundry-jenkins/issues/4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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