Make the link to go back to the merge request more obvious from a job page
Whenever I saw a failed build on a merge request, and clicked on it to go to the build like this: (the image wasn't a failed build, but you get the idea)
And I often want to navigate back to the merge request, but I can't. Clicking on the branch name would send me to the branch page, not the merge request which showed the build in the first place:
It would be great to be able to go back to the merge request where leaded me to the build page.
/cc @ayufan @hazelyang
Activity
Added frontend label
@ayufan it is in the sidebar? Under
Build details@iamphill Interesting. I see the implementation there.
Edited by Kamil TrzcińśkiOh. There's Merge Request. Maybe it should be more visible then?
@markpundsack what do you think?
At any rate, clearly the link is there, but not really in a good UX. I could see moving the MR to the same summary line where the branch is listed. The MR has got to be at least as important as the branch and other information.
Side note, in that screenshot, the summary says "20 hours ago" but the sidebar says "17 hours ago". Presumably they're referring to different things, but what? Is one saying how long ago the pipeline started vs that specific build?
Removed feature proposal label
Not sure I understand that last comment. If you really just want to go to another task (job) in the same build, then already listed in the navigation above. What information is on the build page that you need to select the job that isn't already included on this page?
lol
You're right, I ignored that again. I think the problems were:
- It occupied too much space on top, and it's usually just noise because I want to see the output from this particular job. So usually I just scrolled through it. Perhaps putting them on sidebar somehow would be better?
- Failed jobs are not obvious. They're not in red.
Side note, in that screenshot, the summary says "20 hours ago" but the sidebar says "17 hours ago". Presumably they're referring to different things, but what? Is one saying how long ago the pipeline started vs that specific build?
I think that's because what I showed here was the job which failed "20 hours ago", while I retried it and it passed in "17 hours ago". That means the summary was talking about the entire build status, while the main section was showing a particular job. Not sure if this is confusing. I don't care too much about when for them.
We should make that section more obvious and easier to navigate between related jobs. Discussion at https://gitlab.com/gitlab-org/gitlab-ce/issues/18141.
//cc @dimitrieh
mentioned in issue #24339 (closed)
i think this can be considered part of https://gitlab.com/gitlab-org/gitlab-ce/issues/24339 by making the MR more visible and improving on the current view with perhaps the mini pipeline graph
moved to gitlab#5307
Hey!
GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current
gitlab-cerepository will become a read-only mirror, without any proprietary code. All development is moved to the currentgitlab-eerepository, which we will rename to justgitlabin the coming weeks. As part of this migration, issues will be moved to the currentgitlab-eeproject.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/13855You 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/13855What 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 theee/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/13304Will 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.
