Skip to content

Commit f1a9e63

Browse files
committed
[CI] Fixes missing elasticsearch task namespace renames
1 parent e7bedcd commit f1a9e63

File tree

4 files changed

+5
-5
lines changed

4 files changed

+5
-5
lines changed

elasticsearch-api/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The `rest_api` task needs the test files from Elasticsearch. You can run the rak
2323

2424
Or it can get the version from a running cluster to determine which version and build hash of Elasticsearch to use and test against:
2525

26-
`TEST_ES_SERVER=http://localhost:9200 rake elasticsearch:download_artifacts`
26+
`TEST_ES_SERVER=http://localhost:9200 rake es:download_artifacts`
2727

2828
This will download the necessary files used for the integration tests to `./tmp`.
2929

elasticsearch-api/spec/rest_api/rest_api_yaml_spec.rb

+1-1
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ def skip_test?(test)
3737

3838
if REST_API_YAML_FILES.empty?
3939
LOGGER.error 'No test files found!'
40-
LOGGER.info 'Use rake rake elasticsearch:download_artifacts in the root directory of the project to download the test artifacts.'
40+
LOGGER.info 'Use rake rake es:download_artifacts in the root directory of the project to download the test artifacts.'
4141
exit 1
4242
end
4343

elasticsearch-api/utils/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ This directory hosts The Generator, a tool that generates the classes for each A
88

99
To generate the code, you need to have the Elasticsearch REST API spec files in `tmp/rest-api-spec` in the root of the project. You can run a rake task from the root of the project to download the specs corresponding to the current running cluster:
1010
```bash
11-
$ rake elasticsearch:download_artifacts
11+
$ rake es:download_artifacts
1212
```
1313

1414
Once the JSON files have been downloaded, you need to run (from this folder):
@@ -24,7 +24,7 @@ $ thor code:generate
2424
$ IGNORE_VERSION=true thor code:generate
2525
```
2626

27-
- You can use the environment variable `BUILD_HASH` to update the build hash for the generated code from the `tmp/rest-api-spec/build_hash` file. This file is updated every time you use the `elasticsearch:download_artifacts` Rake task is used in the root of the project to download the latest Elasticsearch specs and tests:
27+
- You can use the environment variable `BUILD_HASH` to update the build hash for the generated code from the `tmp/rest-api-spec/build_hash` file. This file is updated every time you use the `es:download_artifacts` Rake task is used in the root of the project to download the latest Elasticsearch specs and tests:
2828
```bash
2929
$ BUILD_HASH=true thor code:generate
3030
```

rake_tasks/automation.rake

+1-1
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ namespace :automation do
3939
task :codegen do
4040
version = YAML.load_file(File.expand_path("#{__dir__}/../.buildkite/pipeline.yml"))['steps'].first['env']['STACK_VERSION']
4141

42-
Rake::Task['elasticsearch:download_artifacts'].invoke(version)
42+
Rake::Task['es:download_artifacts'].invoke(version)
4343
sh "cd #{CURRENT_PATH.join('elasticsearch-api/utils')} \
4444
&& BUNDLE_GEMFILE=`pwd`/Gemfile \
4545
&& bundle exec thor code:generate"

0 commit comments

Comments
 (0)