cloudfoundry / binary-buildpack Goto Github PK

View Code? Open in Web Editor NEW

30.0 32.0 50.0 15.52 MB

Deploy binaries to Cloud Foundry

License: Apache License 2.0

Shell 49.15% Batchfile 2.79% Go 47.97% Procfile 0.09%

v2b

binary-buildpack's Introduction

Cloud Foundry Binary Buildpack

CF Slack Join us on Slack

A Cloud Foundry buildpack for running arbitrary binary web servers.

Buildpack User Documentation

Official buildpack documentation can be found at binary buildpack docs.

Building the Buildpack

To build this buildpack, run the following command from the buildpack's directory:

Source the .envrc file in the buildpack directory.
```
source .envrc
```
To simplify the process in the future, install direnv which will automatically source .envrc when you change directories.

Install buildpack-packager

go install github.com/cloudfoundry/libbuildpack/packager/buildpack-packager

Build the buildpack

buildpack-packager build [ --cached=(true|false) ]

Use in Cloud Foundry

Upload the buildpack to your Cloud Foundry and optionally specify it by name

cf create-buildpack [BUILDPACK_NAME] [BUILDPACK_ZIP_FILE_PATH] 1
cf push my_app [-b BUILDPACK_NAME]

Testing

Buildpacks use the Cutlass framework for running integration tests.

To test this buildpack, run the following command from the buildpack's directory:

Source the .envrc file in the buildpack directory.
```
source .envrc
```
To simplify the process in the future, install direnv which will automatically source .envrc when you change directories.
Run unit tests
```
./scripts/unit.sh
```
Run integration tests
```
./scripts/integration.sh
```

Contributing

Find our guidelines here.

Help and Support

Join the #buildpacks channel in our Slack community if you need any further assistance.

Reporting Issues

Open a GitHub issue on this project here

binary-buildpack's People

Contributors

Stargazers

Watchers

binary-buildpack's Issues

Unable to run .NET console application

What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?
{
"name": "",
"build": "",
"support": "https://support.pivotal.io",
"version": 0,
"description": "",
"authorization_endpoint": "",
"token_endpoint": "",
"min_cli_version": "6.7.0",
"min_recommended_cli_version": "6.11.2",
"api_version": "2.54.0",
"app_ssh_endpoint": "",
"app_ssh_host_key_fingerprint": "3c:e2:ce:3d:fc:61:f6:84:f9:75:cd:03:c1:b4:c3:73",
"app_ssh_oauth_client": "ssh-proxy",
"logging_endpoint": "",
"doppler_logging_endpoint": "",
"user": ""
}

What version of the buildpack you are using?
version is 1.0.1

If you were attempting to accomplish a task, what was it you were attempting to do?
I'm unable to run a console application. I have said no-route to true, health check status to process, command as <>.exe
What did you expect to happen?
The console app should start like a process

What was the actual behavior?
Even though I gave the start command it is not picking up the same. It says start command cannot be found and it is getting crashed.

logs are as below
Connected, dumping recent logs for app CFConsoleApp in org Foundry Dev / space Microservices as admin...

2017-05-03T17:00:09.76+0530 [STG/0] OUT Downloading binary_buildpack...
2017-05-03T17:00:09.79+0530 [STG/0] OUT Downloaded binary_buildpack
2017-05-03T17:00:09.79+0530 [STG/0] OUT Creating container
2017-05-03T17:00:12.07+0530 [STG/0] OUT Successfully created container
2017-05-03T17:00:12.08+0530 [STG/0] OUT Downloading app package...
2017-05-03T17:00:12.50+0530 [STG/0] OUT Downloaded app package (30.4K)
2017-05-03T17:00:12.50+0530 [STG/0] OUT Staging...
2017-05-03T17:00:12.57+0530 [STG/0] ERR No start command detected
2017-05-03T17:00:12.71+0530 [STG/0] OUT Uploading droplet...
2017-05-03T17:00:12.71+0530 [STG/0] OUT Exit status 0
2017-05-03T17:00:12.71+0530 [STG/0] OUT Staging complete
2017-05-03T17:00:12.71+0530 [STG/0] OUT Uploading droplet, build artifacts cache...
2017-05-03T17:00:12.71+0530 [STG/0] OUT Uploading build artifacts cache...
2017-05-03T17:00:12.77+0530 [STG/0] OUT Uploaded build artifacts cache (87B)
2017-05-03T17:00:35.25+0530 [API/0] OUT Created app with guid 32384a05-4605-4da5-bad1-1c7869993e68
2017-05-03T17:00:37.79+0530 [STG/0] OUT Uploaded droplet (22.1K)
2017-05-03T17:00:37.79+0530 [STG/0] OUT Uploading complete
2017-05-03T17:00:38.10+0530 [CELL/0] OUT Creating container
2017-05-03T17:00:41.72+0530 [CELL/0] OUT Successfully created container
2017-05-03T17:00:42.74+0530 [APP/0] OUT Running bin/release/CFConsoleApp.exe
2017-05-03T17:00:44.36+0530 [API/0] OUT Updated app with guid 32384a05-4605-4da5-bad1-1c7869993e68 ({"state"=>"STARTED"})
2017-05-03T17:00:44.79+0530 [APP/0] OUT Exit status 2
2017-05-03T17:00:45.02+0530 [CELL/0] OUT Exit status -26
2017-05-03T17:00:45.05+0530 [CELL/0] OUT Creating container
2017-05-03T17:00:48.47+0530 [CELL/0] OUT Successfully created container
2017-05-03T17:00:50.45+0530 [APP/0] OUT Running bin/release/CFConsoleApp.exe
2017-05-03T17:00:50.45+0530 [APP/0] OUT Exit status 2
2017-05-03T17:00:50.67+0530 [CELL/0] OUT Exit status -26
2017-05-03T17:00:50.71+0530 [CELL/0] OUT Creating container
2017-05-03T17:00:54.06+0530 [CELL/0] OUT Successfully created container
2017-05-03T17:00:54.97+0530 [APP/0] OUT Running bin/release/CFConsoleApp.exe
2017-05-03T17:00:54.98+0530 [APP/0] OUT Exit status 2
2017-05-03T17:00:56.08+0530 [CELL/0] OUT Exit status -26
2017-05-03T17:01:19.65+0530 [API/0] OUT App instance exited with guid 32384a05-4605-4da5-bad1-1c7869993e68 payload: {"instance"=>"e2857e08-0fba-4ea7-51bc-0970012ecbb3", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* Exited with status 2\n* cancelled", "crash_count"=>1, "crash_timestamp"=>1493811079631692499, "version"=>"a5833d94-0c6e-460c-bb45-08847bd161c1"}
2017-05-03T17:01:25.31+0530 [API/0] OUT App instance exited with guid 32384a05-4605-4da5-bad1-1c7869993e68 payload: {"instance"=>"f0b144ec-7495-451a-6a83-eede6f41e308", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* Exited with status 2\n* cancelled", "crash_count"=>2, "crash_timestamp"=>1493811085286859655, "version"=>"a5833d94-0c6e-460c-bb45-08847bd161c1"}
2017-05-03T17:01:30.70+0530 [API/0] OUT App instance exited with guid 32384a05-4605-4da5-bad1-1c7869993e68 payload: {"instance"=>"66854251-772d-43ec-4674-4bb1ff0258e9", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* Exited with status 2\n* cancelled", "crash_count"=>3, "crash_timestamp"=>1493811090693720364, "version"=>"a5833d94-0c6e-460c-bb45-08847bd161c1"}
2017-05-03T17:01:34.21+0530 [CELL/0] OUT Creating container
2017-05-03T17:01:36.40+0530 [CELL/0] OUT Successfully created container
2017-05-03T17:01:37.51+0530 [APP/0] OUT Running bin/release/CFConsoleApp.exe
2017-05-03T17:01:37.51+0530 [APP/0] OUT Exit status 2
2017-05-03T17:01:38.42+0530 [CELL/0] OUT Exit status -26
2017-05-03T17:02:13.05+0530 [API/0] OUT App instance exited with guid 32384a05-4605-4da5-bad1-1c7869993e68 payload: {"instance"=>"11b4429d-a17d-4ae8-62c5-9667e54fd61a", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* Exited with status 2\n* cancelled", "crash_count"=>4, "crash_timestamp"=>1493811133037413883, "version"=>"a5833d94-0c6e-460c-bb45-08847bd161c1"}

Question on https://github.com/cloudfoundry/binary-buildpack/issues/18

Hi, I'm opening a new issue because I don't know how to reopen any closed issue (sorry for that).

In the:
#18

I read (as said by Stephen Levine):

"Everything in fixtures is test data that isn't included in the buildpack. Those versions don't exist, as you've noticed".

May I kindly ask you to please clarify that? what do you mean with "everything"? and what do you mean that isn't included in the buildpack? for example there is another "fixture" directory in the binary buildpack at https://github.com/cloudfoundry/binary-buildpack/tree/v1.0.17/fixtures.

Finally, that is valid for all the other buildpacks? I mean: is it a standard rule that what is in fixtures is test data that isn't included in the buildpack?

Thanks again.

Release: binary-buildpack (Jan)

Release reminder for binary-buildpack

See diff from latest version and validate if a release is required.
Make sure the latest commit on has passed tests on the CI
Refer release instructions. (private link)

Commit Message

Release: binary-buildpack 1.0.40

Dependency Changes:

No dependency changes

New Commits on Develop:

afabc43 Updating github-config
904c6de Update libbuildpack
e52af8d Update libbuildpack
a5a42f5 Update libbuildpack
4390f83 Adds integration test matrix
a59fdf8 Merge pull request #53 from cloudfoundry/automation/github-config/update
460703b Updating github-config
d9cb16c Updating github-config
b5dc093 Merge pull request #52 from cloudfoundry/automation/github-config/update
75a78a3 Updating github-config
a29c2d6 Update libbuildpack
a868a07 Merge pull request #47 from cloudfoundry/automation/github-config/update
376c8b1 Updating github-config
f5db071 Merge pull request #46 from cloudfoundry/automation/github-config/update
e144cfa Updating github-config