Hi all,
Time was I checked out modules/core from CVS and used cvs_deploy to ensure correct version info. Now we've moved over to git, one should use git_deploy. However I notice that it's a) at dev, and b) has only a small reported number of live sites. Do folk feel git_deploy's ok for live sites? If not, may I ask what people are doing instead?
As a related question, do people feel it's worthwhile checking out from source control rather than just getting via the packager? When I first started using CVS it was to simplify the update process. However I now know about drush update, and wonder if there's any real advantage to sticking with my old ways?
TIA,
Andy
. . . . . . . Andy Fowlston +44 (0)20 8747 5068 andy@pedalo.co.uk Skype: andy.pedalo www.pedalo.co.uk
This email is intended only for the above named addressee/s. This email may be confidential or legally privileged. If you have received this email and you are not a named addressee, you must not use, copy, distribute or disclose the email or any part of its contents or take any action in reliance on it. If you have received this email in error, please email the sender by replying to this message and delete it from your system. All reasonable precautions have been taken to ensure no viruses are present in this email.
pedalo limited cannot accept responsibility for loss or damage arising from the use of this email or attachments and recommends that you subject these to your virus checking procedures prior to use. Any views or opinions presented are solely those of the author and not necessarily those of Pedalo Limited
Please consider the environment before printing this email
we pretty much decided the extra repo data wasn't worth dealing with git submodules or other complex git over git scenarios, so we now just use drush to pull in updates and version them in a repo per project. certainly not the only way, or the best way, but it's a pretty simple way :)
-Benj
On Tue, May 31, 2011 at 7:15 AM, Andy Fowlston andy@pedalo.co.uk wrote:
Hi all,
Time was I checked out modules/core from CVS and used cvs_deploy to ensure correct version info. Now we've moved over to git, one should use git_deploy. However I notice that it's a) at dev, and b) has only a small reported number of live sites. Do folk feel git_deploy's ok for live sites? If not, may I ask what people are doing instead?
As a related question, do people feel it's worthwhile checking out from source control rather than just getting via the packager? When I first started using CVS it was to simplify the update process. However I now know about drush update, and wonder if there's any real advantage to sticking with my old ways?
TIA,
Andy
. . . . . . . Andy Fowlston +44 (0)20 8747 5068 andy@pedalo.co.uk Skype: andy.pedalo www.pedalo.co.uk
This email is intended only for the above named addressee/s. This email may be confidential or legally privileged. If you have received this email and you are not a named addressee, you must not use, copy, distribute or disclose the email or any part of its contents or take any action in reliance on it. If you have received this email in error, please email the sender by replying to this message and delete it from your system. All reasonable precautions have been taken to ensure no viruses are present in this email.
pedalo limited cannot accept responsibility for loss or damage arising from the use of this email or attachments and recommends that you subject these to your virus checking procedures prior to use. Any views or opinions presented are solely those of the author and not necessarily those of Pedalo Limited
Please consider the environment before printing this email
[ Drupal support list | http://lists.drupal.org/ ]
Cheers Benj, yeah that's what we're doing with our latest project. Nice to know we're not alone :)
. . . . . . . Andy Fowlston +44 (0)20 8747 5068 andy@pedalo.co.uk Skype: andy.pedalo www.pedalo.co.uk
This email is intended only for the above named addressee/s. This email may be confidential or legally privileged. If you have received this email and you are not a named addressee, you must not use, copy, distribute or disclose the email or any part of its contents or take any action in reliance on it. If you have received this email in error, please email the sender by replying to this message and delete it from your system. All reasonable precautions have been taken to ensure no viruses are present in this email.
pedalo limited cannot accept responsibility for loss or damage arising from the use of this email or attachments and recommends that you subject these to your virus checking procedures prior to use. Any views or opinions presented are solely those of the author and not necessarily those of Pedalo Limited
Please consider the environment before printing this email --
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Benj Fredrick Sent: 02 June 2011 16:41 To: support@drupal.org Subject: Re: [support] git_deploy & workflow
we pretty much decided the extra repo data wasn't worth dealing with git submodules or other complex git over git scenarios, so we now just use drush to pull in updates and version them in a repo per project. certainly not the only way, or the best way, but it's a pretty simple way :)
-Benj
On Tue, May 31, 2011 at 7:15 AM, Andy Fowlston andy@pedalo.co.uk wrote: Hi all,
Time was I checked out modules/core from CVS and used cvs_deploy to ensure correct version info. Now we've moved over to git, one should use git_deploy. However I notice that it's a) at dev, and b) has only a small reported number of live sites. Do folk feel git_deploy's ok for live sites? If not, may I ask what people are doing instead?
As a related question, do people feel it's worthwhile checking out from source control rather than just getting via the packager? When I first started using CVS it was to simplify the update process. However I now know about drush update, and wonder if there's any real advantage to sticking with my old ways?
TIA,
Andy
. . . . . . . Andy Fowlston +44 (0)20 8747 5068 andy@pedalo.co.uk Skype: andy.pedalo www.pedalo.co.uk
This email is intended only for the above named addressee/s. This email may be confidential or legally privileged. If you have received this email and you are not a named addressee, you must not use, copy, distribute or disclose the email or any part of its contents or take any action in reliance on it. If you have received this email in error, please email the sender by replying to this message and delete it from your system. All reasonable precautions have been taken to ensure no viruses are present in this email.
pedalo limited cannot accept responsibility for loss or damage arising from the use of this email or attachments and recommends that you subject these to your virus checking procedures prior to use. Any views or opinions presented are solely those of the author and not necessarily those of Pedalo Limited
Please consider the environment before printing this email -- [ Drupal support list | http://lists.drupal.org/ ]
-
Andy Fowlston -
Benj Fredrick