Skip to content
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

Add option to show which files were synced to debug sync process. #211

Open
artem-zinnatullin opened this issue Mar 24, 2018 · 3 comments
Open
Assignees
Milestone

Comments

@artem-zinnatullin
Copy link
Contributor

Currently it's pretty hard to understand what bottlenecks the sync process.

An option to show what files get synched might help reveal files that are getting synced unintentionally and slowing down sync process.

@ming13 wdyt?

@artem-zinnatullin
Copy link
Contributor Author

rsync has two options that could potentially help in that:

  • -n, --dry-run show what would have been transferred, we can run rsync twice if Mainframer was launched with this option to show what will be synced and then actually sync it.
  • -v, --verbose increase verbosity

@arturdryomov
Copy link
Contributor

Gradle projects sync a lot of files, but I can see where you are going. I think there is a room for the --verbose flag which will pass it to rsync and ssh.

@artem-zinnatullin
Copy link
Contributor Author

Main idea is to debug cases like:

mainframer make build

# And then run again

mainframer --debug-sync make build

So you could figure what files get regenerated and synced again even after "100%" incremental build.

Regarding ssh, I think that should be a separate flag

@artem-zinnatullin artem-zinnatullin changed the title Add option to show which files were synched to debug sync process. Add option to show which files were synced to debug sync process. Apr 2, 2018
@artem-zinnatullin artem-zinnatullin added this to the v3.0.0 milestone Apr 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants