Commit graph

86 commits

Author SHA1 Message Date
Karthik Rajasekaran
54df3398ea Allow nuget packages to be configured 2017-03-16 12:47:02 -07:00
Karthik Rajasekaran
ed145b37a6 Allow bootstrap directory to be configured 2017-03-10 17:46:12 -08:00
Justin Goshi
663df18046 Unpin stage0 version now that we build the linux portable (#5981) 2017-03-09 09:29:07 -10:00
Justin Goshi
113924eebd Add support to build linux portable (#5938)
* Add support to build with the linux portable

* Pass targets to run for the linux portable

* Address PR comments

* Update the bootstrapper version

* Address the PR comments for improving the help text

* Fixing permissions
2017-03-08 13:37:06 -10:00
Justin Goshi
45a1e9e56c Allow host info passed in from the command line to override machine settings (#5904)
* Allow host info passed in from the command line to override machine settings

* Simplify the logic

* Address PR comments to keep a separate HostRid and HostOSName that are static

* Rename to BuildInfo.props

* Address PR comments

* Fix the previous merge

* Fix spacing

* Address PR comments
2017-03-08 09:10:53 -10:00
Piotr Puszkiewicz
8ca21b67f9 Add relative paths, add logs by default 2017-02-27 17:19:39 -08:00
Omair Majid
d999f22788 Use dotnet-install from the cli master branch
During the cli build, the cli downloads and executes the bootstrap
script from buildtools. The bootstrap script then downloads and executes
the dotnet-install script from cli, but in the 'rel/1.0.0' branch, not
the master branch.

This means that someone building cli's master branch will end up using
the dotnet-install.sh or dotnet-install.ps1 script from cli's rel/1.0.0
branch.

Fix that by telling the bootstrap script to download and use the version
of dotnet-install script from the master branch (which is the current
branch the user is building).

Ideally, we would just call the dotnet-install script in the current
repo/branch, but because the bootstrap script sits in the middle and is
part of a different repository, we can't.

This is a workaround for #5410.
2017-02-13 14:12:19 -05:00
Justin Goshi
50493d2dab Address PR comments 2017-02-08 14:02:29 -08:00
Justin Goshi
2b15651716 Trying to fix the build breaks first 2017-02-07 17:34:41 -08:00
Justin Goshi
b927922b65 Address PR comments and fix build break 2017-02-07 16:52:08 -08:00
Justin Goshi
83b46ebc17 Generate host and build info and store them in .props files 2017-02-07 15:45:19 -08:00
Eric Erhardt
5186d783e8 Update run-build to install the latest stage0 from the master channel. 2017-01-24 12:30:57 -06:00
Eric Erhardt
c481ad9cdc Merge all hard-coded versions and version suffixes to be defined in a single spot. 2017-01-10 20:54:11 -06:00
Livar Cunha
b41eb43883 Updating our projects and test assets to work with the latest SDK. 2017-01-05 19:44:52 -08:00
Livar Cunha
72cd3d7c43 Pinning stage0 to latest and reverting build scripts to use stage0 for now. 2017-01-05 12:40:23 -08:00
Livar Cunha
92ee4aac26 Pinning the CLI version because once this goes in, the next stage0 won't allow for having compile in the csprojs. We will have to update the CLI ones. 2017-01-05 12:31:49 -08:00
Piotr Puszkiewicz
2fbafe6f3f Remove StreamForwarder from CLI tests (#4936)
* WiP

* Replace StreamForwarder with OutputDataReceived

* Add build logging around test execution

* add newlines

* Add handling for the null terminator while maintaining empty lines

* Extra Diag

* Verbose logging for VS Test Console

* Fix asset file locking tests

* Add testcommand timeout + improve dotnet-new tests

* WiP

* Welcome, JoSequ!

* Fix failing tests

* Clean out diagnostics writelines

* self-PR1
2016-12-13 14:15:35 -08:00
Piotr Puszkiewicz
fd9cb55f1a Add msbuild-based stage0 where possible (#4597)
* Add msbuild-based stage0 where possible

* Fix bash initialization script

* Windows Fixes

* Fix dotnet deb tool
2016-11-02 23:01:57 -07:00
Davis Goodin
59a6c72be7 Use --disable-parallel during xplat restores.
Works around NuGet parallel restore timeouts becoming build failures when the machine has a slow connection, for example in our Docker Fedora containers.
2016-10-28 10:53:56 -05:00
Chris R
95f49e6636
Fix build scripts to pass architecture into the bootstrapper. 2016-10-27 11:56:57 -05:00
Chris Rummel
007cfc1f9b Switch to using new bootstrap script to initialize buildtools. (#4349)
* Switch to using new bootstrap script to initialize buildtools.

* Set up the version-specific shared runtime symlink in run-build so buildtools doesn't have to care about it.

* Address code review feedback.

* Addressed code review feedback.

* Change to using bootstrap script for Linux build as well.

* Change to using latest for CLI.
2016-10-25 16:51:41 -07:00
Livar Cunha
0cc3d751e8 Fixes the build by switching our build command to dotnet msbuild, instead of dotnet build3, which expects a Build target. 2016-09-23 09:03:57 -07:00
Piotr Puszkiewicz
43c5a2c59b multi-proc test execution 2016-08-18 17:10:20 -07:00
Jonathan Miller
3a6e15309e Bringing run.exe into the repo and starting with the clean command 2016-07-26 16:15:36 -07:00
Livar Cunha
fd077bbf28 Adding a comment about the code that removes empty spaces from the arguments array but also breaks quoted arguments. We are picking the devil we know in this case. 2016-07-12 11:23:34 -07:00
Livar Cunha
eaf9d9603d Fixing logic to remove already processed arguments in the case of bash scripts and adding a missing come in the case of the powershell script. 2016-07-08 16:40:44 -07:00
Livar Cunha
b1ca63c7de Because we are using a CI that is still built for our old custom build, we are passing arguments there that we no longer need and that MSBuild does not understand. We can't pass them along to MSBuild, so we need to filter them out. This is what we are doing here. 2016-07-08 16:10:08 -07:00
Livar Cunha
3d44a2b189 Adding support to pass parameters to msbuild through build.sh. Now we need to do it for powershell. 2016-07-08 13:38:57 -07:00
Livar Cunha
c2fdd41764 Aligning the two versions of run-build we have in what each do and the parameters they get. 2016-07-07 16:16:53 -07:00
Livar Cunha
ffe995fbab Reverting the change to run-build.sh to handle additional parameters. I don't want to hold this PR for that work. having CI running is more important. 2016-07-06 16:52:58 -07:00
Livar Cunha
5d40e8b734 Fixing Ubuntu packaging issue, part 99 of hopefully 99. 2016-07-06 16:45:41 -07:00
Livar Cunha
8eb05a4deb Addressing code review comments and fixing another issue with deb installer generation. 2016-07-06 14:45:07 -07:00
Livar Cunha
f400160a09 Trying to fix the ubuntu package generation break. I believe it happened because we were loading branchinfo in the init-tools, which means that the env variables defined there were not applied to commands ran from run-build.sh. 2016-07-06 13:35:34 -07:00
Livar Cunha
7e71a0217a Moving a bunch of code from init-tools to run-build.sh because of how exporting works in chained bash scripts. Something down in the tree does not flow back up. 2016-07-06 12:32:38 -07:00
Livar Cunha
889f4c3ec8 Fixing permissions for init-tools.sh and run-build.sh. 2016-07-06 12:04:59 -07:00
Livar Cunha
cdddc2e432 Addressing code review comments. Fixing issue with compile where we were not copying the msbuild files to the right place. Fixed an issue where we were trying to download installers for OSes that don't have installers. Added init-tools scripts. 2016-07-06 12:03:16 -07:00