This is happening randomly on about 10% of my builds running the last few
versions of Jenkins I have run - I am currently up to 1.656. Jenkins runs on a
Debian VM with windows 7/10 nodes. I have 10 builds that are all similar, but
not identical and the issue is random among them. It happens
We use Jenkins to run builds on Linux, transfer the resulting 'artifacts'
(firmware build files) to Windows nodes, then use Robot Framework (RF) and
ultimately our own DLL to transfer firmware files to our proprietary
hardware. Once installed, RF continues to send commands and gather results
A Bugzilla section shows up on the Configure page (http://your
install/configure). It allows three settings:
Bug ID Regex - I have not found this to work completely to include things
like Bug I can only get it to put hyperlinks on numbers. I
use \b#?[0-9]{3}\b because, for now, all of
I agree that .11 is a huge step backwards for me. As far as I can tell,
the build flow plugin no longer triggers the failure event of the email-ext
plugin. So I am no longer getting failure mails for the overall job.
Setting up a new job to handle the failure mail is redundant and can fail
.
The way it is set up is basically an ignore() with another build job
listed below it.
On Thursday, March 6, 2014 9:40:43 AM UTC-7, Tim Jackson wrote:
Given this flow:
def Build = { SpecificBuildSelectorbuildNumber + it +
/buildNumber/SpecificBuildSelector }
def BVT2Rescue = {
build
Given this flow:
def Build = { SpecificBuildSelectorbuildNumber + it +
/buildNumber/SpecificBuildSelector }
def BVT2Rescue = {
build(Restart_NRobotRemote, Test_Automation_Workstation:
BVT2.build.properties['builtOnStr'], WORKSPACE: BVT2.build.workspace)
build(BVT_CR2600, BN2:
