[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition

2016-09-01 Thread james....@capitalone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jimmy Ray edited a comment on  JENKINS-28178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to disable sandbox in CpsScmFlowDefinition   
 

  
 
 
 
 

 
 So, I know I am late to the party on this one, but we have been struggling with similar issues, making choices whether or not to use  `` CpsScmFlowDefinition ``  or  ` CpsFlowDefinition ` .  And it comes down to forced sandbox.  We considered rewriting the plugin, but we don't see that as a sustainable approach.  There are a lot of additional functionality that we would like to use.  I understand the security concerns around allowing sandbox behavior to be disabled at the job level.  It's the tug-of-war between DEV and OPS.  However, I would love to have this functionality.  Is toggling the sandbox behavior for  ` CpsScmFlowDefinition `  being considered?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition

2016-09-01 Thread james....@capitalone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jimmy Ray commented on  JENKINS-28178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to disable sandbox in CpsScmFlowDefinition   
 

  
 
 
 
 

 
 So, I know I am late to the party on this one, but we have been struggling with similar issues, making choices whether or not to use `CpsScmFlowDefinition` or `CpsFlowDefinition`. And it comes down to forced sandbox. We considered rewriting the plugin, but we don't see that as a sustainable approach. There are a lot of additional functionality that we would like to use. I understand the security concerns around allowing sandbox behavior to be disabled at the job level. It's the tug-of-war between DEV and OPS. However, I would love to have this functionality.  Is toggling the sandbox behavior for `CpsScmFlowDefinition` being considered?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] (JENKINS-28178) Option to disable sandbox in CpsScmFlowDefinition

2016-09-01 Thread james....@capitalone.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jimmy Ray edited a comment on  JENKINS-28178  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Option to disable sandbox in CpsScmFlowDefinition   
 

  
 
 
 
 

 
 So, I know I am late to the party on this one, but we have been struggling with similar issues, making choices whether or not to use ` ` CpsScmFlowDefinition` `  or `CpsFlowDefinition`.  And it comes down to forced sandbox.  We considered rewriting the plugin, but we don't see that as a sustainable approach.  There are a lot of additional functionality that we would like to use.  I understand the security concerns around allowing sandbox behavior to be disabled at the job level.  It's the tug-of-war between DEV and OPS.  However, I would love to have this functionality.  Is toggling the sandbox behavior for `CpsScmFlowDefinition` being considered?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





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


[JIRA] [workflow-plugin] (JENKINS-26055) DurableTaskStep

2016-05-31 Thread james....@capitalone.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jimmy Ray commented on  JENKINS-26055 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DurableTaskStep  
 
 
 
 
 
 
 
 
 
 
So, I have a similar need here. I wrote and published the Consul KV Builder Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Consul-KV-Builder+Plugin) that allows jobs to be configured to Read/Write/Delete Key/Value data from/to Hashicorp Consul servers. In the READ mode, the configured build step reads data from Consul and writes ENV variables. So, that currently cannot work with SimpleBuildStep. I am looking into alternatives with SimpleBuildWrapper, but I don't know if that will work either. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.