1 / 64

Introduction to Software Engineering: Tools and Environments

Introduction to Software Engineering: Tools and Environments. Session 10. Oded Lachish Room: Mal 405 Visiting Hours: Wednesday 17:00 to 20:00 Email: oded@dcs.bbk.ac.uk Module URL: http://www.dcs.bbk.ac.uk/~oded/Tools2012-2013/Web/Tools2012-2013.html. Last time.

sagira
Download Presentation

Introduction to Software Engineering: Tools and Environments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Introduction to Software Engineering: Tools and Environments Session 10 Oded Lachish Room: Mal 405 Visiting Hours: Wednesday 17:00 to 20:00 Email: oded@dcs.bbk.ac.uk Module URL: http://www.dcs.bbk.ac.uk/~oded/Tools2012-2013/Web/Tools2012-2013.html

  2. Last time Documentation tools Doxygen and eUML2 “Code generation” tools – eUML2 Ant revisited

  3. Tools Side Dish Environment Variables

  4. Environment Variables • How did eclipse know where to find java • Scan the directory structure (bad idea, why?) • Environment variables  • Probably all operation systems have environment variables. • Environment variables can be accessed by running processes • Environment variables are also play a significant role in the operation of the OS

  5. Important - Environment Variables PATH – list of directories to look for executables JAVA_PATH – location of the Java related files ANT_PATH – location of the Ant related files

  6. Setting - Environment Variables Windows Right click Left click

  7. Environment Variables - Left click

  8. Environment Variables - Left click

  9. Environment Variables - You can add new system variables and edit existing ones

  10. Installing Ant and Setting Environment Variables • URL to download from • http://ant.apache.org/bindownload.cgi • Download: • apache-ant-1.8.2-bin.zip • Store contents in C:\ • So C:\apache-ant-1.8.2 exists

  11. Setting Ant Environment Variables Set ANT_HOME to First left click

  12. Add Ant to Path Environment Variables Semi colon separates directories in list, add “; C:\apache-ant-1.8.2\bin” at the end of the list First left click

  13. Java Server and Servlets

  14. Why do we need Javaserver and Servlets We are going to install Jenkins Jenkins is used through a browser Jenkins uses dynamic page generation The standard browser does supply a sufficient environment for this goal Jenkins requires a Javaserver for this goal We shall use Tomcat as our Javaserver and run Jenkins a java servelet (an extension to Tomcat)

  15. Download Tomcat • URL to download from • http://tomcat.apache.org/download-60.cgi • Download: • 32-bit/64-bit Windows Service Installer • Execute (select all components)

  16. Tomcat Installation – User Name and Password Fill-in Make sure you remember this we will need it

  17. Tomcat Installation – Java Virtual Machine Make sure correct

  18. Tomcat Destination Remember, will be useful

  19. Apache Tomcat Left click

  20. Apache Tomcat – Server Status Left click

  21. This shouldn’t be there at this stage

  22. Next Stage

  23. Until now From here on We have covered many SDLC tools from a single developer s point of view. Project point of view (large project) Integration Collected work of Individual Developers Local Individual Developer Testing QA team Environment

  24. Project Scale Tools Single Developers Tools “light weight” Easy to learn Integrated with IDE Trivial to install and set Massive number of available tools “HEAVY” Easy to learn? Require their own server Installation may require significant effort Relatively small variety of tools

  25. Continuous Integration

  26. Integration • Where all the code goes to (and also the unit tests) • When things go wrong here the price is high • This is the reason the focus is on minimizing the damage when things go wrong

  27. Continuous Integration • Integrate code as soon as possible. • Why? • Each time only a small portion of code is added or changed. Why? • Problems are detected earlier • Easier to find the problem

  28. Jenkins

  29. What is Jenkins A crucial element in continuous integration has two main goals: “Continuously” build and test software projects Monitor externally run jobs

  30. Work Flow with Jenkins A team member/ members commit code to source control repository Jenkins detects that new code has been committed Jenkins usesBuild Tools to build the project and Test tools to test the project Jenkins uses the resulting files to generate reports Jenkins send notification if anything went wrong (build, test failed etc.)

  31. Jenkins as Part of the Big Picture • Easy installation: java -jar jenkins.war, or deploy it in a servlet container. No additional install, no database. • Easy configuration: can be configured entirely from its friendly web GUI with extensive on-the-fly error checks and inline help. There's no need to tweak XML manually anymore, although if you'd like to do so, you can do that, too. • Change set support: can generate a list of changes made into the build from Subversion/CVS. This is also done in a fairly efficient fashion, to reduce the load on the repository.

  32. Jenkins as Part of the Big Picture • Permanent links: Jenkins gives you clean readable URLs for most of its pages, including some permalinks like "latest build"/"latest successful build", so that they can be easily linked from elsewhere. • RSS/E-mail/IM Integration: Monitor build results by RSS or e-mail to get real-time notifications on failures. • JUnit/TestNG test reporting: JUnit test reports can be tabulated, summarized, and displayed with history information, such as when it started breaking, etc. History trend is plotted into a graph.

  33. Jenkins as Part of the Big Picture • Distributed builds: Jenkins can distribute build/test loads to multiple computers. This lets you get the most out of those idle workstations sitting beneath developers' desks. • File fingerprinting: Jenkins can keep track of which build produced which jars, and which build is using which version of jars, and so on. This works even for jars that are produced outside Jenkins, and is ideal for projects to track dependency. • Plugin Support: Jenkins can be extended via 3rd party plugins. You can write plugins to make Jenkins support tools/processes that your team uses.

  34. Jenkins as Part of the Big Picture An “easy” to configure tool that is responsible for the following: Make sure that everything that should be executed is executed when and as soon as possible Collect all the information and process it into coherent reports (imagine have 10 different tools each with its own report)

  35. Jenkins Leg Work

  36. Jenkins – .war file jenkins.war

  37. What to do with the .war file

  38. Jenkins – Nice to Meat You Left click

  39. Jenkins – Plug-ins Left click

  40. Jenkins Plugin manager Left click

  41. Jenkins Git Plugin Installation Success

  42. Jenkins Leg Work New Project

  43. Jenkins new project Write a new Java project Add an Ant build script to the project Store the project in a Git repository

  44. Jenkins New Job Left click

  45. Jenkins New Job 2 Fill in Select

  46. Jenkins New Job Top Fill in Select

  47. Jenkins New Job Middle Select Update to your git repository

  48. Jenkins New Job Update Left click

  49. Jenkins New Job (actually after) Left click Left click

  50. Jenkins Build Page Left click

More Related