![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git-client |
|
Created:
|
09/Jul/14 1:08 PM
|
|
Description:
|
I defined a Jenkins job to checkout the boost repository and its submodules. During the checkout, the submodule init --recursive failed, but the job was marked as a success. The job should have failed because the submodule init reported an error.
Steps I took:
- Define a new Jenkins job "job-does-not-fail-on-submodule-timeout"
- Use Git as the SCM, with git://github.com/boostorg/boost.git as repo
- Add "Additional behaviours" "Advanced sub-module behaviours", and check the "Recursively update submodules" checkbox
- Build that job
It will timeout in 10 minutes because the submodule update cannot complete in 10 minutes. However, the job will be marked as "Successful", even though the submodule update failed.
Job output looked like this:
|
|
Environment:
|
Jenkins 1.554.3
Git plugin 2.2.2
Git client plugin 1.9.1
Debian Linux Testing
|
|
Project:
|
Jenkins
|
|
Priority:
|
Minor
|
|
Reporter:
|
Mark Waite
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.