![]() ![]() ![]() Method sizeĪnd there we hit our first problem, still a simple one. Still a rather simple thing, but can be a quite complex and huge pipeline to run that. ![]() If you have a Project A, B and C and the dependency chain is like A -> B -> C (-> means depends on) then if you build C the result is taken to build B and the result is taken again to build A. Now we added the feature to build a complete dependency chain. So such a generated pipeline can reach up to 1500 lines, depending on the project’s configuration, not a big deal typically. Postbuild phase, reporting, metrics, Jira connectors, etc.The build itself, parallel execution for all existing targets and variants, plus test execution, static code analysis etc.Prebuild phase, things to be done before the real build (reporting, or other stuff).Generation phase, here the build is bootstrapped, the pipeline is generated, loaded and executed.Such a build is quite simple, the Jenkinsfiles just needs two lines for bootstrap out of a jenkins pipeline library and then the CI build itself in it’s standard incarnation has 4 build phases: At work we have enhanced conan.io with an own python build system wrapper, which handles full dependency chains, forward and backward, and is capable of generating Jenkins pipelines for building in the Jenkins CI system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |