{"id":1729,"date":"2016-12-08T15:04:04","date_gmt":"2016-12-08T14:04:04","guid":{"rendered":"https:\/\/blog.mi.hdm-stuttgart.de\/?p=1729"},"modified":"2023-06-07T15:23:52","modified_gmt":"2023-06-07T13:23:52","slug":"snakes-exploring-pipelines-a-system-engineering-and-management-project-2","status":"publish","type":"post","link":"https:\/\/blog.mi.hdm-stuttgart.de\/index.php\/2016\/12\/08\/snakes-exploring-pipelines-a-system-engineering-and-management-project-2\/","title":{"rendered":"Snakes exploring Pipelines – A \u201cSystem Engineering and Management\u201d Project"},"content":{"rendered":"

Part 1: Tool Setup<\/h3>\n

This series of blog entries describes a student project focused on developing an application by using methods like pair programming, test driven development and deployment pipelines. <\/strong><\/p>\n

Welcome to the next part our project, on its way to become the Snake game with the very best underlying code base ever. (If you somehow missed the introduction to our project, you may want to give it a read: Click<\/a> ) Today, we\u2019ll take a look at the most important tools we use for building and versioning our code: Eclipse, Gradle and Github.<\/p>\n

<\/p>\n

Chances are very high that you already have some amount of experience or contact with the Eclipse development environment, if you have a background with software development in general or Java in particular, so it\u2019s probably unnecessary to talk much about it. For now, the important thing is, that Eclipse provides plug-ins for Gradle projects, as well as integration for JUnit from the get-go. (We will need JUnit later on, during the actual development.) And of course, we wanted to use the newest Java version (which is Java 8, at the time of writing).<\/p>\n

\"Fun<\/a>
Fun fact: Java (the island, not the language) is home to lots of dangerous snake species, like the pretty \u201cblue coral snake\u201d above.<\/figcaption><\/figure>\n

Before we dive into the installation, a quick overview of Gradle and Github:
\nGradle<\/a> is a tool used for build automation, mainly for large projects comprising many components which may take a long time to build. It allows to configure the build process, for example building only certain parts of the entire project, and supports parallel and even distributed build processes on multiple CPUs or computers.
\nAs for the installation, the complete instructions can be found here<\/a> and here<\/a>.<\/p>\n

Github<\/a> allows you to host your project files online, using the code versioning software Git (surprise!). Chances are high that you\u2019ve already used Github for downloading projects or code during your software developer-career. With it, you can back up your code remotely, create different development branches, and revert to earlier code versions, among others. Git can become extremely complex, especially when the merge conflicts appear in distributed projects, but with some luck, we won\u2019t have to deal with that.<\/p>\n

The process for setting up Gradle with a Github Repository:<\/p>\n

    \n
  1. If you haven\u2019t already, first install Java (JVM, JDK or JRE. Check the gradle instructions for the exact required versions, as those might change in the future)<\/li>\n
  2. If you\u2019re on Windows, install Git (if you\u2019re on Linux, it\u2019s already pre-installed, yay \ud83d\ude00 )<\/li>\n
  3. Install Gradle (Setting the correct environment variables is important if you want anything to work, take note that the exact process is dependent on your OS. )<\/li>\n
  4. Create a repository on Github<\/li>\n
  5. Clone the repository into your local destination folder by navigating to it with the command shell, then execute git clone https:\/\/github.com\/\u201dpath-to-repo\u201d.git<\/b><\/li>\n
  6. Create a new Java project with Gradle:
    \nNavigate to destination folder, again using the command shell
    \nExecute gradle init –type java-library<\/b><\/li>\n
  7. Create an initial build: gradle build<\/b><\/li>\n
  8. Still in the destination directory, create a .gitignore file, so that you can specify files that you don\u2019t want to add to the repository. For now, add \u201c.gradle\u201d and \u201cbuild\u201d<\/li>\n
  9. Commit the current state of the project with git:
    \nExecute git add .<\/b> (in order to add all files, for single files use git add \u201cfilename\u201d<\/b>)
    \nCommit with git commit -a -m \u201cinitial commit\u201d<\/b><\/li>\n
  10. Push the commit to GitHub: git push origin master<\/b><\/li>\n<\/ol>\n

    Integrating the Gradle-project with Eclipse:<\/p>\n

      \n
    1. Open the \u201cbuild.gradle\u201d file, search for the line apply plugin: \u2018java\u2019<\/b> and add apply plugin: \u2018eclipse\u2019<\/b> :
      \n      \"entry1-buildgradle\"<\/a><\/li>\n
    2. Use the shell, navigate to the project directory and execute gradle eclipse<\/b><\/li>\n
    3. Open Eclipse, choose a workspace, then select File -> Import -> Existing Projects into Workspace
      \nSelect the project folder as root archive
      \nClick finish<\/li>\n
    4. Similar to the process above, add the following files to the existing .gitignore:\n