blob: cee7261843c9f401d6edc97fa0344a702179a747 [file] [log] [blame]
Ales Komarekf9d35ae2016-08-19 10:23:00 +02001
Ales Komarek70fdd162016-08-19 12:28:05 +02002===========
3Artifactory
4===========
Ales Komarekf9d35ae2016-08-19 10:23:00 +02005
Ales Komarek70fdd162016-08-19 12:28:05 +02006JFrog Artifactory is the only Universal Repository Manager supporting all major packaging formats, build tools and CI servers.
7
Ales Komarekf9d35ae2016-08-19 10:23:00 +02008
9Sample pillars
10==============
11
Ales Komarek70fdd162016-08-19 12:28:05 +020012Single artifactory OSS edition from OS package
Ales Komarekf9d35ae2016-08-19 10:23:00 +020013
14.. code-block:: yaml
15
16 artifactory:
17 server:
18 enabled: true
Ales Komarek70fdd162016-08-19 12:28:05 +020019 edition: oss
20 version: 4
21 source:
22 engine: pkg
23
24Single artifactory pro edition from OS package
25
26.. code-block:: yaml
27
28 artifactory:
29 server:
30 enabled: true
31 edition: pro
32 version: 4
33 source:
34 engine: pkg
Ales Komarekf9d35ae2016-08-19 10:23:00 +020035
Ales Komarek441ba232016-08-19 14:00:27 +020036Single artifactory with PostgreSQL database
37
38.. code-block:: yaml
39
40 artifactory:
41 server:
42 database:
43 engine: postgresql
44 host: localhost
45 port: 5432
46 name: artifactory
47 user: artifactory
48 password: pass
49
Ales Komarekf9d35ae2016-08-19 10:23:00 +020050
51Development and testing
52=======================
53
54Development and test workflow with `Test Kitchen <http://kitchen.ci>`_ and
55`kitchen-salt <https://github.com/simonmcc/kitchen-salt>`_ provisioner plugin.
56
57Test Kitchen is a test harness tool to execute your configured code on one or more platforms in isolation.
58There is a ``.kitchen.yml`` in main directory that defines *platforms* to be tested and *suites* to execute on them.
59
60Kitchen CI can spin instances locally or remote, based on used *driver*.
61For local development ``.kitchen.yml`` defines a `vagrant <https://github.com/test-kitchen/kitchen-vagrant>`_ or
62`docker <https://github.com/test-kitchen/kitchen-docker>`_ driver.
63
64To use backend drivers or implement your CI follow the section `INTEGRATION.rst#Continuous Integration`__.
65
66The `Busser <https://github.com/test-kitchen/busser>`_ *Verifier* is used to setup and run tests
67implementated in `<repo>/test/integration`. It installs the particular driver to tested instance
68(`Serverspec <https://github.com/neillturner/kitchen-verifier-serverspec>`_,
69`InSpec <https://github.com/chef/kitchen-inspec>`_, Shell, Bats, ...) prior the verification is executed.
70
Ales Komarek70fdd162016-08-19 12:28:05 +020071Usage
72-----
Ales Komarekf9d35ae2016-08-19 10:23:00 +020073
74.. code-block:: shell
75
76 # list instances and status
77 kitchen list
78
79 # manually execute integration tests
80 kitchen [test || [create|converge|verify|exec|login|destroy|...]] [instance] -t tests/integration
81
82 # use with provided Makefile (ie: within CI pipeline)
83 make kitchen
84
85
Ales Komarekf9d35ae2016-08-19 10:23:00 +020086Read more
87=========
88
Ales Komarek70fdd162016-08-19 12:28:05 +020089* https://www.jfrog.com/confluence/display/RTF/Debian+Repositories
Ales Komarek441ba232016-08-19 14:00:27 +020090* https://www.jfrog.com/confluence/display/RTF/PostgreSQL