Skip to content
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

Add informative pipeline step labels #43

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

gilles-peskine-arm
Copy link
Contributor

@gilles-peskine-arm gilles-peskine-arm commented Apr 21, 2022

Put informative labels on shell steps like ./steps.sh. This makes it easier to locate interesting pipeline steps in the pipeline view.

I also removed some obsolete code that I happened to notice. These removals are unrelated, except inasmuch they meant there were fewer sh steps to consider for labeling.

Test jobs on 7e63a91:

Status: so far the jobs are running fine, but:

WARNING: Unknown parameter(s) found for class type 'org.jenkinsci.plugins.workflow.steps.durable_task.ShellStep': label

The label parameter is listed in the documentation but apparently our version of the relevant plugin is too old (Pipeline: Nodes and Processes < 2.28). Back to the drawing board.

@gilles-peskine-arm gilles-peskine-arm added enhancement New feature or request needs: ci labels Apr 21, 2022
@gilles-peskine-arm gilles-peskine-arm added size-s Estimated task size: small (~2d) needs: work labels Apr 21, 2022
gen_docker_jobs_foreach and gen_node_jobs_foreach were last used for
mbed-crypto only. They became unused when we removed code that was
specific to mbed-crypto, but we didn't notice at the time.

Signed-off-by: Gilles Peskine <[email protected]>
all.sh has supported --list-components since 2.17.0 and 2.16.10. We
don't need a fancy message for antique branches anymore: the exception
from the all.sh call returning a nonzero status will do.

Signed-off-by: Gilles Peskine <[email protected]>
Many sh or bat pipeline steps have an uninformative label. Groovy uses
the script as a label by default, but this is uninformative when the
script is something like "./steps.sh", and it's unreadable or
truncated when the script is very long. In such cases, use an
informative label, containing the job name.

In particular, this makes it possible to quickly search for the
execution of a given all.sh component in the Jenkins pipeline view:
search for "steps.sh #${job_name}", e.g.
"steps.sh #all_u16-test_clang_opt".

Signed-off-by: Gilles Peskine <[email protected]>
@gilles-peskine-arm gilles-peskine-arm force-pushed the dev/gilles-peskine-arm/pipeline-labels branch from 7e63a91 to 055fabb Compare April 21, 2022 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs: ci needs: work priority-low size-s Estimated task size: small (~2d)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants