-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improving Gitlab-CI display #64
Comments
I'm too interested in the first feature requested here (pipeline stages display). If one of the stages failed it's really handy to see which one straight away. I might be able to contribute if I'll find some free time. |
We also needed this so we have implemented this in our fork: milinnovations@3d13b3f |
Closed with pr #75. |
Note that my pull request did not handle point 1 from the original issue, i.e. this one:
Maybe it would be good either to leave this issue as open or create a new issue separately. |
Will create another issue for point 1. |
added as #76 |
I have two features I would like to have in the gitlab-ci plugin.
Gitlab-CI have different stages during a build, like "test", "build", "deploy". The interface is not showing this information.
beeing able to display only a number of builds per project.
For now I'm displaying all the builds for "stared" projects. Let's say I display 10 builds and I try to build "project A" 11 times, I will only see the status of project A in the dashboard.
I would like to be able to say "I want the last 3 builds of each project", maybe grouped by project...
I'm really no nodejs expert so it will be hard for me to help with that, but looking at your code I'm really sure it could be quite easy for a trained dev :
maybe for 1) it would be a rewrite of the project name to include the "stage" ?
for 2) it would be a more complicated filter, at the same place where you sort by date/project ?
I'll ask a friend of mine who is a nodejs dev if he can help, but let me know if you have any clue/time for such features.
Great work btw !
The text was updated successfully, but these errors were encountered: