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

RSS

bitbucket_server (6) Versions 0.1.8

Installs/Configures bitbucket_server

Policyfile
Berkshelf
Knife
cookbook 'bitbucket_server', '~> 0.1.8', :supermarket
cookbook 'bitbucket_server', '~> 0.1.8'
knife supermarket install bitbucket_server
knife supermarket download bitbucket_server
README
Dependencies
Changelog
Quality 67%

Bitbucket server cookbook

Chef cookbook
Build Status
License
Dependency Status
GitHub issues
GitHub pull requests
GitHub contributors

The bitbucket server cookbook is a library cookbook that provides resource primitives for use in recipes.

Requirements

  • Chef 12.7+
  • git 5.8.8+
  • java 8+
  • unzip (to be used if required for backup_client resource)

Platform Support

  • CentOS 7
  • Ubuntu 16.04
  • Debian 8.8
  • Fedora 25
  • Opensuse-leap 42.2

We actively test on above platforms version. But any other linux version that supports systemd should work.

Cookbook Dependencies

  • ark

Bitbucket version

This cookbook only supports versions of bitbucket server 5.0.0 and above.

Usage

Place a dependency on the bitbucket_server cookbook in your cookbook's metadata.rb

depends 'bitbucket_server'

Then, in a recipe within your cookbook:

bitbucket_install 'bitbucket' do
  jre_home "#{node['java']['java_home']}/jre"
end

Custom resources

bitbucket_install

This resource installs a bitbucket server and sets the BITBUCKET_HOME. It expects the JAVA_HOME to be set. If it is not, then jre_home has to be set as an attribute. The usage is:
ruby
bitbucket_install 'bitbucket' do
jre_home "#{node['java']['java_home']}/jre"
end

Below are the attributes supported by this resource:

Property String default required
product String bitbucket false
version String 5.0.1 false
bitbucket_user String atlbitbucket false
bitbucket_group String atlbitbucket false
home_path String /var/atlassian/application-data/bitbucket false
install_path String /opt/atlassian false
checksum String 677528dffb770fab9ac24a2056ef7be0fc41e45d23fc2b1d62f04648bfa07fad false
url_base String http://www.atlassian.com/software/stash/downloads/binary/atlassian-bitbucket false
jre_home String false
jvm_args String false

To unit test the usage of this resource you can use install_bitbucket matcher in chefspec like:

  expect(chef_run).to install_bitbucket('bitbucket').with_jre_home('/usr/lib/jvm/java-8-oracl/jre')

bitbucket_config

This resource configures an already installed bitbucket. The configurations can be provided as a Hash. Below is the usage:
ruby
bitbucket_config 'bitbucket' do
bitbucket_properties node['bitbucket']['properties']
end

or
ruby
bitbucket_config 'bitbucket' do
bitbucket_properties {'setup.displayName' => 'aasdasd','setup.baseUrl' => 'http://localhost:7990'}
end

Below are the attributes supported by this resource:

Property String default required
product String bitbucket false
bitbucket_user String atlbitbucket false
bitbucket_group String atlbitbucket false
home_path String /var/atlassian/application-data/bitbucket false
bitbucket_properties Hash true

To unit test the usage of this resource you can use config_bitbucket matcher in chefspec like:

  expect(chef_run).to config_bitbucket('bitbucket').with_bitbucket_properties('setup.displayName' => 'my bitbucket')

To check the possible configurations to set in the Hash refer to Bitbucket Documentation > Administering Bitbucket Server > Bitbucket Server config properties.
At the minimum it is useful to configure the setup properties mentioned in Bitbucket Documentation > Install or upgrade Bitbucket Server > Bitbucket Server installation guide > Automated setup for Bitbucket Server.

bitbucket_service

This resource is used to create a systemd service config. It will create, enable and start the service. The name of the service is set by the property product. Below is the usage:

bitbucket_service 'bitbucket'

Below are the attributes supported by this resource:

Property String default required
product String bitbucket false
bitbucket_user String atlbitbucket false
install_path String /opt/atlassian false

To unit test the usage of this resource you can use service_bitbucket matcher in chefspec like:

  expect(chef_run).to service_bitbucket('bitbucket')

backup_client

This resource installs bitbucket backup-client and creates the backup properties config file.

Usage :
ruby
backup_client 'bitbucket' do
backup_user 'bitbucket_backup'
backup_password 'passwd'
bitbucket_url 'http://bitbucket_url:7990'
backup_path '/tmp'
end

Below are the attributes supported by this resource:

Property String default required
product String bitbucket false
version String 3.3.2 false
bitbucket_user String atlbitbucket false
bitbucket_group String atlbitbucket false
home_path String /var/atlassian/application-data/bitbucket false
install_path String /opt/atlassian false
bitbucket_url String http://127.0.0.1:7990 false
client_url String http://www.atlassian.com/software/stash/downloads/binary/atlassian-bitbucket false
backup_path String true
backup_user String false
backup_password String false

Testing

chef exec bundle install

To check rake tasks
bash
chef exec bundle exec rake --tasks

To execute lynt and unit tests
bash
chef exec bundle exec rake style
chef exec bundle exec rake unit

or
bash
chef exec bundle exec delivery local lint
chef exec bundle exec delivery local syntax
chef exec bundle exec delivery local unit

or
bash
chef exec bundle exec delivery local all

To execute Integration tests
bash
rake integration:kitchen:<suitename-platform>

for instance:
bash
rake integration:kitchen:default-centos-73

To directly use Kitchen
bash
chef exec kitchen verify <suitename-platform>

for instance:
bash
rake integration:kitchen:default-centos-73

Contributing

  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. Create new Pull Request

License and Author

Author: Bharath Prakash (cippy.bharath@gmail.com)

Author: Raghavendra Gona (graghav@gmail.com)

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

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

ark ~> 3.1.0

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

Change Log

v0.1.8 (2017-07-03)

Full Changelog

Implemented enhancements:

  • Multi OS Support #9

Fixed bugs:

  • Update README.md #52

Merged pull requests:

v0.1.7 (2017-06-25)

Full Changelog

Implemented enhancements:

  • Enhance Bitbucket Config Resource #16
  • Bitbucket Backup Client Resource #15

Closed issues:

  • unit test changes to installation #33
  • Unit test for directory idempotence in bitbucket_install resource #31

Merged pull requests:

v0.1.6 (2017-06-11)

Full Changelog

Fixed bugs:

  • add inspec test for server status check #23
  • Fix Flaky InSpec test #14

Closed issues:

  • Allow JVM_SUPPORT_RECOMMENDED_ARGS to be set #39
  • wrapper cookbooks cannot find the erb template sources #36
  • automated generation of changelog #35
  • unit test version validation #34
  • unit test default value of checksum #32

Merged pull requests:

  • added unit test for jvm args and refactored test cases #40 (bharathcp)

v0.1.5 (2017-06-05)

Full Changelog

Merged pull requests:

  • adding cookbook attribute to template resources #37 (bharathcp)

v0.1.4 (2017-05-31)

Full Changelog

Implemented enhancements:

  • Add Guards in Custom Resource #19
  • Bitbucket changes should notify #17
  • Expose ChefSpec Matchers in Library #11

Fixed bugs:

  • Update Readme #12

Closed issues:

  • Decide on License to use #13

Merged pull requests:

v0.1.3 (2017-05-24)

Full Changelog

v0.1.2 (2017-05-24)

Full Changelog

v0.1.1 (2017-05-24)

Full Changelog

v0.1.0 (2017-05-24)

Merged pull requests:

* This Change Log was automatically generated by github_changelog_generator

Collaborator Number Metric
            

0.1.8 failed this metric

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

Contributing File Metric
            

0.1.8 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.8 passed this metric

No Binaries Metric
            

0.1.8 passed this metric

Testing File Metric
            

0.1.8 passed this metric

Version Tag Metric
            

0.1.8 passed this metric