Yeah with snapshots you have to be much more strict with who does what in what order
but with the method you have above it shouldn't overwrite changes
First thing to check - normal uSync is turned off if you are working this way (so at least Import is set to false in the uSyncBackoffice.config
<import>false</import>
If it's not then normal usync might be the culprit for overwriting.
have a look at the snapshots- based on what you're saying you should have a dev1 and dev2 snapshot, these are cumulative, so if there are things being overwritten they will be in dev2's snapshot - would be intrested in finding out what they are.
--
In theory the process looks ok. as long as dev2 has all the changes in before they make any new ones.
personally If you want to use snapshots to deploy i would consider having a hybrid setup, using just uSync for dev and snapshots for deployment.
For developers working locally i would just use normal uSync - everything will be kept in sync between the devs, all changes will be loaded locally every-time they check out the code .
Then for deployment, i would have the dev prepping the deployment create the snapshot - this would be your 'release' snapshot that you could put onto your server.
That way there is less co-ordination issues between Devs, while still giving you some single point control over what you put on the server.
Usync Snapshots
Hi guys,
We are using Usync Snapshots in our team.
The development process we are following is:
Push changes to Test environment
Firstly, is the above the correct way to do it?
Second, what would be the process if two developers were working at the same time?
Currently we are doing the below but it's overwriting changes:
Thanks!
Hi
Yeah with snapshots you have to be much more strict with who does what in what order
but with the method you have above it shouldn't overwrite changes
First thing to check - normal uSync is turned off if you are working this way (so at least Import is set to false in the uSyncBackoffice.config
If it's not then normal usync might be the culprit for overwriting.
have a look at the snapshots- based on what you're saying you should have a dev1 and dev2 snapshot, these are cumulative, so if there are things being overwritten they will be in dev2's snapshot - would be intrested in finding out what they are.
--
In theory the process looks ok. as long as dev2 has all the changes in before they make any new ones.
personally If you want to use snapshots to deploy i would consider having a hybrid setup, using just uSync for dev and snapshots for deployment.
For developers working locally i would just use normal uSync - everything will be kept in sync between the devs, all changes will be loaded locally every-time they check out the code .
Then for deployment, i would have the dev prepping the deployment create the snapshot - this would be your 'release' snapshot that you could put onto your server.
That way there is less co-ordination issues between Devs, while still giving you some single point control over what you put on the server.
Hi Kevin,
Thanks for the above. It helped a lot!
is working on a reply...