On Mon, Jul 23, 2012 at 9:57 AM, romje <[email protected]> wrote:
> Hi all,
> I wondered if someone went to same conclusions I could have made...
> I 'm working for one very client in France , this company owns seevral
> brands , several entities through fusion and other buy games...
> These companies may work with different software companies like offshore
> indian companies... So the context is really tricky and very restrictive
> that's why the nominal CI context can't be applied (I don't want to give
> production access to developers of offshore comapnies that's why they must
> just provide code+ config and push it into a VCS like system ..This can be
> handled by their customers CI (one of the entity daughters of my own
> client). After this step we could fire through a message an order to start a
> build process into production environment :
> - getting sources from their VCS
> - compiling/testing
> - after manual agreement, automate a deploy on staging...
>
> This is a tricky process but the only one I can imagine...
> Does someone imagined such process ? Is it realistic to customize hudson to
> handle such workflow , providing at any moment a report of the current state
> in the chain ...
The details would depend on the specific VCS, but I'd try to mirror
the developer's VCS repository. For example, if it is in subversion,
you can use svnsync to create an otherwise read-only mirror that your
jenkins can access, and scheduled runs will keep it updated. Then if
the development process changes you can convert your copy to a normal
writable version and continue regardless.
--
Les Mikesell
[email protected]
