[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-10-02 Thread pal...@perforce.com (JIRA) 















































Paul Allen
 resolved  JENKINS-24028 as Fixed


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















Fixed in 1.0.15





Change By:


Paul Allen
(02/Oct/14 3:22 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-10-01 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Code changed in jenkins
User: Paul Allen
Path:
 src/main/java/org/jenkinsci/plugins/p4/workspace/ManualWorkspaceImpl.java
http://jenkins-ci.org/commit/p4-plugin/7536bbf2a32196961baed589f302cd13a122d02b
Log:
  Fixed name in client map for Manual workspaces.

The client name in the RHS of the depot view was not matching the
correct name.  The name was expanded, but not replaced with the '/' and
'=' chars.

Fixes JENKINS-24028





























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-09-08 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Hi ~pallen, have you had a chance to look more into this?



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-09-08 Thread mr...@sjm.com (JIRA) 












































 
Michael Rose
 edited a comment on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















Hi Paul Allen, have you had a chance to look more into this?



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-27 Thread pal...@perforce.com (JIRA) 














































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Thanks for the details.  Kind of odd why the root is null and the view is missing; I'll look into it.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-27 Thread pal...@perforce.com (JIRA) 














































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Thinking about this; Manual mode was the only one I intended to use for variable expansion ${foo} in the View.  However, Template and Streams were the modes I had thought would be used for slave/matrix builds.

As you can see the View is expanded for the Parent as I would expect, but the workspace is assumed to have already been created for the children and so the fields are blank.

I could enhance the plugin to either:

 1. Support view expansion for template workspaces (not possible for streams as the View is managed by the server).

or 

 2. For manual builds, auto create workspaces for the children at build time.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-27 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Either way works for me. If that's not the way you intended for the Manual setup to be used, then there might be more gotcha waiting in option 2; so I'm kind of leaning towards option 1.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-27 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















On the other hand, it is a bit strange that the most flexible setup option is unavailable for one of the base job types. That probably should be fixed, or at least alert the user not to use it when creating a multi-configuration project.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread pal...@perforce.com (JIRA) 














































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















It may be a long shot, but is one of your axis names using a reserved name e.g. 'label'?

(I updated the docs; 'label', 'change', 'status', 'review', 'pass', and 'fail')  Using any of these as axis names will have a strange effect.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Whoops! I didn't realize that label was the default name for the node axis. That solved the problem for the error in my second comment, but the first error still persists.


ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/arch=linux,bar=222,foo=yyy/...' is not under '//JenkinsJob_test-new-p4plugin-arch-linux-bar-222-foo-yyy/...'.

It looks like you don't replace you don't replace special characters in the view. Is there another way that I should be configuring my view that does not involve using the workspace name? The old plugin allowed for a special token to be used in that spot and they just replaced it later.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread pal...@perforce.com (JIRA) 














































Paul Allen
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Are you using a the Manual workspace configuration (or Spec/Static/Stream/Template)?

Please can you send me the workspace view in Jenkins (if using the Manual mode)...
...and the client's view in Perforce. `p4 client -o client_name`

and let me know which view is which.



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-26 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 updated  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















I am using the Manual workspace configuration:


Client view for parent:


Client: JenkinsJob_test-new-p4plugin

Update: 2014/08/22 14:57:04

Access: 2014/08/26 12:22:02

Owner:  integ

Root:   /usr/local/jenkins/jobs/test-new-p4plugin/workspace

Options:noallwrite clobber nocompress unlocked nomodtime normdir

SubmitOptions:  submitunchanged

LineEnd:local

View:
//test_mrose/... //JenkinsJob_test-new-p4plugin/...


Client view for one of the configurations:

Client: JenkinsJob_test-new-p4plugin-arch-linux-bar-111-foo-xxx

Update: 2014/08/26 10:25:33

Access: 2014/08/26 10:25:33

Root:   null

Options:noallwrite noclobber nocompress unlocked nomodtime normdir

SubmitOptions:  submitunchanged

LineEnd:local





Change By:


Michael Rose
(26/Aug/14 5:33 PM)




Attachment:


p4plugin_configurations_issue24028.jpg



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-22 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 reopened  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















I just tried to executed a matrix build with a mixture of user defined axis and node label axis. The parent build properly sync'd and triggered the configuration builds, but all of the configuration build failed in the following way:


Started by upstream project "test-new-p4plugin" build number 12
originally caused by:
 Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on b261806 (linux x86_64-Linux-2.618) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/222/foo/xxx/label/linux
ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/bar=222,foo=xxx,label=linux/...' is not under '//JenkinsJob_test-new-p4plugin-bar-222-foo-xxx-label-linux/...'.

ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/bar=222,foo=xxx,label=linux/...' is not under '//JenkinsJob_test-new-p4plugin-bar-222-foo-xxx-label-linux/...'.

Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

I am using the Manual (custom view) with workspace name set to JenkinsJob_${JOB_NAME} and view set to //test_mrose/... //JenkinsJob_${JOB_NAME}/... 

P4 plugin version: 1.0.12
Jenkins version: 1.575





Change By:


Michael Rose
(22/Aug/14 8:07 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-22 Thread mr...@sjm.com (JIRA) 














































Michael Rose
 commented on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Here is another strange issue. The parent sync'd successfully, but the other configurations did this:


Started by upstream project "test-new-p4plugin" build number 13
originally caused by:
 Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on nile (linux) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/111/foo/xxx/label/linux
Connected to server: perforce2.csdt.sjm.com:1777
Connected to client: JenkinsJob_myspace
SCM Task: cleanup workspace: JenkinsJob_myspace
SCM Task: reverting all pending and shelved revisions.
... list = revert
... rm list | ABANDONED
SCM Task: removing all non-versioned files.
... list = reconcile -n -a
... rm list
SCM Task: restoring all missing and changed revisions.
... list = reconcile -n -ed
... sync -f list
P4: Unable to find label: linux
ERROR: Unable to update workspace: hudson.AbortException: P4: Unable to find label: linux
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

This time I used a static workspace name, but updated the matrix configuration to build sequentially so there wouldn't be any client clobbering.
Client Name: JenkinsJob_myspace
Client View: //test_mrose/... //JenkinsJob_myspace/...



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-08-22 Thread mr...@sjm.com (JIRA) 












































 
Michael Rose
 edited a comment on  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















Here is another strange issue. The parent sync'd successfully, but the other configurations did this:


Started by upstream project "test-new-p4plugin" build number 13
originally caused by:
 Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on nile (linux) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/111/foo/xxx/label/linux
Connected to server: perforce2.csdt.sjm.com:1777
Connected to client: JenkinsJob_myspace
SCM Task: cleanup workspace: JenkinsJob_myspace
SCM Task: reverting all pending and shelved revisions.
... list = revert
... rm list | ABANDONED
SCM Task: removing all non-versioned files.
... list = reconcile -n -a
... rm list
SCM Task: restoring all missing and changed revisions.
... list = reconcile -n -ed
... sync -f list
P4: Unable to find label: linux
ERROR: Unable to update workspace: hudson.AbortException: P4: Unable to find label: linux
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE

This time I used a static workspace name, but updated the matrix configuration to build sequentially so there wouldn't be any client clobbering.
Client Name: JenkinsJob_myspace
Client View: //test_mrose/... //JenkinsJob_myspace/...

The same issue occurs when using streams.
Character Set: none
Stream Codeline: //test_streams/main
Workspace Name Format: jenkins-${NODE_NAME}-${JOB_NAME}



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-07-30 Thread pal...@perforce.com (JIRA) 















































Paul Allen
 closed  JENKINS-24028 as Fixed


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
















Release 1.0.8

Replace "/" "=" and "," with "-" as per old plugin





Change By:


Paul Allen
(30/Jul/14 4:40 PM)




Status:


Open
Closed





Resolution:


Fixed



























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs

2014-07-29 Thread glimb...@gmail.com (JIRA) 














































Grant Limberg
 created  JENKINS-24028


using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs















Issue Type:


Bug



Affects Versions:


current



Assignee:


Paul Allen



Components:


p4



Created:


30/Jul/14 12:23 AM



Description:


When used in a Matrix job, ${JOB_NAME} has a '/' character in it, which is illegal for a workspace name in Perforce.  This should be stripped or replaced.




Environment:


P4 plugin: 1.0.7

Jenkins: 1.574




Project:


Jenkins



Priority:


Major



Reporter:


Grant Limberg

























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







-- 
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.