DOCSLIB.ORG

Build-Management Mit Marktüblichen Tools

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Build-Management Mit Marktüblichen Tools Build-Management mit marktüblichen Tools Björn Feustel Orientation in Objects GmbH Weinheimer Str. 68 Steffen Schluff 68309 Mannheim www.oio.de Version: 2.0 [email protected] Gliederung • Einleitung • Issue-Tracker und IDE • SCM und CI-Server • Release Management • Continuous Delivery • Zusammenfassung und Ausblick © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 2 1 Gliederung • Einleitung • Issue-Tracker und IDE • SCM und CI-Server • Release Management • Continuous Delivery • Zusammenfassung und Ausblick © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 3 Build-Infrastructure – What‘s the fuss? • Ein guter Entwicklungsprozess ist einfach, flexibel und praxisorientiert, d.h.: – Reibungslose Arbeit im Team – Schnelle Entwicklungszyklen – Inhärenter Qualitätsanspruch – Gute Planung und Steuerung • Eine Build-Infrastruktur muss das unterstützen, z. B. durch: – Bereitstellen gemeinsamer, integrierter Entwicklungswerkzeuge – Automatisieren von wiederkehrenden Prozessen – Vorgeben und Prüfen von Konventionen, z.B. Metriken – Vereinfachen der Projektkontrolle • Und wen betrifft es? © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 4 2 Rollenverständnis • Rollenbegriffe sind abhängig • Im Kontext der Präsentation von Projektgröße / -struktur, – Team Organisation • Entwickler, Spezialisten • Ändert den Sourcecode – Developer, Architect • Erstellt Tests/sichert die – Tester / QA Qualität • Kennt (und verbessert) den – Release Engineer & Manager Build-Prozess – Product & Project Manager – Product Owner – Controller – Scrum Master • Scrum Master • Pflegt und optimiert das Projekt • Überwacht und steuert den Projektfortschritt – Stakeholder • Product Owner und Interessenten • Bestimmen die Ziele und Prioritäten © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 5 Bausteine einer modernen Build-Infrastruktur IDE Eclipse Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 6 3 Gliederung • Einleitung • Issue-Tracker und IDE • SCM und CI-Server • Release Management • Continuous Delivery • Zusammenfassung und Ausblick © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 7 Issue-Tracker IDE Eclipse Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 8 4 Issue-Tracker – Synopsis • Aufgabe IDE – Erfasst alle Änderungen und Aktivitäten Issues • Bug Tracking vs. Issue Management vs. SCRUM SCM CI – Ermöggjpglicht die Projektplanung • Features, Versionen, Fix-Termine, Kapazität – Gibt verbindliche Auskunft über den Projekt(zu)stand • Nächste Aufgaben, Versionsfortschritt, Arbeitsauslastung – Entkopplung der Entwicklung von ablenkenden Prozessen • Requirements Management, Change Management • Rollen und Verwendung – Alle: Ermitteln und Pflege des Projektstatus – Alle: Projjpektplanung – Team: Bereitstellen des Arbeitskontexts (Mylyn / Eclipse) • Produkte – Atlassian JIRA, Bugzilla, Roundup, FogBugz, Trac © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 9 IDE – Integrated Development Environment IDE Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 10 5 IDE – Synopsis • Aufgabe IDE – Zentrales Arbeitswerkzeug der Entwickler Issues SCM CI – Maximierunggp der Entwicklerproduktivität • Rollen und Verwendung – Team: Entwicklers Habitat – Team: Allgemeiner Zugriff auf SCM (Subversive) – Team: Kontextbezogener Zugriff auf Issue-Tracker (Mylyn) • Produkte – Eclipse, NetBeans, IntelliJ IDEA © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 11 Demonstration • Issue Tracker: IDE – Organisation der Issues / Release-Notes Issues – Anbindunggp an IDE per Myyylyn (()Atlassian IDE Connector) SCM CI •IDE: IDE – SVN Integration Issues – Changesets verwalten mit Mylyn SCM CI © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 12 6 Issue-Tracker – Das Build-System wächst… IDE Eclipse Mylyn Connector Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 13 IDE – Das Build-System wächst… Subversive IDE Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 14 7 Issue-Tracker – Best Practices & Konventionen • Nachvollziehbarkeit / Reproduzierbarkeit IDE – Arbeiten immer im Kontext eines Issues Issues – Issues nach Versionen erfassen SCM CI • Aktualität – Issues immer auf Personen zuordnen – Änderungen unmittelbar dokumentieren – Medienbruch für den Entwickler vermeiden (z. B. mit Mylyn) – Organisation der Issues optimieren (z.B. mit Greenhopper) • Als Single Point of Truth etablieren – Berührungsängste bei allen Beteiligten abbauen • Aber: Individuals and interactions over processes and tools (Agile Manifesto) © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 15 IDE – Best Practices & Konventionen • Projektweite Vorgaben für alle IDE – Die gleiche IDE (Produkt, Plugins) Issues SCM CI – Das ggg(gleiche Vorgehen (Handling der Issues) – Die gleichen Einstellungen (Code Formatter, Code Syntax, …) • Vermeiden von Tool-Brüchen – Integrierter SVN Client – Integriertes Deployment in lokale Testserver (pre-tested Commit) • Optimieren des Arbeitsflusses – Task/Context Management (z. B. Mylyn / Eclipse oder Cube‘n / NetBeans) – Automatische Prozesse (z. B. „Save Actions“ / Eclipse) • Aber: Build-Prozess muss außerhalb der IDE funktionieren © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 16 8 Gliederung • Einleitung • Issue-Tracker und IDE • SCM und CI-Server • Release Management • Continuous Delivery • Zusammenfassung und Ausblick © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 17 SCM – Software Configuration Management IDE Subversive Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SCM CI-Server Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 18 9 SCM – Synopsis • Aufgabe IDE – Verwaltung sämtlicher Quellartefakte Issues SCM CI • Sourcen, Konfiguration, Dokumentation – Zusammenarbeit im Team ermöglichen – Versionsverwaltung / Baselining • Rollen und Verwendung – Alle: Zugriff auf alle Artefakte und Dokumentation (ViewVC / SVN) – Alle: Nachvollziehen von Änderungen (JIRA Subversion Plugin) – Team: Grundlaggpe für parallele Entwicklung g( (Branch/Merge) • Produkte – SVN, Git, Perforce, Mercurial, CVS © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 19 CI-Server – Continuous Integration Server IDE Subversive Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SVN Plugin SCM CI-Server View VC Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 20 10 CI-Server – Synopsis • Aufgabe IDE – Qualitätssicherung Issues • Automatische Integration SCM CI • AfühAusführen von TtEtllTests, Erstellen von Repor ts • Qualitätshistorie und Trends aufzeigen – Gewährleisten der Reproduzierbarkeit • Ausführen von Referenz-Builds • Automatisches Markieren im SCM – Automatisches Erstellen und Ausliefern des Produktes • Instanziieren der Deployment Pipeline • Rollen und Verwendung – Team: Integrations- und Qualitätsfeedback • Produkte – Hudson, Jenkins, Bamboo, TeamCity, Go, CruiseControl © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 21 Demonstration •SCM: IDE – Nachvollziehbarkeit in JIRA Issues – Reppygository Zugriff mit ViewVC SCM CI •CI-Server: IDE – SVN Anbindung Issues – JIRA Plugin für Hudson SCM CI © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 22 11 SCM – Das Build-System wächst… IDE Subversive Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SVN Plugin SCM CI-Server View VC Subversion Hudson & ViewVC © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 23 CI-Server – Das Build-System wächst… IDE Subversive Eclipse Mylyn Issue-Tracker Atlassian JIRA & Greenhopper SVN Plugin JIRA Plugin SCM CI-Server View VC Subversion Hudson & ViewVC SVN Plugin © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 24 12 SCM – Best Practices & Konventionen • Optimieren des Projektflusses IDE – Tooling beherrschen (Merging) Issues – Häufige Check-ins & Merges (aber: Head stabil halten) SCM CI – Check-in immer au f ein Issu e bez ogen ( z.B . SVN -Hook) – Atomare Check-ins mit aussagekräftigen Kommentaren • Mechanismen zur Projektverfolgung nutzen – Zugriff für alle ermöglichen: ViewVC, Tortoise – Benachrichtigungen (z.B. automatischer Mailversand oder RSS-Feeds) • Konsistenz, Vollständigkeit und Ordnung wahren – Jede Version der Software ist aus dem SCM reproduzierbar – Zentrales Repository bei DVCS verwenden – Alte Daten löschen • Aber: Bei SCM gibt es kein „aber“! © 2011 Orientation in Objects GmbH Build-Management mit marktüblichen Tools 25 CI-Server – Best Practices & Konventionen • Optimieren des Projektflusses IDE – Abwarten des CI-Laufs, ggf. sofort claimen/reparieren Issues – Tests lokal ausführen vor dem Check-in (Pre-Commit Test) SCM CI – Don‘t commit on a broken bu ild – Quantität & Qualität der Tests muss stimmen • Optimieren
Load more

Recommended publications
  • Tuto Documentation Release 0.1.0
    Tuto Documentation Release 0.1.0 DevOps people 2020-05-09 09H16 CONTENTS 1 Documentation news 3 1.1 Documentation news 2020........................................3 1.1.1 New features of sphinx.ext.autodoc (typing) in sphinx 2.4.0 (2020-02-09)..........3 1.1.2 Hypermodern Python Chapter 5: Documentation (2020-01-29) by https://twitter.com/cjolowicz/..................................3 1.2 Documentation news 2018........................................4 1.2.1 Pratical sphinx (2018-05-12, pycon2018)...........................4 1.2.2 Markdown Descriptions on PyPI (2018-03-16)........................4 1.2.3 Bringing interactive examples to MDN.............................5 1.3 Documentation news 2017........................................5 1.3.1 Autodoc-style extraction into Sphinx for your JS project...................5 1.4 Documentation news 2016........................................5 1.4.1 La documentation linux utilise sphinx.............................5 2 Documentation Advices 7 2.1 You are what you document (Monday, May 5, 2014)..........................8 2.2 Rédaction technique...........................................8 2.2.1 Libérez vos informations de leurs silos.............................8 2.2.2 Intégrer la documentation aux processus de développement..................8 2.3 13 Things People Hate about Your Open Source Docs.........................9 2.4 Beautiful docs.............................................. 10 2.5 Designing Great API Docs (11 Jan 2012)................................ 10 2.6 Docness.................................................
    [Show full text]
  • Application Lifecycle Management Tools Open Source
    Application Lifecycle Management Tools Open Source Posh and tropistic Christofer congees almost despondingly, though Sam humiliating his breastworks recoins. Jorge usually assassinates astringently or disrupt crustily when interterritorial Marko voids streakily and convivially. Irresponsible Vijay unround broadly. With the software changes into three core business reason for anyone using powerful lifecycle tools across public activity management The package includes OSS project management tool Redmine and version. This year open source ALM tuleap httpwwwenaleancomentuleap is altogether good start. ALM tools automate the software development and deployment processes help. Micro Focus Application Lifecycle Management ALM software and solutions. Virtual flavor of the product with its embedded and application software before. Greg Lindhorst Principal Program Manager Thursday January 14 2021. The more List and Open-source Tools View ahead complete list ANT Anypoint Platform. Application Lifecycle Management Tools ALM is the continuous process of. Top 10 Application Lifecycle Management Tools For end Year. A degree to two the limitations of save open-source circuit otherwise inadequate tool. Best Free Application Lifecycle Management Software 2021. Each document type main source code is managed with SubversionSVN with. It is free of tools are the advent of the use after year after going through it connects people meet business outcomes as and open application source tools? Application Lifecycle Management SoftLanding. Top Application Lifecycle Management ALM Toolsets InfoQ. They also have original single proponent of truth providing any relevant. Then view the software projects, open application lifecycle management tools on open source option, and hybrid it can create and. Software lifecycle management SLM is the discipline for managing.
    [Show full text]
  • Making Visual Studio Team System Work in Your Organisation Streamline Your Bug Handling and Development Management System
    Making Visual Studio Team System work in your Organisation Streamline your bug handling and development management system Bikes and Mackas… News Flash Visual Studio Team Edition for Database Professionals •New Visual Studio Database Project – import your database schema and put under source control. – build update scripts or packages and provides a deploy tool to the specified database. • Rename Refactoring • New T-SQL Editor • SchemaCompare • DataCompare • Database Unit Testing – using T-SQL or managed code. • DataGenerator – data based upon your existing production databases – can be deployed to a database prior to running unit tests thus ensuring consistent test results About Adam • Chief Architect for www.ssw.com.au doing: – internal corporate development and – generic off-the-shelf databases – Clients: Royal & SunAlliance, Westbus, Microsoft… • SSW Develops custom solutions for businesses across a range of industries such as Government, banking, insurance and manufacturing since 1990 • President .Net User Group, Sydney • Speaker for Microsoft TechEd and Roadshows, Dev Conn, VSLive…. • Microsoft Regional Director, Australia • [email protected] Agenda 1.History of Bug Systems 2. Exploring VSTS / TFS (a tour) 3. What’s wrong with VSTS for me 4. The Education - What you can customize 5. The Solution - including 3rd Parties How Bug Tracking Systems Work • Everyone needs one – even Microsoft! • Basic Requirements –Searchable – Reportable – Notifications when done •Nice-To-Haves – Source Control Integration – IDE integration (optional)
    [Show full text]
  • A Platform for Software Debugging and Crash Reporting
    Backtrace - A Platform for Software Debugging and Crash Reporting The Backtrace Vision 1 The Backtrace Platform 2 Capture 2 Analyze 3 Resolve 4 Comparing Backtrace with Generic Error Monitoring Tools 5 Backtrace Advantages 6 Feature & Capabilities List 8 The Backtrace Vision Backtrace was founded with a vision to build the best cross-platform, native application crash and error reporting technology for today’s complex software, video game systems, embedded technology, and IoT devices. The software development teams that work in these environments now have a greater impact on how the company performs. When software fails to perform consistently, customers will disappear and employees will function less efficiently. Backtrace developed a platform that empowers organizations to make new and better choices for investing in software. The Backtrace platform has broken new ground with technology that: A. Captures and analyzes crash data from multiple platforms, including desktop (Windows, Mac), mobile (iOS, Android) server systems (Linux), embedded devices (Linux, RTOS), and video game consoles, with new levels of granularity. B. Provides teams with easy to use analytics to prioritize bugs and application failures based on their impact. C. Enables collaboration and integration with the tools you have in place today to speed ability to resolve the issue. Page 1 of 9 Proprietary The Backtrace Platform Backtrace gives your team the automation and diagnostic tools they need to spot errors that matter, understand their impact, explore the context, and zero in on causes in hours or minutes instead of days or weeks. Backtrace is a turn-key solution that was purpose-built for crash and exception analysis.
    [Show full text]
  • Jenkins Job Builder Documentation Release 3.10.0
    Jenkins Job Builder Documentation Release 3.10.0 Jenkins Job Builder Maintainers Aug 23, 2021 Contents 1 README 1 1.1 Developers................................................1 1.2 Writing a patch..............................................2 1.3 Unit Tests.................................................2 1.4 Installing without setup.py........................................2 2 Contents 5 2.1 Quick Start Guide............................................5 2.1.1 Use Case 1: Test a job definition................................5 2.1.2 Use Case 2: Updating Jenkins Jobs...............................5 2.1.3 Use Case 3: Working with JSON job definitions........................6 2.1.4 Use Case 4: Deleting a job...................................6 2.1.5 Use Case 5: Providing plugins info...............................6 2.2 Installation................................................6 2.2.1 Documentation.........................................7 2.2.2 Unit Tests............................................7 2.2.3 Test Coverage..........................................7 2.3 Configuration File............................................7 2.3.1 job_builder section.......................................8 2.3.2 jenkins section.........................................9 2.3.3 hipchat section.........................................9 2.3.4 stash section...........................................9 2.3.5 __future__ section.......................................9 2.4 Running.................................................9 2.4.1 Test Mode...........................................
    [Show full text]
  • Discovering Community Patterns in Open-Source: a Systematic Approach and Its Evaluation
    Empirical Software Engineering https://doi.org/10.1007/s10664-018-9659-9 Discovering community patterns in open-source: a systematic approach and its evaluation Damian A. Tamburri1 · Fabio Palomba2 · Alexander Serebrenik3 · Andy Zaidman4 © The Author(s) 2018 Abstract “There can be no vulnerability without risk; there can be no community without vulnerability; there can be no peace, and ultimately no life, without community.” - [M. Scott Peck] The open-source phenomenon has reached the point in which it is virtually impossible to find large applications that do not rely on it. Such grand adoption may turn into a risk if the community regulatory aspects behind open-source work (e.g., contribution guidelines or release schemas) are left implicit and their effect untracked. We advocate the explicit study and automated support of such aspects and propose YOSHI (Yielding Open-Source Health Information), a tool able to map open-source communities onto community patterns,sets of known organisational and social structure types and characteristics with measurable core attributes. This mapping is beneficial since it allows, for example, (a) further investigation of community health measuring established characteristics from organisations research, (b) reuse of pattern-specific best-practices from the same literature, and (c) diagnosis of organ- isational anti-patterns specific to open-source, if any. We evaluate the tool in a quantitative empirical study involving 25 open-source communities from GitHub, finding that the tool offers a valuable basis to monitor key community traits behind open-source development and may form an effective combination with web-portals such as OpenHub or Bitergia. We made the proposed tool open source and publicly available.
    [Show full text]
  • Atlassian: Analysis and Strategic Recommendation
    University of Montana ScholarWorks at University of Montana Undergraduate Theses and Professional Papers 2017 Atlassian: Analysis and strategic recommendation Ryann M. Carlson University of Montana, Missoula, [email protected] Follow this and additional works at: https://scholarworks.umt.edu/utpp Part of the Strategic Management Policy Commons Let us know how access to this document benefits ou.y Recommended Citation Carlson, Ryann M., "Atlassian: Analysis and strategic recommendation" (2017). Undergraduate Theses and Professional Papers. 167. https://scholarworks.umt.edu/utpp/167 This Professional Paper is brought to you for free and open access by ScholarWorks at University of Montana. It has been accepted for inclusion in Undergraduate Theses and Professional Papers by an authorized administrator of ScholarWorks at University of Montana. For more information, please contact [email protected]. ATLASSIAN: ANALYSIS AND STRATEGIC RECOMMENDATION By RYANN MARIE CARLSON Undergraduate Professional Paper presented in partial fulfillment of the requirements for the University Scholar distinction Davidson Honors College University of Montana Missoula, MT May 2017 Approved by: Suzanne Tilleman, Ph.D., Faculty Mentor Management and Marketing Department, School of Business Administration ABSTRACT Carlson, Ryann, B.S., May 2017 Management Information Systems Atlassian: Analysis and strategic recommendation Faculty Mentor: Suzanne Tilleman, Ph.D. This research consists of an external and internal analysis of, as well as a strategic recommendation for Atlassian, an Australian software company. The external analysis will use various frameworks to analyze the following: changes and trends in the environment, Porter’s Five Forces industry analysis, competitor analysis, industry segmentation and demand issues and opportunities in the industry. The internal analysis will use various frameworks to perform an internal resource assessment, financial resources assessment and assessment of opportunities for the company.
    [Show full text]
  • Spiraplan External Bug Tracking Integration Guide
    SpiraTest / SpiraTeam / SpiraPlan® | External Bug-Tracking Integration Guide Inflectra Corporation Date: July 8th, 2019 Contents Introduction SpiraTest® provides an integrated, holistic Introduction ........................................... 1 Quality Assurance (QA) management solution that manages requirements, tests and incidents 1. Setting up Data Synchronization ...... 2 in one environment, with complete traceability from inception to completion. 2. Using SpiraTeam with JIRA 5+ ........ 9 SpiraTeam® is an integrated Application 3. Using SpiraTeam with JIRA 3 / 4.... 34 Lifecycle Management (ALM) system that manages your project's requirements, releases, 4. Using SpiraTest with Bugzilla ......... 48 test cases, issues and tasks in one unified environment. SpiraTeam® contains all of the 5. Using SpiraTest with MS-TFS ........ 60 features provided by SpiraTest® - our highly acclaimed quality assurance system and 6. Using SpiraTest with FogBugz ....... 84 SpiraPlan® - our agile-enabled project management solution. 7. Using SpiraTeam with Mantis ......... 96 However, many organizations may be already 8. Using SpiraTeam with ClearQuest 107 using other bug-tracking systems and not want to have to migrate all their users over to 9. Using SpiraTeam with IBM RTC... 119 SpiraTeam. Therefore SpiraPlan, SpiraTest and SpiraTeam are capable of integrating with a 10. Using Spira with Axosoft 14+ ..... 127 variety of commercial and open-source bug- tracking systems. 11. Using SpiraTeam with Redmine . 138 This guide outlines how to integrate and use 12. Using Spira with VersionOne...... 149 SpiraTest, SpiraPlan and SpiraTeam in conjunction with other external Bug/Issue 13. Using Spira with OnTime 11 ....... 159 Tracking systems. 14. Using Spira with GitHub ............. 172 This guide assumes that the reader is familiar with both SpiraTeam and the appropriate tool 15.
    [Show full text]
  • Documentation for JIRA Administrators 7.0 Documentation for JIRA Administrators 7.0 2
    Documentation for JIRA Administrators 7.0 Documentation for JIRA Administrators 7.0 2 Contents Installing JIRA applications . 6 JIRA application requirements . 6 Installing Java . 8 Supported platforms . 10 End of support announcements . 13 Installing JIRA applications on Windows . 16 Uninstalling JIRA applications from Windows . 21 Installing JIRA applications on Linux . 21 Uninstalling JIRA applications from Linux . 26 Connecting JIRA applications to a database . 26 Connecting JIRA applications to PostgreSQL . 27 Connecting JIRA applications to MySQL . 30 Connecting JIRA applications to Oracle . 35 Connecting JIRA applications to SQL Server 2008 . 37 Tuning database connections . 41 Surviving connection closures . 52 Switching databases . 54 Installing JIRA applications from an archive file on Windows, Linux or Solaris . 55 Installing JIRA Data Center . 58 Running the setup wizard . 62 JIRA applications and project types overview . 65 Licensing and application access . 68 License compatibility . 69 Extending JIRA applications . 70 Administering projects and links across multiple applications . 71 Integrating with development tools . 72 Administering Bitbucket and GitHub with JIRA applications . 76 Linking a Bitbucket or GitHub repository with JIRA . 77 Managing linked Bitbucket and GitHub accounts . 83 Enabling DVCS smart commits . 84 Configure Automatic Team Invites . 85 Synchronize an account . 86 Troubleshoot the DVCS Connector . 87 Integrating with collaboration tools . 91 Using AppLinks to link to other applications . 93 Integrating with other tools . 95 Listeners . 96 Managing add-ons . 98 Managing webhooks . 99 Services . 101 Upgrading JIRA applications . 102 Upgrading JIRA applications manually . 103 Upgrading JIRA applications with a fallback method . 109 Upgrading JIRA applications using a rapid upgrade method . 113 Skipping major versions when upgrading JIRA applications .
    [Show full text]
  • Remote Agents — Insecure Agents Would Result in Spurious Builds
    Build and Test Automa0on at Livermore Compung Naonal Center for Computaonal Sciences Seminar Presented at Oak Ridge Naonal Laboratory Todd Gamblin Center for Applied Scien#fic Compu#ng October 20, 2015 LLNL-PRES-678531 This work was performed under the auspices of the U.S. Department of Energy by Lawrence Livermore National Laboratory under contract DE-AC52-07NA27344. Lawrence Livermore National Security, LLC Modern so8ware developers employ a range of collaborave tools. § Collaborave web applicaons: — Wikis (MediaWiki, Trac, Confluence) — Issue trackers (RoundUp, Bugzilla, JIRA) — Repository systems (Stash, Bitbucket, GitHub, GitLab) § Automated Tes#ng: — Build & Test / Con#nuous Integraon (Jenkins, Bamboo, Travis CI) — Also generally involves a web dashboard. § Package Management / automated build: — Homebrew, MacPorts, RPM, apt-get, yum, BSDPorts, Emerge/Gentoo — For HPC: Spack, Smithy, Easybuild For many open source projects, this infrastructure is freely available. Not widely available inside HPC centers. 2 LLNL-PRES-678531 This talk gives an overview of two tools currently in use at Livermore Compung 1. Atlassian Bamboo Con#nuous Integraon — Security challenges for CI — How Bamboo was deployed securely at LLNL 2. The Spack Package Manager — Developed at LLNL — Handles combinatorial build explosion Spack — Now in use to build/test produc#on codes 3 LLNL-PRES-678531 Web-based tools are o8en difficult to deploy in HPC environments § Two-factor authen#caon o^en hard to integrate with many web applicaons. § Security policies require more strict permissions than most open source tools offer. — Tools o^en assume trust among users. — Many tools don’t have fine-grained access controls. § Maintenance costs are higher with security — With no permissions, need an instance per team • Centers can’t maintain all the instances.
    [Show full text]
  • Estudos Preliminares
    IGOR BESSA MENEZE PODER JUDICIÁRIO S JOSE MARIO VIANA JUSTIÇA DO TRABALHO BARBOSA JUNIOR LENIVIA TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO DE CASTRO E SILVA MENDES FRANCISC O JONATHAN SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO REBOUCAS MAIA Estudos Preliminares Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. Estudos Preliminares - Contratação de Suporte Técnico, incluindo atualizações evolutivas e corretivas, para a ferramenta Atlassian Jira e Plugins eazyBI Reports and Charts e Git Integration. 1 PODER JUDICIÁRIO JUSTIÇA DO TRABALHO TRIBUNAL REGIONAL DO TRABALHO DA 7ª REGIÃO SECRETARIA DE TECNOLOGIA DA INFORMAÇÃO E COMUNICAÇÃO Sumário ANÁLISE DE VIABILIDADE DA CONTRATAÇÃO (Art.14) 4 Contextualização 4 Definição e Especificação dos Requisitos da Demanda (Art. 14, I) 5 Requisitos de Negócio 5 Requisitos Técnicos 6 Requisitos Temporais 6 Soluções Disponíveis no Mercado de TIC (Art. 14, I, a) 7 Contratações Públicas Similares (Art. 14, I, b) 10 Outras Soluções Disponíveis (Art. 14, II, a) 11 Portal do Software Público Brasileiro (Art. 14, II, b) 11 Alternativa no Mercado de TIC (Art. 14, II, c) 12 Modelo Nacional de Interoperabilidade – MNI (Art. 14, II, d) 12 Infraestrutura de Chaves Públicas Brasileira – ICP-Brasil (Art. 14, II, e) 12 Modelo de Requisitos Moreq-Jus (Art. 14, II, f) 12 Análise Comparativa dos Custos das Soluções (Art. 14, III) 12 Escolha e Justificativa da Solução (Art. 14, IV) 15 Descrição da Solução (Art. 14, IV,a) 21 Alinhamento da Solução (Art. 14, IV, b) 22 Benefícios Esperados (Art. 14, IV, c) 22 Relação entre a Demanda Prevista e a Contratada (Art.
    [Show full text]
  • Design Options of Store-Oriented Software Ecosystems: an Investigation of Business Decisions ∗
    Design Options of Store-Oriented Software Ecosystems: An Investigation of Business Decisions ∗ Bahar Jazayeri1, Olaf Zimmermann2, Gregor Engels1, Jochen K¨uster3, Dennis Kundisch1, Daniel Szopinski1 1 Paderborn University, Germany fbahar.jazayeri,gregor.engels,dennis.kundisch,[email protected] 2 University of Applied Sciences of Eastern Switzerland, Switzerland [email protected] 3 Bielefeld University of Applied Sciences, Germany [email protected] Abstract. Nowadays companies like Apple create ecosystems of third- party providers and users around their software platforms. Often online stores like Apple App Store are created to directly market third-party solutions. We call such ecosystems store-oriented software ecosystems. While the architecture of these ecosystems is mainly derived from busi- ness decisions of their owners, ecosystems with greatly different archi- tectural designs have been created. This diversity makes it challenging for future ecosystem providers to understand which architectural design is suitable to fulfill certain business decisions. In turn, opening a plat- form becomes risky while endangering intellectual property or scarifying quality of services. In this paper, we identify three main design options of store-oriented software ecosystems by classifying existing ecosystems based on similarities in their business decisions. We elaborate on the design options, discuss their main contributions, and provide exemplary ecosystems. Our work provides aspiring ecosystem providers with the reusable knowledge of existing ecosystems and helps them to take more informed architectural decisions and reduce risks in future. Keywords: Software ecosystems, Reusable designs, Variabilities 1 Introduction Software ecosystems have become an emerging architectural approach for many companies to grow. The term software ecosystem is inspired from ecological ecosystems that are the result of an interplay between organisms as well as interactions with a physical environment [1].
    [Show full text]