Re: NEW: devel/gitlab-ci-multi-runner
On Tue, Aug 16, 2016 at 09:04:00AM +0200, Frank Groeneveld wrote: > Got some feedback off-list. I've incorporated these fixes (missing >, > added homepage, license on seperate line). Any other comments? Ping? Thanks. Frank gitlab-ci-multi-runner-1.4.1.tar.gz Description: application/tar-gz
Re: NEW: devel/gitlab-ci-multi-runner
On Wed, Aug 10, 2016 at 12:37:33PM +0200, Frank Groeneveld wrote: > Attached a port for gitlab-ci-multi-runner: > > --- > A runner for Gitlab CI. It runs tests and sends the results to GitLab. > GitLab CI is the open-source continuous integration service included > with GitLab that coordinates the testing. > --- > > My previous attempt stranded because I needed some upstream patches and > a prebuilt docker image. I've solved this problem by just simply > disabling the docker parts, we won't be able to use that on OpenBSD > anyway. > > What do you think, can this be imported? > > Thanks > > Frank Got some feedback off-list. I've incorporated these fixes (missing >, added homepage, license on seperate line). Any other comments? Thanks. Frank gitlab-ci-multi-runner-1.4.1.tar.gz Description: application/tar-gz
NEW: devel/gitlab-ci-multi-runner
Attached a port for gitlab-ci-multi-runner: --- A runner for Gitlab CI. It runs tests and sends the results to GitLab. GitLab CI is the open-source continuous integration service included with GitLab that coordinates the testing. --- My previous attempt stranded because I needed some upstream patches and a prebuilt docker image. I've solved this problem by just simply disabling the docker parts, we won't be able to use that on OpenBSD anyway. What do you think, can this be imported? Thanks Frank gitlab-ci-multi-runner-1.4.1.tar.gz Description: application/tar-gz
Re: NEW: devel/gitlab-ci-multi-runner
On Mon, Jul 11, 2016 at 06:00:50PM -0500, Amit Kulkarni wrote: > I think you missed ports lock, you will have to wait a month or so before > port imports can start again. Thanks for the reply, but my first concern is cleaning up this port and resolving the two problems. Do you have any suggestions for that? Thanks! Frank
Re: NEW: devel/gitlab-ci-multi-runner
On 2016/07/11 18:00, Amit Kulkarni wrote: > I think you missed ports lock, you will have to wait a month or so before > port imports can start again. Nothing has been announced about when port imports can start again.
Re: NEW: devel/gitlab-ci-multi-runner
On Mon, Jul 11, 2016 at 2:07 PM, Frank Groeneveld < frank+openbsd-po...@frankgroeneveld.nl> wrote: > On Mon, Apr 18, 2016 at 09:51:08PM +0200, Frank Groeneveld wrote: > > Attached a port for gitlab-ci-multi-runner: > > > > --- > > A runner for Gitlab CI. It runs tests and sends the results to GitLab. > > GitLab CI is the open-source continuous integration service included > > with GitLab that coordinates the testing. > > --- > > > > My upstream patches have not all been accepted yet. I'm still waiting > > on one update of a vendored package: > > https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/139 > > > > For now, I've included that patch in its most simple form in the port. > > This results in a very long filename though, so the port is attached as > > zip file (tar could not store this long name). What's the best way to > > shorten this patch name? > > > > The final problem is the referenced prebuilt.tar.gz. I believe this is > > a very simple Docker container image that can be used by > > gitlab-ci-multi-runner to start a docker container on a docker host. > > This file is however not versioned and I'm not sure whether the contents > > will change in the future. If so, it will of course result in checksum > > errors. Should we/I cache this file somewhere and version it with the > > date? > > Anybody care to help me with these questions? I would really like to get > this imported. > > Thanks! > > Frank > > I think you missed ports lock, you will have to wait a month or so before port imports can start again.
Re: NEW: devel/gitlab-ci-multi-runner
On Mon, Apr 18, 2016 at 09:51:08PM +0200, Frank Groeneveld wrote: > Attached a port for gitlab-ci-multi-runner: > > --- > A runner for Gitlab CI. It runs tests and sends the results to GitLab. > GitLab CI is the open-source continuous integration service included > with GitLab that coordinates the testing. > --- > > My upstream patches have not all been accepted yet. I'm still waiting > on one update of a vendored package: > https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/139 > > For now, I've included that patch in its most simple form in the port. > This results in a very long filename though, so the port is attached as > zip file (tar could not store this long name). What's the best way to > shorten this patch name? > > The final problem is the referenced prebuilt.tar.gz. I believe this is > a very simple Docker container image that can be used by > gitlab-ci-multi-runner to start a docker container on a docker host. > This file is however not versioned and I'm not sure whether the contents > will change in the future. If so, it will of course result in checksum > errors. Should we/I cache this file somewhere and version it with the > date? Anybody care to help me with these questions? I would really like to get this imported. Thanks! Frank
