Build reproducibility Jenkins tests: confusing UX and implementation
Currently we always trigger a build of this job once we’ve built an ISO,
and then this job decides whether it has been triggered for a good
reason, writes this down using a flag file, and then N build steps each
test whether they should do something or not (<=> whether the flag
file exists), and if not, the build is marked as succeeded even when it
has actually not tested anything. We should decide once for all whether
a reproducibly_build_Tails_ISO downstream job shall be run for a
given ISO.
It seems the conditional-buildstep plugin would be a “nicer solution” to
use this plugin to determine if the job needs to reproduce an ISO or
not, rather than the “ugly workaround” implemented first by using steps.
For that to work, we need to have a newer version of Jenkins, given the
dependencies of this plugin.
But it might not be the best option, especially wrt. reporting to developers/reviewers, see below.
Related issues
- Related to #12633 (closed)
- Related to #16959
Original created by @bertagaz on 14875 (Redmine)