As we rolled out our cloud management CLI suite 'r3'  almost a year ago, we are deprecating the old legacy commands for deploying customer code into our infrastructure.
This affects the following commands:
Starting today those commands will deploy the code and always return code 250 and a deprecation message when the deploy was successful.
You should switch to the r3-command to deploy your code  by 27th September 2018. After this date the mentioned commands will be removed.
root360 Cloud Management CLI Suite r3
Default Deployment: How deployment via CLI is working
Docker (ECS) Deployment: root360 Container Platform Deployment
Due to a security patch the deploy script deploy.py is deprecated since today. Please check your deployment processes.
Currently the GitLab Service is experiencing disruptions. This might cause deployment failures.
The status can be checked at https://status.gitlab.com/
Problems should be resolved. https://status.gitlab.com/
The problems occur again
Problems should be resolved by Gitlab. https://status.gitlab.com/
We've noticed an increased amount of errors in deployments that use Bitbucket.org.
We are in contact with Bitbucket.org to locate the cause.
We'll keep you posted here.
11:30 Our tests show that the regions Ireland and USA are not affected by this issue.
13:00 Bitbucket confirmed an issue of the connection between there data centers causing this issue
see https://status.bitbucket.org/ for current status on Bitbuckets side
13:45 Bitbucket found the cause with their network vendor and are working to solve it
17:00 issue was solved by Bitbucket and there network vendor; our tests confirm that the issue is solved
Root360 Code Deploy downloads the source code of our customers onto a storage within the infrastructure. (see our blog post  for more details)
During this process the source code is compressed to improve download speed during the scaling of the web servers.
We now improved the compression process to be up to 4 times faster.
Our tests showed no impact on the scaling time of the web servers and reduced the compression time for 600 MB source code from ~4 minutes to ~50 seconds.
This speedup is now live for all our customers.
Today, we released our late february release of the Cloud Management CLI.
The changes focused on:
- major bugfixes for container deployment (r3 container) and database management (r3 db) as well as minor fixes for CLI auto-completion
- reorganisation of the code for regular software deployments (r3 [instance] deploy)
The update had been released to all customer environments in all regions this morning.
The latest Updates for r3 had been released to all customer environments. Besides providing prettier response to ease understanding we focused on supportive functions for the deployment process. From now on you can not only see, which roles you are able to deploy, you can also find out what are the actual sources configured per default for them (1).
Furthermore we updated and extended our Knowledge Base articles on the topic. Feel free to visit our Knowledge Base (2) or the handbook on r3 (3).
r3 [instance] deploy --list-sources [-r, --role ROLENAME]
r3 [instance] deploy --list-roles
r3 instance list
We reduced the amount of error messages printed out by our deploy.py command. See https://root360.atlassian.net/wiki/spaces/KB/pages...
Error messages that are the result of other failing deployment steps are now skipped unless full debug mode (-dd) is used. This way real error messages can be found easily in the output.