Suggestions:
1) since they have ssh access to dev web server, why not use a ssh
tunnel so they don't need their own repo copy? That way they will onl
transfert what is needed for compilation.
2) Assuming you put artefacts in scm (a project for 'repo'), does it
improve the build process (eg, faster than a rsync of same datas)? Will
it not be a pain for developper to keep that scm repo up 2 date? If
answer are Yes and No, i see no reason for not doing it :D
Chris Helck a écrit :
> Hello,
>
> I need advice. Our production builds are handled by a separate group.
> They do the builds in a locked room with limited access to the company
> infrastructure, and no access to the outside world. They have access to
> our SCM. In the room they have a web server that has ssh access to a
> development web server.
>
> To do a maven based build they first rsync their web server's repo with
> the development one. Then the build machine accesses their web server.
>
> This is a pain for both developers and the build group. So, I'm thinking
> I should just put an image of the repo in SCM. This gives them a good
> audit trail and control. To do a build they first update the repo to the
> head of the SCM, then fetch the source code by a label, and finally kick
> off maven.
>
> I know SCM people don't like to put artifacts into SCM, but this seems
> like a reasonable use. Are there any maven specific issues/problems that
> this may cause?
>
> Thanks,
> Christopher Helck
>
>
> **********************************************************************
> This communication and all information (including, but not limited to,
> market prices/levels and data) contained therein (the "Information") is
> for informational purposes only, is confidential, may be legally
> privileged and is the intellectual property of ICAP plc and its affiliates
> ("ICAP") or third parties. No confidentiality or privilege is waived or
> lost by any mistransmission. The Information is not, and should not
> be construed as, an offer, bid or solicitation in relation to any
> financial instrument or as an official confirmation of any transaction.
> The Information is not warranted, including, but not limited, as to
> completeness, timeliness or accuracy and is subject to change
> without notice. ICAP assumes no liability for use or misuse of the
> Information. All representations and warranties are expressly
> disclaimed. The Information does not necessarily reflect the views of
> ICAP. Access to the Information by anyone else other than the
> recipient is unauthorized and any disclosure, copying, distribution or
> any action taken or omitted to be taken in reliance on it is prohibited. If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and
> notify the sender.
> **********************************************************************
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
