Problem: unpacked m0reportbug artifacts are inconvenient #1551

Closed vvv closed 5 years ago

Unpacked m0reportbug archives cannot be easily attached to Jira tickets. Also navigating them using GitLab UI is a real pain: too many clicks are required to reach any file of interest.

Solution: pass m0reportbug archives to the artifacts unpacked.

Add st-single_ prefix to m0reportbug archive files.

merged

enabled an automatic merge when the pipeline for fbe2dc9bf60c7f0f1043e503e1884d17cd16cb06 succeeds

unmarked as a Work In Progress

resolved all discussions

added 7 commits

b3b5b45b - Problem: unpacked m0reportbug artifacts are inconvenient
ecbab557 - Problem: error during GitLab CI artifact generation
a66c58f5 - .gitlab-ci.yml: simplify m0trace.* collection
c73fc78b - .gitlab-ci.yml: s/PREFIX/JOB_NAME/ to be more specific
fbe2dc9b - .gitlab-ci.yml: use a variable for artifact's file name prefix
f9f67b1e - XXX-DELETEME Checking if $PREFIX is set in `artifacts:`
e530df8c - XXX DELETEME: trigger CI failure

Compare with previous version

Right, . is invalid in host names.

centos75_ part comes from m0vg. That will be needed when we have several target platforms.

st-single_halond.m0trace.txt.xz is a long sequence of characters and it is used 3 times. I wanted to put it into a variable. Which would have to be used inside M0VG command and locally. That is why I needed variable expansion within the here document (<<EOF, not <<'EOF').

Where does centos75_ part come from?

As for the dash before {s,ut,m}, I used dot symbol initially, but it would give hostnames like halon6697.s_centos75_cmu.local — those would be invalid AFAIU.

added 2 commits

dcc51c01 - .gitlab-ci.yml: use a variable for artifact's file name prefix
dc4bc62f - XXX DELETEME: trigger CI failure

Compare with previous version

This yields in VM names like this:

root@qb06n4-m02:/etc# virsh list
 Id    Name                           State
----------------------------------------------------
 1610  halon6697-s_centos75_cmu       running
 1611  halon6697-ut_centos75_cmu      running
 1612  halon6697-m_centos75_cmu       running
 1613  halon6697-m_centos75_ssu1      running
 1614  halon6697-m_centos75_ssu2      running
 1615  halon6697-m_centos75_client1   running

if you're OK with it, I'm OK too.

the old naming was like this halon6697s_centos75_cmu

Do you think \$ are more explicit and conventional and using <<'EOF' would be too subtle for people to notice it?

added 4 commits

af690ee0 - .gitlab-ci.yml: simplify m0trace.* collection
4c0cf5ad - .gitlab-ci.yml: s/PREFIX/JOB_NAME/ to be more specific
3ab56a88 - .gitlab-ci.yml: use a variable for artifact's file name prefix
065b8d28 - XXX DELETEME: trigger CI failure

Compare with previous version

added 5 commits

7a08583c...3f2bacc4 - 2 commits from branch master
c184abdf - Problem: unpacked m0reportbug artifacts are inconvenient
a9ac7857 - Problem: error during GitLab CI artifact generation
47391844 - XXX DELETEME: trigger CI failure

Compare with previous version

OK, I've succeeded in breaking artifacts collection code. :boom:

added 2 commits

2dae86da - Problem: error during GitLab CI artifact generation
7a08583c - XXX DELETEME: trigger CI failure

Compare with previous version

changed the description

marked as a Work In Progress

Seagate / halon

Problem: unpacked m0reportbug artifacts are inconvenient #1551