tequilaOS/platform_build_blueprint
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
platform_build_blueprint/.travis.yml

27 lines
461 B
YAML
Raw Normal View History

Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
language: go
Update travis to use go 1.5 Update .travis.yml to specify go 1.5.1, and update build.ninja.in to include the new in line function names used by go 1.5.
2015-11-09 21:56:38 +01:00
go:
- 1.5.1
Switch to custom-built ninja v1.6.0
2015-07-24 05:27:41 +02:00
cache:
directories:
- $HOME/ninjabin
Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
install:
Switch to custom-built ninja v1.6.0
2015-07-24 05:27:41 +02:00
- ./.travis.install-ninja.sh
- export PATH=$PATH:~/ninjabin
Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
Fix running travis on forked repos If we're not on the official repo, link the directory structure around so that go can still find the code.
2015-07-24 03:19:18 +02:00
before_script:
- source .travis.fix-fork.sh
Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
script:
Enforce gofmt in travis Run gofmt -l . during travis to catch pull requests that have not had gofmt run on them. Change-Id: Ibfdf988a535d82721f3c4bc328b189f606f12778
2016-08-11 19:12:46 +02:00
- ./.travis.gofmt.sh
Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
- go test ./...
- mkdir stage
Add build wrapper to do stage selection before ninja This wrapper script can be used instead of ninja to ensure the build won't get stuck building the primary builder. An example of when this would happen: 1. Do a successful build 2. Sync/make a change in the primary builder (soong, etc) that depends on a blueprint change. 3. The next build would notice that change, and rewind to the primary stage to rebuild the builder. That build would fail. 4. Sync/fix the blueprint code. 5. The next build would still fail. The bootstrap stage would need to be run in order to fix the primary stage, but we're still stuck in the primary stage. The only way to switch stages is to successfully complete everything required to choose the next stage. This generally isn't a problem in the main stage, since there is no code being built in the dependency chain leading up to stage selection. Any existing wrappers (like soong) can execute this wrapper (optionally skipping ninja execution) if they're worried about the above situation. This isn't strictly required -- running ninja directly will still work in most cases, you'll just need to re-run bootstrap.bash if you get into a bad state. Change-Id: I5901d7240a1daa388a786ceb1c8259502fc14058
2015-12-10 03:03:13 +01:00
- cd stage
Add .travis.yml to configure CI
2015-03-21 06:53:30 +01:00
- ../bootstrap.bash
Add build wrapper to do stage selection before ninja This wrapper script can be used instead of ninja to ensure the build won't get stuck building the primary builder. An example of when this would happen: 1. Do a successful build 2. Sync/make a change in the primary builder (soong, etc) that depends on a blueprint change. 3. The next build would notice that change, and rewind to the primary stage to rebuild the builder. That build would fail. 4. Sync/fix the blueprint code. 5. The next build would still fail. The bootstrap stage would need to be run in order to fix the primary stage, but we're still stuck in the primary stage. The only way to switch stages is to successfully complete everything required to choose the next stage. This generally isn't a problem in the main stage, since there is no code being built in the dependency chain leading up to stage selection. Any existing wrappers (like soong) can execute this wrapper (optionally skipping ninja execution) if they're worried about the above situation. This isn't strictly required -- running ninja directly will still work in most cases, you'll just need to re-run bootstrap.bash if you get into a bad state. Change-Id: I5901d7240a1daa388a786ceb1c8259502fc14058
2015-12-10 03:03:13 +01:00
- ./blueprint.bash
Simplify bootstrap tl;dr: Read if you don't use the wrapper or use SKIP_NINJA Previously, we were relying on the ninja behavior of restarting the build when the build.ninja file was updated to switch between different bootstrap stages. But that means that every step that could produce a build.ninja must pass in order to switch to a different stage. That wasn't a big problem when we had a two stage build -- there was very little that could fail in the second stage before we chose to go back to the first stage. But when we had a three stage build, it was possible to get into a state (usually during development) where you were in the second stage, but the build was failing because the first stage needed to be run. This was fixed in d79f1af7423e0ef7a13573efdae5100a57fabc82 by adding a wrapper that always started building at the first stage. But this kept all of the complexity of using ninja restarts without any of the benefits, so this change removes that complexity and just runs each stage sequentially in the wrapper. So the wrapper is now required. Since we're no longer going through choosestage, we can also skip the template parsing for the later stages that don't need to be templated -- this can save a couple of seconds for large files. In addition to all of the above, this also lets Soong reduce the number of times the main ninja file is loaded. We had been running the wrapper once (3 stages), then running ninja again after combining the Soong-generated build.ninja with the Kati-generated build.ninja. This change lets us removing the intermediate parsing of Soong's build.ninja, so that we only execute ninja 3 times per build. It also lets us have dependencies on pools or rules from Kati in the primary builder, since we're never executing the main build.ninja without the Kati build.ninja. The wrapper has a new option, NINJA to provide the path to ninja. This used to be hardcoded to `ninja`, and will still default to that. But we'll be running the first two bootstrap stages with $NINJA even if SKIP_NINJA is set. The wrapper passes "-w dupbuild=err" to ninja now -- this really should always be turned on if you care about reliable builds. Change-Id: I6f656b74eb3d064b8b9e69d1d6dac1129d72b747
2016-08-13 21:42:11 +02:00
- diff -us ../build.ninja.in .minibootstrap/build.ninja.in
Add test suite for bootstrapping This only checks to make sure that for a given updated file, the bootstrap stage is properly run. It doesn't actually check to make sure that anything was rebuilt. Change-Id: I9cb6ff1d483264da30e43d5580361d93b148f42c
2015-07-23 02:05:51 +02:00
- ../tests/test.sh
Import globbing from Soong Add globbing with dependency checking to blueprint. Calling ModuleContext.GlobWithDeps or SingletonContext.GlobWithDeps will return a list of files that match the globs, while also adding efficient dependencies to rerun the primary builder if a file that matches the glob is added or removed. Also use the globbing support for optional_subdirs=, subdirs= and build= lines in blueprints files. The globbing slightly changes the behavior of subname= lines, it no longer falls back to looking for a file called "Blueprints". Blueprint files that need to include a subdirectory with a different name can use build= instead of subdir= to directly include them. The Blueprints file is updated to reset subname="Blueprints" in case we want to include subdirectories inside blueprint and the primary builder has changed the subname. Also adds a new test directory that contains a simple primary builder tree to test regeneration for globbing, and runs the tests in travis. Change-Id: I83ce525fd11e11579cc58ba5308d01ca8eea7bc6
2016-11-01 19:10:51 +01:00
- ../tests/test_tree_tests.sh
Reference in a new issue Copy permalink