add the ability to delete an environment

Description

I don't always use the on_stop functionality with gitlab CI's environments. An environment can cease to exist due to actions taken outside of gitlab CI. It would nice to be able to delete and/or mark dead an environment, so that the environments screen is not cluttered with incorrect information.

added ~19173 feature proposal labels

mentioned in issue #26564 (closed)

I now have two environments called staging, one with a capital S, really confusing, would be great to be able to remove it without using the API :D

Found this thread while trying to solve the same problem. I'll leave it as-is for now, but I'm adding my vote to this feature too. Good to know I can do it through the API if I need to.

I totally agree. While environments are automatically created out of a gitlab-ci.yml file, but persist if the environment names change, it makes sense to be able to delete them manually.

Apparently the only way right now to delete an environment is via rest API: https://docs.gitlab.com/ce/api/enviroments.html#delete-an-environment

It would be nice to have it in the GUI as well... I guess.

Another workaround is to rename builds into something like _trash/env-build-name - if there are just a few ones.

Yep, it really make sense to delete environments. Created tons of environments testing the build and now i can't delete

I needed this too. After using the API, the environment is deleted but it's still being listed in the Environments tab. When clicking in the environment it returns a 404.

Weird, after a while the environments are not there anymore.

Adding link to the correct API Docs: https://docs.gitlab.com/ce/api/environments.html#delete-an-environment

moved to gitlab#7344

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785