Mads Jon Nielsen
Mads Jon Nielsen
Our production and staging environment went down across two K8S clusters and eight Docker Swarm clusters in three different psychical locations the 19th of July and again this morning (24th...
It definently was on purpose. "normally" programmers specify hardpinned include dependencies. Only developers actively working on a module/include would use have to use `--fetch-includes`, because they utilize "master/latest/branches"
I'm ok with it.. :+1:
I don't think the `release:` keyword is used by gitlab-ci-local in any way, shape or form.
These works. ``` mjn@mjn-laptop:~/workspace/gitlab-com-ci-debugging$ GCL_TIMESTAMPS=false gitlab-ci-local parsing and downloads finished in 57 ms json schema validated in 177 ms test starting shell (test) test $ echo hello test > hello...
I'm not sure I understand how this would benefit your local flow Please attach a good example that illustrates problems that this feature would address.
Yeah, i agree :+1: You mind making a PR?
https://github.com/firecow/gitlab-ci-local/pull/1439 Is now merged and published @ANGkeith
You need to put a lot more context into this issue. I have no idea what kind of code I should write to implement this :smile: Just reopen this issue...
Supporting these custom executors is going to be a major undertaking. I'm not going to work on this, but we will leave this open in case others want to implement...