Development

#7240 (Sync does not list changed files)

You must first sign up to be able to contribute.

Ticket #7240 (reopened documentation)

Opened 4 years ago

Last modified 1 year ago

Sync does not list changed files

Reported by: amadeus Assigned to: fabien
Priority: major Milestone: 1.3.0 alpha2
Component: tasks Version: 1.4.19
Keywords: sync, rsync, deploy verbose Cc: joshua@enradia.com
Qualification: Unreviewed

Description

project:deploy or sync no longer lists the file changes even when --verbose --progress --stats is passed as rsync options. I does sync fine but it makes dry run a bit useless.

Change History

09/29/09 19:58:44 changed by fabien

  • status changed from new to closed.
  • resolution set to invalid.

use the -t option top have a verbose output.

(follow-up: ↓ 3 ) 07/05/10 16:26:14 changed by Matt.Robinson

(Sorry for commenting on an old bug, I don't know if I should reopen this bug, or file a new one.)

Respectfully, I do not think this bug is invalid. I've had this problem since I started using 1.3 beta, and 1.4 release. I'm now on the 1.4 SVN branch, and I still get no output at all from the project:deploy task. Adding the -t option does not help (my rsync manpage tells me that -t checks file modification timestamps. How is that related to output? Is there more than one version of rsync?)

If I run the rsync command that is generated by the sfProjectDeployTask myself (i.e., paste it onto the command-line and run it), then output is returned. However, project:deploy returns no output and never has, no matter what options I pass it.

This is an example of an rsync command generated by sfProjectDeployTask. It produces output when run manually, but not when run by the task: rsync --dry-run -azC --force --delete --progress --exclude-from=config/rsync_exclude.txt -e "ssh -p22" ./ user@example.com:/opt/my-sf-project/

This is the observed behaviour on all symfony projects I've started. In addition, the task does not produce any log file output, despite the task's heavy use of $this->log(). Perhaps this is due to it not accessing any symfony application context or log configuration?

(in reply to: ↑ 2 ; follow-up: ↓ 4 ) 07/05/10 17:44:06 changed by amadeus

Like this:

./symfony project:deploy production --trace

or

./symfony project:deploy production -t

-t is not related to rsync. I think that symfony catches any output in a buffer and -t makes it show perhaps.

Replying to Matt.Robinson:

(Sorry for commenting on an old bug, I don't know if I should reopen this bug, or file a new one.) Respectfully, I do not think this bug is invalid. I've had this problem since I started using 1.3 beta, and 1.4 release. I'm now on the 1.4 SVN branch, and I still get no output at all from the project:deploy task. Adding the -t option does not help (my rsync manpage tells me that -t checks file modification timestamps. How is that related to output? Is there more than one version of rsync?) If I run the rsync command that is generated by the sfProjectDeployTask myself (i.e., paste it onto the command-line and run it), then output is returned. However, project:deploy returns no output and never has, no matter what options I pass it. This is an example of an rsync command generated by sfProjectDeployTask. It produces output when run manually, but not when run by the task: rsync --dry-run -azC --force --delete --progress --exclude-from=config/rsync_exclude.txt -e "ssh -p22" ./ user@example.com:/opt/my-sf-project/ This is the observed behaviour on all symfony projects I've started. In addition, the task does not produce any log file output, despite the task's heavy use of $this->log(). Perhaps this is due to it not accessing any symfony application context or log configuration?

(in reply to: ↑ 3 ) 07/05/10 17:51:12 changed by Matt.Robinson

Replying to amadeus:

Like this: ./symfony project:deploy production --trace or ./symfony project:deploy production -t

Thank you! That's been bothering me for about a year.

10/15/10 14:21:19 changed by zevero

  • status changed from closed to reopened.
  • type changed from defect to documentation.
  • component changed from other to tasks.
  • version changed from 1.3.0 alpha1 to 1.4.x DEV.
  • keywords changed from sync,rsync to sync,rsync, deploy verbose.
  • resolution deleted.

Ah ... after more than a year ... after hundreds of deploys ... finally I found the solution in this bug-report!!! A stupid -t!!!

Please document the --trace or -t option in the help for the deploy task!

Thanks!!

06/20/12 07:21:18 changed by zevero

  • keywords changed from sync,rsync, deploy verbose to sync, rsync, deploy verbose.
  • priority changed from minor to major.
  • version changed from 1.4.x DEV to 1.4.19.

Please update the documentation. Nearly 2 years from my last post, I had the same problem ... and again it took me quite some time, to find out!!!

It d be better to have a quite option and tracing enabled by default