Hi,
I tried and I am not able to recreate this error.
Currently it looks like this could be an issue because stream name given doesnot exist in the workspace.
Can you share your jenkins pipeline logs, from jobs folder please share config.xml and build.xml so that we can understand your problem better?

What stream name are you using. What's the output of the "p4 streams "given stream name""?

Note: I have tried in windows 11 x64 with p4 plugin 1.17.0 and jenkins 2.479.2.

If stream is selected as workspace behavior, it cannot be empty.

Workspace behavior is "Manual (custom view)", Stream and Stream at change both are empty.

In manual (custom view) either stream or view mappings should be given.
I am pretty certain this is some configuration issue.

Can you share your jenkins pipeline logs, from jobs folder please share config.xml and build.xml so that we can understand your problem better?

Hi, I'm seeing the same issue with 1.17.0 version. In my case it's a scripted pipeline and also a custom view. The checkout step looks something like this:

String mapping(String workspace, String branch, String arch, String type) {
  final String depotPath = "//depot/${type}";
  final String workSpacePath = "//${workspace}/depot/${type}";

  String mapping = """
    ${depotPath}/${branch}/... ${workSpacePath}/${branch}/...
    //depot/prod/MAIN/unittests/services/testrunner/... //${workspace}/depot/prod/MAIN/unittests/services/testrunner/...
    //depot/prod/MAIN/unittests/services/automation/... //${workspace}/depot/prod/MAIN/unittests/services/automation/...
    //depot/tests/services/MAIN/automation/tools/linux/... //${workspace}/depot/tests/services/MAIN/automation/tools/linux/...
    //depot/tests/services/MAIN/automation/tools/common/... //${workspace}/depot/tests/services/MAIN/automation/tools/common/...
    //depot/tests/services/MAIN/automation/playbooks/... //${workspace}/playbooks/...
    //depot/tests/services/MAIN/media/... //${workspace}/depot/tests/services/MAIN/media/...
  """.stripIndent();

  return mapping;
}

...

checkout perforce(
  credential: '[creds]',
  populate: autoClean(
    delete: true, modtime: false, pin: change, quiet: true, replace: true,
    tidy: false, parallel: [
      enable: true, minbytes: '1024', minfiles: '1', threads: '4'
    ]
  ),
  workspace: manualSpec(
    name: workspace,
    charset: 'none', pinHost: false, spec: clientSpec(
      allwrite: false, backup: true, changeView: '', clobber: true,
      compress: true, line: 'LOCAL', locked: false, modtime: false,
      rmdir: true, serverID: '', streamName: '', type: 'WRITABLE',
      view: mapping(workspace, branch, mapping, type)
    )
  )
)

I'm happy to provide additional information if needed.

jwierzbi andreas_rueger could you please provide the log that contains the stack trace for the following exception?
ERROR: P4: Task Exception: java.lang.RuntimeException: P4JAVA: Error in finding type of stream.java.lang.IndexOutOfBoundsException: 
stream.java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0

Also share the following:

output of: "p4 streams" command

config.xml and build.xml from jobs folder.

Hi,

thank you for looking into this. I completely forgot to say that before. Enclosed please find the complete folder of a job named "Hello World" including two builds. Build 1 was successful with P4 plugin 1.16.0 and build 2 with P4 plugin version 1.17.0 ended with failure. I have anonymized the data. The output of the "p4 streams" command on the jenkins server is: No such stream.

Best regards
Andreas

could you please provide the log that contains the stack trace for the following exception?

There's not much of a stack trace. The only thing I can see is:

14:15:33  ERROR: P4: Task Exception: java.lang.RuntimeException: P4JAVA: Error in finding type of stream.java.lang.IndexOutOfBoundsException: Index 0 out of bounds for length 0
14:15:33  ERROR: Maximum checkout retry attempts reached, aborting 

Log attached (albeit redacted):.p4_1.17.0_pipeline_failure.log.

p4 streams returns (same as in andreas_rueger 's case):

No such stream. 

We don't use streams at all (as far as I know).

I'll attach the build.xml and config.xml a bit later if still necessary. Need to anonymise them beforehand.

Thanks andreas_rueger  and jwierzbi . Based on the comments below we have been able to recreate the issue. We will fix it in next release, 1.17.1.

Workaround till fix is provided: Please create a any stream. Its fine if its empty as well. Then build pipeline will execute. This issue is happening as jenkins is not able to find any stream when running p4 stream command.

Thank you for the update, Dhaval.