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

Please support .net core 1.0.0-rc4-004771 #7301

Closed
thiennn opened this issue Feb 10, 2017 · 8 comments
Closed

Please support .net core 1.0.0-rc4-004771 #7301

thiennn opened this issue Feb 10, 2017 · 8 comments

Comments

@thiennn
Copy link

@thiennn thiennn commented Feb 10, 2017

As Microsoft has released the new version of .netcore sdk. https://blogs.msdn.microsoft.com/dotnet/2017/02/07/announcing-net-core-tools-updates-in-vs-2017-rc/

Could you please support it?

@BanzaiMan
Copy link
Member

@BanzaiMan BanzaiMan commented Feb 10, 2017

Please mention @Joshua-Anderson @akoeplinger @nterry for C# inquiries, as documented in https://docs.travis-ci.com/user/languages/csharp. Thanks.

@am11
Copy link

@am11 am11 commented Mar 7, 2017

@Joshua-Anderson @akoeplinger @nterry, @blackdwarf

TravisCI seems to be downloading the SDK from the following URL:

https://dotnetcli.azureedge.net/dotnet/preview/Installers/1.0.0-rc4-004915/dotnet-dev-osx-x64.1.0.0-rc4-004915.pkg

which returns 404. However, the URL formed by the CLI's obtain script is:

https://dotnetcli.azureedge.net/dotnet/Sdk/1.0.0-rc4-004915/dotnet-dev-osx-x64.1.0.0-rc4-004915.tar.gz

It seems like after certain version (rc3 or preview2), they changed the URL format. Can we conditionally form the download URL based on the version where it stared to differ?

@am11
Copy link

@am11 am11 commented Mar 7, 2017

(or perhaps incorporate CLI's obtain script as is)

@ThePadawan
Copy link

@ThePadawan ThePadawan commented Mar 9, 2017

As of yesterday, 1.0.4 and 1.1.1 are no longer in preview.

Since the project.json-based infrastructure is now being steadily phased out, I would love to switch my projects over to the .csproj-based infrastructure, but won't do so without proper CI support.

@Joshua-Anderson @akoeplinger @nterry
Please advise if I can support you in any way to support the new .NET Core SDK versions.

@Joshua-Anderson
Copy link

@Joshua-Anderson Joshua-Anderson commented Mar 9, 2017

@ThePadawan They should be supported now on linux and OSX!

@akoeplinger
Copy link

@akoeplinger akoeplinger commented Mar 9, 2017

@ThePadawan note that 1.0.4 and 1.1.1 are the version numbers of .NET Core, but we're using the version number of the .NET Core Tooling/SDK (aka CLI) in the dotnet key (an SDK can install multiple .NET Core runtimes).

The SDK is at version 1.0.1, so just use dotnet: 1.0.1.

akoeplinger added a commit to akoeplinger/docs-travis-ci-com that referenced this issue Mar 9, 2017
We can close a bunch of old issues with this:

Fixes travis-ci/travis-ci#7301
Fixes travis-ci/travis-ci#7255
Fixes travis-ci/travis-ci#7026
Fixes travis-ci/travis-ci#4663

This one was done a while ago:
Fixes travis-ci/travis-ci#5189
@thiennn
Copy link
Author

@thiennn thiennn commented Mar 10, 2017

Yeah, it works. Thank you so much

@thiennn thiennn closed this Mar 10, 2017
@ThePadawan
Copy link

@ThePadawan ThePadawan commented Mar 10, 2017

Thank you so much, I will try this out ASAP 🍠 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants
You can’t perform that action at this time.