![]() So I know what you are thinking at this point. With that in mind, it's great that we have moved this information into the project, but how does this get used for a build. What technologies does my project interact with?.This file holds the answers to the standard project question everyone asks when they join a project: There are some added bonuses from this file as well. pnxci.yaml file which lives in the root directory of each project, enabling PreviousNext staff to make changes as required. The workflow / steps committed to be stored in the project.A minimal amount of Puppet to setup some Jenkins jobs.Quite alot of YAML for one build right? However, the bigger concern is that the infrastructure (pull_request field) and the projects workflow (steps field) are all in the same file. The workflowĪs I mentioned above, if a change had to be made in a projects' build process Sys Ops would have to make the change in the backend, this was done via a YAML file which Puppet consumed and used to update the Jenkins host configuration.ĭescription: 'This build is triggered by Github pull requests.' So let's talk about the new architecture and how we solve these problems. Less reliance on Jenkins for functionality. ![]() We also want to move to a CI with the following goals:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |