maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/Makefile

94 lines
2.8 KiB
Makefile
Raw Normal View History

Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
SHELL=/bin/bash
Install GoMetaLinter in Travis And also rejigger the Makefiles to properly error if it's missing.
2017-06-21 23:23:48 +02:00
.SHELLFLAGS=-e
Rename pulumi/lumi to pulumi/pulumi-fabric We are renaming Lumi to Pulumi Fabric. This change simply renames the pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other changes that will follow soon afterwards.
2017-08-02 18:25:22 +02:00
PROJECT=github.com/pulumi/pulumi-fabric
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
PROJECT_PKGS=$(shell go list ./cmd/... ./pkg/... | grep -v /vendor/)
Test more examples Tests all of our commonly used examples. Also sets test parallelism to 10 by default since we are I/O bound on API calls to the resource providers. Also avoids using larger EC2 examples in our samples so that we can keep our test costs lower :-).
2017-06-16 02:42:53 +02:00
TESTPARALLELISM=10
Sketch a `mu build` command and its scaffolding This adds a bunch of general scaffolding and the beginning of a `build` command. The general engineering scaffolding includes: * Glide for dependency management. * A Makefile that runs govet and golint during builds. * Google's Glog library for logging. * Cobra for command line functionality. The Mu-specific scaffolding includes some packages: * mu/pkg/diag: A package for compiler-like diagnostics. It's fairly barebones at the moment, however we can embellish this over time. * mu/pkg/errors: A package containing Mu's predefined set of errors. * mu/pkg/workspace: A package containing workspace-related convenience helpers. in addition to a main entrypoint that simply wires up and invokes the CLI. From there, the mu/cmd package takes over, with the Cobra-defined CLI commands. Finally, the mu/pkg/compiler package actually implements the compiler behavior. Or, it will. For now, it simply parses a JSON or YAML Mufile into the core mu/pkg/api types, and prints out the result.
2016-11-15 20:30:34 +01:00
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
ECHO=echo -e
Disable gotype linter This disables gotype as a linter, since it depends on object files in an annoying way (and doesn't add much beyond go build anyway). From alecthomas/gometalinter#206, it sounds like the current plan is to remove gotype entirely from the set of linters GML runs.
2017-06-21 23:46:03 +02:00
GOMETALINTERBIN=gometalinter
Tidy up more lint This change fixes a few things: * Most importantly, we need to place a leading "." in the paths to Gometalinter, otherwise some sub-linters just silently skip the directory altogether. errcheck is one such linter, which is a very important one! * Use an explicit Gometalinter.json file to configure the various settings. This flips on a few additional linters that aren't on by default (line line length checking). Sadly, a few that I'd like to enable take waaaay too much time, so in the future we may consider a nightly job (this includes code similarity, unused parameters, unused functions, and others that generally require global analysis). * Now that we're running more, however, linting takes a while! The core Lumi project now takes 26 seconds to lint on my laptop. That's not terrible, but it's long enough that we don't want to do the silly "run them twice" thing our Makefiles were previously doing. Instead, we shall deploy some $$($${PIPESTATUS[1]}-1))-fu to rely on the fact that grep returns 1 on "zero lines". * Finally, fix the many issues that this turned up. I think(?) we are done, except, of course, for needing to drive down some of the cyclomatic complexity issues (which I'm possibly going to punt on; see pulumi/lumi#259 for more details).
2017-06-22 21:09:46 +02:00
GOMETALINTER=${GOMETALINTERBIN} --config=Gometalinter.json
Disable gotype linter This disables gotype as a linter, since it depends on object files in an annoying way (and doesn't add much beyond go build anyway). From alecthomas/gometalinter#206, it sounds like the current plan is to remove gotype entirely from the set of linters GML runs.
2017-06-21 23:46:03 +02:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: default
Install before test The tests can depend on the lumi binary (e.g., for integration testing), so we need to run install before test in the Makefile.
2017-08-06 17:44:04 +02:00
default: banner vet install test lint_quiet
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: all
Install before test The tests can depend on the lumi binary (e.g., for integration testing), so we need to run install before test in the Makefile.
2017-08-06 17:44:04 +02:00
all: banner_all vet install test lint_quiet lumijs lumirtpkg lumijspkg lumipkg
Add nightly build target Adds a nightly build target that runs the long running provider and examples tests. Enables travis to run this on cron jobs, which we will configure to trigger nightly.
2017-06-16 18:50:56 +02:00
.PHONY: nightly
Run integration tests This change runs the examples integration tests for every test run. They used to be split out because the AWS tests take so long, but now those are in their own separate package. Running the integration tests here more frequently will prevent breaking the most basic Lumi CLI commands and capabilities.
2017-08-06 17:26:20 +02:00
nightly: all gocover
Update to Go 1.8.2
2017-05-24 20:58:58 +02:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: banner
Update to Go 1.8.2
2017-05-24 20:58:58 +02:00
banner:
Rename pulumi/lumi to pulumi/pulumi-fabric We are renaming Lumi to Pulumi Fabric. This change simply renames the pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other changes that will follow soon afterwards.
2017-08-02 18:25:22 +02:00
@$(ECHO) "\033[1;37m=====================\033[0m"
@$(ECHO) "\033[1;37mPulumi Fabric (Quick)\033[0m"
@$(ECHO) "\033[1;37m=====================\033[0m"
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;33mRunning quick build; to run full tests, run 'make all'\033[0m"
@$(ECHO) "\033[0;33mRemember to do this before checkin, otherwise your CI will fail\033[0m"
Only run quick tests for `make`; add a `make full` target The AWS tests take a while to run and it's easy to forget. Further, they are going to start taking quite a bit longer very soon. So, this change introduces a `make full` target, which is what our CI tests run. But the ordinary `make` skips the long tests for faster inner loop verification. Over time, I'm sure we'll get far more sophisticated with the split between inner vs. outer loop testing, especially for performance, stress, and so on.
2017-06-02 19:30:57 +02:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: banner_all
banner_all:
Rename pulumi/lumi to pulumi/pulumi-fabric We are renaming Lumi to Pulumi Fabric. This change simply renames the pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other changes that will follow soon afterwards.
2017-08-02 18:25:22 +02:00
@$(ECHO) "\033[1;37m====================\033[0m"
@$(ECHO) "\033[1;37mPulumi Fabric (Full)\033[0m"
@$(ECHO) "\033[1;37m====================\033[0m"
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: install
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
install:
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;32mINSTALL:\033[0m"
Fix some lint in our lint After 233c5a8 landed, I noticed there are a few things to be fixed up: * Run gometalinter in all the right places. We need to run both in lint and lint_quiet targets. I've also cleaned up some of the logic around what to suppress so there's less repetition. * We currently @ meaningful commands, which is unfortunate, since it makes debugging Makefiles tough (especially when looking at CI build logs). Going forward, we should only use @ for meaningless commands, like @echo. * The AWS project wasn't actually running tslint, because it needs to say `tslint './pack/**/*.ts' --exclude='./pack/node_modules/**'`. The current script of `tslint lib/aws/pack/...` wasn't actually running lint, hence we missed a lot of AWS lint issues. * Fix up the issues that these fixes uncovered. Mostly err shadowing.
2017-06-21 22:24:35 +02:00
go install ${PROJECT}/cmd/lumi
go install ${PROJECT}/cmd/lumidl
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: lint
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
lint:
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;32mLINT:\033[0m"
Tidy up more lint This change fixes a few things: * Most importantly, we need to place a leading "." in the paths to Gometalinter, otherwise some sub-linters just silently skip the directory altogether. errcheck is one such linter, which is a very important one! * Use an explicit Gometalinter.json file to configure the various settings. This flips on a few additional linters that aren't on by default (line line length checking). Sadly, a few that I'd like to enable take waaaay too much time, so in the future we may consider a nightly job (this includes code similarity, unused parameters, unused functions, and others that generally require global analysis). * Now that we're running more, however, linting takes a while! The core Lumi project now takes 26 seconds to lint on my laptop. That's not terrible, but it's long enough that we don't want to do the silly "run them twice" thing our Makefiles were previously doing. Instead, we shall deploy some $$($${PIPESTATUS[1]}-1))-fu to rely on the fact that grep returns 1 on "zero lines". * Finally, fix the many issues that this turned up. I think(?) we are done, except, of course, for needing to drive down some of the cyclomatic complexity issues (which I'm possibly going to punt on; see pulumi/lumi#259 for more details).
2017-06-22 21:09:46 +02:00
$(GOMETALINTER) ./pkg/... | sort ; exit "$${PIPESTATUS[0]}"
$(GOMETALINTER) ./cmd/lumi/... | sort ; exit "$${PIPESTATUS[0]}"
$(GOMETALINTER) ./cmd/lumidl/... | sort ; exit "$${PIPESTATUS[0]}"
Fix some lint in our lint After 233c5a8 landed, I noticed there are a few things to be fixed up: * Run gometalinter in all the right places. We need to run both in lint and lint_quiet targets. I've also cleaned up some of the logic around what to suppress so there's less repetition. * We currently @ meaningful commands, which is unfortunate, since it makes debugging Makefiles tough (especially when looking at CI build logs). Going forward, we should only use @ for meaningless commands, like @echo. * The AWS project wasn't actually running tslint, because it needs to say `tslint './pack/**/*.ts' --exclude='./pack/node_modules/**'`. The current script of `tslint lib/aws/pack/...` wasn't actually running lint, hence we missed a lot of AWS lint issues. * Fix up the issues that these fixes uncovered. Mostly err shadowing.
2017-06-21 22:24:35 +02:00
# In quiet mode, suppress some messages.
Rename pulumi/lumi to pulumi/pulumi-fabric We are renaming Lumi to Pulumi Fabric. This change simply renames the pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other changes that will follow soon afterwards.
2017-08-02 18:25:22 +02:00
# - "or be unexported": TODO[pulumi/pulumi-fabric#191]: will fix when we write all of our API docs
Fix some lint in our lint After 233c5a8 landed, I noticed there are a few things to be fixed up: * Run gometalinter in all the right places. We need to run both in lint and lint_quiet targets. I've also cleaned up some of the logic around what to suppress so there's less repetition. * We currently @ meaningful commands, which is unfortunate, since it makes debugging Makefiles tough (especially when looking at CI build logs). Going forward, we should only use @ for meaningless commands, like @echo. * The AWS project wasn't actually running tslint, because it needs to say `tslint './pack/**/*.ts' --exclude='./pack/node_modules/**'`. The current script of `tslint lib/aws/pack/...` wasn't actually running lint, hence we missed a lot of AWS lint issues. * Fix up the issues that these fixes uncovered. Mostly err shadowing.
2017-06-21 22:24:35 +02:00
# - "Subprocess launching with variable": we intentionally launch processes dynamically.
Rename pulumi/lumi to pulumi/pulumi-fabric We are renaming Lumi to Pulumi Fabric. This change simply renames the pulumi/lumi repo to pulumi/pulumi-fabric, without the CLI tools and other changes that will follow soon afterwards.
2017-08-02 18:25:22 +02:00
# - "cyclomatic complexity" (disabled in config): TODO[pulumi/pulumi-fabric#259]: need to fix many of these.
Tidy up more lint This change fixes a few things: * Most importantly, we need to place a leading "." in the paths to Gometalinter, otherwise some sub-linters just silently skip the directory altogether. errcheck is one such linter, which is a very important one! * Use an explicit Gometalinter.json file to configure the various settings. This flips on a few additional linters that aren't on by default (line line length checking). Sadly, a few that I'd like to enable take waaaay too much time, so in the future we may consider a nightly job (this includes code similarity, unused parameters, unused functions, and others that generally require global analysis). * Now that we're running more, however, linting takes a while! The core Lumi project now takes 26 seconds to lint on my laptop. That's not terrible, but it's long enough that we don't want to do the silly "run them twice" thing our Makefiles were previously doing. Instead, we shall deploy some $$($${PIPESTATUS[1]}-1))-fu to rely on the fact that grep returns 1 on "zero lines". * Finally, fix the many issues that this turned up. I think(?) we are done, except, of course, for needing to drive down some of the cyclomatic complexity issues (which I'm possibly going to punt on; see pulumi/lumi#259 for more details).
2017-06-22 21:09:46 +02:00
LINT_SUPPRESS="or be unexported|Subprocess launching with variable"
A few tweaks to lint fixes
2017-06-14 01:47:55 +02:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: lint_quiet
Run golint during make This change runs golint during make by default, but suppresses the class of errors we are currently permitting into the code (just those about public documentation on APIs).
2017-04-12 20:01:16 +02:00
lint_quiet:
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;32mLINT (quiet):\033[0m"
Tidy up more lint This change fixes a few things: * Most importantly, we need to place a leading "." in the paths to Gometalinter, otherwise some sub-linters just silently skip the directory altogether. errcheck is one such linter, which is a very important one! * Use an explicit Gometalinter.json file to configure the various settings. This flips on a few additional linters that aren't on by default (line line length checking). Sadly, a few that I'd like to enable take waaaay too much time, so in the future we may consider a nightly job (this includes code similarity, unused parameters, unused functions, and others that generally require global analysis). * Now that we're running more, however, linting takes a while! The core Lumi project now takes 26 seconds to lint on my laptop. That's not terrible, but it's long enough that we don't want to do the silly "run them twice" thing our Makefiles were previously doing. Instead, we shall deploy some $$($${PIPESTATUS[1]}-1))-fu to rely on the fact that grep returns 1 on "zero lines". * Finally, fix the many issues that this turned up. I think(?) we are done, except, of course, for needing to drive down some of the cyclomatic complexity issues (which I'm possibly going to punt on; see pulumi/lumi#259 for more details).
2017-06-22 21:09:46 +02:00
$(GOMETALINTER) ./pkg/... | grep -vE ${LINT_SUPPRESS} | sort ; exit $$(($${PIPESTATUS[1]}-1))
$(GOMETALINTER) ./cmd/lumi/... | grep -vE ${LINT_SUPPRESS} | sort ; exit $$(($${PIPESTATUS[1]}-1))
$(GOMETALINTER) ./cmd/lumidl/... | grep -vE ${LINT_SUPPRESS} | sort ; exit $$(($${PIPESTATUS[1]}-1))
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;33mlint was run quietly; to run with noisy errors, run 'make lint'\033[0m"
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: vet
vet:
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;32mVET:\033[0m"
Fix some lint in our lint After 233c5a8 landed, I noticed there are a few things to be fixed up: * Run gometalinter in all the right places. We need to run both in lint and lint_quiet targets. I've also cleaned up some of the logic around what to suppress so there's less repetition. * We currently @ meaningful commands, which is unfortunate, since it makes debugging Makefiles tough (especially when looking at CI build logs). Going forward, we should only use @ for meaningless commands, like @echo. * The AWS project wasn't actually running tslint, because it needs to say `tslint './pack/**/*.ts' --exclude='./pack/node_modules/**'`. The current script of `tslint lib/aws/pack/...` wasn't actually running lint, hence we missed a lot of AWS lint issues. * Fix up the issues that these fixes uncovered. Mostly err shadowing.
2017-06-21 22:24:35 +02:00
go tool vet -printf=false cmd/ pkg/
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: test
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
test:
Switch to /bin/bash as the shell for our Makefiles This should fix the issues with escaping in Travis (fingers crossed). Also specifies the -e flag for echo, since switching the shell to bash led to ANSI escape codes being uninterpreted by default.
2017-06-22 23:57:09 +02:00
@$(ECHO) "\033[0;32mTEST:\033[0m"
Run integration tests This change runs the examples integration tests for every test run. They used to be split out because the AWS tests take so long, but now those are in their own separate package. Running the integration tests here more frequently will prevent breaking the most basic Lumi CLI commands and capabilities.
2017-08-06 17:26:20 +02:00
go test -cover -parallel ${TESTPARALLELISM} ${PROJECT_PKGS} ./examples
Enable parallel tests This change enables parallelism for our tests. It also introdues a `test_core` Makefile target to just run the core engine tests, and not the providers, since they take a long time. This is intended only as part of the inner developer loop.
2017-06-01 23:01:26 +02:00
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
.PHONY: lumijs
lumijs:
@cd ./cmd/lumijs && $(MAKE)
Clean up the Makefile This adds a bunch of independent targets to the Makefile, to help run individual commands as needed. It also skips running `golint` by default (per golint's advice, actually), because it spews lots of documentation-related things at the moment, which we are intentionally ignoring. (Mainly just hundreds of public members without comments; eventually we'll need to tackle this.)
2017-01-28 00:42:55 +01:00
Refactor runtime functionality This change splits the core Lumi library -- which is meant to be a pure LumiJS library without any special status -- from the runtime library -- which is really meant to be the underpinnings of "special" functionality that integrates with the runtime in sophisticated ways. After this change, LumiRT is at the very bottom, and, despite it using a subset of LumiJS, it must not trigger any functionality that would mandate the use of the LumiJS runtime library. Atop that, the LumiJS library is layered. And finally, above that, Lumi depends on LumiJS.
2017-06-14 03:11:59 +02:00
lumirtpkg:
@cd ./lib/lumirt && $(MAKE)
Also build the Lumi stdlib during `make all`
2017-06-02 23:50:35 +02:00
lumijspkg:
@cd ./lib/lumijs && $(MAKE)
Refactor runtime functionality This change splits the core Lumi library -- which is meant to be a pure LumiJS library without any special status -- from the runtime library -- which is really meant to be the underpinnings of "special" functionality that integrates with the runtime in sophisticated ways. After this change, LumiRT is at the very bottom, and, despite it using a subset of LumiJS, it must not trigger any functionality that would mandate the use of the LumiJS runtime library. Atop that, the LumiJS library is layered. And finally, above that, Lumi depends on LumiJS.
2017-06-14 03:11:59 +02:00
lumipkg:
@cd ./lib/lumi && $(MAKE)
Goodbye, custom AWS provider code :disappointed_relieved: Preparing to RI the tfbridge branch into master.
2017-07-21 23:36:58 +02:00
.PHONY: lumirtpkg lumijspkg lumipkg
Makeify more; add a "full build" target (#193) * Makeify more; add a "full build" target This change uses make for more of our tree. Namely, the AWS provider and LumiJS compilers each now use make to build and/or install them. Not only does this bring about some consistency to how we build and test things, but also made it easy to add a full build target: $ make all This target will build, test, and install the core Go tools, the LumiJS compiler, and the AWS provider, in that order. Each can be made in isolation, however, which ensures that the inner loop for those is fast and so that, when it comes to finishing pulumi/lumi#147, we can easily split them out and make from the top.
2017-06-02 23:26:34 +02:00
Publish built binaries upon successful push CI to master This adds a new make target, publish, that will create a release package and upload it to an S3 bucket. This package simply contains the built CLI plus the core library packages, lumi, lumirt, and lumijs. This target is invoked automatically at the end of a successful Travis run against a push to master.
2017-07-20 20:06:24 +02:00
publish:
Make a publish script; fix sed for multi-OS compat This change creates a scripts/ folder, moves our existing shell script, gocover.sh, underneath it, and factors the publish logic out of the Makefile and into the publish.sh file. The syntax for sed differs between Mac OS X and GNU versions of the tool, which is rather annoying. This fixes it by leveraging the fact that `sed -i.bak ...` works, although we now need to clean up the *.bak file left behind. (No big deal and way better than maintaining OS-dependent logic.)
2017-07-21 18:37:14 +02:00
@$(ECHO) "\033[0;32mPublishing current release:\033[0m"
./scripts/publish.sh
Publish built binaries upon successful push CI to master This adds a new make target, publish, that will create a release package and upload it to an S3 bucket. This package simply contains the built CLI plus the core library packages, lumi, lumirt, and lumijs. This target is invoked automatically at the end of a successful Travis run against a push to master.
2017-07-20 20:06:24 +02:00
.PHONY: publish
Sketch a `mu build` command and its scaffolding This adds a bunch of general scaffolding and the beginning of a `build` command. The general engineering scaffolding includes: * Glide for dependency management. * A Makefile that runs govet and golint during builds. * Google's Glog library for logging. * Cobra for command line functionality. The Mu-specific scaffolding includes some packages: * mu/pkg/diag: A package for compiler-like diagnostics. It's fairly barebones at the moment, however we can embellish this over time. * mu/pkg/errors: A package containing Mu's predefined set of errors. * mu/pkg/workspace: A package containing workspace-related convenience helpers. in addition to a main entrypoint that simply wires up and invokes the CLI. From there, the mu/cmd package takes over, with the Cobra-defined CLI commands. Finally, the mu/pkg/compiler package actually implements the compiler behavior. Or, it will. For now, it simply parses a JSON or YAML Mufile into the core mu/pkg/api types, and prints out the result.
2016-11-15 20:30:34 +01:00
Add Go code coverage reports to nightly tests Adds a make task to generate code coverage for all Go sources. That make task re-runs the tests, and can be fairly expensive, so it is enabled only in the nightly tests for now. Part of #206.
2017-06-24 00:11:20 +02:00
.PHONY: gocover
gocover:
@$(ECHO) "\033[0;32mGO CODE COVERAGE:\033[0m"
Make a publish script; fix sed for multi-OS compat This change creates a scripts/ folder, moves our existing shell script, gocover.sh, underneath it, and factors the publish logic out of the Makefile and into the publish.sh file. The syntax for sed differs between Mac OS X and GNU versions of the tool, which is rather annoying. This fixes it by leveraging the fact that `sed -i.bak ...` works, although we now need to clean up the *.bak file left behind. (No big deal and way better than maintaining OS-dependent logic.)
2017-07-21 18:37:14 +02:00
./scripts/gocover.sh
Add Go code coverage reports to nightly tests Adds a make task to generate code coverage for all Go sources. That make task re-runs the tests, and can be fairly expensive, so it is enabled only in the nightly tests for now. Part of #206.
2017-06-24 00:11:20 +02:00
Reference in a new issue Copy permalink