Some topics about Gradle that were unclear or strange for me are explained

1. Gradle explained
Andrey Mukamolov

2. Plan
1. Preface
2. What is build system
3. What is special about Gradle
4. Examples

3. Preface
● Gradle is cool but complex
● Not so much devs understand it

4. Build systems
Build automation is the process of automating the creation of a software build and the associated processes including:
compiling computer source code into binary code, packaging binary code, and running automated tests.
Wiki
Build automation software => build systems

5. Build systems: example
● Make
● Maven
● Apache Ant
● MSBuild
● Xcodebuild
● … and Gradle

6. What’s in common?
Do some stuff on input files and produce output files

7. Gradle
● Script-based builds
● Extendable
● Dependencies management
● Lots of presets
● Kotlin DSL :)

8. Gradle termins
● Task - executable build step: assemble, compile, jar, prepare
● Plugin - defines tasks and their order
● Module - your code etc.
● Project - set of modules

9. Plugins
Gradle has set of default plugins for Java, Kotlin, Groovy, etc
But you need to tell Gradle to apply them to your project

10. Tasks are code

11. Tasks are code

12. Tasks are code

13. Build cache
● Downloaded dependencies
● Compiled code
● Test results
● Processed assets

14. Don’t execute task if its input
haven’t changed from
previous execution

15. buildSrc
● Default “project”
● Can define other plugins
● Extra tasks, plugins and code
● Cover logic with tests
● Usage: extra stuff for main build scripts

16. Thanks!