User login

Home ›
 CVS update, Piston update, and SVN commit of Drupal core upgrade for deployed site

CVS update, Piston update, and SVN commit of Drupal core upgrade for deployed site

in

I am not entirely sure Piston provides a vital role here, but for now I'd just like to say it worked!

Here is the very basic test. Ordinarily you wouldn't be updating core immediately after deploying a new site, but unlike me ordinarily you would be paying attention.

Many of these commands produce lots and lots of output which is skipped here, but some of which will be mentioned below for orientation and knowing what to expect. On a test server:

sudo /srv/scripts/agaric-newproject.sh 6 example example.edu
cd /sites/example/www/
vi CHANGELOG.txt

Shows that Drupal is at 6.3, looking at the most recent (topmost) logged change.

Now (with credit to Using CVS to maintain a Drupal website) we update Drupal core in the central SVN repository that Piston draws from, in a local checkout of this portion at least of the repository structure:

cd /RCS/agaric/drupal-core/drupal-6/
cvs update -r DRUPAL-6-4 -dP
sudo /srv/scripts/svn_add_delete_files

Back to the test server, in /sites/example/www

NOTE: The next line doesn't actually update anything, but experience shows that Piston needs this redundant update or it will fail.

sudo svn update
sudo piston update
sudo svn status -u
sudo svn commit -m "our updated Drupal core"
vi CHANGELOG.txt

Now shows "Drupal 6.4, 2008-08-13" which means success!

The piston update took a very long time, hanging at "Merging local changes back in" for about five minutes. Not a good sign. Here's the full output:

Processing '.'...
Fetching remote repository's latest revision and UUID
Restoring remote repository to known state at r7321
Updating remote repository to r7325
Processing adds/deletes
Merging local changes back in
Removing temporary files / folders
Updating Piston properties
Updated to r7325 (145 changes)

For a bit more about Agaric's use of Piston, see adding a new version of drupal core to Agaric's piston-enabled deployment system.

Apologies for the mane steps specific to Agaric's set-up. We're happy to share all the scripts, and the most exciting part of this documentation is the cvs update -r DRUPAL-6-4 -dP.

Resolution

Comments

When Piston had *not* been used originally

Submitted by Benjamin Melançon on November 26, 2008 - 4:43am.

and attempting to use it caused a whole ton of conflicts

sudo svn revert -R .

saved the day.

Paving the way to just use

sudo cvs update -r DRUPAL-6-6 -dP

directly on the site.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Internal paths in single or double quotes, written as "internal:node/99", for example, are replaced with the appropriate absolute URL or path. Paths to files in single or double quotes, written as "files:somefile.ext", for example, are replaced with the appropriate URL that can be used to download the file.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <blockquote> <small> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <p> <br> <strike> <table> <tr> <td> <thead> <th> <tbody> <tt> <output>
  • You may post code using <code>...</code> (generic) or <?php ... ?> (highlighted PHP) tags.
  • Lines and paragraphs break automatically.

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.