-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug with parallel deploy to same host #1271
Conversation
support multiple hostname? |
What do you mean? |
Version 5.0.3
|
No, use opposite way) host('111.111.111.111','222.222.222.222')
->stage('test')
->set("branch", "develop")
->user("user")
->port("666")
->set('deploy_path', '~/temp/test'); |
@antonmedv |
Yes, stage and only be one per host. Try to use roles. They are designed to do such thing too. |
thx |
It seems like role can be only one per host too.
I will use several domains for one host to solve it. |
Please show deploy.php |
|
First call to host('a')
->hostname('xx.xx.xx.xx')
->stage('production')
->set('deploy_path', '~');
host('b')
->hostname('yy.yy.yy.yy')
->stage('production')
->set('deploy_path', '~');
host('c')
->hostname('xx.xx.xx.xx')
->stage('staging')
->set('deploy_path', '~');
host('d')
->hostname('yy.yy.yy.yy')
->stage('staging')
->set('deploy_path', '~');
host('e')
->hostname('xx.xx.xx.xx')
->stage('test')
->set('deploy_path', '~'); |
Hi. I'm using 5.0.3 and I have same problem. It doesn't work. test:
hostname: IP1
user: user1
forwardAgent: true
multiplexing: false
stage: stagging
deploy_path: "~"
production:
hostname: IP1
user: user2
forwardAgent: true
multiplexing: false
stage: production
deploy_path: "~" It works: host('test')
->hostname('IP1')
->stage('stagging')
->user('user1')
->forwardAgent(true)
->multiplexing(false)
->set('deploy_path', '~');
host('production')
->hostname('IP1')
->stage('production')
->user('user2')
->forwardAgent(true)
->multiplexing(false)
->set('deploy_path', '~'); |
Fix will be soon, in 5.1.0 |
Now in master |
@antonmedv - this change appears like it may have broken rsync process. Will raise this shortly in another issue, once i get a chance to look over this in more detail.. Here's a quick summary.. On my system, v5.1.1 appears to attempt to connect to the host, rather than the hostname specified
|
@matthew-muscat please open an issue |
Now it's possible to parallel deploy with this configuration: