How to auto deploy a jar file using travis into cloudfoundry My jar is built using ant .I have published my code and travis able to build the code automatically ,but i am not sure how to auto deploy

Hi All, As we worked on better documenting how app usage events and service usage events work [1] in the cloud controller api, we uncovered that service usage events do not currently expire

Hi Marco, We instrumented the collector and found that none of the existing CF components provide any tags which would be overridden by the latest collector change. So this change shouldn't affect

Thanks Marco - for everyone else on the list, we reached out to Marco after this email, and opened a tracker story[1] to do deeper analysis of collector tags that may change. Thus far we have found

Dear Erik, thanks for the detailed explanation and the heads-up. A few comments and questions below.

Hello Robert, Unfortunately, your use use case is not currently supported. dashboard_url is only supported in the initial response from the broker, even though the service instance may be

Hi Swatz, In your config file, you will have to use 'datadog-firehose-nozzle' as the username and the password you specified when you created the uaa client. And no, there is no need to restart

Why, yes, yes it does. Somehow missed this feature. Thanks! //Simon

simon, are you aware of the environment variable groups feature [1]? does that capability address this need to consistently expose env variables to all apps across the

Hi all, The loggregator team has been working to maintain metric parity between the CF collector[1] and the firehose[2] in the short term.This is to help CF operators feel confident they can move

Hihi. In our environment we provide two different CF installations, each of them resides in a different VLAN. Apps in each environment are interested in different services, Graphite, statsd, sentry

Can someone please help me with above data-dog error?

On behalf of the Lattice team, I am pleased to welcome v0.3.3 of Lattice! Lattice v0.3.3 is a follow-on release, firming up Buildpack support and polishing the CLI. If you're using Lattice v0.3.0,

The CF Routing team has begun collaborating with the CAPI team on support for Route Services in Cloud Controller, and soon we will begin work on support for TCP Routing (and multiple container

Hi, We think this message was dropped and so we are posting it again. How long of a timeout are you seeing? The gorouter and ha_proxy have a default timeout of 15 minutes. If you are using an ELB or

Erik, That's very helpful, thank you! Qing

Hi R M, We think that this message may have been lost so we are resending it. Are you able to deploy other applications? This error seems to stem from mounted disk problems. Could you see if the

Hi Owais, We think this message may have been lost so we are sending it again. We compiled one back in December, I can't think of anything that would have changed since

When the cloud controller instances come up, they install any buildpacks configured in the manifest. If you want a buildpack NOT to be replaced automatically (because you've updated it yourself),

steps: 1. replace php_buildpack 2. stop all components by "nova stop" 3. start all components by "nova start" 4. check php_buildpack I expected it was the version in step 1. However, step 4 got the