| Ales Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 1 | |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 2 | =========== |
| 3 | Artifactory |
| 4 | =========== |
| Ales Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 5 | |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 6 | JFrog Artifactory is the only Universal Repository Manager supporting all major packaging formats, build tools and CI servers. |
| 7 | |
| Ales Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 8 | |
| 9 | Sample pillars |
| 10 | ============== |
| 11 | |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 12 | Single artifactory OSS edition from OS package |
| Ales Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 13 | |
| 14 | .. code-block:: yaml |
| 15 | |
| 16 | artifactory: |
| 17 | server: |
| 18 | enabled: true |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 19 | edition: oss |
| 20 | version: 4 |
| 21 | source: |
| 22 | engine: pkg |
| 23 | |
| 24 | Single 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 Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 35 | |
| 36 | |
| 37 | Development and testing |
| 38 | ======================= |
| 39 | |
| 40 | Development and test workflow with `Test Kitchen <http://kitchen.ci>`_ and |
| 41 | `kitchen-salt <https://github.com/simonmcc/kitchen-salt>`_ provisioner plugin. |
| 42 | |
| 43 | Test Kitchen is a test harness tool to execute your configured code on one or more platforms in isolation. |
| 44 | There is a ``.kitchen.yml`` in main directory that defines *platforms* to be tested and *suites* to execute on them. |
| 45 | |
| 46 | Kitchen CI can spin instances locally or remote, based on used *driver*. |
| 47 | For local development ``.kitchen.yml`` defines a `vagrant <https://github.com/test-kitchen/kitchen-vagrant>`_ or |
| 48 | `docker <https://github.com/test-kitchen/kitchen-docker>`_ driver. |
| 49 | |
| 50 | To use backend drivers or implement your CI follow the section `INTEGRATION.rst#Continuous Integration`__. |
| 51 | |
| 52 | The `Busser <https://github.com/test-kitchen/busser>`_ *Verifier* is used to setup and run tests |
| 53 | implementated in `<repo>/test/integration`. It installs the particular driver to tested instance |
| 54 | (`Serverspec <https://github.com/neillturner/kitchen-verifier-serverspec>`_, |
| 55 | `InSpec <https://github.com/chef/kitchen-inspec>`_, Shell, Bats, ...) prior the verification is executed. |
| 56 | |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 57 | Usage |
| 58 | ----- |
| Ales Komarek | f9d35ae | 2016-08-19 10:23:00 +0200 | [diff] [blame] | 59 | |
| 60 | .. code-block:: shell |
| 61 | |
| 62 | # list instances and status |
| 63 | kitchen list |
| 64 | |
| 65 | # manually execute integration tests |
| 66 | kitchen [test || [create|converge|verify|exec|login|destroy|...]] [instance] -t tests/integration |
| 67 | |
| 68 | # use with provided Makefile (ie: within CI pipeline) |
| 69 | make kitchen |
| 70 | |
| 71 | |
| 72 | |
| 73 | Read more |
| 74 | ========= |
| 75 | |
| Ales Komarek | 70fdd16 | 2016-08-19 12:28:05 +0200 | [diff] [blame^] | 76 | * https://www.jfrog.com/confluence/display/RTF/Debian+Repositories |