December 2015
Intermediate to advanced
152 pages
3h 16m
English
Content preview from Extending JenkinsBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
Start your free trial
Use case scenario 3 – helping your users through UI automation
Customizing and automating the Jenkins user interface can help and empower users of your Jenkins instance to help themselves.
By ensuring that it is possible only for your users to input valid data, we can greatly reduce the risk of invalid input and the resulting issues, which should improve the user experience too.
The most common way to do this is to validate the user input at runtime. For example, if your job prompts the user to enter a day of the week or a build number, you may assign this to a variable called something like $WEEKDAY or $MY_BUILD_NUM respectively.
We can then set up our job to ensure that the supplied user data is valid—if the value of $WEEKDAY is not a valid day ...