[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in

2015-08-25 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28311 
 
 
 
  Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Gautier 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28311) Create CloudFoundry services via Plug-in

2015-06-11 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Ok, this is now implemented in v1.4 which I just pushed. It will be available tomorrow. Instead of the "Also delete bound services" checkbox, I ended up putting a "Reset service if already exists" checkbox after every service that you create. It's consistent with with "Reset app if already exists" checkbox, it allows the use-case of having one service reset and not the other, and it was actually easier to code in the UI (I'm not sure it's possible to have a single checkbox appear if the user adds one or more items from a repeating list, using Jelly taglibs). 
Cheers! 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28311 
 
 
 
  Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Gautier 
 
 
 

Status:
 
 In Progress Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Is

[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in

2015-06-03 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier started work on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 William Gautier 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier edited a comment on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works.If a service with the same name already exists, it  will  would  display a message about it, but  will  would  continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't.In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier edited a comment on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works.If a service with the same name already exists, it would display a message about it, but would continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't.In case of a  complete  reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier edited a comment on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. If a service with the same name already exists, it will display a message about it, but will continue normally without overwriting it, since the case of resetting the services would be covered by the "Also delete bound services" checkbox. This way you can also make sure services are created if they don't exist, but without having to reset them if they don't. In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation.I'll keep looking into 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-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier edited a comment on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication.Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. In case of a reset, this would also make sure the services are created after the app reset, but before the app re-creation. I'll keep looking into 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-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier commented on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 
Thinking about it more and trying it out, having another post-build action means that you'd have to specify the target, org, space, and your credentials again, which doesn't seem elegant. Internally, there would also be quite a bit of code duplication. 
Perhaps a simpler solution would be, in addition to the "Also delete bound services" checkbox mentioned previously, have an Add button labelled "Create services before application", which would expand to reveal "name", "type" and "plan" text fields, with the possibility of clicking Add again for more services, similarly to how the "Environment Variables" Add button works. 
I'll keep looking into 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-28311) Create CloudFoundry services via Plug-in

2015-06-02 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier commented on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 
Ah, you're right, I forgot that's not in the manifest anymore. In that case it seems your idea of making another post build action is probably the best, but that means in the case where you want to replace both the app and the services, service deletion and recreation will happen before the app deletion and recreation. This might be ok, but I will have to make sure nothing's wrong with that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in

2015-05-29 Thread andreas.buc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Buchen commented on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 

"Create services if they don't exist" under that, so it's available for either services in manifest files or services in the Jenkins config.
 
Not sure if this sufficient. At least to my knowledge, the manifest only contains the service instance name. But you would need service name ("postgress") and plan ("free") to actually be able to create it. I guess those additional parameters one would have to provide to the Jenkins plug-in?!? 
One cloud also also think along the lines of having another "post build action" besides "deploy to CF". For example, create (and drop and create) service instance. 
Thanks for the great work. The plug-in is being used daily  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28311) Create CloudFoundry services via Plug-in

2015-05-28 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier commented on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 
Somehow I missed this ticket earlier this month, sorry about that. 
That was definitely planned at some point, for the convenience of being able to push an app straight from a repo with no previous setup. For some reason though, Cloud Foundry dropped this functionality from the cf client (creating a service specified in manifest.yml straight from a cf push) so I decided to release the Jenkins plugin without it too. 
Seems like adding two checkboxes would cover all cases:  
 

"Also delete bound services" under the "Reset app if exists" checkbox, only available if that checkbox is checked.
 

"Create services if they don't exist" under that, so it's available for either services in manifest files and services in the Jenkins config.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28311) Create CloudFoundry services via Plug-in

2015-05-28 Thread willi...@activestate.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Gautier edited a comment on  JENKINS-28311 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 
 Somehow I missed this ticket earlier this month, sorry about that.That was definitely planned at some point, for the convenience of being able to push an app straight from a repo with no previous setup. For some reason though, Cloud Foundry dropped this functionality from the cf client (creating a service specified in manifest.yml straight from a cf push) so I decided to release the Jenkins plugin without it too.Seems like adding two checkboxes would cover all cases: * "Also delete bound services" under the "Reset app if exists" checkbox, only available if that checkbox is checked.* "Create services if they don't exist" under that, so it's available for either services in manifest files  and  or  services in the Jenkins config. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-28311) Create CloudFoundry services via Plug-in

2015-05-08 Thread andreas.buc...@gmail.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Buchen created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28311 
 
 
 
  Create CloudFoundry services via Plug-in  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 William Gautier 
 
 
 

Components:
 

 cloudfoundry-plugin 
 
 
 

Created:
 

 08/May/15 11:56 AM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andreas Buchen 
 
 
 
 
 
 
 
 
 
 
Hi William, 
do you have any plans to add functionality to create/delete services? 
I would like to setup my job so that I not only completely reset the application pushed, but also delete the service (a database) and create a from scratch and bind it to the application. 
Maybe it is a different "post build action", maybe an option to your plugin. 
Of course, I could isntall the cf command line utility. And add a shell build step. But then I cannot share the credentials - even have to put them visibly into the build job. 
Do you have such scenarios? Anf if so, how to you handle them? 
Andreas. 
BTW, thanks for your work. Plugin is being used all the time.