On 16/12/2014 10:15, Jo Shields wrote:
Hi,
We're looking to use Jenkins w/ workflow to replace our in-house CI
system. However, there's a bunch of stuff that doesn't seem to be
present in the addin (some of it might be missing features, some might
be plugin compatibility, some might be me not seeing something in the
documentation)
if something is missing and you find a way to do it - pull requests with
updated documentation would be welcomed.
1) How can I change the title of a step in the "Running Steps" page?
"Shell Script" three dozen times is not useful. I'd like to be able to
change this header.
Its not possible as far as I am aware - and it was something I mentioned
a few months ago.
However - in my previous usage of this - it didn't really matter about
the 50 shell scripts - as they where grouped logically into several areas
(build it, test it, deploy it to clean test system, test test system,
deploy it to another test system (with live data), test it, deploy it to
live...)
So all we cared about at the top level was which part of the thing
failed (building, testing or deploying...) - and then when something
failed - it doesn't matter its called "shell script" as its failed and
you are interested in the logs!
This grouping can be acheived with the 'stage' step.
Cloudbees announced a really great visualization for this (non free) but
the basis is there in the open source version for you to write your own
visualization.
https://www.cloudbees.com/products/jenkins-enterprise/plugins/workflow-stage-view-plugin
2) How can I time out the build on inactivity? Sometimes our test
suite can get stuck - we use build-timeout to kill unresponsive processes
look at the timeout step.
I believe (not used it) that this is implemented with something like
|timeout('180s') {
sh 'thisMayHang.sh'
}
|
3) How can I add annotation to "Running Steps"? For example, that
screen would be much more useful if a test suite step could explicitly
list the failed tests right from that page, rather than needing to
click through to the logs (or use another plugin like
build-failure-analyzer)
if your test suite can output junit style reports (or cucumber/gherkin
maybe coming soon) then you just need to call the plugin to parse these
and they will be displayed in the main page as a trend etc just like
with normal jobs.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54900E6C.3020805%40teilo.net.
For more options, visit https://groups.google.com/d/optout.
