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

Select Status


xldeploy (4) Versions 1.0.0

Installs and configures XL Deploy from XebiaLabs

cookbook 'xldeploy', '= 1.0.0', :supermarket
cookbook 'xldeploy', '= 1.0.0'
knife supermarket install xldeploy
knife supermarket download xldeploy
Quality 29%

XL Deploy

Build Status


XL Deploy is the only application release automation solution that is agentless across all target platforms. Connect to Windows and Unix target systems using proven, industry-standard remote protocols; no agent installation and maintenance, no overhead on the target systems, no firewall ports to be opened, and no security reviews.

Server requirements

To install the XL Deploy server, the following prerequisites must be met:

  1. XL Deploy license: You can download your license from
  2. Operating system: Windows or Unix-family operating system running Java.
  3. Java Runtime Environment: JDK 7 (Oracle, IBM or Apple)
  4. RAM: At least 2GB of RAM available for XL Deploy.
  5. Hard disk space: Sufficient hard disk space to store the XL Deploy repository. This depends on your usage of XL Deploy. See Determining hard disk space requirements.

Depending on the environment, the following may also be required:

  1. Database: XL Deploy's Jackrabbit repository supports a number of different databases. For more information, see Configuring the repository.
  2. LDAP: To enable group-based security, an LDAP x.509 compliant registry is needed. For more information, see Configuring LDAP security.

Download Installation Archive
The cookbook is using wget to download the installation archive from xebialabs.
Set attribute ['xldeploy']['downloadurl'] to this installation archive.
Set attribute default['xldeploy']['username'] = 'supplied by xebialabs'
Set attribute default['xldeploy']['password'] = 'supplied by xebialabs'

Using the default recipe the below steps are executed
1. Creates xldeploy user and group.
2. Creates an installation directory /opt/xl-deploy-4.5.x-server. This can be changed via attributes.
3. wgets the XL Deploy installation archive from the ['xldeploy']['downloadurl'] attribute.
4. Extracts the archive into the installation directory.
5. Change ownership of the installation directory to be owned by xldeploy user and group.
6. Configure the deployit.conf through the setup.config.txt.erb template. All values in this setup file can be overwritten by attributes.
7. Kick off xldeploy installation program ( included in installation archive).
8. Configure xldeploy as a service (runit).

Post Installation

Add the license file to your installation directory ~/conf directory and restart XLDeploy service

sv down xldeploy; sv up xldeploy


  1. Fork it!
  2. Create your feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request :D

License & Authors

  • Authors: Robert Castelle & Bernie Durfee
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

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.

Dependent cookbooks

runit ~> 1.5
java ~> 1.25
tar ~> 0.5

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Collaborator Number Metric

1.0.0 failed this metric

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

Contributing File Metric

1.0.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, and your repo must contain a file

Foodcritic Metric

1.0.0 failed this metric

FC055: Ensure maintainer is set in metadata: xldeploy/metadata.rb:1
FC056: Ensure maintainer_email is set in metadata: xldeploy/metadata.rb:1
FC066: Ensure chef_version is set in metadata: xldeploy/metadata.rb:1
FC069: Ensure standardized license defined in metadata: xldeploy/metadata.rb:1
Run with Foodcritic Version 12.2.1 with tags metadata,correctness ~FC031 ~FC045 and failure tags any

License Metric

1.0.0 failed this metric

xldeploy does not have a valid open source license.
Acceptable licenses include Apache-2.0, apachev2, Apache 2.0, MIT, mit, GPL-2.0, gplv2, GNU Public License 2.0, GPL-3.0, gplv3, GNU Public License 3.0.

No Binaries Metric

1.0.0 passed this metric

Testing File Metric

1.0.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, and your repo must contain a file

Version Tag Metric

1.0.0 passed this metric