You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Pull Request created in integrations repository: https://github.com/elastic/integrations/pull/6756
92
+
93
+
This comment triggers this [Buildkite pipeline](https://github.com/elastic/elastic-package/blob/6f084e21561105ac9773acab00c3439251f111a0/.buildkite/pipeline.test-with-integrations-repo.yml) ([Buildkite job](https://buildkite.com/elastic/elastic-package-test-with-integrations)).
94
+
95
+
This pipeline creates a new draft Pull Request in integration updating the required dependencies to test your own changes. As a new pull request is created, a CI
96
+
job will be triggered to test all the packages defined in this repository. A new comment with the link to this new Pull Request will be posted in your package-spec Pull Request.
97
+
98
+
**IMPORTANT**: Remember to close this PR in the integrations repository once you close the package-spec Pull Request.
99
+
100
+
Usually, this process would require the following manual steps:
101
+
1. Create your elastic-package pull request and push all your commits
102
+
2. Get the SHA of the latest changeset of your PR:
103
+
```bash
104
+
$ git show -s --pretty=format:%H
105
+
1131866bcff98c29e2c84bcc1c772fff4307aaca
106
+
```
107
+
3. Go to the integrations repository, and update go.mod and go.sum with that changeset:
108
+
```bash
109
+
cd /path/to/integrations/repostiory
110
+
go mod edit -replace github.com/elastic/elastic-package=github.com/<your_github_user>/elastic-package@1131866bcff98c29e2c84bcc1c772fff4307aaca
111
+
go mod tidy
112
+
```
113
+
4. Push these changes into a branch and create a Pull Request
114
+
- Creating this PR would automatically trigger a new Jenkins pipeline.
115
+
116
+
64
117
## Commands
65
118
66
119
`elastic-package` currently offers the commands listed below.
@@ -512,21 +565,6 @@ The following settings are available per profile:
512
565
Elasticsearch in stacks managed by elastic-package. It is recommended to use
513
566
an absolute path, out of the `.elastic-package` directory.
514
567
515
-
## Development
516
-
517
-
Even though the project is "go-gettable", there is the `Makefile` present, which can be used to build, format or vendor
518
-
source code:
519
-
520
-
`make build` - build the tool source
521
-
522
-
`make format` - format the Go code
523
-
524
-
`make install` - build the tool source and move binary to `$GOBIN`
525
-
526
-
`make vendor` - vendor code of dependencies
527
-
528
-
`make check` - one-liner, used by CI to verify if source code is ready to be pushed to the repository
529
-
530
568
## Release process
531
569
532
570
This project uses [GoReleaser](https://goreleaser.com/) to release a new version of the application (semver). Release publishing
returnfmt.Errorf("packages with dashboards exported since Kibana %s may not be installed till %s, please export the dashboard/s from a different version", minVersion, maxVersion)
- Pull Request created in integrations repository: https://github.com/elastic/integrations/pull/6756
92
+
93
+
This comment triggers this [Buildkite pipeline](https://github.com/elastic/elastic-package/blob/6f084e21561105ac9773acab00c3439251f111a0/.buildkite/pipeline.test-with-integrations-repo.yml) ([Buildkite job](https://buildkite.com/elastic/elastic-package-test-with-integrations)).
94
+
95
+
This pipeline creates a new draft Pull Request in integration updating the required dependencies to test your own changes. As a new pull request is created, a CI
96
+
job will be triggered to test all the packages defined in this repository. A new comment with the link to this new Pull Request will be posted in your package-spec Pull Request.
97
+
98
+
**IMPORTANT**: Remember to close this PR in the integrations repository once you close the package-spec Pull Request.
99
+
100
+
Usually, this process would require the following manual steps:
101
+
1. Create your elastic-package pull request and push all your commits
102
+
2. Get the SHA of the latest changeset of your PR:
103
+
```bash
104
+
$ git show -s --pretty=format:%H
105
+
1131866bcff98c29e2c84bcc1c772fff4307aaca
106
+
```
107
+
3. Go to the integrations repository, and update go.mod and go.sum with that changeset:
108
+
```bash
109
+
cd /path/to/integrations/repostiory
110
+
go mod edit -replace github.com/elastic/elastic-package=github.com/<your_github_user>/elastic-package@1131866bcff98c29e2c84bcc1c772fff4307aaca
111
+
go mod tidy
112
+
```
113
+
4. Push these changes into a branch and create a Pull Request
114
+
- Creating this PR would automatically trigger a new Jenkins pipeline.
115
+
116
+
64
117
## Commands
65
118
66
119
`elastic-package` currently offers the commands listed below.
@@ -112,21 +165,6 @@ The following settings are available per profile:
112
165
Elasticsearch in stacks managed by elastic-package. It is recommended to use
113
166
an absolute path, out of the `.elastic-package` directory.
114
167
115
-
## Development
116
-
117
-
Even though the project is "go-gettable", there is the `Makefile` present, which can be used to build, format or vendor
118
-
source code:
119
-
120
-
`make build` - build the tool source
121
-
122
-
`make format` - format the Go code
123
-
124
-
`make install` - build the tool source and move binary to `$GOBIN`
125
-
126
-
`make vendor` - vendor code of dependencies
127
-
128
-
`make check` - one-liner, used by CI to verify if source code is ready to be pushed to the repository
129
-
130
168
## Release process
131
169
132
170
This project uses [GoReleaser](https://goreleaser.com/) to release a new version of the application (semver). Release publishing
0 commit comments