EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #03870

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

[EP-tech] Re: Promotion mechanism (dev-live)

Hi Nick.,

What you are describing sounds like the way we do things.

We have all work performed in development server.  Committed to svn. . Then a release version/bundle is made.

On the test and prod servers, we have some .sh scripts to pull the release bundle,  and then run a set of updates to certain files,  eg adjust templates to change wording, 'dev' to 'test' etc., as well as other appropriate system settings.

All up,  a push to test takes a minute or two, and a roll back to a previous release the same. Not that we go backwards in test much.

Sign off is performed on the version in test, and then the same release can be pushed to prod.

If this is the sort of thing you are looking for,  let me know and I will track down more details when I get back to my desk on Monday.

Cheers

Matt



-------- Original message --------
From: "Sheppard, Nick"
Date:31/01/2015 00:13 (GMT+10:00)
To: eprints-tech@ecs.soton.ac.uk
Subject: [EP-tech] Promotion mechanism (dev-live)

Apologies in advance if I’m using incorrect terminology as I try to translate a conversation with technical colleagues.

We are trying to set up a promotion mechanism – using Subversion – whereby a web developer based in the library can pull down eprints-dev, edit, and put back up to Subversion -> eprints-dev.leedsbeckett.ac.uk for testing before promoting to the live code and on to eprints.leedsbeckett.ac.uk.

As I understand my colleagues aren’t finding this entirely straightforward due to various eprints-dev parameters / configurations. Is anyone able to offer any tips on setting up a promotion mechanism?

Thanks

Nick






_____________________________________________________________
This email (including any attached files) is confidential and is for the intended recipient(s) only. If you received this email by mistake, please, as a courtesy, tell the sender, then delete this email.

The views and opinions are the originator's and do not necessarily reflect those of the University of Southern Queensland. Although all reasonable precautions were taken to ensure that this email contained no viruses at the time it was sent we accept no liability for any losses arising from its receipt.

The University of Southern Queensland is a registered provider of education with the Australian Government.
(CRICOS Institution Code QLD 00244B / NSW 02225M, TEQSA PRV12081 )