DOCSLIB.ORG

Serengeti Data & Tech Sheet

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Serengeti Data & Tech Sheet PROMISING THE POSSIBLE, DELIVERING EVEN MORE! Serengeti Data & Tech Sheet More than half of EU enterpris- We’ve never lived in a time like this. ● DevOps es that recruited or tried to recruit ● Automated testing. ICT specialists had difficulties in In the EU, the vast majority of all filling ICT vacancies. Specifically: enterprise software development We have development centers in Austrian (78%), Dutch (69%) and comes from external partners and Ukraine and Croatia and sales offic- German (64%) companies were their engineers. To excel now, you es in The Netherlands and Germany. above the EU average having need a great engineering team. Your trouble finding software engineers innovation often comes right from We enable seamless team extension and other ICT specialists that team. by mirroring the processes and de- velopment environment of our de- Eurostat, December 2018. That is the reason why we used manding clients. Our global team more than 10 years of experience in of over 150 engineers are adept in offsite software delivery and built our all major technology platforms and Is it challenging team extension engagement mod- possess unique development skills to find software el. It is a model that assures instant and real-world experience. engineering capacity and flexibility, engineers? but it is specially designed to pro- Today, our business continues to ex- vide shortest time to maximum pro- pand rapidly. We maintain 100% ref- The software development in- ductivity, team stability and minimum erence ability by meeting and often dustry is in a tight hiring spot. We management overhead. exceeding our clients high level of know that stable and skilled en- expectations. gineering teams build exception- Serengeti is a software develop- al products. However, finding the ment business focused on core Since our client need us for critical people you need isn’t easy, and product development. support in the development of their it’s a time and cost investment. complex core business applications, We provide self-managed engineer- our teams consist of very experienced If you hire the wrong engineers -- or ing teams to rapidly scale product and highly educated engineers. fail to hire them at all -- you can lose development capacity and acceler- months on a business-critical proj- ate the release of products. With our ect - and the standard hiring pro- focus on industries like logistics, en- Breakdown of Serengeti cess does not always get you the ergy, health, industrial manufactur- software engineers best engineers. ing, and finance, we provide teams by seniority level that understand specific industry More importantly the competition is requirements and understand the also looking for these experts. broad business picture. 12% Junior Additionally, there are numerous With our broad technical expertise, business models today. Each lead- we can consult and implement inno- 17% 43% er has their own experiences, and vations based on advanced trends: Mid Lead those experiences inform their ap- proach. The biz world is moving ● Cloud faster than ever. Organizations pivot ● IoT 28% on a dime. Requirements are always ● Machine learning Senior changing. R&D needs more flexibili- ● Computer vision ty and agility. ● Augmented reality SERENGETI | DATA & TECH SHEET 1 PROMISING THE POSSIBLE, DELIVERING EVEN MORE! TEAM EXTENSION MODEL Due to the sheer number of engi- - Focus neers on staff, Team Extension sup pliers have more depth in estab- Build chemistry Proof of concept Consulting lished and emerging technologies Establish communication Productivity Flexibility Transfer knowledge Capacity Reliability than in-house teams -- and they also 8 have more exposure to engineering AMBASSADORS TEAMS & TEAMLEADS SCALABLE TEAMS 7 best practices across various client 6 engagements. 5 (engineers) 4 Think of it like this: they often al- 3 ready cooperate with other mar- 2 ket-leading companies and they Team size Team 1 ONSITE TRANSITION OFFSITE know very well what are engineer- ing best-practices that others are 1 2 3 4 5 6 7 8 using. That’s big. Their consulting Time (months) capability is precious. Suppliers that offer Team Extension Team Extension Supplier management experience Model have fewer distractions from is critical to ensure efficient and ef- internal politics, leading to higher Model fective ramp-up, minimum client productivity. They are also capable management overhead and main- of looking at things from a different In the Team Extension Model, tenance of the high level of commu- angle and coming with fresh ideas Serengeti is a supplier responsi- nication required for a high-trust col- for problem-solving. ble for maintaining a stable offsite laborative environment. development team that seamless- ly integrates with the client’s in- Once activated, the Team Exten- Limitations and ternal engineering team. sion Model is agile, efficient, and scalable. Challenges Serengeti is responsible for manag- ing the remote team and delivering Basically, we become your offsite team. If the supplier team is kept too according to the client’s roadmap, We become your trusted partner. small by the client (<5), then they product requirements, and timeline. may not leverage the full benefits Once the Team Extension Model is of supplier management. in place; it is perfectly complement- Why the Team ed by supplier consulting capabilities If gaps in the work require core teams Extension Model is -- where the client can benefit from to be dissolved and re-established, suppliers’ broad technical and busi- much of the learning and scalability the right approach ness experience. benefits are lost. A core team of en- gineers must always be maintained The Team Extension Model is How the Team Extension Model for Team Extension Model to deliver generally considered the most helps specifically with core prod- maximum effectiveness. successful approach for achiev- uct development? ing long-term, win-win outsourc- Likewise, if the anticipated duration ing relationships for core software You can add engineers and keep of the engagement is too short, there product development. your internal processes. Everyone is less time for the client to benefit working on your product should from the alignment and knowledge In this model, the supplier maintains be using the same processes, transfer that is achieved during the a dedicated core team that emulates tools and quality standards. If you engagement ramp-up phase. an engineering center owned by the have a flat organization, increas- client. Its advantages are scalability ing headcount creates an addi- We help you find the right mix to and flexibility in team size, composi - tional internal difficulty for man- get your core products upgraded or tion and skill set, as well as the add- agement. Team Extension model in-market. We do it faster, more ef- ed focus of team management ex- provides self – managed autono- fectively, and more productively than perienced in similar engagements. mous teams. an internal team can do alone. SERENGETI | DATA & TECH SHEET 2 PROMISING THE POSSIBLE, DELIVERING EVEN MORE! About Serengeti Breakdown of Serengeti’s and ISO 27001:2013 certified. Engineers education level These certificates are of utmost im- portance because they confirm the Serengeti is an international soft- 6% quality of the organization’s quality - ware development nearshoring and High management and information secu consulting company. School rity management. It was founded in 2007 and has been ISO certification improves the ser- continuously growing revenue, em - 34% vice and standardizes the entire ployee count, and level of expertise. Bachelor business. Because of our distinctive engage - 60% Master & Ph.D. ment model, we have become a val - Our work is mostly client’s core ued partner for companies in the fi - product development. Therefore, nancial, logistics, energy, healthcare, maximum security and confidenti- and industrial manufacturing. ality are a top priority. We take cli- ent domain know-how and IP rights Our slogan is “Promising the pos - protection very seriously and ensure sible, delivering even more!”. that our clients, with our teams, have More than 60% of our newly recruit- same or better protection as they Our top priority is to provide pro - ed engineers come to us via inter- would have with their internal devel- fessional services that exceed the nal references while we hire the rest opment teams. expectations of what our clients of engineers after a rigorous selec- imagine could be possible with out - tion process, where the job is offered Our ISO certificate and other mea- sourced engineering. only to 15% of candidates. sures help ensure protection. We seat each client’s team in a sepa- Teamwork is one of our core capa- Although recruiting talented soft- rate room, our teams go through bilities -- both between Serenge- ware engineers is challenge every- strict preparation and education ti engineers and between our engi- where in the world, Serengeti uses for every new engagement, we neers and your engineers. We select its exceptional employer brand to have rigorous internal processes and foster those unique individu- attract a large number of good and rules about which content and als with strong talent, great attitude, candidates. knowledge can be shared, we pro- and energy, and ensure that they will vide strong management involve- always work well within a team. Serengeti is also ISO 9001:2015 ment and control. Tech Sheet SELECTED TECHNOLOGIES .NET framework related Software testing technologies: SQL; TOAD), PostgreSQL,
Load more

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]