Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

RSS

ctfhooks (1) Versions 0.1.0

Installs/Configures TeamForge and Chef integration

Berkshelf/Librarian
Policyfile
Knife
cookbook 'ctfhooks', '~> 0.1.0'
cookbook 'ctfhooks', '~> 0.1.0', :supermarket
knife cookbook site install ctfhooks
knife cookbook site download ctfhooks
README
Dependencies
Quality

TeamForge-Chef Integration Cookbook

Installs scripts and associated automation needed to get CollabNet TeamForge and Chef integrated.

Requirements

CollabNet TeamForge Server plus some nodes to deploy software to.

Attributes

See attributes/default.rb for default values.

chefauth

  • node['ctfhooks']['chefauth']['sf-admin-home'] - the default install location of CollabNet TeamForge and hence the home directory of the 'sf-admin' user
  • node['ctfhooks']['chefauth']['chef-server-url'] - the Chef server to contact in the asynchronous callback scripts

Recipes

default

Does nothing.

client

Convenient recipe that includes user and sudoers recipes to make the integration work. 'client' runs on each application server;

server

Convenient recipe that includes relevant individual recipes to make the integration work. 'server' runs on the TeamForge server itself and installs the asynchronous hook and authentication components (e.g. Chef configurations)

artifact_update_hook

Installs the artifact update hook script, which is a template, into the asynchronous hooks directory.

chefauth

Sets up the TeamForge server so that Knife, running under the 'sf-admin' (TeamForge) user ID, can authenticate to the Chef server as a client.

We assume that a user called 'sf-admin' has been created ahead of time on the Chef server, and that the 'sf-admin.pem' can be placed manually on the TeamForge server.

hooks

Installs the Java-to-arbitrary-language bridge, hooks.jar, on the TeamForge server, so that the artifact_update Ruby script can run.

While hooks.jar is not officially supported by CollabNet, some directions on its design can be found on CollabNet's blog: http://blogs.collab.net/teamforge/custom-workflow-in-teamforge-a-guide-to-iaf-event-handlers

A version of hooks.jar that supports passing flex field data as environment variables is included. It was retrieved from here: http://forums.open.collab.net/ds/viewMessage.do?dsForumId=738&dsMessageId=486169

sudoers

Sets up sudoers on client machines so that the 'sf-admin' user can run Chef client as root (or signal the currently-running daemon to restart).

Note: The sf-admin user needs to be able to run the commands in this recipe without requiring a TTY. You can set this up in your main sudoers file if necessary (e.g. using Opscode's sudo cookbook), or if you're running OpenSSH >= 5.9, the RequestTTY option can be used in the host's ssh_options to always force the creation of a TTY.

user

Sets up a user called sf-admin on client machines.

License and Author

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Dependent cookbooks

users >= 0.0.0
sudo >= 0.0.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric
            

0.1.0 failed this metric

Failure: Cookbook has 0 collaborators. A cookbook must have at least 2 collaborators to pass this metric.

Contributing File Metric
            

0.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a CONTRIBUTING.md file

Foodcritic Metric
            

0.1.0 failed this metric

FC064: Ensure issues_url is set in metadata: ctfhooks/metadata.rb:1
FC065: Ensure source_url is set in metadata: ctfhooks/metadata.rb:1
FC066: Ensure chef_version is set in metadata: ctfhooks/metadata.rb:1
FC067: Ensure at least one platform supported in metadata: ctfhooks/metadata.rb:1
FC069: Ensure standardized license defined in metadata: ctfhooks/metadata.rb:1
Run with Foodcritic Version 11.1.0 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric
            

0.1.0 passed this metric

No Binaries Metric
            

0.1.0 failed this metric

Failure: Cookbook should not contain binaries. Found:
ctfhooks/files/default/hooks.jar

Publish Metric
            

0.1.0 passed this metric

Supported Platforms Metric
            

0.1.0 failed this metric

ctfhooks should declare what platform(s) it supports.

Testing File Metric
            

0.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must contain a TESTING.md file

Version Tag Metric
            

0.1.0 failed this metric

Failure: To pass this metric, your cookbook metadata must include a source url, the source url must be in the form of https://github.com/user/repo, and your repo must include a tag that matches this cookbook version number