Currently, project-specific configs tend to be kept in the jenkins-inception project repo (but kept out of version control via gitignore. This poses some problems:
configs (including data_bags for team members that are used to give access to the server, and also jenkins-specific configs) should be kept in the project repo, ideally with the jenkins-inception project linked to a certain commit using submodule reference.
explictly ignoring these configs in the location where they are "first class citizens" means that they are often not committed to any sort of version control. It's an extra step to move them into the project repo every time they're changed, since they are not usable in the project repo.
Suggested solution:
Add the jenkins-inception project as a submodule in drupal-skeletor.
Allow the config path to be customizable via opt flag, so that real files can be stored in project repo and symlinked into jenkins-inception locations. Consider symlinking roles/config.yml to the project repo location where they will be vers-ctrld, and using the appropriate rsync flag to make sure they still get sent to the remote jenkins server when running knife solo cook:
https://lists.samba.org/archive/rsync/2006-November/016724.html
Currently, project-specific configs tend to be kept in the jenkins-inception project repo (but kept out of version control via gitignore. This poses some problems:
Suggested solution:
roles/config.ymlto the project repo location where they will be vers-ctrld, and using the appropriate rsync flag to make sure they still get sent to the remote jenkins server when runningknife solo cook: https://lists.samba.org/archive/rsync/2006-November/016724.html