Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • otb otb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 207
    • Issues 207
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Main Repositories
  • otbotb
  • Wiki
  • OTB Continuous Integration platform

OTB Continuous Integration platform · Changes

Page history
Update OTB Continuous Integration platform authored Jul 01, 2019 by Guillaume Pasero's avatar Guillaume Pasero
Hide whitespace changes
Inline Side-by-side
OTB-Continuous-Integration-platform.md
View page @ ed7e3b0d
## General description
The role of the Continuous Integration platform is to validate the different
commits pushed to OTB repository. When commits are pushed, either on the main
repository or on a fork, the platform triggers a pipeline with several jobs to
......@@ -34,7 +36,28 @@ When a pipeline ends, there are two cases:
Failed jobs can be retried if you think the failure was not bound to your commit.
What about baseline files? They are now stored in the main OTB repository, under
## Q: What about baseline files?
They are now stored in the main OTB repository, under
`Data` folder. You can update them with a plain commit on your feature branch.
Note that the data files are tracked with [Git LFS](https://git-lfs.github.com/)
, so you need to install this extension.
\ No newline at end of file
, so you need to install this extension.
## Q: How do I get a test result back from CI?
You have a failing test and you want to analyse the output. Here is how you can do it:
* First step is to check information available on the CDash report (link should be available at the end of the job logs).
* If this is not enough to investigate, you can download the test output:
* Find the file name of the test output (let say `myOutput.tif`)
* Edit the file `.gitlab-ci.yml` and locate the job where your test fails
* In the job description, add this section
```
artifacts:
when: always
expire_in: 24 hrs
paths:
- build/Testing/Temporary/myOutput.tif
```
Then commit this change, and when the job completes (still failing), you can browse the artifacts and download the file you need.
\ No newline at end of file
Clone repository
  • Deprecated Info
  • Help for release actions
  • How to contribute to QGIS related to OTB processing provider
  • How to deprecate
  • List of publications mentioning OTB
  • Migration guide OTBv8
  • OTB Continuous Integration platform
  • OTB Users Day 2018
  • PSC meetings
  • Remote Modules
  • Remove OSSIM
  • Home
  • uploads
    • d7dcea8f9f7385fc40a5cc8328f02520
      • filterRefactoring