There were several questions for information. I'll try to bring some structure in them, and then answer them one by one.
- What does the build folder for the build look like?
- Does the log file exist?
- Are there any other errors in the Jenkins logs that seem relevant?
- Do you know if the build that was broken was building when Jenkins was restarted for the plugin update, or had it already completed?
- For builds before the upgrade, the full build log should work ok (some markup will not be displayed correctly), but the step logs are expected to be broken. Is that what you are seeing?
- I am not quite sure what you mean by "full build step logs".
- Do we have a reproducible bug?
- marco_andries are you still seeing this issue?
- Can you answer the questions in my earlier comment?
- Can you attach the Pipeline script that is failing so we can see what it is doing?
Question 1
I am unsure what kind of answer you want:
- a screenshot of the build folder?
- a directory listing of the build folder?
- a tarball of the build folder?
I don't have ssh access to the server that runs Jenkins, and I don't know what you want, so I will take a brute force approach. Difficult also works. I am going to make a job that runs ls -ld $(find /var/lib/jenkins). Please let me know what exactly you need, because I guess that the directory listing may also contain confidential information.
Question 2
How can I find out if the log file exists?
Question 3
Which Jenkins logs exactly? I'd be happy to provide you the information if I know where to look.
Question 4
This is an ambiguous question, the literal answer would be "I know", but that would not be helpful. I will instead answer with steps to reproduce:
- Pipeline Job Plugin is at version 1.28.
- Start a failing job, job 1, and let it finish.
- Look at the console output of job 1 -> there is console output for job 1.
- Upgrade Pipeline Job Plugin to > 1.28.
- Restart Jenkins.
- Look at console output of job 1 -> there is console output for job 1.
- Start a failing job, job 2, and let it finish.
- Look at the console output of job 2 -> the console output for job 2 is empty.
- Downgrade Pipeline Job Plugin to 1.28.
- Restart Jenkins.
- Look at the console output of job 1 -> there is console output for job 1.
- Look at the console output of job 2 -> the console output for job 2 is empty.
- Start a failing job, job 3, and let it finish.
- Look at the console output of job 3 -> there is console output for job 3.
Question 5
For builds from before the update, there is indeed a console log, as described in my answer to question 4.
I do not know about markup, is that important or relevant, and if so, how can I verify this?
The step logs are expected to be broken.
-> I don't understand what this means, could you please explain?
Question 6
Is this a question for marco_andries or for beyerj?
Question 7
Is this a question for marco_andries or for beyerj/dnusbaum?
Question 8
Yes, we are still seeing this issue.
Question 9
I am collaborating with marco_andries in providing you the answers.
Question 10
test-pipeline-Jenkinsfile
There were several questions for information. I'll try to bring some structure in them, and then answer them one by one.
Question 1
I am unsure what kind of answer you want:
I don't have ssh access to the server that runs Jenkins, and I don't know what you want, so I will take a brute force approach. Difficult also works. I am going to make a job that runs ls -ld $(find /var/lib/jenkins). Please let me know what exactly you need, because I guess that the directory listing may also contain confidential information.
Question 2
How can I find out if the log file exists?
Question 3
Which Jenkins logs exactly? I'd be happy to provide you the information if I know where to look.
Question 4
This is an ambiguous question, the literal answer would be "I know", but that would not be helpful. I will instead answer with steps to reproduce:
Question 5
For builds from before the update, there is indeed a console log, as described in my answer to question 4.
I do not know about markup, is that important or relevant, and if so, how can I verify this?
-> I don't understand what this means, could you please explain?
Question 6
Is this a question for marco_andries or for beyerj?
Question 7
Is this a question for marco_andries or for beyerj/dnusbaum?
Question 8
Yes, we are still seeing this issue.
Question 9
I am collaborating with marco_andries in providing you the answers.
Question 10
test-pipeline-Jenkinsfile