[JIRA] [cloudfoundry-plugin] (JENKINS-29514) Temporary files aren't cleaned before Jenkins master is restarted
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-29514 Temporary files aren't cleaned before Jenkins master is restarted 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-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier closed an issue as Fixed Jenkins / JENKINS-28602 Error: Default domain calculated from api domain 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
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-29717) Exception during push
Title: Message Title William Gautier resolved as Fixed Version 1.4.2 is out now and includes this fix. You should see the correct CloudOperationException when doing your push. Jenkins / JENKINS-29717 Exception during push Change By: William Gautier Status: InProgress 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 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
Title: Message Title William Gautier resolved as Fixed Version 1.4.2 is out now and has backwards compatibility with configurations from old versions. Jenkins / JENKINS-28885 NPE when deploying w/o any services Change By: William Gautier Status: InProgress 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 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-29717) Exception during push
Title: Message Title William Gautier commented on JENKINS-29717 Re: Exception during push On second thought, I've decided to temporarily include my version of the cf-java-client which includes the fix from the pull request, until my pull request gets included in a new version of the upstream repo (which might take some time considering the latest commit is 2 months ago) So the Jenkins plugin v1.4.2 will correctly show you a CloudOperationException with the error message from the target. 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-29717) Exception during push
Title: Message Title William Gautier commented on JENKINS-29717 Re: Exception during push Bad news, the latest version of the cf-java-client has a different problem which causes an exception when doing a job polling request for a job that failed... I've created a pull request for it, but it won't help until the next cf-java-client release. Since I've already commited it, I will still release a new version (which fixes another bug) with the updated cf-java-client, but chances are you will meet a NullPointerException instead of this Could not read JSON error, so it won't do you much good. 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-29717) Exception during push
Title: Message Title William Gautier edited a comment on JENKINS-29717 Re: Exception during push Foundsometimetolookintothis.Theproblemisthatthecf-java-client1.0.6isassumingeveryresponsetoajobpollingrequesttobeajsonmappableto`MapString,MapString,String`.[(Link)|https://github.com/cloudfoundry/cf-java-client/blob/1aa083608ca6710d2cd81bf95db37947518a12a1/cloudfoundry-client-lib/src/main/java/org/cloudfoundry/client/lib/rest/CloudControllerClientImpl.java#L1286]Howeverincaseofanerror,[thejsonreturned|http://apidocs.cloudfoundry.org/215/jobs/retrieve_job_with_known_failure.html]hasanextrafield'error_details',whichdoesn'tfitintothatMap,causingtheerror.Luckily[thiswasalreadyfixedinamorerecentversion|https://github.com/cloudfoundry/cf-java-client/blob/master/cloudfoundry-client-lib/src/main/java/org/cloudfoundry/client/lib/rest/CloudControllerClientImpl.java#L1444],soallI'llneedtodoisupdatemydependencyofthecf-java-client. Thiswon'tfixyourerror,butatleastyou'llbeabletoseewhattheerroractuallyis:) 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-29717) Exception during push
Title: Message Title William Gautier commented on JENKINS-29717 Re: Exception during push Found some time to look into this. The problem is that the cf-java-client 1.0.6 is assuming every response to a job polling request to be a json mappable to `MapString, MapString, String`. (Link) However in case of an error, the json returned has an extra field 'error_details', which doesn't fit into that Map, causing the error. Luckily this was already fixed in a more recent version, so all I'll need to do is update my dependency of the cf-java-client. 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-29717) Exception during push
Title: Message Title William Gautier edited a comment on JENKINS-29717 Re: Exception during push Foundsometimetolookintothis.Theproblemisthatthecf-java-client1.0.6isassumingeveryresponsetoajobpollingrequesttobeajsonmappableto`MapString,MapString,String`.[(Link)|https://github.com/cloudfoundry/cf-java-client/blob/1aa083608ca6710d2cd81bf95db37947518a12a1/cloudfoundry-client-lib/src/main/java/org/cloudfoundry/client/lib/rest/CloudControllerClientImpl.java#L1286]Howeverincaseofanerror,[thejsonreturned|http://apidocs.cloudfoundry.org/215/jobs/retrieve_job_with_known_failure.html]hasanextrafield'error_details',whichdoesn'tfitintothatMap,causingthe error exception .Luckily[thiswasalreadyfixedinamorerecentversion|https://github.com/cloudfoundry/cf-java-client/blob/master/cloudfoundry-client-lib/src/main/java/org/cloudfoundry/client/lib/rest/CloudControllerClientImpl.java#L1444],soallI'llneedtodoisupdatemydependencyofthecf-java-client.Thiswon'tfixyourerror,butatleastyou'llbeabletoseewhattheerroractuallyis:) 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-29717) Exception during push
Title: Message Title William Gautier started work on JENKINS-29717 Change By: William Gautier Status: Open InProgress 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-29717) Exception during push
Title: Message Title William Gautier commented on JENKINS-29717 Re: Exception during push Somebody else also reported this problem. I believe this is the cf-java-client receiving an unexpected json from the push call, probably receiving an error from the target. Unfortunately that deserialization error from the cf-java-client is masking the actual error from the target. I'm going to look into this. 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
Title: Message Title William Gautier started work on JENKINS-28885 Change By: William Gautier Status: Open InProgress 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
Title: Message Title William Gautier commented on JENKINS-28885 Re: NPE when deploying w/o any services Thanks to what Steven has found, I figured out what was happening. 1.4.0 introduced a new configuration field for the creation of services. But the publisher constructor is only called when you go in your job's configuration page and click Apply or Save. So if you upgrade from an old version of the plugin, and run a new build without changing the configuration page, this new field stays null since you skip the constructor and the null check. It seems Jenkins provides a method to implement in order to deal with this backwards compatibility problem, as described on this wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility I'll be looking at how other plugins implement this method, and I'll release a new minor version soon that will fix backwards compatibility. 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-29514) Temporary files aren't cleaned before Jenkins master is restarted
Title: Message Title William Gautier resolved as Fixed This should now be fixed in the new minor version 1.4.1. Jenkins / JENKINS-29514 Temporary files aren't cleaned before Jenkins master is restarted Change By: William Gautier Status: InProgress 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 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-29514) Temporary files aren't cleaned before Jenkins master is restarted
Title: Message Title William Gautier commented on JENKINS-29514 Re: Temporary files aren't cleaned before Jenkins master is restarted Yes that's an oversight, I misunderstood how deleteOnExit() worked. Thanks for the report, I'll be working on this. 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-29514) Temporary files aren't cleaned before Jenkins master is restarted
Title: Message Title William Gautier started work on JENKINS-29514 Change By: William Gautier Status: Open InProgress 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
Title: Message Title William Gautier commented on JENKINS-28885 Re: NPE when deploying w/o any services It seems a saved 1.3.x configuration does not convert well into the 1.4 configuration because of the added option. I'll have to see what I can do about that next time. To fix your problem, have you tried adding a service creation, applying the changes, then removing the service creation and applying the changes again, like Andreas did? 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
Title: Message Title William Gautier commented on JENKINS-28885 Re: NPE when deploying w/o any services Then this might just be a fluke in the conversion of your existing configuration to the new version. I'll wait a while and close this if you or nobody else meets this anymore. 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
Title: Message Title
William Gautier edited a comment on JENKINS-28885
Re: NPE when deploying w/o any services
StrangelyIcan'treproducethis.Itwouldalsohavebeencaughtbytheautomatedtests.AnullserviceToCreatevarshouldbecaughthereduringtheconstructiontoo,whichmakesthisdoublystrange:https://github.com/ActiveState/cloudfoundry-jenkins/blob/08761076bf672a94fe2e8a76ef246feec143eb8e/src/main/java/com/activestate/cloudfoundryjenkins/CloudFoundryPushPublisher.java#L77MaybethisisduetodifferencesinthewaydifferentJenkinsversionshandleemptyrepeatablelists. Whatversionareyouusing? Canyouattachthe{{config.xml}}filewhichshouldbein{{jenkins/jobs/your-job-name/}}?Thanks!
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
Title: Message Title
William Gautier edited a comment on JENKINS-28885
Re: NPE when deploying w/o any services
StrangelyIcan'treproducethis.Itwouldalsohavebeencaughtbytheautomatedtests.AnullserviceToCreatevarshouldbecaughthereduringtheconstructiontoo,whichmakesthisdoublystrange:https://github.com/ActiveState/cloudfoundry-jenkins/blob/08761076bf672a94fe2e8a76ef246feec143eb8e/src/main/java/com/activestate/cloudfoundryjenkins/CloudFoundryPushPublisher.java#L77MaybethisisduetodifferencesinthewaydifferentJenkinsversionshandleemptyrepeatablelists.Canyouattachthe {{ config.xml }} filewhichshouldbein {{ jenkins/jobs/your-job-name/ }} ?Thanks!
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
Title: Message Title William Gautier commented on JENKINS-28885 Re: NPE when deploying w/o any services Strangely I can't reproduce this. It would also have been caught by the automated tests. A null serviceToCreate var should be caught here during the construction too, which makes this doubly strange: https://github.com/ActiveState/cloudfoundry-jenkins/blob/08761076bf672a94fe2e8a76ef246feec143eb8e/src/main/java/com/activestate/cloudfoundryjenkins/CloudFoundryPushPublisher.java#L77 Maybe this is due to differences in the way different Jenkins versions handle empty repeatable lists. Can you attach the config.xml file which should be in jenkins/jobs/your-job-name/? Thanks! 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
Title: Message Title William Gautier edited a comment on JENKINS-28885 Re: NPE when deploying w/o any services StrangelyIcan'treproducethis.Itwouldalsohavebeencaughtbytheautomatedtests.AnullserviceToCreatevarshouldbecaughthereduringtheconstructiontoo,whichmakesthisdoublystrange:https://github.com/ActiveState/cloudfoundry-jenkins/blob/08761076bf672a94fe2e8a76ef246feec143eb8e/src/main/java/com/activestate/cloudfoundryjenkins/CloudFoundryPushPublisher.java#L77MaybethisisduetodifferencesinthewaydifferentJenkinsversionshandleemptyrepeatablelists.Canyouattachtheconfig.xmlfilewhichshouldbeinjenkins/jobs/your-job-name/?Thanks! 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
Title: Message Title
William Gautier edited a comment on JENKINS-28885
Re: NPE when deploying w/o any services
StrangelyIcan'treproducethis.Itwouldalsohavebeencaughtbytheautomatedtests.AnullserviceToCreatevarshouldbecaughthereduringtheconstructiontoo,whichmakesthisdoublystrange:https://github.com/ActiveState/cloudfoundry-jenkins/blob/08761076bf672a94fe2e8a76ef246feec143eb8e/src/main/java/com/activestate/cloudfoundryjenkins/CloudFoundryPushPublisher.java#L77MaybethisisduetodifferencesinthewaydifferentJenkinsversionshandleemptyrepeatablelists. Whatversionareyouusing? Canyouattachthe{{config.xml}}filewhichshouldbein{{jenkins/jobs/your-job-name/}}?Thanks!
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
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: InProgress 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 Issues
[JIRA] [cloudfoundry-plugin] (JENKINS-28311) Create CloudFoundry services via Plug-in
Title: Message Title William Gautier started work on JENKINS-28311 Change By: William Gautier Status: Open InProgress 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-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier resolved as Fixed Fixed in https://github.com/jenkinsci/cloudfoundry/commit/9f2693ee5953baf6c2f0f30f4bb99119c8ed06a9 Will be in v1.4, with the service creation feature. Jenkins / JENKINS-28602 Error: Default domain calculated from api domain Change By: William Gautier Status: InProgress 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 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
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
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
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinkingaboutitmoreandtryingitout,havinganotherpost-buildactionmeansthatyou'dhavetospecifythetarget,org,space,andyourcredentialsagain,whichdoesn'tseemelegant.Internally,therewouldalsobequiteabitofcodeduplication.Perhapsasimplersolutionwouldbe,inadditiontotheAlsodeleteboundservicescheckboxmentionedpreviously,haveanAddbuttonlabelledCreateservicesbeforeapplication,whichwouldexpandtorevealname,typeandplantextfields,withthepossibilityofclickingAddagainformoreservices,similarlytohowtheEnvironmentVariablesAddbuttonworks. Incaseofareset,thiswouldalsomakesuretheservicesarecreatedaftertheappreset,butbeforetheappre-creation. I'llkeeplookingintoit. 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
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinkingaboutitmoreandtryingitout,havinganotherpost-buildactionmeansthatyou'dhavetospecifythetarget,org,space,andyourcredentialsagain,whichdoesn'tseemelegant.Internally,therewouldalsobequiteabitofcodeduplication.Perhapsasimplersolutionwouldbe,inadditiontotheAlsodeleteboundservicescheckboxmentionedpreviously,haveanAddbuttonlabelledCreateservicesbeforeapplication,whichwouldexpandtorevealname,typeandplantextfields,withthepossibilityofclickingAddagainformoreservices,similarlytohowtheEnvironmentVariablesAddbuttonworks. Ifaservicewiththesamenamealreadyexists,itwilldisplayamessageaboutit,butwillcontinuenormallywithoutoverwritingit,sincethecaseofresettingtheserviceswouldbecoveredbytheAlsodeleteboundservicescheckbox.Thiswayyoucanalsomakesureservicesarecreatediftheydon'texist,butwithouthavingtoresetthemiftheydon't. Incaseofareset,thiswouldalsomakesuretheservicesarecreatedaftertheappreset,butbeforetheappre-creation.I'llkeeplookingintoit. 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
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinkingaboutitmoreandtryingitout,havinganotherpost-buildactionmeansthatyou'dhavetospecifythetarget,org,space,andyourcredentialsagain,whichdoesn'tseemelegant.Internally,therewouldalsobequiteabitofcodeduplication.Perhapsasimplersolutionwouldbe,inadditiontotheAlsodeleteboundservicescheckboxmentionedpreviously,haveanAddbuttonlabelledCreateservicesbeforeapplication,whichwouldexpandtorevealname,typeandplantextfields,withthepossibilityofclickingAddagainformoreservices,similarlytohowtheEnvironmentVariablesAddbuttonworks.Ifaservicewiththesamenamealreadyexists,it will would displayamessageaboutit,but will would continuenormallywithoutoverwritingit,sincethecaseofresettingtheserviceswouldbecoveredbytheAlsodeleteboundservicescheckbox.Thiswayyoucanalsomakesureservicesarecreatediftheydon'texist,butwithouthavingtoresetthemiftheydon't.Incaseofareset,thiswouldalsomakesuretheservicesarecreatedaftertheappreset,butbeforetheappre-creation.I'llkeeplookingintoit. 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
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in Thinkingaboutitmoreandtryingitout,havinganotherpost-buildactionmeansthatyou'dhavetospecifythetarget,org,space,andyourcredentialsagain,whichdoesn'tseemelegant.Internally,therewouldalsobequiteabitofcodeduplication.Perhapsasimplersolutionwouldbe,inadditiontotheAlsodeleteboundservicescheckboxmentionedpreviously,haveanAddbuttonlabelledCreateservicesbeforeapplication,whichwouldexpandtorevealname,typeandplantextfields,withthepossibilityofclickingAddagainformoreservices,similarlytohowtheEnvironmentVariablesAddbuttonworks.Ifaservicewiththesamenamealreadyexists,itwoulddisplayamessageaboutit,butwouldcontinuenormallywithoutoverwritingit,sincethecaseofresettingtheserviceswouldbecoveredbytheAlsodeleteboundservicescheckbox.Thiswayyoucanalsomakesureservicesarecreatediftheydon'texist,butwithouthavingtoresetthemiftheydon't.Incaseofa complete reset,thiswouldalsomakesuretheservicesarecreatedaftertheappreset,butbeforetheappre-creation.I'llkeeplookingintoit. 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
Title: Message Title William Gautier edited a comment on JENKINS-28311 Re: Create CloudFoundry services via Plug-in SomehowImissedthisticketearlierthismonth,sorryaboutthat.Thatwasdefinitelyplannedatsomepoint,fortheconvenienceofbeingabletopushanappstraightfromarepowithnoprevioussetup.Forsomereasonthough,CloudFoundrydroppedthisfunctionalityfromthecfclient(creatingaservicespecifiedinmanifest.ymlstraightfromacfpush)soIdecidedtoreleasetheJenkinspluginwithoutittoo.Seemslikeaddingtwocheckboxeswouldcoverallcases:*AlsodeleteboundservicesundertheResetappifexistscheckbox,onlyavailableifthatcheckboxischecked.*Createservicesiftheydon'texistunderthat,soit'savailableforeitherservicesinmanifestfiles and or servicesintheJenkinsconfig. 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-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier commented on JENKINS-28602 Re: Error: Default domain calculated from api domain There is a getDefaultDomain() method in the cf-java-client, so this should be possible, and probably should have been done in the first place. It will need a little refactoring since the domain is currently needed before the client is instantiated, but this shouldn't be too much trouble so I'll work on 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-28602) Error: Default domain calculated from api domain
Title: Message Title William Gautier started work on JENKINS-28602 Change By: William Gautier Status: Open InProgress 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
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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier resolved as Fixed I tried a few things, but unfortunately I did not manage to find the cause of this yet. This problem appeared with the internal dependency changes from v1.3.1, so I've decided to revert those changes for now That change had real convenience benefits for future work and I'm not satisfied with having to revert it, but this way the current version is not broken. I will be able to find a way to get the dependency changes back later, especially now that I know that this problem exists and how to test it. The revert is in version 1.3.3. Please update your plugin and this problem should be gone. Jenkins / JENKINS-28210 FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Change By: William Gautier Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [cloudfoundry-plugin] (JENKINS-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Itriedafewthings,butunfortunatelyIdidnotmanagetofindthecauseofthisyet.Thisproblemappearedwiththeinternaldependencychangesfromv1.3.1,soI'vedecidedtorevertthosechangesfornow . ThatchangehadrealconveniencebenefitsforfutureworkandI'mnotsatisfiedwithhavingtorevertit,butthiswaythecurrentversionisnotbroken.Iwillbeabletofindawaytogetthedependencychangesbacklater,especiallynowthatIknowthatthisproblemexistsandhowtotestit.Therevertisinversion1.3.3.Pleaseupdateyourpluginandthisproblemshouldbegone. 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier started work on JENKINS-28210 Change By: William Gautier Status: Open InProgress 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Just an update, 3 people have reported this now so I've confirmed it. I haven't been able to reproduce it myself, but somebody gave me access to a Jenkins instance where this problem happens. I'll be taking a look as soon as I have some free cycles. 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Lookslikeit'shavingproblemsconnectingtoLoggregator.ButIcan'tseemtoreproduceyourissue.*DoespushingyourapptoyourtargetviatheCloudFoundrycommandlineclientwork?*Haveyoutriedadifferentapplication,oradifferentcloudtarget(suchasafreetrial form from run.pivotal.io)?*DoescheckingResetappifalreadyexistschangeanything? 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier edited a comment on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype ItriedagainbutIcan'treproducethis.Usingyourownapplication,thesameJenkinsversion,andabrandnewrun.pivotal.iotrial,yourapplicationpushesfinewithme. Isit It's possiblethatthiscomesfromyourTomcatinstallation ? . Googlingtheexception,Ifound[thisthread|https://groups.google.com/forum/#!topic/cometd-users/0V5YmtrAHi8]whichcouldindicatetheproblemcomesfromadependencyconflict. 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype I tried again but I can't reproduce this. Using your own application, the same Jenkins version, and a brand new run.pivotal.io trial, your application pushes fine with me. Is it possible that this comes from your Tomcat installation? Googling the exception, I found this thread which could indicate the problem comes from a dependency conflict. 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-28210) FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype
Title: Message Title William Gautier commented on JENKINS-28210 Re: FATAL: javax.websocket.ContainerProvider: Provider org.apache.tomcat.websocket.WsContainerProvider not a subtype Looks like it's having problems connecting to Loggregator. But I can't seem to reproduce your issue. Does pushing your app to your target via the Cloud Foundry command line client work? Have you tried a different application, or a different cloud target (such as a free trial form run.pivotal.io)? Does checking Reset app if already exists change anything? 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-25884) configure name of manifest.yml
William Gautier closed JENKINS-25884 as Fixed configure name of manifest.yml Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier closed JENKINS-27119 as Fixed path attribute in manifest.yml is not evaluated relative to the manifest.yml file Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier closed JENKINS-27146 as Fixed Deploying an applicatin w/ no-route fails because route deletion fails Change By: William Gautier (20/Apr/15 11:48 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier resolved JENKINS-27119 as Fixed path attribute in manifest.yml is not evaluated relative to the manifest.yml file Fixed in https://github.com/jenkinsci/cloudfoundry/commit/7ccca26c11bb0702619d28ba58e81546c7ff0f1e Will be available in v1.3 soon Change By: William Gautier (09/Mar/15 9:33 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Indeed, I started using java.nio.file.Path in the latest commit, and it looks like it converts file paths to the current file system's syntax. Jenkins' FilePath should be able to parse any kind of path, so I believe this is only a failure of the tests. It shouldn't be too much trouble to change them to succeed no matter the file system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Re-Fixed in https://github.com/jenkinsci/cloudfoundry/commit/bf79387ddf68259b227eb1f73cccba6d6e94fbbe Hopefully for good this time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26546) Deploy all applications defined in manifest.yml file
William Gautier closed JENKINS-26546 as Fixed Deploy all applications defined in manifest.yml file Change By: William Gautier (03/Mar/15 5:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25882) Integrate with credentials plugin
William Gautier closed JENKINS-25882 as Fixed Integrate with credentials plugin Change By: William Gautier (03/Mar/15 5:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26182) Services Are Not Persisted In Configuration
William Gautier closed JENKINS-26182 as Fixed Services Are Not Persisted In Configuration Change By: William Gautier (03/Mar/15 5:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26598) CloudFoundry client needs proxy configuration for deployment
William Gautier closed JENKINS-26598 as Fixed CloudFoundry client needs proxy configuration for deployment Change By: William Gautier (03/Mar/15 5:26 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25884) configure name of manifest.yml
William Gautier resolved JENKINS-25884 as Fixed configure name of manifest.yml Token macros expansion now implemented in https://github.com/jenkinsci/cloudfoundry/commit/bdf318f12da0a27f49f619226a625be1ca1add59 Will be available in v1.3 Change By: William Gautier (03/Mar/15 5:33 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier resolved JENKINS-27146 as Fixed Deploying an applicatin w/ no-route fails because route deletion fails Fixed in https://github.com/jenkinsci/cloudfoundry/commit/559ceb0ffad960cc058026f2edbf9da6f1cf08e3 Will be available in v1.3 Change By: William Gautier (03/Mar/15 5:31 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier started work on JENKINS-27119 path attribute in manifest.yml is not evaluated relative to the manifest.yml file Change By: William Gautier (03/Mar/15 5:37 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails No problem! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27119) path attribute in manifest.yml is not evaluated relative to the manifest.yml file
William Gautier commented on JENKINS-27119 path attribute in manifest.yml is not evaluated relative to the manifest.yml file Confirmed, will be fixed in v1.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25884) configure name of manifest.yml
William Gautier started work on JENKINS-25884 configure name of manifest.yml Change By: William Gautier (02/Mar/15 8:32 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Would you prefer to update your pull request or should I fix this problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails You're right, looks like the noroute option is supposed to unbind, not remove. The Go client unbinds all routes from the application. There is a way to unbind routes from the Java client, but it's hidden in the updateApplicationUris() method. If you follow to the private removeUris() method, you'll see that it unbinds routes. So it seems that unbinding every route from an app would be simply done by passing an empty List to updateApplicationUris(). As a final note: I was actually wrong earlier when saying that createApplication() always creates a route. Passing an empty List as the `uris` parameter creates no route. Knowing this, it would be best to prevent the route creation if `noroute` is set, before calling updateApplicationUris(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier commented on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Thanks for the pull request! From what I understand CloudFoundryClient.createApplication() always creates a new route, so it is then deleted if "no-route: true" is set. That was a bit of a naive implementation of "no-route". Looking into it, the CF Go client's documentation says "no-route: Do not map a route to this app and remove routes from previous pushes of this app.". So to copy this behaviour it would be best to just cycle through all routes and delete them. Also this way you wouldn't have to check if the particular route created during this deployment exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier edited a comment on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Thanks for the pull request! From what I understand CloudFoundryClient.createApplication() always creates a new route, so it is then deleted if "no-route: true" is set. That was a bit of a naive implementation of "no-route", coded when createApplication() would always run. Looking into it, the CF Go client's documentation says "no-route: Do not map a route to this app and remove routes from previous pushes of this app.". So to copy this behaviour it would be best to just cycle through all routes and delete them. Also this way you wouldn't have to check if the particular route created during this deployment exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier edited a comment on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Thanks for the pull request! From what I understand CloudFoundryClient.createApplication() always creates a new route, so it is then deleted if "no-route: true" is set. That was a bit of a naive implementation of "no-route", coded when createApplication() would always run. Looking into it, the CF Go client's documentation says "no-route: Do not map a route to this app and remove routes from previous pushes of this app.". So to copy this behaviour it would be best to just cycle through all routes and delete them. Also this way you wouldn't have to check if the particular route created during this deployment exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27146) Deploying an applicatin w/ no-route fails because route deletion fails
William Gautier edited a comment on JENKINS-27146 Deploying an applicatin w/ no-route fails because route deletion fails Thanks for the pull request! From what I understand CloudFoundryClient.createApplication() always creates a new route, so it is then deleted if "no-route: true" is set. That was a bit of a naive implementation of "no-route", coded when createApplication() would always run. Looking into it, the CF Go client's documentation says "no-route: Do not map a route to this app and remove routes from previous pushes of this app.". So to copy this behaviour it would be best to just cycle through all routes and delete them. Also this way you wouldn't have to check if the particular route created during this deployment exists. You can edit your pull request or I can take care of it later, whatever you prefer. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25884) configure name of manifest.yml
William Gautier commented on JENKINS-25884 configure name of manifest.yml Custom manifest files added in this commit: https://github.com/jenkinsci/cloudfoundry/commit/9ab60ab82c8e32b235058f35aec81469cd8ac68d Now integrated in v1.2 TokenMacros will be available in v1.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-25882) Integrate with credentials plugin
William Gautier resolved JENKINS-25882 as Fixed Integrate with credentials plugin Integration with the Credential Plugin was added in this commit: https://github.com/jenkinsci/cloudfoundry/commit/3c94b18278b65d2e18e1dce6b885b8b59814fedc And available in v1.2 (For some reason the bot didn't close this bug with my commit tag) Change By: William Gautier (24/Feb/15 6:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26598) CloudFoundry client needs proxy configuration for deployment
William Gautier resolved JENKINS-26598 as Fixed CloudFoundry client needs proxy configuration for deployment Pull request was merged in this commit: https://github.com/jenkinsci/cloudfoundry/commit/0ed6e60b07cc0793a5dcfd31924a20718d92eb10 And available in v1.2 (For some reason the bot didn't close this bug with my commit tag) Change By: William Gautier (24/Feb/15 6:56 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26182) Services Are Not Persisted In Configuration
William Gautier commented on JENKINS-26182 Services Are Not Persisted In Configuration Fixed by https://github.com/ActiveState/cloudfoundry-jenkins/commit/f94966d8a19f1c2f029ed3c17262b935e76f27db and available in v1.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26182) Services Are Not Persisted In Configuration
William Gautier resolved JENKINS-26182 as Fixed Services Are Not Persisted In Configuration Change By: William Gautier (10/Feb/15 9:06 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26546) Deploy all applications defined in manifest.yml file
William Gautier resolved JENKINS-26546 as Fixed Deploy all applications defined in manifest.yml file Related to: https://github.com/ActiveState/cloudfoundry-jenkins/issues/1 Fixed by https://github.com/ActiveState/cloudfoundry-jenkins/commit/07bc7598b32e2b279316d0908c4b3a337490 and available in v1.1. Support for configuration that affects all applications is not implemented yet, but may be in the future. Change By: William Gautier (27/Jan/15 9:43 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26598) CloudFoundry client needs proxy configuration for deployment
William Gautier commented on JENKINS-26598 CloudFoundry client needs proxy configuration for deployment Thanks for the pull request! On the GitHub pull request page, you wrote that you ended up taking the proxy configuration from the JVM, which is to say, from the system property "http.proxy", and not from the Jenkins :Manage Plugins, Advanced" page. However if I understand correctly, this should come down to the same result, as the help bubble on that page says "The value you submit here will be set as http.proxyHost system property". It also appears in some wiki pages. So your change should be fine. Nevertheless, I did a quick search, and it seems the convention is to go through Jenkins by using "jenkins.model.Jenkins.getInstance().proxy", as seen in this example in the async-http-client plugin and other examples, so this might be more appropriate? This plugin is my only contribution to Jenkins so far, so I am not very aware of its ecosystem. Maybe Daniel can clarify what's the recommended way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26598) CloudFoundry client needs proxy configuration for deployment
William Gautier edited a comment on JENKINS-26598 CloudFoundry client needs proxy configuration for deployment Thanks for the pull request! On the GitHub pull request page, you wrote that you ended up taking the proxy configuration from the JVM, which is to say, from the system property "http.proxy", and not from the Jenkins "Manage Plugins, Advanced" page. However if I understand correctly, this should come down to the same result, as the help bubble on that page says "The value you submit here will be set as http.proxyHost system property". It also appears in some wiki pages. So your change should be fine. Nevertheless, I did a quick search, and it seems the convention is to go through Jenkins by using "jenkins.model.Jenkins.getInstance().proxy", as seen in this example in the async-http-client plugin and other examples, so this might be more appropriate? This plugin is my only contribution to Jenkins so far, so I am not very aware of its ecosystem. Maybe Daniel can clarify what's the recommended way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26546) Deploy all applications defined in manifest.yml file
William Gautier started work on JENKINS-26546 Deploy all applications defined in manifest.yml file Change By: William Gautier (22/Jan/15 7:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26546) Deploy all applications defined in manifest.yml file
William Gautier commented on JENKINS-26546 Deploy all applications defined in manifest.yml file Multi-apps manifest files are not a feature yet since the majority of Jenkins jobs will be to build a single app. However I will start working on it for next version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26182) Services Are Not Persisted In Configuration
William Gautier commented on JENKINS-26182 Services Are Not Persisted In Configuration There seems to be two bugs in your bug report. First, the UI did not show the services configuration when you reloaded the configuration page. I was able to reproduce this and the fix will be in the next version. Second, you are getting a 400 Bad Request that I cannot reproduce. The error message is really unhelpful here, which is my fault. The next version will display more information in case of CloudFoundryException, which might help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
