honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/.gitignore

59 lines
959 B
Plaintext
Raw Normal View History

Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# intellij files
update .gitignore
2011-12-05 18:11:12 -05:00
.idea/
*.iml
ignore intellij project/workspace files closes #9044
2014-12-23 02:05:01 -05:00
*.ipr
*.iws
Build: use separate build directories for eclipse and intellij This fixes the problem where doing a gradle clean from the command line completely breaks the IDE.
2016-02-04 18:44:30 -05:00
build-idea/
Improve IntelliJ IDE integration (#53747) This commit makes a number of improvements when importing the Elasticsearch project into IntelliJ IDEA. Specifically: - Contributing documentation has been updated to reflect that the   'idea' task should no long be used and Gradle project import is   instead the officially supported way of setting up the project. - Attempts to run the 'idea' task will result in a failure with a   message directing folks to our CONTRIBUTING.md document. - The project JDK is explicit set rather that using whatever JAVA_HOME   is. - Gradle build operation delegation is disabled, and test execution is   configured to 'choose per test'. - Gradle is configured to inherit the project JDK. - Some code style conventions are automatically configured. - File encoding is explicitly set to UTF-8. - Parallel module compilation is enabled and deprecated feature   warnings are disabled. - A remote debug run configuration using listen mode is created. - JUnit runner is configured with required system properties. - License headers are configured such that Apache 2 is the default   notice added to all source files with exception of source in /x-pack   which will use the Elastic license.
2020-03-19 14:43:33 -04:00
out/
# include shared intellij config
!.idea/scopes/x_pack.xml
!.idea/inspectionProfiles/Project_Default.xml
Fix nasty errors when importing into IntelliJ
2020-03-24 00:31:04 -04:00
!.idea/runConfigurations/Debug_Elasticsearch.xml
Improve IntelliJ IDE integration (#53747) This commit makes a number of improvements when importing the Elasticsearch project into IntelliJ IDEA. Specifically: - Contributing documentation has been updated to reflect that the   'idea' task should no long be used and Gradle project import is   instead the officially supported way of setting up the project. - Attempts to run the 'idea' task will result in a failure with a   message directing folks to our CONTRIBUTING.md document. - The project JDK is explicit set rather that using whatever JAVA_HOME   is. - Gradle build operation delegation is disabled, and test execution is   configured to 'choose per test'. - Gradle is configured to inherit the project JDK. - Some code style conventions are automatically configured. - File encoding is explicitly set to UTF-8. - Parallel module compilation is enabled and deprecated feature   warnings are disabled. - A remote debug run configuration using listen mode is created. - JUnit runner is configured with required system properties. - License headers are configured such that Apache 2 is the default   notice added to all source files with exception of source in /x-pack   which will use the Elastic license.
2020-03-19 14:43:33 -04:00
Add generated benchmark files to gitignore (#51000) When building IntelliJ generates several source files related to the benchmarks. This commit adds that path to the gitignore so these don't get accidentally committed.
2020-01-14 18:18:28 -05:00
# These files are generated in the main tree by IntelliJ
benchmarks/src/main/generated/*
[Packaging] Run tests in vagrant This creates a module in qa called vagrant that can be run if you have vagrant and virtualbox installed and will run the packaging tests in trusty and centos-7.0. You can ask it to run tests in other linuxes. This is the full list: * precise aka Ubuntu 12.04 * trusty aka Ubuntu 14.04 * vivid aka Ubuntun 15.04 * wheezy aka Debian 7, the current debian oldstable distribution * jessie aka Debian 8, the current debina stable distribution * centos-6 * centos-7 * fedora-22 * oel-7 There is lots of documentation on how to do this in the TESTING.asciidoc. Closes #12611
2015-08-04 09:36:22 -04:00
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# eclipse files
adding ability for gradle to create eclipse project files and classpaths
2011-05-23 10:14:22 -04:00
.project
.classpath
Consolidate .gitignore entires for eclipse Rather than specify paths for the .gitignored files that Eclipse uses for project management just ignore all files and directories that look like those directories. That way we can add new subprojects and we won't need add more .gitignore entries.
2015-07-28 18:13:02 -04:00
.settings
Build: use separate build directories for eclipse and intellij This fixes the problem where doing a gradle clean from the command line completely breaks the IDE.
2016-02-04 18:44:30 -05:00
build-eclipse/
added netbeans ignores
2011-12-08 03:47:07 -05:00
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# netbeans files
added netbeans ignores
2011-12-08 03:47:07 -05:00
nb-configuration.xml
nbactions.xml
Add info to _cat/nodes, add _cat/indices.
2013-07-15 16:28:38 -04:00
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# gradle stuff
.gradle/
build/
Build: Update gitignore to keep maven targets on master See #14364
2015-10-29 18:55:41 -04:00
Cleanup .gitignore (#30145) Adds the `.vscode` directory to `.gitignore`. This didn't come up when we had x-pack in a different repository than Elasticsearch because I'd open the directory that contained both of them in VSCode. Now that they are merged I tend to just open the Elasticsearch repository which causes VSCode to create this directory that we don't need to commit. Also removes leftover maven files from `.gitignore`.
2018-04-25 22:11:40 -04:00
# vscode stuff
.vscode/
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# testing stuff
**/.local*
.vagrant/
Validate alias names the same as index names Applied (almost) the same rules we use to validate index names to new alias names. The only rule not applies it "must be lowercase". We have tests that don't follow that rule and I except there are lots of examples of camelCase alias names in the wild. We can add that validation but I'm not sure it is worth it. Closes #20748 Adds an alias that starts with `#` to the BWC index and validates that you can read from it and remove it. Starting with `#` isn't allowed after 5.1.0/6.0.0 so we don't create the alias or check it after those versions.
2016-10-05 16:24:22 -04:00
/logs/
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
# osx stuff
.DS_Store
Add BWC layer to seq no infra and enable BWC tests (#22185) Sequence BWC logic consists of two elements: 1) Wire level BWC using stream versions. 2) A changed to the global checkpoint maintenance semantics. For the sequence number infra to work with a mixed version clusters, we have to consider situation where the primary is on an old node and replicas are on new ones (i.e., the replicas will receive operations without seq#) and also the reverse (i.e., the primary sends operations to a replica but the replica can't process the seq# and respond with local checkpoint). An new primary with an old replica is a rare because we do not allow a replica to recover from a new primary. However, it can occur if the old primary failed and a new replica was promoted or during primary relocation where the source primary is treated as a replica until the master starts the target. 1) Old Primary & New Replica - this case is easy as is taken care of by the wire level BWC. All incoming requests will have their seq# set to `UNASSIGNED_SEQ_NO`, which doesn't confuse the local checkpoint logic (keeping it at `NO_OPS_PERFORMED`) 2) New Primary & Old replica - this one is trickier as the global checkpoint service currently takes all in sync replicas into consideration for the global checkpoint calculation. In order to deal with old replicas, we change the semantics to say all *new node* in sync replicas. That means the replicas on old nodes don't count for the global checkpointing. In this state the seq# infra is not fully operational (you can't search on it, because copies may miss it) but it is maintained on shards that can support it. The old replicas will have to go through a file based recovery at some point and will get the seq# information at that point. There is still an edge case where a new primary fails and an old replica takes over. I'lll discuss this one with @ywelsch as I prefer to avoid it completely. This PR also re-enables the BWC tests which were disabled. As such it had to fix any BWC issue that had crept in. Most notably an issue with the removal of the `timestamp` field in #21670. The commit also includes a fix for the default value of the seq number field in replicated write requests (it was 0 but should be -2), that surface some other minor bugs which are fixed as well. Last - I added some debugging tools like more sane node names and forcing replication request to implement a `toString`
2016-12-19 07:08:24 -05:00
# default folders in which the create_bwc_index.py expects to find old es versions in
/backwards
/dev-tools/backwards
Remove old docs gitignores and comment on docs build dir
2015-12-16 14:56:55 -05:00
# needed in case docs build is run...maybe we can configure doc build to generate files under build?
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
html_docs
Remove old docs gitignores and comment on docs build dir
2015-12-16 14:56:55 -05:00
# random old stuff that we should look at the necessity of...
Organize and annotate gitignores
2015-12-15 21:51:38 -05:00
/tmp/
Build: use separate build directories for eclipse and intellij This fixes the problem where doing a gradle clean from the command line completely breaks the IDE.
2016-02-04 18:44:30 -05:00
eclipse-build
Make sure the clean task doesn't break test fixtures (#43641) Use a dedicated fixture dir.
2019-07-08 10:49:33 -04:00
Add generated benchmark files to gitignore (#51000) When building IntelliJ generates several source files related to the benchmarks. This commit adds that path to the gitignore so these don't get accidentally committed.
2020-01-14 18:18:28 -05:00
# projects using testfixtures
Make sure the clean task doesn't break test fixtures (#43641) Use a dedicated fixture dir.
2019-07-08 10:49:33 -04:00
testfixtures_shared/
Move periodic job to ES repo (#48570) * Move periodic job to ES repo This change kickstarts the process of moving CI job definitions to this repo. * Added a minimal readme to provide pointers to the documentation * Update .ci/README.md Co-Authored-By: Rory Hunter <pugnascotia@users.noreply.github.com> * Update .ci/README.md Co-Authored-By: Rory Hunter <pugnascotia@users.noreply.github.com> * point to main repo * PR review * Add link to JJBB
2019-11-13 10:12:00 -05:00
# These are generated from .ci/jobs.t
.ci/jobs/