[petsc-dev] Gitlab workflow discussion with GitLab developers

[jacob.fai at gmail.com]

1. Allow searching pipeline jobs by name, type, or tag. I want to be able to
find all "linux-cuda-double-64idx" jobs that ran in the last 24 hours, or
all jobs that have the tag gpu:nvidia for example. Currently I must manually
click through the pages and snoop on everyone's pipelines. It would be nice
if the https://gitlab.com/petsc/petsc/-/jobs page had the same "filter"
search box that pipelines have. 
2. The filter pipelines needs to be able to search for "awaiting approval".
I like to cancel all the zombie jobs that MRs create due to auto-pipelines,
which so far I have done by manually checking my MRs after pushes.

Best regards,

Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391

| -----Original Message-----
| From: petsc-dev <petsc-dev-bounces at mcs.anl.gov> On Behalf Of Lawrence
| Mitchell
| Sent: Friday, January 21, 2022 04:32
| To: Barry Smith <bsmith at petsc.dev>
| Cc: petsc-dev <petsc-dev at mcs.anl.gov>
| Subject: Re: [petsc-dev] Gitlab workflow discussion with GitLab developers
| 
| 
| > On 21 Jan 2022, at 01:05, Barry Smith <bsmith at petsc.dev> wrote:
| >
| > I got asked to go over some of my Gitlab workflow uses next week with
| some Gitlab developers; they do this to understand how Gitlab is used, how
| it can be improved etc.
| >
| >  If anyone has ideas on topics I should hit, let me know. I will hit
them on
| the brokenness of appropriate code-owners not being automatically added
| to reviewers. And support for people outside of the Petsc group to set
more
| things when they make MRs. And being to easily add non-PETSc folks as
| reviewers.
| 
| At least in my experience reviewing large (by diffstat measures) in the
| browser (I use Safari) is nigh-on unusable since the web interface grinds
to a
| halt, and has various other bugs.
| 
| Of course one should aim for small code changes that are easy to review,
but
| often a small code change will produce large changes in the test output
files
| (which have to appear in the MR, or else one merges broken code).
| 
| Some examples, if I go to one of Jacob's recent cleanup MRs:
| https://gitlab.com/petsc/petsc/-/merge_requests/4700/diffs
| 
| Dragging the scroll bar is very laggy (I guess there's some background
thread
| trying to load things from somewhere?).
| 
| Semi-randomly, if I click to add a comment on a change, the page jumps
back
| to the start and I lose my place.
| 
| This seems slightly better in Brave (Chromium).
| 
| I don't know enough about how the web interface/database integration
| works, but grinding to a halt on a 6000 line diff is unfortunate.
| 
| Lawrence