[JIRA] [p4] (JENKINS-24599) Parameters are not resolved in stream

[morne.joubert@u-blox.com (JIRA)]

Morne Joubert created JENKINS-24599 Parameters are not resolved in stream Issue Type: Bug Assignee: Unassigned Components: p4 Created: 05/Sep/14 1:36 PM Description: I pass the stream in as a parameter: perforceStream If i use ${perforceStream} then i get the following: ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Error detected at line 18. Stream '${perforceStream}' must begin with '//'. Project: Jenkins Priority: Major Reporter: Morne Joubert

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira

[daniel@beckweb.net (JIRA)]

Daniel Beck updated JENKINS-24599

Parameters are not resolved in stream

Asking for a new feature. Any field is by default not replacing variables like this. Change By: Daniel Beck (05/Sep/14 8:39 PM) Issue Type: Bug New Feature

[mrose@sjm.com (JIRA)]

Michael Rose commented on JENKINS-24599

Parameters are not resolved in stream

Is this really a new feature? Token substitution works fine for the manual client setup option (excluding matrix projects).

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-24599

Parameters are not resolved in stream

A quick workaround would be '//${streamDepot}/${codeline}' or '//${streamPath} The '//' is a sanity check; to use a ${var} param I would need to test the expanded var. However, depending on how you set the ${var} it may not be valid on the page check.

[daniel@beckweb.net (JIRA)]

Daniel Beck updated JENKINS-24599

Parameters are not resolved in stream

Michael Rose: My apologies; I'm just doing basic checks on incoming issues and don't know all the plugins – it read like a feature request given the error message, and many users have a habit to report minor feature requests/improvements as critical bugs Change By: Daniel Beck (06/Oct/14 4:30 PM) Issue Type: New Feature Bug

[mrose@sjm.com (JIRA)]

Michael Rose commented on JENKINS-24599

Parameters are not resolved in stream

No problem Daniel Beck and full disclosure I filed a couple ticket last week that ended up not being "defects" or "features" (if you get my drift). Paul Allen: The workaround looks fine to me. Are $streamDepot, $codeline, $streamPath example variables or real keywords? And if they are real keywords are there any others (e.g. $clientName)?

[pallen@perforce.com (JIRA)]

Paul Allen commented on JENKINS-24599

Parameters are not resolved in stream

No, they were just example variables. The only 'special' variables are: ${label}, ${change}, ${status}, ${pass}, ${fail}. They are reserved for the Review/Shelve feature (avoid using them as 'axis' names in a multi config project).

[pallen@perforce.com (JIRA)]

Paul Allen resolved JENKINS-24599 as Won't Fix

Parameters are not resolved in stream

As outlined the sanity check can't necessarily expand the ${var}. The alternative would be to remove the check altogether. If common use changes from explicit paths to expanded vars then I may change the sanity check. Change By: Paul Allen (13/Oct/14 9:55 AM) Status: Open Resolved Resolution: Won't Fix

[mrose@sjm.com (JIRA)]

Michael Rose commented on JENKINS-24599

Parameters are not resolved in stream

I just tried using the '//${streamDepot}/${codeline}' workaround and the build errored out. The error was 12:50:09 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Stream '//${P4DEPOT}/${P4ROJ}' doesn't exist. 12:50:09 12:50:09 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Stream '//${P4DEPOT}/${P4ROJ}' doesn't exist.

[mrose@sjm.com (JIRA)]

Michael Rose edited a comment on JENKINS-24599

Parameters are not resolved in stream

I just tried using the '//${streamDepot}/${codeline}' workaround and the build errored out. The error was 12:50:09 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Stream '//${P4DEPOT}/${P4CODELINE}' doesn't exist. 12:50:09 12:50:09 ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Stream '//${P4DEPOT}/${P4CODELINE}' doesn't exist. I define P4DEPOT and P4CODELINE using dynamic (but readonly) parameters.