[Gnu-arch-users] ARCH usage schema for automated updates live files after maintainer commits

[Попков Александр]

Hello GNU ARCH users!

 

Advice me please better ARCH usage schema for next situation:

 

1. One development server with one-per-developer account;

2. One live (production) server with running services;

3. Source files in project – are PERL files and binary build are not needed;

4. Each developer must have possibility to:

    4a. Edit project files;

    4b. Commit own changes (from self-owned archive?) to main arch archive;

    4c. Do some actions for update project files on live server

          to latest version of project from main arch archive on development server;

5. Developers (but maintainer) must NOT have direct access to project files on live server,

     for maintainer be sure what all project’s changes are logged in changelog;

6. After (before?) all changes (commits) to main arch archive system must run some test

    associated with particular project. If test fails – rollback or cancel commit.

7. After each commit to main arch archive system must send e-mail to maintainer;

8. Only maintainer must have rights for making new category/branch/version in main arch archive;

9. After maintainer make new version of particular project system must send e-mail to all project developers;

   (and developers go to update own local copies of changed project?);

10. Updating project files on live server process must have two cases:

     10a. Update files in “TEST” location, for manual testing on LIVE server.

     10b. Update files in “HOT” (production) location on LIVE server.

 

Thanks in advance!