-
-
Notifications
You must be signed in to change notification settings - Fork 171
Closed
Labels
Description
Currently, it looks like all Jenkins jobs are configured through the web interface. It would be advantageous if all of the jobs were managed through pipelines (a Jenkins 2 feature), which allows for job configuration to be checked into version control. This would allow for more transparency in the configuration, and using a normal code review process to approve changes.
Some key points to consider are...
- where should the pipeline files live? should they be in the project itself (travis-style), or should they live in nodejs/build in a jenkins directory?
- migrating the jobs with no downtime
- since job configuration is being checked into source control, is there a better way to manage admin groups/users, with the additional metadata?
If this all sounds alright, I can try and draft up a more complete project plan and migration strategy :)