From users-return-16636-apmail-subversion-users-archive=subversion.apache.org@subversion.apache.org Thu Nov 8 22:41:14 2012 Return-Path: X-Original-To: apmail-subversion-users-archive@minotaur.apache.org Delivered-To: apmail-subversion-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C79DD0FF for ; Thu, 8 Nov 2012 22:41:14 +0000 (UTC) Received: (qmail 66159 invoked by uid 500); 8 Nov 2012 22:41:13 -0000 Delivered-To: apmail-subversion-users-archive@subversion.apache.org Received: (qmail 66117 invoked by uid 500); 8 Nov 2012 22:41:13 -0000 Mailing-List: contact users-help@subversion.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@subversion.apache.org Received: (qmail 66107 invoked by uid 99); 8 Nov 2012 22:41:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 22:41:13 +0000 X-ASF-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.18.0.26] (HELO exprod5og113.obsmtp.com) (64.18.0.26) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 22:41:03 +0000 Received: from alpmlip14.e2k.ad.ge.com ([165.156.5.1]) (using TLSv1) by exprod5ob113.postini.com ([64.18.4.12]) with SMTP ID DSNKUJw06EAtRKJEyEnFjl/Y45T4r2fzCBVR@postini.com; Thu, 08 Nov 2012 14:40:43 PST Received: from unknown (HELO cinmlef06.e2k.ad.ge.com) ([3.159.213.37]) by alpmlip14.e2k.ad.ge.com with ESMTP; 08 Nov 2012 17:39:16 -0500 Received: from ALPMLVEM16.e2k.ad.ge.com ([3.159.18.65]) by cinmlef06.e2k.ad.ge.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 8 Nov 2012 17:39:15 -0500 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CDBE01.E19BE0E5" Subject: SVN Usage Questions Date: Thu, 8 Nov 2012 17:39:09 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SVN Usage Questions Thread-index: Ac29+lSc7xDBMgPeS/iAVTfGBjKlEg== From: "Ahmed, Omair (GE Oil & Gas)" To: X-OriginalArrivalTime: 08 Nov 2012 22:39:15.0696 (UTC) FILETIME=[E1D91F00:01CDBE01] X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. ------_=_NextPart_001_01CDBE01.E19BE0E5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, =20 I am looking for some guidance on where to store build artifacts in SVN. Our projects are organized in the typical fashion: =20 /trunk/Customer1/ ../../src ../../database /branch /tags /release =20 Our official build server is a QNX system, a Unix-like OS. =20 =20 Our proposed process calls for the build engineer to copy the code from the SVN repo to the build server. When a build has been executed, where should we copy the artifacts (the executables) back to? Is the /release directory appropriate or is the another "standard" way to store the artifacts?=20 =20 How are other people handling this?=20 =20 Secondly, if we check-in to the /release folder, what mechanism is there to readily identify the artifacts. Do we create a /release/rel_1 type structure or is there some labeling convention available in SVN? Unless I am I missing something very obvious, I don't see a way to apply labels in SVN. =20 Please advise. ------_=_NextPart_001_01CDBE01.E19BE0E5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I am looking = for some guidance on where to store build artifacts in SVN. Our projects = are organized in the typical fashion:

 

/trunk/Customer1/

../../src

../../database

/branch

/tags

/release

 

Our official = build server is a QNX system, a Unix-like OS.  

 

Our proposed = process calls for the build engineer to copy the code from the SVN repo = to the build server. When a build has been executed, where should we = copy the artifacts (the executables) back to? Is the /release directory = appropriate or is the another “standard” way to store the = artifacts?

 

How are other people handling this?

 

Secondly, if = we check-in to the /release folder, what mechanism is there to readily = identify the artifacts. Do we create a /release/rel_1 type structure or = is there some labeling convention  available in SVN? Unless I am I = missing something very obvious, I don’t see a way to apply labels = in SVN.

 

Please advise.

------_=_NextPart_001_01CDBE01.E19BE0E5--