Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to deploy to EB using pipelines


We have established pipelines scripts that work very well. Lately, we decided to deploy to elastic beanstalk automatically, with the use of bitbucket pipelines and following the tutorial which uses the command 'eb deploy' to deploy. Apparently, this command fails on pipelines. The config files seem legit because it runs locally. It also runs from inside a container of the same image that we have specified in the pipelines file and also by using docker exec from the local to run the command inside a container of the same image. The following are the pipelines file and the error we get using 'eb deploy --verbose' command. I am obviously missing something. Any help or direction would be appreciated. Thanking you in advance. 

- step:
deployment: staging
- composer
- php -r "file_exists('.env') || copy('.env.example', '.env');"
- cat .env
- composer install
- php artisan cache:clear
- php artisan migrate
- php artisan db:seed
- eb init KMLT-staging-ttl -r eu-central-1 -p "64bit Amazon Linux 2017.09 v2.6.4 running PHP 7.1"
- eb deploy --verbose
- postgres

+ eb deploy --verboseINFO: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ebcli/core/", line 41, in run_app File "/usr/lib/python2.7/site-packages/cement/core/", line 797, in run return_val = self.controller._dispatch() File "/usr/lib/python2.7/site-packages/cement/core/", line 472, in _dispatch return func() File "/usr/lib/python2.7/site-packages/cement/core/", line 475, in _dispatch self._parse_args() File "/usr/lib/python2.7/site-packages/cement/core/", line 452, in _parse_args File "/usr/lib/python2.7/site-packages/cement/core/", line 1076, in _parse_args for res in'post_argument_parsing', self): File "/usr/lib/python2.7/site-packages/cement/core/", line 150, in run res = hook[2](*args, **kwargs) File "/usr/lib/python2.7/site-packages/ebcli/core/", line 35, in pre_run_hook set_profile(app.pargs.profile) File "/usr/lib/python2.7/site-packages/ebcli/core/", line 47, in set_profile profile = commonops.get_default_profile() File "/usr/lib/python2.7/site-packages/ebcli/operations/", line 973, in get_default_profile profile = get_config_setting_from_branch_or_default('profile') File "/usr/lib/python2.7/site-packages/ebcli/operations/", line 1008, in get_config_setting_from_branch_or_default setting = get_setting_from_current_branch(key_name) File "/usr/lib/python2.7/site-packages/ebcli/operations/", line 991, in get_setting_from_current_branch branch_name = source_control.get_current_branch() File "/usr/lib/python2.7/site-packages/ebcli/objects/", line 184, in get_current_branch stdout, stderr, exitcode = self._run_cmd(revparse_command, handle_exitcode=False) File "/usr/lib/python2.7/site-packages/ebcli/objects/", line 480, in _run_cmd stdout, stderr, exitcode = exec_cmd(cmd) File "/usr/lib/python2.7/site-packages/cement/utils/", line 40, in exec_cmd proc = Popen(cmd_args, *args, **kw) File "/usr/lib/python2.7/", line 390, in __init__ errread, errwrite) File "/usr/lib/python2.7/", line 1024, in _execute_child raise child_exceptionOSError: [Errno 2] No such file or directoryINFO: OSError - [Errno 2] No such file or directory

1 comment

I got the exact same error, any luck?


Log in or Sign up to comment

Atlassian Community Events