Views: Displaying Job Parameters

0 views
Skip to first unread message

Jan-Benedict Glaw

unread,
Jan 29, 2026, 5:36:31 AM (8 days ago) Jan 29
to jenkins-j...@googlegroups.com
Hi!

I'm doing good progress describing my jobs (almost all are actually
templates) in JJB, however I found an oddity with displaying job
parameters in a view.

As I'm buiding jobs to test (among others) the GNU Toolchain,
I came up with this for building GNU AS (gas, part of GNU Binutils):

---------------------------------------------------------------
- job-template:
name: gas-{target}
description: GAS for {target}
concurrent: true
publishers:
- archive:
artifacts: 'artidir/**'
allow-empty: true
fingerprint: true
default-excludes: false
- workspace-cleanup
wrappers:
- workspace-cleanup
parameters:
- string:
name: rev
default: master
description: "GIT revision to build"
- string:
name: compiler_suite
default: "gcc-snapshot"
description: "One of gcc-system, gcc-snapshot, clang-<v> or local"
- string:
name: local_binutils_rev
default: ""
description: "For local Binutils: Which one?"
- string:
name: local_gas_rev
default: ""
description: "For local GAS: Which one?"
- string:
name: local_gdb_rev
default: ""
description: "For local GDB: Which one?"
- string:
name: local_gcc_rev
default: ""
description: "For local GCC: Which one?"
builders:
- shell:
!include-raw-verbatim: __init.sh
- shell:
!include-raw-expand: gas.sh

- project:
name: gas
target:
!include: gas_target.inc
jobs:
- gas-{target}
---------------------------------------------------------------

`gas_target.inc` contains a list of targets I want `gas` to be build for, eg.
- 'aarch64-elf'
- 'aarch64-linux'
- 'alpha-dec-vms'
- 'alpha-linux'
- 'alpha-linux-gnu'

`__init.sh` prepares some build helper scripts, and
`gas.sh` does the actual building (within a Docker container.)

I want to be able to build all the software using different
compilers (those available on the system, eg. plain `gcc`, as well as
that from Debian's `gcc-snapshot` package, clang and a local-built
HEAD gcc, or specific older GCC/GAS/Binutils versions that can be
requested by parameters.)

The views are all similar:
---------------------------------------------------------------
- view:
name: GAS
view-type: list
description: GNU Assembler
regex: '^gas-.*'
columns:
- status
- weather
- job
- last-success
- last-failure
- last-duration
- build-button
- extra-build-parameter: rev

---------------------------------------------------------------


It would be nice to see that GIT revision was requested (usually
that's `master`, `main` or `trunk`, but it can be a specific GIT
revision to allow for bisecting.) With the above View snippet, I
expected to see exactly the `rev` content, but Jenkins actually
displays all parameters. Is that expected? Or do I use it wrongly?

Thanks,
Jan-Benedict

--
signature.asc
Reply all
Reply to author
Forward
0 new messages