This repository has been archived by the owner on Dec 17, 2019. It is now read-only.
Write a description of what happens in a build #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a (draft) of a write-up that attempts to explain what happens when we perform a clean build on this project.
@joethe pointed out that I could use the `-m` flag to get a trace of what `gradle` will run without having all the output clutter, so I included that trace early in the write-up.
joethe
approved these changes
May 15, 2017
| :server:build SKIPPED | ||
| ``` | ||
|
|
||
| These appear in the order in which they will need to be executed, which is sort of the reverse of the dependency graph. If a `gradle` task (e.g., `build`) depends on another `gradle` task (e.g., `check`), then the dependent task (`check`) appears first because it has to be completed before `build` can be considered done. The exact order you get might vary, especially if you (or we) have made some changes to the configuration or the codebase since this was written. Since the dependency graph is really a _graph_ there can be sets of tasks where there is no specified or required ordering among them. At the top level, for example, this has some of the `:server` tasks before the `:client` tasks, but I think that could have done all or most of the `:server` tasks after doing all the `:client` tasks. |
There was a problem hiding this comment.
Is check really the "dependent task" here? This is a bit nitpick-ey, but wouldn't that imply that check depends on build, and not the other way around?
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a (draft) of a write-up that attempts to explain what happens when we perform a clean build on this project.
I'm not at all sure that everything here is correct, and would love feedback, suggestions, additions, etc.