-
Task
-
Resolution: Unresolved
-
Major
-
None
-
Perforce plugin 1.3.35 (current latest for July 30 2015)
Jenkins 1.580.3
I'm running into these issues: JENKINS-6257 JENKINS-15698
I'm using dynamic workers allocation in our private openstack cluster through Openstack Cloud plugin 1.8.
I see Perforce Plugin cannot resolve host names of those new workers. I suspect it fails with NPE or something because it cannot checkout files to the new worker.
I have to delete the old workspace (leftover from another worker) and restart the build. this time it will work.
but if next build happens on a yet another new worker, I have to repeat this: delete the workspace and re-run the build.
so.. why not use IP address if hostname cannot be resolved? or just always use IP address for perforce workspaces. maybe transform it to something Perforce-friendly like 192-168-1-123.
this bug blocks us from using dynamic openstack workers with Perforce plugin
- is related to
-
JENKINS-15698 Perforce can't get hostname for slaves
-
- Open
-
-
-
- Closed
-
[JENKINS-29734] use IP address when cannot resolve hostname for slaves
Alex Java
created issue -
Alex Java
made changes -
| Link |
New:
This issue is related to |
Alex Java
made changes -
| Link | New: This issue is related to JENKINS-15698 [ JENKINS-15698 ] |
Alex Java
made changes -
| Environment |
New:
Perforce plugin 1.3.35 (current latest for July 30 2015) Jenkins 1.580.3 |
|
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
| Assignee | Original: Rob Petti [ rpetti ] |
| Workflow | Original: JNJira [ 164717 ] | New: JNJira + In-Review [ 181695 ] |
Jenkins IRC Bot
made changes -
| Component/s | New: p4-plugin [ 19224 ] | |
| Component/s | Original: perforce-plugin [ 15506 ] |