Return-Path: X-Original-To: distix@pieni.net Delivered-To: distix@pieni.net Received: from yaffle.pepperfish.net (yaffle.pepperfish.net [88.99.213.221]) by pieni.net (Postfix) with ESMTPS id 73FFA432E4 for ; Wed, 20 Jun 2018 13:45:47 +0000 (UTC) Received: from platypus.pepperfish.net (unknown [10.112.101.20]) by yaffle.pepperfish.net (Postfix) with ESMTP id 3BB71414F5 for ; Wed, 20 Jun 2018 14:45:47 +0100 (BST) Received: from ip6-localhost.nat ([::1] helo=platypus.pepperfish.net) by platypus.pepperfish.net with esmtp (Exim 4.80 #2 (Debian)) id 1fVdQh-0006Ig-67; Wed, 20 Jun 2018 14:45:47 +0100 Received: from [148.252.241.226] (helo=somnambulist.local) by platypus.pepperfish.net with esmtpsa (Exim 4.80 #2 (Debian)) id 1fVdQg-0006IR-7B for ; Wed, 20 Jun 2018 14:45:46 +0100 Date: Wed, 20 Jun 2018 14:45:44 +0100 From: Daniel Silverstone To: ick-discuss@ick.liw.fi Message-ID: <20180620134544.5wzm5rfff2oxqp5n@somnambulist.local> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170113 (1.7.2) X-Pepperfish-Transaction: 9c56-f603-cfe9-771c X-Pepperfish-Transaction-By: platypus Subject: Re: Ick and checking out source from git X-BeenThere: ick-discuss@ick.liw.fi X-Mailman-Version: 2.1.5 Precedence: list List-Id: discussions about the ick CI system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ick-discuss-bounces@ick.liw.fi Errors-To: ick-discuss-bounces@ick.liw.fi On Wed, Jun 20, 2018 at 15:30:49 +0300, Lars Wirzenius wrote: > I'd like to support this for any number of repositories. I suggest the > following: > > parameters: > git: > - url: ssh://git@git.example.com/foo.git > ref: master > dir: foo > - url: ssh://git@git.example.com/foo-debian.git > ref: master > dir: foo/debian > > The above would do the same things as the two git clones above. > > What do you all think? Especially you, Daniel? Would that be an acceptable > design (at least for now)? So my main concern with this is that it remains a problem for the case of genericisation. I currently have a single pipeline step which uses a parameter to configure the git repository to pull from. What I'd like would be something akin to Ansible's use of jinja2 to do: parameters: git: - url: "ssh://git@server/{{ source_name }}.git" ref: master dir: "{{ source_name }}" - url: "ssh://git@server/{{ source_name }}/debian.git" ref: master dir: "{{ source_name }}/debian" Failing that kind of capability, your suggestion would at least mean I could move the clones out of the shell steps I suppose :-) D. -- Daniel Silverstone http://www.digital-scurf.org/ PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69 _______________________________________________ ick-discuss mailing list ick-discuss@ick.liw.fi https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi