Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/207e2b57f8614c3c#

Hi everyone!

We have added a nice and really useful feature in our 5.1.3 release allow
us to more streamline the deployment processes for Database changes to DEV
and LIVE sites. It's fully described here Improving Project Deployment
Processes to DEV or LIVE servers<https://groups.google.com/d/topic/in-portal-dev/Xnc-SFIK1Bk/discussion>
 servers.

I am thinking we can take it a little bit further and add the ability to
output/show the actually comments or notes whatever we call them from
"project_upgrades.sql" file after Deploy button was hit in the Admin or
OnDeploy script was ran via "do_update" script.

The main goal of this change is to show the developer which Revision has
been executed + see any of Additional Notes supplied by developers. The
output can be shown right below the Toolbar buttons and can look something
like this:

============
*# r2: Separate CMS Blocks for Logged-in / Non-Logged in (#34344)*
# make existing content blocks for non logged-in users only
# create logged-in version of content blocks from their non logged-in
in version
*

# r3: User Attachments (#34351)*
*  
# r4: Admin of Portals (#34354)*
============

Also, it would be nice to show OK or FAILED next to each Revision and may
be show failed SQL so it's easier to catch those cases when something went
wrong and you need to know where exactly it stopped.

Please give me your opinion on this idea.DA

Related Tasks

Jira Legacy
serverIn-Portal Issue Tracker
keyINP-983