Re: [Yade-dev] Call for testing, updated yadedaily packages
Bruno Chareyre said: (by the date of Mon, 15 Jul 2019 18:26:07 +0200) > > in practice any computer can have a gitlab-runner installed. You could [...] > Fair point. > > The "only" problem is that this solution requires that you have a trusted > > PC that runs almost all the time. > > > > What about using yade-runner for this (it would make sense to have both the > credentials and the repository in Grenoble)? This can be yade-runner, or the server that hosts yade-dem.org. Anything you decide is safe and secure enough. And perhaps giving Anton access would solve all the problems. Anton would just send you an id_rsa_yade.pub for ssh, and you are all set! :) Unfortunately I cannot provide a secure server here at Gdańsk. At least at the moment. I can provide compute resources for compiling though :) cheers Janek ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] Call for testing, updated yadedaily packages
On Sat, 13 Jul 2019 at 01:28, wrote: > in practice any computer can have a gitlab-runner installed. You could > place the private key on a PC that you control with gitlab-runner > installed. Use the tag to mark it as the one used only for building > packages and nothing else to save your resources. By this way your private > key would be securely connected to the gitlab framework > Fair point. > The "only" problem is that this solution requires that you have a trusted > PC that runs almost all the time. > What about using yade-runner for this (it would make sense to have both the credentials and the repository in Grenoble)? Bruno ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] Call for testing, updated yadedaily packages
Hi Anton, On Fri, 12 Jul 2019 at 19:03, Anton Gladky wrote: > Comments, critic are > very welcome. > This is great! Thank you very much. Was there specific difficulties with ubuntu16.04 (even if it's getting old I'm sure there would be users of it)? If yes, then let it be. If it just needs to add a name in [1] then it's maybe worth it. [1] https://gitlab.com/yade-dev/trunk/merge_requests/185/diffs#9e4f27c17b0dc74b4dff4de88036f97a4daf0f00_0_7 > > p.s. just curious about the amazonaws hosting, issues with gitlab.com? > If it helps local server yade-dem.org can be used to. Nothing against > > Now it is done on my laptop and I am just using the Amazon S3 for testing > purposes. > We can surely use it further, but I would also prefer to move to > yade-dem.org. > But we need to coordinate that. > Ok. There are two questions then: - Where to host: yade-dem.org is available like before (it's on a brand new hardware and it should stay for years), we need to give you access to it I guess. - Who/how to sign the packages: I don't see it very convenient if you have to do anything manually, we are updating master many times a day at the moment. Or maybe a few of us need to learn how to do it to. > Theoretically, we could use the gitlab infrastructure to build the > repository as well. > But the problem is that it should be signed by the private yade-GPG key. > And I would escape to upload this private key into the gitlab servers due > to security concerns. Maybe I am missing something. > I know exactly what you mean. That's why currently yade-dem.org does wget the documentation from gitlab (checking every 10 minutes or so) instead of gitlab pushing actively. We did not like giving credentials to gitlab. I don't think you missed anything, there is no escape on this aspect. Regards Bruno ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
