Date: Mon, 2 Jul 2018 18:24:48 +0300
From: Lars Wirzenius <liw@liw.fi>
To: ick-discuss@ick.liw.fi
Message-ID: <20180702152447.GA2363@exolobe3.liw.fi>
MIME-Version: 1.0
User-Agent: Mutt/1.10.0 (2018-05-17)
Subject: Making the "git" action in ick more useful
Precedence: list
Content-Type: multipart/mixed; boundary="===============5779175466179041238=="
Mime-version: 1.0
Sender: ick-discuss-bounces@ick.liw.fi
Errors-To: ick-discuss-bounces@ick.liw.fi


--===============5779175466179041238==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd"
Content-Disposition: inline


--vkogqOf2sHV7VnPd
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

The current version of ick has a "git action", which works like this:

* requires the project parameters git_url, git_ref, git_dir

* is run on the host, not in a container, because it uses the host's
  (which is a worker) ssh key to access the git server, if access is
  via ssh

* if the directory named in git_dir does NOT exist, effecitvely runs
  "git clone $git_url $git_dir" (except without shell quoting issues)

* if the git_dir directory DOES exist, runs, in that directory:
  "git remote update --prune"

* the above commands do all the network operations; the user is then
  expected to run other commands, inside the container, to do anything
  else to access the right ref ("git checkout $git_ref" etc)


This design means that only the parts that are absolutely necessary to
run outside the container are done there, and the user has the
flexibility to customise the rest. The goal is for ick to provide a
default "prepare_workspace" pipeline that does all the things that
typical users require, so each user is not forced to reinvent a
triangular wheel, loosely attached.

However, the above design isn't flexible enough for Daniel, who needs
to access multiple git repositories, not just once, and build a tree
of clones. I'll let Daniel tell us what his use-case is like. (I think
I know, but it's better if he tells it himself. I can be a bit of a
broken telephone.)

Let the Brainst Orming begin. (See description of this product:
https://www.amazon.de/dp/B00UWNJ9OI/)

--=20
I want to build worthwhile things that might last. --joeyh

--vkogqOf2sHV7VnPd
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEETNTnrewG6wEE1EJ3bC+mFux6IDEFAls6Q78ACgkQbC+mFux6
IDE7ZA/+MWrcftsa3I4O+FHPEPOeOXIyUegQEzVK7lyLzmfR1zRC/Tq0kzocrWPD
4refg1mplsihl7m+jPDCNsU09RG02wSaFeVMJVQwirT8cOCchnTnXoe83Lmk0ivE
oIqKn1LAzKg7RqXXGbeAYmK6KYNN07uK9rtIlugUNWibAQyGM6vxfohi8a1zQUyZ
FsW4Or882V5KR9zVGaSH/r6dWBQmQUE90d9EqGby3aeK9S7SNiEvSr0INtBEBHJV
ixeDTeGEqrlFBMwSm0+3d54V3pnCwb0oOePCbQyYJ428+7lBSUHDnV5R6ptAJ4xa
RYso/qLxy3WTgLTFnMQ+kOWOWKzFGL7/NU3muXT0EsJso5K+1aMzNneeLa3w48e/
/KzIhZq1vRnkXtUA/nFLL0wKtPyHvG6wpYEnZ+Eazq4YqUjDKaIauSGPZrvjV+em
zSj7Lz07U88xEyhK+wdDNqRkZekLOQ1uYEXED8V0KpPpzK8mxR2kOwOALYtt14vp
JWJtGtUcDIaCmZD1a71Bd0NvwY79ehh3r8VUnSF5BQu43WQfFrgRfOR4G2n4OqJH
deCNYvEYNlnpdXcTgNK5BPNwC0/6ltb02d2S1VGoL47Ckhn4i6wK9gF/9jHiR4zr
BJBHUgwesRw03MG+U3WAgkl+aP/Ah7D4PB5kh8BvuCp2UizZ1d0=
=zgJ+
-----END PGP SIGNATURE-----

--vkogqOf2sHV7VnPd--


--===============5779175466179041238==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ick-discuss mailing list
ick-discuss@ick.liw.fi
https://listmaster.pepperfish.net/cgi-bin/mailman/listinfo/ick-discuss-ick.liw.fi

--===============5779175466179041238==--