[JIRA] [p4-plugin] (JENKINS-31862) "Build Now" should trigger Perforce polling

[email protected] (JIRA) Mon, 18 Jan 2016 02:50:14 -0800

Title: Message Title

Paul Allen commented on

JENKINS-31862

The message "Label as change" comes from the extra logging I added to "CheckoutTask.java". As you can see in the code snippet here:

 
                                                    // if label is specified then update
String lblStr = expand.get(ReviewProp.LABEL.toString());
if (lblStr != null && !lblStr.isEmpty()) {
	try {
		// if build is a change-number passed as a label
		int change = Integer.parseInt(lblStr);
		build = new P4Revision(change);
		p4.log("... Label as change: " + build);
	} catch (NumberFormatException e) {
		if (!"now".equals(lblStr)) {
			build = new P4Revision(lblStr);
			p4.log("... Label: " + build);
		}
	}
}
 
                                                

The label can be defined by a user in the "Populate options" --> "Pin build at Perforce Label" or set automatically if the "Polling build filters" --> "Polling per Change" is enabled.

It is expose to Swarm and Jenkins as an environment variable $

{p4.label}

; this used to appear as $

{label}

, but conflicted with the default Axis name for Matrix builds.

Polling will build a global list (for that Job) of changes that need to be built. If it finds a change then this list will apply to the build now button. I think the issue might be that the list is not cleared after the polling build and the 'Poll Now' button picks up the previous change.

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4-plugin] (JENKINS-31862) "Build Now" should trigger Perforce polling

Reply via email to