3 ms·

What are the top 3 basic and important things that GitLab could add?

by sytse 6y ago

majkinetor 6y ago
1. running CI locally 2. issue relations in core 3. getting a repository file via curl easily (yeah, seriously)
- mokha 6y ago
  1. It does take some effort to get the gitlab-runner to run locally but it is possible to use the shell runner. This does require that you connect the gitlab-runner to an instance of GitLab. If I understand correctly, I think you're asking for the ability to take a `.gitlab-ci.yml` file and run the job(s) locally from your shell without requiring it go through the gitlab-runner and connecting to a GitLab instance. Please correct me if I'm off. 2. I'm not sure I understand what this means. 3. I think this is already possible. E.g. `curl https://gitlab.com/gitlab-org/security-products/license-management/-/raw/master/LICENSE` https://gitlab.com/gitlab-org/security-products/license-mana.... Can you elaborate with a few more details on this?
  - majkinetor 6y ago
    1. a lot of effort and I never want to repeat that, ever 2. issue relations is when you connect issues to other issues (for example, Redmine has both sub-issues and related issues) 3. Can you try that when repo is authorized and let me know how it went ?
    - mokha 6y ago
      1. Yes, I agree. This is something that I personally would like to improved. 2. Oh, I see. I don't have much experience with this one. 3. Got ya. So cURLing a raw file from a private repo. How would you like that to work?
      - majkinetor 6y ago
        3. I have a link to a file already (in a browser URL bar), let me use it with token or something easy (for example the way most RSS with auth are constructed so that you don't need to set up credentials when 'subscribing') instead of looking for project IDs and constructing path that GitLab can swallow as a query parameter, fighting all kind of nonsence in the process. FYI, nobody I know did that in a minute (and minute is much for such task) and everybody was like _fuck this shit, I'll just clone entire repo to use a single file_, 15 minutes later.
- sytse 6y ago
  Thanks, those are clear and concrete. Some quick thoughts (can’t get detailed ones since GitLab is having a friends and family day): 1. This works but not nearly with all functionality. 2. Maybe an options to have related in core and more detailed relations like blocking in a paid version. 3. I’m surprised this isn’t possible already. Is this easy to contribute for anyone?
- JetSpiegel 6y ago
  3.1. Get a sane link to a build artifact (something like latest `master`). This can be worked around if you just publish them on Gitlab Pages, a nice solution now that they even have authentication.

What are the top 3 basic and important things that GitLab could add?

by sytse 6y ago

What are the top 3 basic and important things that GitLab could add?

majkinetor 6y ago

1. running CI locally 2. issue relations in core 3. getting a repository file via curl easily (yeah, seriously)

mokha 6y ago
1. It does take some effort to get the gitlab-runner to run locally but it is possible to use the shell runner. This does require that you connect the gitlab-runner to an instance of GitLab. If I understand correctly, I think you're asking for the ability to take a `.gitlab-ci.yml` file and run the job(s) locally from your shell without requiring it go through the gitlab-runner and connecting to a GitLab instance. Please correct me if I'm off. 2. I'm not sure I understand what this means. 3. I think this is already possible. E.g. `curl https://gitlab.com/gitlab-org/security-products/license-management/-/raw/master/LICENSE` https://gitlab.com/gitlab-org/security-products/license-mana.... Can you elaborate with a few more details on this?
- majkinetor 6y ago
  1. a lot of effort and I never want to repeat that, ever 2. issue relations is when you connect issues to other issues (for example, Redmine has both sub-issues and related issues) 3. Can you try that when repo is authorized and let me know how it went ?
  - mokha 6y ago
    1. Yes, I agree. This is something that I personally would like to improved. 2. Oh, I see. I don't have much experience with this one. 3. Got ya. So cURLing a raw file from a private repo. How would you like that to work?
    - majkinetor 6y ago
      3. I have a link to a file already (in a browser URL bar), let me use it with token or something easy (for example the way most RSS with auth are constructed so that you don't need to set up credentials when 'subscribing') instead of looking for project IDs and constructing path that GitLab can swallow as a query parameter, fighting all kind of nonsence in the process. FYI, nobody I know did that in a minute (and minute is much for such task) and everybody was like _fuck this shit, I'll just clone entire repo to use a single file_, 15 minutes later.
sytse 6y ago
Thanks, those are clear and concrete. Some quick thoughts (can’t get detailed ones since GitLab is having a friends and family day): 1. This works but not nearly with all functionality. 2. Maybe an options to have related in core and more detailed relations like blocking in a paid version. 3. I’m surprised this isn’t possible already. Is this easy to contribute for anyone?
JetSpiegel 6y ago
3.1. Get a sane link to a build artifact (something like latest `master`). This can be worked around if you just publish them on Gitlab Pages, a nice solution now that they even have authentication.