| ... | ... | @@ -42,8 +42,19 @@ Failed jobs can be retried if you think the failure was not bound to your commit |
|
|
|
|
|
|
|
## Q: What can I find in the job artifacts?
|
|
|
|
|
|
|
|
Most of the jobs will produce artifacts. They are often log files, but some of them have more value for the developer:
|
|
|
|
|
|
|
|
Most of the jobs will produce artifacts. They are often log files, but some of them
|
|
|
|
have more value for the developer:
|
|
|
|
|
|
|
|
* all the `*-prepare` jobs produce a text file `sb_branch.txt` that identifies the
|
|
|
|
XDK to be used (it is actually a branch name in the `superbuild-artifact` repository).
|
|
|
|
* the job `centos-xdk-build` produces a standalone binary `OTB-*.run` for Linux 64
|
|
|
|
* the job `ubuntu-xdk-build-doc` produces a standalone binary `OTB-*.run` for Linux 64, plus
|
|
|
|
CookBook and Doxygen documentation
|
|
|
|
* the job `macos-xdk-build` produces a standalone binary `OTB-*.run` for macOS
|
|
|
|
* the job `windows-10-build` produces a standalone binary `OTB-*.zip` for Windows 10 64bit
|
|
|
|
* the job `windows-8-build` produces a standalone binary `OTB-*.zip` for Windows 8.1 32bit
|
|
|
|
|
|
|
|
Note: the artifacts are kept only 24h on the Gitlab server
|
|
|
|
|
|
|
|
## Q: Why some features are disabled when I push from my OTB fork?
|
|
|
|
|
| ... | ... | |
