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

102 lines
3 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
Fix Makefile on Fedora
2017-08-24 01:51:16 +02:00
.SHELLFLAGS=-ec
Install GoMetaLinter in Travis And also rejigger the Makefiles to properly error if it's missing.
2017-06-21 23:23:48 +02:00
Rename pulumi-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
PROJECT=github.com/pulumi/pulumi
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/)
Restore TESTPARALLELISM to 10 Now that we no longer recursively call yarn via yarn run and scripts, we can use a `--mutex network` directive in a .yarnrc file at the root of the repository to prevent multiple copies of yarn running concurrently.
2017-10-14 00:45:50 +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
Construct version based on git information We use `git describe --tags` to construct a version number based on the current version tag. The properties VERSION (when using make) and Version (when using MSBuild) can be explicitly set to use a fixed value instead. Fixes #13
2017-10-16 22:50:00 +02:00
VERSION=$(shell git describe --tags 2>/dev/null)
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
Use explicit targets in Makefile for Travis Defer build and publish logic into the makefiles instead of trying to use Travis to do so. This let's us sidestep Travis's not great error handling (see pulumi/home#21 for more details)
2017-09-28 20:53:08 +02:00
.PHONY: all
Wire up Lumi to the new runtime strategy :fire: :fire: :fire: :boat: :fire: :fire: :fire: Getting closer on #311.
2017-08-30 03:24:12 +02:00
all: banner_all core sdk/nodejs integrationtest
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
Use explicit targets in Makefile for Travis Defer build and publish logic into the makefiles instead of trying to use Travis to do so. This let's us sidestep Travis's not great error handling (see pulumi/home#21 for more details)
2017-09-28 20:53:08 +02:00
nightly: all gocover
Make all by default
2017-08-06 17:52:32 +02:00
.PHONY: core
Drop explicit `vet` target Gometalinter runs `vet` as one of the many linters, so we need not run it again.
2017-11-01 00:49:15 +01:00
core: test install lint
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"
Construct version based on git information We use `git describe --tags` to construct a version number based on the current version tag. The properties VERSION (when using make) and Version (when using MSBuild) can be explicitly set to use a fixed value instead. Fixes #13
2017-10-16 22:50:00 +02:00
go install -ldflags "-X main.version=${VERSION}" ${PROJECT}
go install -ldflags "-X main.version=${VERSION}" ${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
Track resources that are pending deletion in checkpoints. During the course of a `pulumi update`, it is possible for a resource to become slated for deletion. In the case that this deletion is part of a replacement, another resource with the same URN as the to-be-deleted resource will have been created earlier. If the `update` fails after the replacement resource is created but before the original resource has been deleted, the snapshot must capture that the original resource still exists and should be deleted in a future update without losing track of the order in which the deletion must occur relative to other deletes. Currently, we are unable to track this information because the our checkpoints require that no two resources have the same URN. To fix this, these changes introduce to the update engine the notion of a resource that is pending deletion and change checkpoint serialization to use an array of resources rather than a map. The meaning of the former is straightforward: a resource that is pending deletion should be deleted during the next update. This is a fairly major breaking change to our checkpoint files, as the map of resources is no more. Happily, though, it makes our checkpoint files a bit more "obvious" to any tooling that might want to grovel or rewrite them. Fixes #432, #387.
2017-10-05 23:08:35 +02:00
.PHONY: format
format:
find . -iname "*.go" -not -path "./vendor/*" | xargs gofmt -s -w
Rename `lint_quiet` to `lint` We have some lint debt (around exported functions being underdocumented) so we have a custom target that ignores some lint warnings. However, that target (which is the only lint target that needs to be clean to check in) is called `lint_quiet` instead of `lint` which is our normal linting target. Rename the target so your fingers can learn that `make lint` is always the right way to run linting before checkin.
2017-11-01 00:39:23 +01:00
.PHONY: lint_full
lint_full:
@$(ECHO) "\033[0;32mLINT (full):\033[0m"
Rename pulumi-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
$(GOMETALINTER) main.go | sort ; exit "$${PIPESTATUS[0]}"
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]}"
Rename pulumi-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
$(GOMETALINTER) ./cmd/... | 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-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
# - "or be unexported": TODO[pulumi/pulumi#191]: will fix when we write all of our API docs
Rename `lint_quiet` to `lint` We have some lint debt (around exported functions being underdocumented) so we have a custom target that ignores some lint warnings. However, that target (which is the only lint target that needs to be clean to check in) is called `lint_quiet` instead of `lint` which is our normal linting target. Rename the target so your fingers can learn that `make lint` is always the right way to run linting before checkin.
2017-11-01 00:39:23 +01:00
LINT_SUPPRESS="or be unexported"
A few tweaks to lint fixes
2017-06-14 01:47:55 +02:00
Rename `lint_quiet` to `lint` We have some lint debt (around exported functions being underdocumented) so we have a custom target that ignores some lint warnings. However, that target (which is the only lint target that needs to be clean to check in) is called `lint_quiet` instead of `lint` which is our normal linting target. Rename the target so your fingers can learn that `make lint` is always the right way to run linting before checkin.
2017-11-01 00:39:23 +01:00
.PHONY: lint
lint:
@$(ECHO) "\033[0;32mLINT:\033[0m"
Rename pulumi-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
$(GOMETALINTER) main.go | grep -vE ${LINT_SUPPRESS} | sort ; exit $$(($${PIPESTATUS[1]}-1))
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))
Rename pulumi-fabric to pulumi This includes a few changes: * The repo name -- and hence the Go modules -- changes from pulumi-fabric to pulumi. * The Node.js SDK package changes from @pulumi/pulumi-fabric to just pulumi. * The CLI is renamed from lumi to pulumi.
2017-09-22 04:18:21 +02:00
$(GOMETALINTER) ./cmd/... | grep -vE ${LINT_SUPPRESS} | sort ; exit $$(($${PIPESTATUS[1]}-1))
Rename `lint_quiet` to `lint` We have some lint debt (around exported functions being underdocumented) so we have a custom target that ignores some lint warnings. However, that target (which is the only lint target that needs to be clean to check in) is called `lint_quiet` instead of `lint` which is our normal linting target. Rename the target so your fingers can learn that `make lint` is always the right way to run linting before checkin.
2017-11-01 00:39:23 +01:00
@$(ECHO) "\033[0;33mlint was run quietly; to run with noisy errors, run 'make lint_full'\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: 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"
Lower timeout The tests usually complete in about 15 seconds, so let's lower the timeout to fail a little faster in cases where we have hangs in `pulumi` itself.
2017-10-28 00:36:28 +02:00
go test -timeout 2m -cover -parallel ${TESTPARALLELISM} ${PROJECT_PKGS}
Make all by default
2017-08-06 17:52:32 +02:00
.PHONY: integrationtest
integrationtest:
@$(ECHO) "\033[0;32mINTEGRATION TEST:\033[0m"
Early-out integration tests if PATH is incorrect. This provides a friendlier experience if the nodejs language service is not on the path. Also, print a helpful message at the end of `make configure` if PATH has not yet been setup.
2017-09-18 22:06:59 +02:00
@if [ -z "`which pulumi-langhost-nodejs`" ]; then $(ECHO) Please add "`pwd`/sdk/nodejs/bin" to your path before running integration tests. && exit 1; fi
Simplify `go test` invocation
2017-11-01 00:42:16 +01:00
go test -cover -parallel ${TESTPARALLELISM} ./examples ./tests
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
Eliminate lumi, lumijs, and lumirt packages This change gets rid of the old-style @pulumi/lumi, @pulumi/lumijs, and @pulumi/lumirt packages. Instead, we have the new Node.js SDK.
2017-08-28 18:17:52 +02:00
sdk/nodejs:
@cd ./sdk/nodejs && $(MAKE)
.PHONY: sdk/nodejs
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
Use explicit targets in Makefile for Travis Defer build and publish logic into the makefiles instead of trying to use Travis to do so. This let's us sidestep Travis's not great error handling (see pulumi/home#21 for more details)
2017-09-28 20:53:08 +02:00
# The travis_* targets are entrypoints for CI.
.PHONY: travis_cron
travis_cron: nightly
.PHONY: travis_push
travis_push: all publish
.PHONY: travis_pull_request
travis_pull_request: all
.PHONY: travis_api
travis_api: all
Reference in a new issue Copy permalink