Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I think you have the answer to your question within your own question, but let me make it a bit more explicit. You said: The problem is, sometimes downloading from Perforce fails If P4 fails ...
Answer
#1: Initial revision
by
ghost-in-the-zsh
·
2020-11-23T23:45:48Z (over 3 years ago)
I think you have the answer to your question within your own question, but let me make it a bit more explicit. You said: > The problem is, sometimes downloading from Perforce fails If P4 fails to download the file, then it follows that the task will fail to delete the (non-existent) file(s). What you need to check is *why* P4 is failing to download the file(s). You'll need to check the tasks logs. > How can I even start investigating this? You should start with the **Console Output** menu link within the task itself, shown below:  You should be able to find out more, depending on how you've configured your jobs, plugins, and/or scripts being used by them. Regarding scripts, printing to STDOUT will make those messages show up in the Jenkins job logs. To find the log for a particular job, you have to go into the job. You'll see a list of tasks that have already run, or are currently running, enumerated by job IDs as shown below:  Click on the relevant one task record, and find the console output link shown earlier. Unfortunately, the next steps in your investigation will depend on what you find there, if anything. If you don't find anything, start looking at plugin/task configuration options and tweak them to see how you can get more info. There's really not much more that I can say here, given your description.