Customizable environment deployment section and state overview (great for just devs doing deployment) #11783

New Issue

GiteaMirror · 2025-11-02T09:47:37-06:00

GiteaMirror commented

2025-11-02 09:47:37 -06:00

Originally created by @uvulpos on GitHub (Oct 4, 2023).

Feature Description

As a DevOps engineer for different project environments (test, staging, beta, prod), I like the overview of the Azure Classic Pipeline Artifacts & Stages, to see which environment has which version deployed and to deploy another version by button click. This could trigger a CI pipeline. This makes deployment for normal devs much easier and convenient.

The button press could trigger a certain CI event like ondeployment or something and the given data is the branch the user is in. The feedback if the deploment was successful could be established by a successful or failed ci pipeline (doesn't have to be correct on manual deployments, an indication is enough for me)

On the other hand it could also mean if you develop a library, that you create a new release this way (like the go repo). You can probably think that further and further. Now I would be interested in your input. Do you think this makes sense? Feature / Environment branches can make problems and some devops engineers complain about them, so this could be a viable alternative in tracking versions for environment.

Screenshots

Azure View

How it could look like (just dirty figma sketch)

.
(stage + production deployment is forbidden by repo in this sketch)

Originally created by @uvulpos on GitHub (Oct 4, 2023). ### Feature Description As a DevOps engineer for different project environments (test, staging, beta, prod), I like the overview of the Azure Classic Pipeline Artifacts & Stages, to see which environment has which version deployed and to deploy another version by button click. This could trigger a CI pipeline. This makes deployment for normal devs much easier and convenient. The button press could trigger a certain CI event like ondeployment or something and the given data is the branch the user is in. The feedback if the deploment was successful could be established by a successful or failed ci pipeline (doesn't have to be correct on manual deployments, an indication is enough for me) On the other hand it could also mean if you develop a library, that you create a new release this way (like the go repo). You can probably think that further and further. Now I would be interested in your input. Do you think this makes sense? Feature / Environment branches can make problems and some devops engineers complain about them, so this could be a viable alternative in tracking versions for environment. ### Screenshots ## Azure View <img width="550" alt="Screenshot 2023-10-04 at 16 52 03" src="https://github.com/go-gitea/gitea/assets/53957681/3993e982-562b-41c9-b129-a2eb79fdb799"> ## How it could look like (just dirty figma sketch) <img width="550" alt="Screenshot 2023-10-04 at 16 52 03" src="https://github.com/go-gitea/gitea/assets/53957681/cac7cf55-19fc-4a55-84d3-ce5f4d9ad4c2"> <img width="550" alt="Screenshot 2023-10-04 at 16 52 03" src="https://github.com/go-gitea/gitea/assets/53957681/f816006a-869c-4d07-8ab7-43f5d7b2980b">. (stage + production deployment is forbidden by repo in this sketch)

GiteaMirror added the topic/gitea-actions type/proposal labels 2025-11-02 09:47:37 -06:00

GiteaMirror commented

2025-11-02 09:47:38 -06:00

@uvulpos commented on GitHub (Oct 9, 2023):

@techknowlogick do you have feedback on my proposal? Do you think it would make deployments easier for devs? Or is it just more work for DevOps engineers that do it anyway?

(Trying to start a debate)

@uvulpos commented on GitHub (Oct 9, 2023): @techknowlogick do you have feedback on my proposal? Do you think it would make deployments easier for devs? Or is it just more work for DevOps engineers that do it anyway? (Trying to start a debate)

GiteaMirror commented

2025-11-02 09:47:38 -06:00

@puni9869 commented on GitHub (Oct 9, 2023):

Just a thought why not using a drop down as github in actions --> sample image select the branch and deploy on environment. It will be much simpler and will not clutter in UI on code page. It is related to actions page.

@puni9869 commented on GitHub (Oct 9, 2023): Just a thought why not using a drop down as github in actions --> sample image select the branch and deploy on environment. It will be much simpler and will not clutter in UI on code page. It is related to actions page. <img width="1033" alt="image" src="https://github.com/go-gitea/gitea/assets/80308335/862b9e06-be32-44c9-9e02-82847891282c">

GiteaMirror commented

2025-11-02 09:47:38 -06:00

@uvulpos commented on GitHub (Oct 9, 2023):

I'm open for any suggestions, this was just my first thought 🙂
Agree with the point of beeing cluttery when you don't want it. In this View it also makes sense to me, but seems a bit hidden. 🤔 Maybe you could implement both, so the dashboard on the main page is hideable and just visible for maintainers after you activate it in settings. wdyt?

@uvulpos commented on GitHub (Oct 9, 2023): I'm open for any suggestions, this was just my first thought 🙂 Agree with the point of beeing cluttery when you don't want it. In this View it also makes sense to me, but seems a bit hidden. 🤔 Maybe you could implement both, so the dashboard on the main page is hideable and just visible for maintainers after you activate it in settings. wdyt?

GiteaMirror commented

2025-11-02 09:47:39 -06:00

@uvulpos commented on GitHub (Oct 9, 2023):

I'm afraid if you dont show the menu to some devs faces they wont recognize the feature

@uvulpos commented on GitHub (Oct 9, 2023): I'm afraid if you dont show the menu to some devs faces they wont recognize the feature

GiteaMirror commented

2025-11-02 09:47:39 -06:00

@puni9869 commented on GitHub (Oct 9, 2023):

We have action page for ci activity, then we can package this feature there and as a soft link we can post where ever required.

@puni9869 commented on GitHub (Oct 9, 2023): We have action page for ci activity, then we can package this feature there and as a soft link we can post where ever required.

GiteaMirror commented

2025-11-02 09:47:39 -06:00

@uvulpos commented on GitHub (Oct 9, 2023):

allrighty 😄 then lgtm 👍🏻

@uvulpos commented on GitHub (Oct 9, 2023): allrighty 😄 then lgtm 👍🏻

GiteaMirror commented

2025-11-02 09:47:40 -06:00

@enkelmedia commented on GitHub (Sep 17, 2024):

This would have been such a great addition and would make Gitea a “one stop shop” for CI/CD for a team like ours.

@enkelmedia commented on GitHub (Sep 17, 2024): This would have been such a great addition and would make Gitea a “one stop shop” for CI/CD for a team like ours.

GiteaMirror commented

2025-11-02 09:47:40 -06:00

@uvulpos commented on GitHub (Sep 18, 2024):

@enkelmedia Thank you for your support. Do you have any suggestions on how the feature could be even better for you? I would like to refine the idea a little more ✌🏻

@uvulpos commented on GitHub (Sep 18, 2024): @enkelmedia Thank you for your support. Do you have any suggestions on how the feature could be even better for you? I would like to refine the idea a little more ✌🏻

GiteaMirror commented

2025-11-02 09:47:40 -06:00

@enkelmedia commented on GitHub (Sep 18, 2024):

@uvulpos I would be happy to provide ideas on this, I've been working quite a lot with Octopus Deploy (similar to Azure Pipelines) and the overview-feature (your first screenshot) is also really valuable.

But at the end of the day, most of the time you really just want a release to be automatically deployed to test and then use some easily accessible mechanism to promote the release to stage, prod etc. (depending on your pipeline setup).

Is this something that is planned for implementation of just at a proposal stage?

@enkelmedia commented on GitHub (Sep 18, 2024): @uvulpos I would be happy to provide ideas on this, I've been working quite a lot with Octopus Deploy (similar to Azure Pipelines) and the overview-feature (your first screenshot) is also really valuable. But at the end of the day, most of the time you really just want a release to be automatically deployed to test and then use some easily accessible mechanism to promote the release to stage, prod etc. (depending on your pipeline setup). Is this something that is planned for implementation of just at a proposal stage?

GiteaMirror commented

2025-11-02 09:47:41 -06:00

@uvulpos commented on GitHub (Sep 18, 2024):

@enkelmedia I'm afraid it is still just a proposal.

@uvulpos commented on GitHub (Sep 18, 2024): @enkelmedia I'm afraid it is still just a proposal.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#11783