For main, will ci.freebsd.org display under "Build description" text like: main-c255728-g99d1a7829f88 ?

Mark Millard marklmi at yahoo.com
Sat Jan 9 05:39:33 UTC 2021



On 2021-Jan-8, at 20:43, Li-Wen Hsu <lwhsu at freebsd.org> wrote:

> On Sat, Jan 9, 2021 at 8:38 AM Mark Millard via freebsd-git
> <freebsd-git at freebsd.org> wrote:
>> 
>> What sort of text will appear under "Build description" for
>> htts://ci.frebsd.org once main finally starts getting CI
>> builds again?
>> 
>> Will it be like the uname output (invented example)?:
>> 
>> main-c255728-g99d1a7829f88
> 
> In short, I'm not sure, but very likely. Currently there is a
> stranding issue that Jenkins doesn't provide an easy way to get
> abbreviated commit hash. This is not a blocking issue, and there are
> still waysto get it, but may need more time to test and implement.
> 
> I haven't decided what is the best to put into the build description
> (and even haven't taught ci.freebsd.org about git. but should be
> soon!)
> I was thinking just using the abbreviated commit hash, but it might be
> a good idea to also prefix or suffix the commits count. I'll check if
> it is possible and easy to get this.  I'm not sure it still needs to
> include the branch name in the build description, as it is already in
> the job name, and on artifact.freebsd.org, there are parent
> directories with branch names.

Cool.

The below is "just me", not some sort of grand claim
about general use. Just something to consider.

I can think of one reason to have the Branch name in the
"Build description" on the https://ci.freebsd.org/ page:
there is no way to sort the display using multiple fields
to subsort in a specific order. Someday there will be
both main and stable-13 that are both git-only. I'd prefer
to be able to look at an order that keeps the two in
separate groups, each sub-sorted by the c?????? figures,
even if the c?????? part happened to be the same at some
point on the separate branches. As near as I can tell
having descriptions something like [invented examples,
illustrative context notes added in ()'s]:

main-c255727-gc98a764c681f      (say powerpc64)
main-c255727-gc98a764c681f      (say amd64)
main-c255728-g187e9abe180d      (say amd64)
main-c255728-g187e9abe180d      (say powerpc64)
main-c255740-g085d41abe5f1      (say amd64)
main-c255740-g085d41abe5f1      (say powerpc64)
main-c255760-g79302a6304b1      (say amd64)
main-c255760-g79302a6304b1      (say powerpc64)
stable-13-c255728-g42022ab2ee2f (say powerpc64)
stable-13-c255728-g42022ab2ee2f (say amd64)
stable-13-c255759-g085d41abe5f1 (say amd64)
stable-13-c255759-g085d41abe5f1 (say powerpc64)

would mean that sorting on "Build description" in the
web page would do that. Having the following would not
(variant of invented examples above):

c255727-gc98a764c681f (so: main) (I'll not show amd64 vs. powerpc64 here)
c255727-gc98a764c681f (so: main)
c255728-g187e9abe180d (so: main)
c255728-g187e9abe180d (so: main)
c255728-g42022ab2ee2f (so: stable-13)
c255728-g42022ab2ee2f (so: stable-13)
c255740-g085d41abe5f1 (so: main)
c255740-g085d41abe5f1 (so: main)
c255759-g085d41abe5f1 (so: stable-13)
c255759-g085d41abe5f1 (so: stable-13)
c255760-g79302a6304b1 (so: main)
c255760-g79302a6304b1 (so: main)

Eventually 3 would be interlaced: stable-13, stable-14, and
main. Note that the c?????? being the same is not the
major point or case, just a limiting condition of what
I view as my needing more manual scanning/filtering effort
when reviewing the list for my purposes. It is just not
an order that I find easy to use for much.

Sorting based on "Name" would not keep the c?????? figures
grouped at all.

"S", "W", "Last Success", "Last Failure", and "Last Duration"
on the https://ci.freebsd.org/ page just do not fit the
specific type of grouping at all. (They are useful for other
activities.)

https://ci.freebsd.org/tinderbox/ does not sort/group by
c?????? in a branch. So I historically found it harder to
use for the specific purpose, compared to
https://ci.freebsd.org/ sorted in Build description order.

===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)



More information about the freebsd-git mailing list