Le 28/02/2014 09:30, Yuriy Tymchuk a écrit :
Thank you Goubier.
I’m very sorry again for bothering, but I can’t compose the workflow.
Usually my workflow is like that:
1. CI is building the image from the MC configuration testing and
zipping it.
1- Use a configuration which clones in read-write mode: that is ssh
(prepare a ssh key for the CI that is just registered to the git
repository as having read access is probably enough). After the tests,
ask CI to zip the directory containing the image.
2. I download the image and code the project.
2- Download the zip, extract the folder, open the image and code the
project.
3. I commit my stuff to the repository that is already available in the
image (because of CI) and it goes back to step 1.
3- Same. Don't forget to push at the end of the day[1].
(I don’t download the fresh image every time I commit, but I always
start a day from fresh image)
I don’t really see how I can do that with git.
With gitfiletree as it is now, I don't see how you wouldn't be able to
do that :) To the condition that you don't zip only the image (and the
changes and ...) but just directly the directory containing the image.
Gitfiletree clones in there.
But if you want or find another way, let me know :)
[1] Ok, still, maybe there is a point there: the path to the repository
clone may well be encoded as an absolute path, and, therefore, moving
the directory elsewhere could be tricky. This is something I can look
into if you choose that git workflow.
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
