Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to .NET 3.0 and C# 8.0 (#4097) #4101

Merged
merged 6 commits into from
Sep 30, 2019
Merged

Move to .NET 3.0 and C# 8.0 (#4097) #4101

merged 6 commits into from
Sep 30, 2019

Conversation

Mpdreamz
Copy link
Member

  • initial move to .NET Core 3.0

  • bump to .net sdk 3.0.100 and update our build files to install it for now while the images catch up

  • move scripts to 3.0 since we call dotnet run on them, exclude new types from codestandards test that all types live in Elasticsearch.Net/NEST namespace

  • build tooling moved from 2.2 to 3.0

  • move all netcoreapp over to 3.0

  • move to range on RegexCollection no longer accepts Last()

  • update our own dependencies

  • make 2.2 available for canary so that rewrite using 2.2 tools still works

  • fix yaml indentation

  • disable ingest-attachemnt for now, installl has stderr on 8.0.0 which abstractions does not yet handle

  • move rewriter and differ to local dotnet tools

  • no longer need to install 2.2 sdk for differ

(cherry picked from commit 9bbffad)

* initial move to .NET Core 3.0

* bump to .net sdk 3.0.100 and update our build files to install it for now while the images catch up

* move scripts to 3.0 since we call dotnet run on them, exclude new types from codestandards test that all types live in Elasticsearch.Net/NEST namespace

* build tooling moved from 2.2 to 3.0

* move all netcoreapp over to 3.0

* move to range on RegexCollection no longer accepts Last()

* update our own dependencies

* make 2.2 available for canary so that rewrite using 2.2 tools still works

* fix yaml indentation

* disable ingest-attachemnt for now, installl has stderr on 8.0.0 which abstractions does not yet handle

* move rewriter and differ to local dotnet tools

* no longer need to install 2.2 sdk for differ

(cherry picked from commit 9bbffad)
@Mpdreamz
Copy link
Member Author

Two integration test failures one is due to the seed opened #4104 to fix that.

The other is a ProcessClusterEventTimeoutException which is unreproducable and not related to these changes.

build.bat seed:71011 integrate 7.1.0 "writable" "getrepository" `

@Mpdreamz
Copy link
Member Author

Since the doc generation PR is now pending as per #4113 moving ahead and merging this in.

@Mpdreamz Mpdreamz merged commit 30dbd3c into 7.x Sep 30, 2019
@Mpdreamz Mpdreamz deleted the feature/7.x/core-3 branch September 30, 2019 12:24
russcam pushed a commit that referenced this pull request Oct 1, 2019
* Move to .NET 3.0 and C# 8.0 (#4097)

* initial move to .NET Core 3.0

* bump to .net sdk 3.0.100 and update our build files to install it for now while the images catch up

* move scripts to 3.0 since we call dotnet run on them, exclude new types from codestandards test that all types live in Elasticsearch.Net/NEST namespace

* build tooling moved from 2.2 to 3.0

* move all netcoreapp over to 3.0

* move to range on RegexCollection no longer accepts Last()

* update our own dependencies

* make 2.2 available for canary so that rewrite using 2.2 tools still works

* fix yaml indentation

* disable ingest-attachemnt for now, installl has stderr on 8.0.0 which abstractions does not yet handle

* move rewriter and differ to local dotnet tools

* no longer need to install 2.2 sdk for differ

(cherry picked from commit 9bbffad)

* update Elastic.* packages and reenable attachment plugin on writable cluster

* same elastic version as other branhces

* NuGet.config and nuget.config both existed in the repos

* update to latest abstractions that is more lenient on stderr from plugin installs

* update abstractions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant