Official Docker Image

[unacceptable]

It would be great if this had an official docker image from you. Here is what I was thinking for a run syntax:

docker run -it mdubourg001/glci --only-jobs # or whatever extra args are provided.

Here is what I think that the Dockerfile should look like:

# docker build -t glci:local . && docker run -it glci:local

# I couldn't find a better image that worked (apparently python's a dependency)
FROM okdocker/pynode

RUN yarn global add glci # maybe we want to install from the local version?

ENTRYPOINT ["/usr/local/bin/glci"]
CMD ["--help"]

Here's an example of me running a local version of it:

I'd be happy to help incorporate the CI portion of it if you want help.

Thanks for making some amazing tooling! This fills a need that I have had for some time, but was too lazy to try to tackle.

[mdubourg001]

Hi there,

The goal of glci is really to be used (ran) locally to "pre-validate" your CI Pipelines while making changes to them. As glci already creates a new Docker container for each CI job he runs and automatically removes it when the job succeeds or fails, why would you want to run glci itself in Docker ? I'm not sure to understand the purpose here, could you explain ?

However, thanks for your interest in the tool !

[unacceptable]

@mdubourg001,

I can think of two use cases for this:

1. For developers who want to run glci, but don't have glci or yarn installed locally, and don't want to install them on their system. I think that this approach is probably the future of a lot of CLI tools (in fact tools like trivy and hadolint are doing this now).
2. CI as validation of a GitLab library (before that library is called) - This would also require a flag like --file to specify the yaml file to test. In gitlab this second use case would look something like this:

validate-gitlab-ci:
  stage: lint
  script:
  - find . -name "*.y*ml" -exec glci --file "{}" ";"
  image:
    name: mdubourg001/glci:0.0.3
    entrypoint:
      - '/usr/bin/env'
  except:
  - tags

Let me know what you think about these two use cases. I know that they are probably quite a bit different than what you initially imagined.

Respectfully,
Robert J.