elastic-package(builder tool) installed - follow the Getting started guide to install the tool.- There is a PR open to the Package Storage/snapshot with your built integration. This will be done automatically by the Integrations repository CI when it detects an unreleased version of your package in the Integrations repository.
- You have a fork of
https://github.com/elastic/package-storagein your account.
-
Please review this PR on your own and if the CI is happy, merge it.
-
Release changes to the stage using 1-click Jenkins form (need to be signed in).
-
If you're happy with the package, tested with Kibana and generally it's fine - promote your packages to the staging or production:
elastic-package promote
The tool will open 2 PRs (promote and delete) to the package-storage: target and source branches.
Please review both PRs on your own, check if CI is happy and merge - first target, then source. Once any PR is merged, the CI will kick off a job to bake a new Docker image of package-storage (tracking). Ideally the "delete" PR should be merged once the CI job for "promote" is done, as the Docker image of previous stage depends on the later one.
-
Use the 1-click from point 2. to release new revision of the package-storage.