Gradle User Guide

Total Page:16

File Type:pdf, Size:1020Kb

Gradle User Guide Gradle User Guide Version 2.14.1 Copyright © 2007-2015 Hans Dockter, Adam Murdoch Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Table of Contents I. ABOUT GRADLE 1. Introduction 2. Overview II. WORKING WITH EXISTING BUILDS 3. Installing Gradle 4. Using the Gradle Command-Line 5. The Gradle Wrapper 6. The Gradle Daemon 7. Dependency Management Basics 8. Introduction to multi-project builds 9. Continuous build 10. Using the Gradle Graphical User Interface 11. The Build Environment 12. Troubleshooting 13. Embedding Gradle using the Tooling API III. WRITING GRADLE BUILD SCRIPTS 14. Build Script Basics 15. Build Init Plugin 16. Writing Build Scripts 17. More about Tasks 18. Working With Files 19. Using Ant from Gradle 20. The Build Lifecycle 21. Wrapper Plugin 22. Logging 23. Dependency Management 24. Multi-project Builds 25. Gradle Plugins 26. Standard Gradle plugins 27. The Project Report Plugin 28. The Build Dashboard Plugin 29. Comparing Builds 30. Publishing artifacts 31. The Maven Plugin 32. The Signing Plugin 33. Ivy Publishing (new) 34. Maven Publishing (new) 35. The Distribution Plugin 36. The Announce Plugin 37. The Build Announcements Plugin IV. EXTENDING THE BUILD 38. Writing Custom Task Classes 39. Writing Custom Plugins 40. The Java Gradle Plugin Development Plugin 41. Organizing Build Logic 42. Initialization Scripts 43. The Gradle TestKit V. BUILDING JVM PROJECTS 44. Java Quickstart 45. The Java Plugin 46. Web Application Quickstart 47. The War Plugin 48. The Ear Plugin 49. The Jetty Plugin 50. The Application Plugin 51. The Java Library Distribution Plugin 52. Groovy Quickstart 53. The Groovy Plugin 54. The Scala Plugin 55. The ANTLR Plugin 56. The Checkstyle Plugin 57. The CodeNarc Plugin 58. The FindBugs Plugin 59. The JDepend Plugin 60. The PMD Plugin 61. The JaCoCo Plugin 62. The Sonar Plugin 63. The SonarQube Runner Plugin 64. The OSGi Plugin 65. The Eclipse Plugins 66. The IDEA Plugin VI. THE SOFTWARE MODEL - NEXT GENERATION GRADLE BUILDS 67. Rule based model configuration 68. Software model concepts 69. Implementing model rules in a plugin 70. Building Java Libraries 71. Building Play applications 72. Building native software 73. Extending the software model VII. APPENDIX A. Gradle Samples B. Potential Traps C. The Feature Lifecycle D. Gradle Command Line E. Documentation licenses Glossary List of Examples 4.1. Executing multiple tasks 4.2. Excluding tasks 4.3. Abbreviated task name 4.4. Abbreviated camel case task name 4.5. Selecting the project using a build file 4.6. Selecting the project using project directory 4.7. Forcing tasks to run 4.8. Obtaining information about projects 4.9. Providing a description for a project 4.10. Obtaining information about tasks 4.11. Changing the content of the task report 4.12. Obtaining more information about tasks 4.13. Obtaining detailed help for tasks 4.14. Obtaining information about dependencies 4.15. Filtering dependency report by configuration 4.16. Getting the insight into a particular dependency 4.17. Information about properties 5.1. Running the Wrapper task 5.2. Wrapper task 5.3. Wrapper generated files 5.4. Generating a SHA-256 hash 5.5. Configuring SHA-256 checksum verification 7.1. Declaring dependencies 7.2. Definition of an external dependency 7.3. Shortcut definition of an external dependency 7.4. Usage of Maven central repository 7.5. Usage of JCenter repository 7.6. Usage of a remote Maven repository 7.7. Usage of a remote Ivy directory 7.8. Usage of a local Ivy directory 7.9. Publishing to an Ivy repository 7.10. Publishing to a Maven repository 8.1. Listing the projects in a build 10.1. Launching the GUI 11.1. Setting properties with a gradle.properties file 11.2. Configuring an HTTP proxy 11.3. Configuring an HTTPS proxy 14.1. Your first build script 14.2. Execution of a build script 14.3. A task definition shortcut 14.4. Using Groovy in Gradle's tasks 14.5. Using Groovy in Gradle's tasks 14.6. Declaration of task that depends on other task 14.7. Lazy dependsOn - the other task does not exist (yet) 14.8. Dynamic creation of a task 14.9. Accessing a task via API - adding a dependency 14.10. Accessing a task via API - adding behaviour 14.11. Accessing task as a property of the build script 14.12. Adding extra properties to a task 14.13. Using AntBuilder to execute ant.loadfile target 14.14. Using methods to organize your build logic 14.15. Defining a default task 14.16. Different outcomes of build depending on chosen tasks 16.1. Accessing property of the Project object 16.2. Using local variables 16.3. Using extra properties 16.4. Configuring arbitrary objects 16.5. Configuring arbitrary objects using a script 16.6. Groovy JDK methods 16.7. Property accessors 16.8. Method call without parentheses 16.9. List and map literals 16.10. Closure as method parameter 16.11. Closure delegates 17.1. Defining tasks 17.2. Defining tasks - using strings for task names 17.3. Defining tasks with alternative syntax 17.4. Accessing tasks as properties 17.5. Accessing tasks via tasks collection 17.6. Accessing tasks by path 17.7. Creating a copy task 17.8. Configuring a task - various ways 17.9. Configuring a task - with closure 17.10. Defining a task with closure 17.11. Adding dependency on task from another project 17.12. Adding dependency using task object 17.13. Adding dependency using closure 17.14. Adding a 'must run after' task ordering 17.15. Adding a 'should run after' task ordering 17.16. Task ordering does not imply task execution 17.17. A 'should run after' task ordering is ignored if it introduces an ordering cycle 17.18. Adding a description to a task 17.19. Overwriting a task 17.20. Skipping a task using a predicate 17.21. Skipping tasks with StopExecutionException 17.22. Enabling and disabling tasks 17.23. A generator task 17.24. Declaring the inputs and outputs of a task 17.25. Task rule 17.26. Dependency on rule based tasks 17.27. Adding a task finalizer 17.28. Task finalizer for a failing task 18.1. Locating files 18.2. Creating a file collection 18.3. Using a file collection 18.4. Implementing a file collection 18.5. Creating a file tree 18.6. Using a file tree 18.7. Using an archive as a file tree 18.8. Specifying a set of files 18.9. Copying files using the copy task 18.10. Specifying copy task source files and destination directory 18.11. Selecting the files to copy 18.12. Copying files using the copy() method without up-to-date check 18.13. Copying files using the copy() method with up-to-date check 18.14. Renaming files as they are copied 18.15. Filtering files as they are copied 18.16. Nested copy specs 18.17. Using the Sync task to copy dependencies 18.18. Creating a ZIP archive 18.19. Creation of ZIP archive 18.20. Configuration of archive task - custom archive name 18.21. Configuration of archive task - appendix & classifier 19.1. Using an Ant task 19.2. Passing nested text to an Ant task 19.3. Passing nested elements to an Ant task 19.4. Using an Ant type 19.5. Using a custom Ant task 19.6. Declaring the classpath for a custom Ant task 19.7. Using a custom Ant task and dependency management together 19.8. Importing an Ant build 19.9. Task that depends on Ant target 19.10. Adding behaviour to an Ant target 19.11. Ant target that depends on Gradle task 19.12. Renaming imported Ant targets 19.13. Setting an Ant property 19.14. Getting an Ant property 19.15. Setting an Ant reference 19.16. Getting an Ant reference 19.17. Fine tuning Ant logging 20.1. Single project build 20.2. Hierarchical layout 20.3. Flat layout 20.4. Modification of elements of the project tree 20.5. Adding of test task to each project which has certain property set 20.6. Notifications 20.7. Setting of certain property to all tasks 20.8. Logging of start and end of each task execution 22.1. Using stdout to write log messages 22.2. Writing your own log messages 22.3. Using SLF4J to write log messages 22.4. Configuring standard output capture 22.5. Configuring standard output capture for a task 22.6. Customizing what Gradle logs 23.1. Definition of a configuration 23.2. Accessing a configuration 23.3. Configuration of a configuration 23.4. Module dependencies 23.5. Artifact only notation 23.6. Dependency with classifier 23.7. Iterating over a configuration 23.8. Client module dependencies - transitive dependencies 23.9. Project dependencies 23.10. File dependencies 23.11. Generated file dependencies 23.12. Gradle API dependencies 23.13. Gradle's Groovy dependencies 23.14. Excluding transitive dependencies 23.15. Optional attributes of dependencies 23.16. Collections and arrays of dependencies 23.17. Dependency configurations 23.18. Dependency configurations for project 23.19. Configuration.copy 23.20. Accessing declared dependencies 23.21. Configuration.files 23.22. Configuration.files with spec 23.23. Configuration.copy 23.24. Configuration.copy vs. Configuration.files 23.25. Adding central Maven repository 23.26. Adding Bintray's JCenter Maven repository 23.27. Using Bintrays's JCenter with HTTP 23.28. Adding the local Maven cache as a repository 23.29.
Recommended publications
  • Maksym Govorischev
    Maksym Govorischev E-mail : [email protected] Skills & Tools Programming and Scripting Languages: Java, Groovy, Scala Programming metodologies: OOP, Functional Programming, Design Patterns, REST Technologies and Frameworks: - Application development: Java SE 8 Spring Framework(Core, MVC, Security, Integration) Java EE 6 JPA/Hibernate - Database development: SQL NoSQL solutions - MongoDB, OrientDB, Cassandra - Frontent development: HTML, CSS (basic) Javascript Frameworks: JQuery, Knockout - Build tools: Gradle Maven Ant - Version Control Systems: Git SVN Project Experience Project: JUL, 2016 - OCT, 2016 Project Role: Senior Developer Description: Project's aim was essentially to create a microservices architecture blueprint, incorporating business agnostic integrations with various third-party Ecommerce, Social, IoT and Machine Learning solutions, orchestrating them into single coherent system and allowing a particular business to quickly build rich online experience with discussions, IoT support and Maksym Govorischev 1 recommendations engine, by just adding business specific services layer on top of accelerator. Participation: Played a Key developer role to implement integration with IoT platform (AWS IoT) and recommendation engine (Prediction IO), by building corresponding integration microservices. Tools: Maven, GitLab, SonarQube, Jenkins, Docker, PostgreSQL, Cassandra, Prediction IO Technologies: Java 8, Scala, Spring Boot, REST, Netflix Zuul, Netflix Eureka, Hystrix Project: Office Space Management Portal DEC, 2015 - FEB, 2016
    [Show full text]
  • Gradle User Guide
    Gradle User Guide Version 2.2.1 Copyright © 2007-2012 Hans Dockter, Adam Murdoch Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically. Table of Contents 1. Introduction 1.1. About this user guide 2. Overview 2.1. Features 2.2. Why Groovy? 3. Tutorials 3.1. Getting Started 4. Installing Gradle 4.1. Prerequisites 4.2. Download 4.3. Unpacking 4.4. Environment variables 4.5. Running and testing your installation 4.6. JVM options 5. Troubleshooting 5.1. Working through problems 5.2. Getting help 6. Build Script Basics 6.1. Projects and tasks 6.2. Hello world 6.3. A shortcut task definition 6.4. Build scripts are code 6.5. Task dependencies 6.6. Dynamic tasks 6.7. Manipulating existing tasks 6.8. Shortcut notations 6.9. Extra task properties 6.10. Using Ant Tasks 6.11. Using methods 6.12. Default tasks 6.13. Configure by DAG 6.14. Where to next? 7. Java Quickstart 7.1. The Java plugin 7.2. A basic Java project 7.3. Multi-project Java build 7.4. Where to next? 8. Dependency Management Basics 8.1. What is dependency management? 8.2. Declaring your dependencies 8.3. Dependency configurations 8.4. External dependencies 8.5. Repositories 8.6. Publishing artifacts 8.7. Where to next? 9. Groovy Quickstart 9.1. A basic Groovy project 9.2.
    [Show full text]
  • Android Programming Cookbook I
    Android Programming Cookbook i Android Programming Cookbook Android Programming Cookbook ii Contents 1 Android Tutorial For Beginners 1 1.1 What is Android?...................................................1 1.2 Installing Android Studio...............................................1 1.3 Android versions and Android SDK Manager....................................7 1.4 Supporting different screen sizes...........................................7 1.5 Android Project Structure...............................................8 1.6 Create "Hello Android World" application......................................9 1.6.1 Create a New Android Studio Project....................................9 1.6.2 Create the source code of a simple FirstAndroidApplication Activity.................... 13 1.6.3 Create the layout of the project........................................ 14 1.6.4 Android Manifest............................................... 14 1.6.5 Edit the FirstAndroidApplication dimensions................................ 15 1.6.6 Edit the FirstAndroidApplication strings................................... 15 1.6.7 Add the drawable for every screen density.................................. 15 1.6.8 Build, compile and run............................................ 16 1.7 Download the Android Studio Project........................................ 18 1.8 How to continue?................................................... 18 2 Android Project migration from Eclipse to Android Studio 19 2.1 Why to use Android Studio over Eclipse ADT?..................................
    [Show full text]
  • Modern Web Development with Kotlin a Concise and Practical Step-By-Step Guide
    Modern Web Development with Kotlin A concise and practical step-by-step guide Denis Kalinin This book is for sale at http://leanpub.com/modern-web-development-with-kotlin This version was published on 2019-06-04 This is a Leanpub book. Leanpub empowers authors and publishers with the Lean Publishing process. Lean Publishing is the act of publishing an in-progress ebook using lightweight tools and many iterations to get reader feedback, pivot until you have the right book and build traction once you do. © 2016 - 2019 Denis Kalinin Contents Preface ...................................................... 1 Build tools ................................................... 4 Command line .............................................. 4 Gradle ................................................... 5 Editing source files .............................................. 9 Using Atom ................................................ 9 Using IntelliJ IDEA ............................................ 11 Language fundamentals ........................................... 13 Using the REPL .............................................. 13 Defining values .............................................. 13 Lambdas .................................................. 15 Type hierarchy .............................................. 16 Nullable types ............................................... 17 Collections ................................................. 18 Defining classes .............................................. 20 Defining objects ............................................
    [Show full text]
  • Code Smell Prediction Employing Machine Learning Meets Emerging Java Language Constructs"
    Appendix to the paper "Code smell prediction employing machine learning meets emerging Java language constructs" Hanna Grodzicka, Michał Kawa, Zofia Łakomiak, Arkadiusz Ziobrowski, Lech Madeyski (B) The Appendix includes two tables containing the dataset used in the paper "Code smell prediction employing machine learning meets emerging Java lan- guage constructs". The first table contains information about 792 projects selected for R package reproducer [Madeyski and Kitchenham(2019)]. Projects were the base dataset for cre- ating the dataset used in the study (Table I). The second table contains information about 281 projects filtered by Java version from build tool Maven (Table II) which were directly used in the paper. TABLE I: Base projects used to create the new dataset # Orgasation Project name GitHub link Commit hash Build tool Java version 1 adobe aem-core-wcm- www.github.com/adobe/ 1d1f1d70844c9e07cd694f028e87f85d926aba94 other or lack of unknown components aem-core-wcm-components 2 adobe S3Mock www.github.com/adobe/ 5aa299c2b6d0f0fd00f8d03fda560502270afb82 MAVEN 8 S3Mock 3 alexa alexa-skills- www.github.com/alexa/ bf1e9ccc50d1f3f8408f887f70197ee288fd4bd9 MAVEN 8 kit-sdk-for- alexa-skills-kit-sdk- java for-java 4 alibaba ARouter www.github.com/alibaba/ 93b328569bbdbf75e4aa87f0ecf48c69600591b2 GRADLE unknown ARouter 5 alibaba atlas www.github.com/alibaba/ e8c7b3f1ff14b2a1df64321c6992b796cae7d732 GRADLE unknown atlas 6 alibaba canal www.github.com/alibaba/ 08167c95c767fd3c9879584c0230820a8476a7a7 MAVEN 7 canal 7 alibaba cobar www.github.com/alibaba/
    [Show full text]
  • Maven Vs Gradle
    Maven vs Gradle This is a working document on the topic of converting from gradle to maven. If you add items / questions / etc, please tag and maybe color it (e.g., <dl>...) to make it easier to track things. Open questions / issues are in red. At a high level the motivations are: improve consumability of Edgent by users add publishing of signed Edgent binary release artifacts (JAR, WAR) in maven repos ultimately cease creating signed binary release bundles (tgz) simplify the build tooling the gradle scripting has some non-standard / complicated processing either out of ignorance or to achieve certain things TODO add the "why the complications" note here. (manifest classpath, binary bundle tgz with transitive deps, ...) Suspect that to simplify maven based tooling we'd need to eliminate some of those things (which would also simplify gradle stuff) Chris Dutz created PR-309 for working on a maven based system. PR-309 now includes a maven wrapper (mvnw). Set JAVA_HOME and then use "mvnw" instead of "mvn" below and you don't have to manually install maven. Or, to manually install maven https://maven.apache.org/download.cgi https://maven.apache.org/install.html Maven concepts: lifecycles, phases, goals, plugins High level building and testing mvn clean install # builds and tests add -DskipTests to omit testing, --fail-at-end for "continue"-like mvn clean package # a bit fewer phases than install mvn clean compile # even fewer/faster mvn site:site site:staging # see target/stagingindex.html mvn dependency:copy-dependencies # copies all dep
    [Show full text]
  • Verifying Android Applications Using Java Pathfinder
    Verifying Android Applications Using Java PathFinder by Heila-Marié Botha Dissertation presented for the degree of Doctor of Philosophy in Computer Science in the Faculty of Science at Stellenbosch University Supervisors: Prof. W Visser and Prof. AB van der Merwe December 2017 Stellenbosch University https://scholar.sun.ac.za Declaration By submitting this dissertation electronically, I declare that the entirety of the work contained therein is my own, original work, that I am the sole author thereof (save to the extent explicitly otherwise stated), that reproduction and publication thereof by Stellenbosch University will not infringe any third party rights and that I have not previously in its entirety or in part submitted it for obtaining any qualification. December 2017 Date: . Copyright © 2017 Stellenbosch University All rights reserved. i Stellenbosch University https://scholar.sun.ac.za Abstract Verifying Android Applications Using Java PathFinder H. Botha Department of Computer Science University of Stellenbosch, Private Bag X1, Matieland 7602, South Africa. Dissertation: PhD (Computer Science) November 2017 Current dynamic analysis tools for Android applications do not achieve acceptable code coverage since they can only explore a subset of the behav- iors of the applications and do not have full control over the environment in which they execute. In this work model checking is used to systemati- cally and more effectively explore application execution paths using state matching and backtracking. In particular, we extend the Java PathFinder (JPF) model checking environment for Android. We describe the difficul- ties one needs to overcome as well as our current approaches to handling these issues. We obtain significantly higher coverage using shorter event sequences on a representative sample of Android apps, when compared to Dynodroid and Sapienz, the current state-of-the-art dynamic analysis tools for Android applications.
    [Show full text]
  • Gradle in Action by Benjamin Muschko
    S AMPLE CHAPTER IN ACTION Benjamin Muschko FOREWORD BY Hans Dockter MANNING Gradle in Action by Benjamin Muschko Chapter 2 Copyright 2014 Manning Publications brief contents PART 1INTRODUCING GRADLE .................................................1 1 ■ Introduction to project automation 3 2 ■ Next-generation builds with Gradle 22 3 ■ Building a Gradle project by example 48 PART 2MASTERING THE FUNDAMENTALS .................................73 4 ■ Build script essentials 75 5 ■ Dependency management 105 6 ■ Multiproject builds 133 7 ■ Testing with Gradle 157 8 ■ Extending Gradle 191 9 ■ Integration and migration 223 PART 3FROM BUILD TO DEPLOYMENT ...................................247 10 ■ IDE support and tooling 249 11 ■ Building polyglot projects 282 12 ■ Code quality management and monitoring 310 13 ■ Continuous integration 337 14 ■ Artifact assembly and publishing 359 15 ■ Infrastructure provisioning and deployment 395 iii Next-generation builds with Gradle This chapter covers ■ Understanding how Gradle compares to other build tools ■ Describing Gradle’s compelling feature set ■ Installing Gradle ■ Writing and executing a simple Gradle script ■ Running Gradle on the command line For years, builds had the simple requirements of compiling and packaging soft- ware. But the landscape of modern software development has changed, and so have the needs for build automation. Today, projects involve large and diverse software stacks, incorporate multiple programming languages, and apply a broad spectrum of testing strategies. With the rise of
    [Show full text]
  • Security and Privacy of Secure Messaging Services
    Security and Privacy of Secure Messaging Services A Case Study of Wire DIPLOMARBEIT zur Erlangung des akademischen Grades Diplom-Ingenieur im Rahmen des Studiums Software Engineering & Internet Computing eingereicht von Andreas Boll, BSc Matrikelnummer 0825205 an der Fakultät für Informatik der Technischen Universität Wien Betreuung: Privatdoz. Mag.rer.soc.oec. Dipl.-Ing. Dr.techn. Edgar Weippl Mitwirkung: Univ.Lektor Dipl.-Ing. Dr.techn. Georg Merzdovnik, BSc Die approbierte gedruckte Originalversion dieser Diplomarbeit ist an der TU Wien Bibliothek verfügbar. The approved original version of this thesis is available in print at TU Wien Bibliothek. Wien, 3. März 2020 Andreas Boll Edgar Weippl Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.at Die approbierte gedruckte Originalversion dieser Diplomarbeit ist an der TU Wien Bibliothek verfügbar. The approved original version of this thesis is available in print at TU Wien Bibliothek. Security and Privacy of Secure Messaging Services A Case Study of Wire DIPLOMA THESIS submitted in partial fulfillment of the requirements for the degree of Diplom-Ingenieur in Software Engineering & Internet Computing by Andreas Boll, BSc Registration Number 0825205 to the Faculty of Informatics at the TU Wien Advisor: Privatdoz. Mag.rer.soc.oec. Dipl.-Ing. Dr.techn. Edgar Weippl Assistance: Univ.Lektor Dipl.-Ing. Dr.techn. Georg Merzdovnik, BSc Die approbierte gedruckte Originalversion dieser Diplomarbeit ist an der TU Wien Bibliothek verfügbar. The approved original version of this thesis is available in print at TU Wien Bibliothek. Vienna, 3rd March, 2020 Andreas Boll Edgar Weippl Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel.
    [Show full text]
  • USING the GROOVY ECOSYSTEM for RAPID JVM DEVELOPMENT Schalk W
    USING THE GROOVY ECOSYSTEM FOR RAPID JVM DEVELOPMENT Schalk W. Cronjé #ACCU2016 ACCU Bristol 2016 ABOUT ME Email: [email protected] Twitter / Ello : @ysb33r 1 2 SDKMAN Manages parallel version of multiple SDKs Mostly for (but not limited to) JVM-related systems Windows users can use Posh-GVM (Powershell) Windows 10 Bash ?? curl -s http://get.sdkman.io | bash 3 . 1 SDKMAN DEMO 3 . 2 SdkMan: http://sdkman.io Posh-GVM: https://github.com/ofreud/posh-gvm @sdkmanager 3 . 3 APACHE GROOVY A dynamic & static typed language for the JVM with REPL capability. 3 . 4 GROOVY VS JAVA In Groovy: All class members are public by default No need to create getters/setters for public elds Both static & dynamic typing supported def means Object 4 . 1 CALLING METHODS class Foo { void bar( def a,def b ) {} } def foo = new Foo() foo.bar( '123',456 ) foo.bar '123', 456 foo.with { bar '123', 456 } 4 . 2 CALLING METHODS WITH CLOSURES class Foo { void bar( def a,Closure b ) {} } def foo = new Foo() foo.bar( '123',{ println it } ) foo.bar ('123') { println it } foo.bar '123', { println it } 4 . 3 MAPS IN GROOVY Hashmaps in Groovy are simple to use def myMap = [ plugin : 'java' ] Maps are easy to pass inline to functions project.apply( plugin : 'java' ) Which can also be written as project.with { apply plugin : 'java' } 4 . 4 LISTS IN GROOVY Lists in Groovy are simple too def myList = [ 'clone', 'http://github.com/ysb33r/GradleLectures' ] This makes it possible write a method call as args 'clone', 'http://github.com/ysb33r/GradleLectures' 4 .
    [Show full text]
  • Reproducible Builds Summit III Berlin, Germany
    Reproducible Builds Summit III Berlin, Germany. October 31 – November 2, 2017 Event Documentation Aspiration, 2973 16th Street, Suite 300, San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • aspirationtech.org Table of Contents Agenda..........................................................................................................................................4 Session Notes.............................................................................................................................10 Day 1.......................................................................................................................................10 Agenda brainstorming........................................................................................................10 Working sessions I..............................................................................................................17 Reviewing existing reproducible builds tools.................................................................17 Discussing the current status of .buildinfo files..............................................................22 What is the ecosystem around rpm?..............................................................................23 End user tools: What does exist, what is still needed....................................................25 Working sessions II.............................................................................................................27 How to fix the current issues with BUILD_PATH_PREFIX_MAP?.................................27
    [Show full text]
  • Tools and Processes for Creating and Maintaining Own Linux Based Distributions in Corporate Environment
    Tools and processes for creating and maintaining own Linux based distributions in corporate environment Juhani Heliö Helsinki April 28, 2017 UNIVERSITY OF HELSINKI Department of Computer Science HELSINGIN YLIOPISTO — HELSINGFORS UNIVERSITET — UNIVERSITY OF HELSINKI Tiedekunta — Fakultet — Faculty Laitos — Institution — Department Faculty of Science Department of Computer Science Tekijä — Författare — Author Juhani Heliö Työn nimi — Arbetets titel — Title Tools and processes for creating and maintaining own Linux based distributions in corporate environment Oppiaine — Läroämne — Subject Computer Science Työn laji — Arbetets art — Level Aika — Datum — Month and year Sivumäärä — Sidoantal — Number of pages April 28, 2017 70 pages + 17 appendices Tiivistelmä — Referat — Abstract Nokia has been maintaining its own Linux distribution, dubbed Nokia Linux, for quite some time, and while the distribution has been successful, supporting it has become tedious at very least. The current version of Nokia Linuxes build system builds a monolithic distribution. This creates a multitude of problems ranging from having to rebuild all of the distribution’s software packages after patching a single package to not being able to efficiently customise images according to user needs. The current version also lacks any kind of stable release management causing every user to either maintain their own stable releases or having to constantly update from the official version. Apart from being too monolithic, the support of the software packages is insufficient. An efficient support team needs to be created to answer any internal support requests Nokia Linux users might have. In this thesis we first define our corporate environmental needs. We identify three needs: support, storage and security. We then define three methods for organising the support.
    [Show full text]