4 ms·

This feature is currently broken. It can let deploys run without builds/tests passing. https://gitlab.com/gitlab-org/gitlab/-/issues/31526 https://gitlab.com/g

This feature is currently broken. It can let deploys run without builds/tests passing. https://gitlab.com/gitlab-org/gitlab/-/issues/31526 https://gitlab.com/gitlab-org/gitlab/-/issues/31526

lindsayolson 6y ago
Hi! GitLab Community Advocate here: I noticed the issue you linked is closed. I believe the conversation is continued here: https://gitlab.com/gitlab-org/gitlab/-/issues/213080 https://gitlab.com/gitlab-org/gitlab/-/issues/213080 Hope that is helpful. If so, feel free to add a comment so the team can see.
- deckar01 6y ago
  Due to that issue being closed maintainers assumed it was fixed and went around closing related issues without testing if the problems were fixed. https://gitlab.com/gitlab-org/gitlab/issues/198570#note_293646250 https://gitlab.com/gitlab-org/gitlab/issues/198570#note_2936... I have had a really negative experience reporting bugs to GitLab in the last 12 months. I have spent tons of time investigating bugs in new features only to have the devs ignore it. It feels like they are sweeping things under the rug so they can hit deadlines for officially announcing new features. https://gitlab.com/gitlab-org/gitlab/-/issues/39534#note_283794210 https://gitlab.com/gitlab-org/gitlab/-/issues/39534#note_283...
  - ahuang1018 6y ago
    Hi! GitLab Community Advocate here - I agree that we need to get better how we improve the quality and performance of existing features/bugs. I am sorry for the negative experience you had. Please ping me on any long standing issues/bugs that are important to you and I'll do my best to route it to the directly responsible individuals. For the new features part, going fast is a core part of our strategy, as is focusing on breadth over depth (https://about.gitlab.com/company/strategy/#breadth-over-dept... https://about.gitlab.com/company/strategy/#breadth-over-dept...). Not only does this provide an easier path to collaborate and contribute for the wider community, it allows us to shorten the feedback loop with everyone that uses GitLab so that we can invest our time and effort in the areas that matter most to the wider community.Hope this is helpful.
  - furkanayhan 6y ago
    Hello Jared! GitLab Senior Backend Engineer - Verify (CI) here - Thanks for reaching out! I'll try to explain current situation of these issues. 1. https://gitlab.com/gitlab-org/gitlab/-/issues/198570 https://gitlab.com/gitlab-org/gitlab/-/issues/198570 We know that this bug with DAG/needs is quite annoying. That's why we've been actively discussing about this bug in other issue: https://gitlab.com/gitlab-org/gitlab/-/issues/213080 https://gitlab.com/gitlab-org/gitlab/-/issues/213080 Can you please take a look at the discussions there? 2. https://gitlab.com/gitlab-org/gitlab/-/issues/39534 https://gitlab.com/gitlab-org/gitlab/-/issues/39534 Unfortunately we had no choice but to give an option to fix this behavior, instead of fixing it. That's because, if we fixed this bug immediately, it would probably break existing pipelines. That's why we allowed users to fix this behavior themselves (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24605 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24605). Hope this is helpful and please feel free to contact us if you have any questions/feedbacks. Thanks!
    - deckar01 6y ago
      These two issues illustrate that GitLab has a quality control problem. If devs aren't dog fooding these features, the community should be given more time to beta test them before the APIs are declared stable.

This feature is currently broken. It can let deploys run without builds/tests passing. https://gitlab.com/gitlab-org/gitlab/-/issues/31526 https://gitlab.com/gitlab-org/gitlab/-/issues/31526

lindsayolson 6y ago

Hi! GitLab Community Advocate here: I noticed the issue you linked is closed. I believe the conversation is continued here: https://gitlab.com/gitlab-org/gitlab/-/issues/213080 https://gitlab.com/gitlab-org/gitlab/-/issues/213080 Hope that is helpful. If so, feel free to add a comment so the team can see.

deckar01 6y ago
Due to that issue being closed maintainers assumed it was fixed and went around closing related issues without testing if the problems were fixed. https://gitlab.com/gitlab-org/gitlab/issues/198570#note_293646250 https://gitlab.com/gitlab-org/gitlab/issues/198570#note_2936... I have had a really negative experience reporting bugs to GitLab in the last 12 months. I have spent tons of time investigating bugs in new features only to have the devs ignore it. It feels like they are sweeping things under the rug so they can hit deadlines for officially announcing new features. https://gitlab.com/gitlab-org/gitlab/-/issues/39534#note_283794210 https://gitlab.com/gitlab-org/gitlab/-/issues/39534#note_283...
- ahuang1018 6y ago
  Hi! GitLab Community Advocate here - I agree that we need to get better how we improve the quality and performance of existing features/bugs. I am sorry for the negative experience you had. Please ping me on any long standing issues/bugs that are important to you and I'll do my best to route it to the directly responsible individuals. For the new features part, going fast is a core part of our strategy, as is focusing on breadth over depth (https://about.gitlab.com/company/strategy/#breadth-over-dept... https://about.gitlab.com/company/strategy/#breadth-over-dept...). Not only does this provide an easier path to collaborate and contribute for the wider community, it allows us to shorten the feedback loop with everyone that uses GitLab so that we can invest our time and effort in the areas that matter most to the wider community.Hope this is helpful.
- furkanayhan 6y ago
  Hello Jared! GitLab Senior Backend Engineer - Verify (CI) here - Thanks for reaching out! I'll try to explain current situation of these issues. 1. https://gitlab.com/gitlab-org/gitlab/-/issues/198570 https://gitlab.com/gitlab-org/gitlab/-/issues/198570 We know that this bug with DAG/needs is quite annoying. That's why we've been actively discussing about this bug in other issue: https://gitlab.com/gitlab-org/gitlab/-/issues/213080 https://gitlab.com/gitlab-org/gitlab/-/issues/213080 Can you please take a look at the discussions there? 2. https://gitlab.com/gitlab-org/gitlab/-/issues/39534 https://gitlab.com/gitlab-org/gitlab/-/issues/39534 Unfortunately we had no choice but to give an option to fix this behavior, instead of fixing it. That's because, if we fixed this bug immediately, it would probably break existing pipelines. That's why we allowed users to fix this behavior themselves (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24605 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/24605). Hope this is helpful and please feel free to contact us if you have any questions/feedbacks. Thanks!
  - deckar01 6y ago
    These two issues illustrate that GitLab has a quality control problem. If devs aren't dog fooding these features, the community should be given more time to beta test them before the APIs are declared stable.