Move CI job config entries from legacy to new config
What does this MR do?
This MR extracts jobs configuration logic from legacy CI config processor to the new code.
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
- Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the style guides -
Branch has no merge conflicts with master
(if you do - rebase it please)
Merge request reports
Activity
Added 1 commit:
- 9686a4f2 - Remove code creating job hash from legacy CI config
Added 1 commit:
- 5b7f211c - Add new CI config entry that holds jobs definition
mentioned in issue #18920 (closed)
Added 1 commit:
- e00ae9a8 - Add new CI config entry for single job in pipeline
Added 1 commit:
- 6ae80732 - Add ability to define nodes in new CI config entry
Added 1 commit:
- dbab56a9 - Create composite job entries in new CI config
Added 1 commit:
- b1b0c18b - Add hidden job in new CI config that is irrelevant
Added 1 commit:
- 580c4e18 - Move decision about relevant jobs to new CI config
Added 1 commit:
- 4491bf28 - Move CI job config validations to new classes
Added 1 commit:
- 6f02da2c - Simplify legacy CI config processor a little
Added 1 commit:
- b0ae0d73 - Use only node factory to create CI config entries
Added 1 commit:
- fea77624 - Delegate methods to default CI entry if undefined
Added 1 commit:
- de8b93bb - Improve validation of CI config entry if composite
Please register or sign in to reply