winhamwr / ci-infrastructure Goto Github PK

Should mkfs.xfs /dev/foo if the volume isn't XFS formatted. Maybe add this as just a step in the README?

Every single Jenkins install is going to want to turn on some level of authentication at the minimum. Provide that with a default admin user as a sane default.

Explain how to use data bags or node configuration options to manage plugin installs with chef.

Librarian looks awesome, and we should use it. Copy/pasting 3rd-party code in to a repo makes baby jesus cry.

It does add a ruby dependency though, which means folks will have to set up both a python and ruby environment. I think this is worth it, but I'm open to suggestions.

$fix node:ec2-184-72-16-29.us-west-1.compute.amazonaws.com deploy_chef Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 602, in main docstring, callables, default = load_fabfile(fabfile) File "/usr/local/lib/python2.7/dist-packages/fabric/main.py", line 161, in load_fabfile imported = importer(os.path.splitext(fabfile)[0]) File "/root/.virtualenvs/ci-instructure/src/littlechef/littlechef/runner.py", line 24, in <module> from paramiko.config import SSHConfig as _SSHConfig ImportError: No module named paramiko.config

I've completed all the steps listed in the configuration - and I've hit a wall with the above command and call traceback...

Does it matter where I cloned my repo? It's under /home/username/bin/ci-infrastructure

Create a base job configuration for checking out a project from a git repo and then running jshint on a directory.

Should include documentation and a way to customize the script via node config or databags. Or maybe that's too hard and just manually editing the config is the only way to provide enough flexibility?