DOCSLIB.ORG

Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs 1/30/13 FishEye and Crucible 2.8 Released: Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs Atlassian Home Get Help Marketplace Search Blogs All Blogs Products Developer News Dev Tools Releases, tips, tricks and a FishEye and Crucible 2.8 Released: Faster whole lot more about source Browsing, Speedier Collaboration Cycles code, builds, code review and everything in between. Dev Tools RSS Feed By Giancarlo Lionetti, Product Marketing Manager - … Dev Tools, Crucible, FishEye Dev Tools Email Subscription On August 15, 2012 Dev Tools Archives Introducing the newest versions of FishEye and Crucible. Together, FishEye and Crucible put Category Archive... development teams into the fast lane as they collaborate on code – sharing, visualizing and viewing code repositories, as well as performing collaborative peer code reviews. FishEye 2.8 and Crucible 2.8 make code browsing and sharing whiplash fast – regardless of whether you’re using Git, SVN or another SCM. Both FishEye and Crucible deliver tight integration with JIRA, Popular Posts Atlassian’s project tracking tool, and connect to Subversion, CVS, Git, Mercurial and Perforce. Stash 2.0 – Powered by Git. Controlled by You. From SVN to Git: How Atlassian Made the Switch Without Sacrificing Active Development FishEye and Crucible 2.9 Released: Focus on Performance Simplified Administration, Stronger JIRA Integration In software development, every millisecond counts. Development teams are constantly trying to From SVN to Git: How Atlassian shave off seconds for each operation performed and the sum of each time savings drives Made the Switch Without Sacrificing whether projects hit their release date and whether products succeed or fail. The FishEye and Active Development – the Technical Crucible team are constantly gnawing on this challenge of improving dev speed. Browsing Side source, searching for artifacts, creating reviews and speeding up collaboration cycles are a Feel the Love with Bamboo 4.4! critical part of the development process, and they should be fast. We’ve structured our effort for both today’s releases and our upcoming releases on this theme. Popular Tags Faster Page Loads, Smoother Browsing plugins 186 Seeing the big picture is key for all developers, especially team leads and their wikis 126 managers. So, we started with the concept of summit 114 improving page load times as the area where press releases 109 we can create the biggest customer benefits. While the improved page load times ripple out atlassiantv 91 across the product, let’s take a sec to deep wiki 82 dive into the impact we find with Activity development tools 81 Streams. Streams provide a high level view plugin 81 into your projects, showing commit and code review activity in real-time. They are not just video and audio 74 provided on the project level, you can view buzz 73 Activity Streams for repositories, directories, author, project and even individual files. Activity Stream page load times have improved by up to 50 times. Check out the difference from data tested on a load testing instance of FishEye and Crucible. Local Atlassian Blogs Along with making page loads faster, we also made sure that the user experience on the Activity Spain Blog blogs.atlassian.com/2012/08/fisheye-crucible-28-dev-speed-code-collaboration/ 1/6 1/30/13 FishEye and Crucible 2.8 Released: Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs Streams improved as well. If you love Facebook and Twitter’s “infinite scroll”, you’ll enjoy the Germany Blog same experience browsing your commits and reviews chronologically on Activity Streams Japan Blog pages. Did we stop at Activity Streams? Nope. The FishEye and Crucible Performance Team made improvements to load times of other key pages, including the Projects list (that one’s for you, Enterprise users!). Getting Social Another important area for boosting team speed is accelerating the collaboration cycle. FishEye and Crucible 2.8 introduce some key social features to help assure that the right person on your team gets the right info at the right time. @mentions Easily bring members of your team into a code discussion by @mentioning them in a review or changeset comment. Just type “@” + their name as part of your comment and they will receive a notification that they have been mentioned. From there, the conversation can take place in er, *toggles*... RT @atlassian: Crucible or changeset comments where it’s available to everyone, instead of being hidden in Bamboo 4.4 is out today! Task your email. Pull them into the conversation – your code will benefit from it! goggles, Amazon VPC Why @mention? support, and other popular 1. Casually bring in contributors and stakeholders for richer collaboration. Want input requests! from a UX Designer or Product Manager who wouldn’t normally be included in a technical http://t.co/sc8B6WK1 review? A simple @mention brings them into the conversation and gives them a chance to lend their expertise. @AtlDevTools 10 hours ago 2. Draw in technical experts from inside or outside the immediate team. @mentions are a non-intrusive way to widen the discussion by inviting specific individuals for specific threads of conversation, without the burden of adding them to the review workflow every time. 3. Transparency is just plain helpful when it comes to coding. You know it, we know it. Web Filter Lite This web page is blocked because it violates network policy. If you have any questions, Please contact your netw ork administrator. Host: www.youtube.com URL: http://www.youtube.com/embed/UFNPgfQFJHk Reason: Available on kiosk computers, see reception to purchase codes. Share Code and Reviews with your Team blogs.atlassian.com/2012/08/fisheye-crucible-28-dev-speed-code-collaboration/ 2/6 1/30/13 FishEye and Crucible 2.8 Released: Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs Software development is not just about coding. It’s a network of developers collaborating on a common project. When collaborating, it is important to get information to members of your team (and outside your team) fast. Every aspect of FishEye and Crucible is easy to share between team mates because everything is just a URL away. All it takes to share any artifact with your team is switching over to your email or IM applications to share information. But we weren’t satisfied with that. FishEye and Crucible 2.8 make the sharing of information super- quick. With the new Share Button you can instantly share repositories, reviews, commits, files and diffs with members of your team or users new to FishEye and Crucible. That means no switching between applications! Click Share, specify the users you’d like to notify by username or email address, provide a quick message for context and FishEye and Crucible will keep your team up-to-date. Subversion 1.7 Support Satisfying a highly voted feature request, we now fully support Subversion 1.7, making FishEye and Crucible more compatible with your Subversion environments. Try FishEye and Crucible 2.8 New to FishEye or Crucible? Start a free trial today and get up and running in minutes. Already using FishEye or Crucible? Your upgrade awaits you. Check out our full FishEye and Crucible release notes to get started. blogs.atlassian.com/2012/08/fisheye-crucible-28-dev-speed-code-collaboration/ 3/6 1/30/13 FishEye and Crucible 2.8 Released: Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs Atlassian HipChat - Group chat and IM + productivity = awesome » Announcing Stash 2.0 - Powered by Git, Secured by You » Comments (9) Still no stash integration By Rob V on August 15, 2012 / Reply Hi Rob, We don’t have a native integration with Stash yet but linking it to FishEye / Crucible together is already possible (http://blogs.atlassian.com/2012/07/linking-your-stash-git- repositories-to-crucible-for-code-reviews). As it is mentioned in the post we chose to prioritize performance improvements for FishEye, helping our customers to stay productive as they grow. Building a native integration via AppLinks is something that we would like to offer but I cannot give you a concrete deadline regarding this. Finally I would like to mention that it is possible to leverage the plugin SDK to build integrations between FishEye / Crucible and Stash. The SDK is something that we really believe in and that we developed to give our customers the flexibility of creating their own extensions, not having to rely on us for every feature they would like to have. More information about the plugin SDK can be find at https://developer.atlassian.com/display/FECRUDEV/FishEye+and+Crucible+Plugin+Guide. Cheers, Sten Pittet FishEye / Crucible Product Manager By Sten Pittet on August 15, 2012 / Reply Is a windows service included yet? The hacks that are currently needed to make it run as a windows service are insane. By William H on August 15, 2012 / Reply Hi William, Unfortunately, a Windows service is not included in this release. We have took some time to improve our docs to hopefully make the process a bit easier. https://confluence.atlassian.com/display/FISHEYE/Installing+FishEye+on+Windows Cheers! Giancarlo Lionetti Atlassian By Giancarlo Lionetti on August 16, 2012 Hi, I was hoping this version would have a way to automate code reviews, at least to a point. Is there a way to achieve that with this version? That must be a common usecase for Crucible… Thanks, Peter By Peter T on August 16, 2012 / Reply Hi Peter, blogs.atlassian.com/2012/08/fisheye-crucible-28-dev-speed-code-collaboration/ 4/6 1/30/13 FishEye and Crucible 2.8 Released: Faster Browsing, Speedier Collaboration Cycles | Atlassian Blogs Could you expand on what you are looking for when you say automate code reviews? There is currently a plugin available for FishEye/Crucible that automatically creates a review for each commit made on a FishEye repository.
Load more

Recommended publications
  • User Documentation for Crucible 3.4 User Documentation for Crucible 3.4 2
    User documentation for Crucible 3.4 User documentation for Crucible 3.4 2 Contents Getting Started . 5 Supported platforms . 5 End of Support Announcements for Crucible . 7 End of Support Announcement for IBM ClearCase . 10 Installing Crucible on Windows . 11 Running Crucible as a Windows service . 13 Installing Crucible on Linux and Mac . 17 Configuring JIRA Integration in the Setup Wizard . 20 Starting to use Crucible . 27 Using Crucible . 35 Using the Crucible screens . 36 Using the Review Dashboard . 38 Browsing all reviews . 40 Browsing source files . 41 Crucible Icons . 42 Searching Crucible . 43 Viewing people's statistics in Crucible . 48 Browsing projects . 52 Viewing Project Statistics . 53 Changing your User Profile . 55 Using favourites . 55 Using Keyboard Shortcuts in Crucible . 57 The Crucible workflow . 58 Defining your workflow . 63 Roles and Status Classifications . 65 Creating a review . 66 Creating a review from FishEye . 70 Creating a review from JIRA . 71 Creating a review from a URL . 72 Creating a Snippet Review . 72 Creating reviews from the command line . 73 Adding content to the review . 75 Iterative reviews . 80 Creating patch files for pre-commit reviews . 83 Choosing reviewers . 90 Performing the review . 92 Starting a review . 93 Adding comments . 94 Changeset discussions . 96 Flagging defects . 97 Creating JIRA issues from the review . 98 Viewing reports . 99 Review Coverage report . 101 Completing your review . 105 Using the Review History Dialog . 107 Using RSS feeds in Crucible . 108 Using Wiki Markup in Crucible . 108 Tracking Crucible Review Metrics . 113 Using Progress Tracking . 113 Using Time Tracking . 115 JIRA integration in Crucible .
    [Show full text]
  • Jetbrains Upsource Comparison Upsource Is a Powerful Tool for Teams Wish- Key Benefits Ing to Improve Their Code, Projects and Pro- Cesses
    JetBrains Upsource Comparison Upsource is a powerful tool for teams wish- Key benefits ing to improve their code, projects and pro- cesses. It serves as a polyglot code review How Upsource Compares to Other Code Review Tools tool, a source of data-driven project ana- lytics, an intelligent repository browser and Accuracy of Comparison a team collaboration center. Upsource boasts in-depth knowledge of Java, PHP, JavaScript, Integration with JetBrains Tools Python, and Kotlin to increase the efcien- cy of code reviews. It continuously analyzes Sales Contacts the repository activity providing a valuable insight into potential design problems and project risks. On top of that Upsource makes team collaboration easy and enjoyable. Key benefits IDE-level code insight to help developers Automated workflow, to minimize manual tasks. Powerful search engine. understand and review code changes more efectively. Smart suggestion of suitable reviewers, revi- IDE plugins that allow developers to partici- sions, etc. based on historical data and intel- pate in code reviews right from their IDEs. Data-driven project analytics highlighting ligent progress tracking. potential design flaws such as hotspots, abandoned files and more. Unified access to all your Git, Mercurial, Secure, and scalable. Perforce or Subversion projects. To learn more about Upsource, please visit our website at jetbrains.com/upsource. How Upsource Compares to Other Code Review Tools JetBrains has extensively researched various As all the products mentioned in the docu- tools to come up with a useful comparison ment are being actively developed and their table. We tried to make it as comprehensive functionality changes on a regular basis, this and neutral as we possibly could.
    [Show full text]
  • Veni, Vidi, Vici
    Code Review: Veni, ViDI, Vici Yuriy Tymchuk, Andrea Mocci, Michele Lanza REVEAL @ Faculty of Informatics - University of Lugano, Switzerland Abstract—Modern software development sees code review as For example many of them leverage static code analysis a crucial part of the process, because not only does it facilitate techniques, like the ones provided by FindBugs [5], to spot the sharing of knowledge about the system at hand, but it may implementation problems. However, the results from such also lead to the early detection of defects, ultimately improving techniques are poorly integrated in a code review process, as the quality of the produced software. Although supported by we will see later. numerous approaches and tools, code review is still in its infancy, and indeed researchers have pointed out a number of We propose an approach to augment code review by inte- shortcomings in the state of the art. grating software quality evaluation, and more general design We present a critical analysis of the state of the art of code assessment, not only as a first class citizen, but as the core review tools and techniques, extracting a set of desired features concern of code review. Our approach, called Visual Design that code review tools should possess. We then present our vision Inspection (ViDI), uses visualization techniques to drive the and initial implementation of a novel code review approach quality assessment of the reviewed system, exploiting data named Visual Design Inspection (ViDI), illustrated through a set obtained through static code analysis. ViDI enables intuitive of usage scenarios. ViDI is based on a combination of visualization and easy defect fixing, personalized annotations, and review techniques, design heuristics, and static code analysis techniques.
    [Show full text]
  • Documentation for Fisheye 2.8 Documentation for Fisheye 2.8 2
    Documentation for FishEye 2.8 Documentation for FishEye 2.8 2 Contents Getting started . 8 Supported platforms . 8 End of Support Announcements for FishEye . 12 End of Support Announcement for IBM ClearCase . 14 End of Support Announcement for Internally Managed Repositories . 14 Installing FishEye on Windows . 16 Running FishEye as a Windows service . 19 Installing FishEye on Linux and Mac . 23 Starting to use FishEye . 26 Configuring JIRA Integration in the Setup Wizard . 31 Using FishEye . 38 Using the FishEye Screens . 39 Browsing through a repository . 41 Searching FishEye . 44 Viewing a File . 49 Viewing File Content . 50 Using Side by Side Diff View . 51 Viewing a File History . 53 Viewing the Changelog . 54 FishEye Charts . 56 Using Favourites in FishEye . 61 Changeset Discussions . 64 Viewing the commit graph for a repository . 64 Viewing People's Statistics . 68 Using smart commits . 70 Changing your User Profile . 75 Re-setting your password . 79 Antglob Reference Guide . 80 Date Expressions Reference Guide . 81 EyeQL Reference Guide . 82 Administering FishEye . 88 Managing your repositories . 89 Adding an External Repository . 91 CVS . 92 Git . 93 Mercurial . 96 Perforce . 98 Subversion . 101 SVN fisheye.access . 105 SVN tag and branch structure . 106 Adding an Internal Repository . 114 Enabling Repository Management in FishEye . 115 Creating Git Repositories . 117 Forking Git Repositories . 119 Deleting a Git Repository . 122 Setting up a Repository Client . 122 CVS Client . 122 Git Client . 122 Mercurial Client . 122 Perforce Client . 123 Subversion Client . 124 Native Subversion Client . 124 SVNkit Client . 126 Re-indexing your Repository . 126 Repository Options . 128 Authentication . 130 Created by Atlassian in 2012.
    [Show full text]
  • REMOTE Preferredsubmitted to Others Without His Explicit Permission
    For more on Gilbert’s job hunt visit Gilbert’s personal web site Copyright 2021 by Gilbert Healton. Gilbert’s details can not be http://resume.healton.net/ REMOTE PREFERREDsubmitted to others without his explicit permission. Gilbert Healton [email protected] Perl-5, C, Linux with strong mentoring, planning. https://www.linkedin.com/in/ghealton/ Multii-language team software engineer. Now strongest in Perl, C, shell Arenas: commands, SQL. Linux and UNIX. History of Template Toolkit, HTML, Remote work ●●●● JavaScript, Apache, TCP/IP, networking, Git, and SVN. Very strong Back ends ●●●●● design, mentoring, documentation. Great customer support. Telcom ●●●● Net Security ○●●● 2020-08 to Software Developer – SMD Delivery – ESP 2021-06 Hard Skills: bash, zsh, Remote. Coding ●●●● C, perl, lua. Working on cloud based SMTP engine. Analyst ●●●●● AWS (AL1, ✔ Feature improvements written in C and Lua. Perl tests. Design ●●●●● Athena SQL, ✔ Document processes and on boarding processes. Documents ●●●● builds, ...) ✔ Use Circonus graphs to analyze failures. Debugging ●●●● github, git, ✔ Use git and Mercurial tools for reviews and source 2038 Bug fix ●●●● Mercurial management. Networking: (hg, Fisheye, ✔ “Interrupt Team” duties included 24x7 on-call duties, ssh, rsync, ○●●● Bamboo). starting build pipelines, responding to problems & requests. dev/tcp TCP/IP sockets ○●●● 2020-03 to Shell Developer – back end – energy sector Message queues ○●●● 2020-08 EOC Soft Skills: bash, ksh, DXC Technology. Remote multinational. Migrating large distributed AIX applications to Linux. Detail attention ●●●● csh, RHEL Life Learning ●●●● ✔ Quickly migrated scripts from suite with the most scripts. Oracle, perl, Legacy Apps ●●●●● ✔ Writing scripts to scan and automate code changes. AutoSys shell Mentoring ●●●●● Scripts, ✔ Bringing automated tests to environment without any.
    [Show full text]
  • Integrating Static Code Analysis and Defect Tracking
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS Integrating Static Code Analysis and Defect Tracking MASTER THESIS Jakub Papcun Brno, 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Supervisor: Ing. RNDr. Barbora Bühnová, Ph.D. iv Acknowledgements I would like to thank my supervisor, Barbora Bühnová, for providing valuable feedback and guidance. I would also like to thank Ronny Kolb, for his patient guidance and all the advice he gave me during whole work on the thesis. Last but not least I would like to thank all members of ACT team in Honeywell ACS in Brno for all their help and inputs to my thesis. v Abstract Static code analysis is a powerful way of improving the quality of source code. Using tools such as Klocwork, issues in source code can be automatically detected. Some of those issues represent defects injected during implementation activities or even during earlier develop- ment phases. These issues should be properly tracked and analyzed. The present thesis investigates on how to best integrate static code analysis and defect tracking with the goal of using static code analysis data for project tracking and continuous improvement of the development process used by teams in Honeywell ACS. The thesis in- cludes the analysis of the state-of-the-art and state-of-the-practice regarding defect tracking from static code analysis tools.
    [Show full text]
  • Applying Agile Project Management for Accelerator Controls Software W
    RPPB05 Proceedings of ICALEPCS07, Knoxville, Tennessee, USA APPLYING AGILE PROJECT MANAGEMENT FOR ACCELERATOR CONTROLS SOFTWARE W. Sliwinski, N. Stapley, CERN, Geneva, Switzerland Abstract engineers, who are members of AB-CO group, develop Developing accelerator controls software is a frameworks, core components and complete systems. challenging task requiring not only a thorough knowledge Thus, the users’ community is diverse, the level of of the different aspects of particle accelerator operations, proficiency in programming varies and many people but also application of good development practices and within it work on temporary basis (such as project robust project management tools. Thus, there was a associates, fellows and technical students) for the Large demand for a complete environment for both developing Hadron Collider (LHC) start up. and deploying accelerator controls software, as well as the Requirements of the Process tools to manage the projects. As an outcome, a versatile development process was formulated, covering the Taking into account the needs of the controls controls software life cycle from the inception phase up to community and the specific nature of the controls domain, the release and deployment of the deliverables. In a list of requirements can be formulated which addition, a development environment was created characterize the properties of the anticipated development providing management tools that: standardize the process: common infrastructure for all the concerned projects; help • Maximise ease of use by providing a quick to organize work within project teams; ease the process of comprehension time (particularly significant for versioning and releasing; and provide an easy integration temporary members). of the test procedures and quality assurance reports.
    [Show full text]
  • TCD65-141111-2205-6028.Pdf
    1. TeamCity Documentation . 3 1.1 TeamCityReference . 4 1.1.1 What's New in TeamCity 6.5 . 4 1.1.2 Getting Started . 10 1.1.3 Concepts . 14 1.1.3.1 Agent Home Directory . 15 1.1.3.2 Agent Requirements . 16 1.1.3.3 Agent Work Directory . 16 1.1.3.4 Authentication Scheme . 16 1.1.3.5 Build Agent . 17 1.1.3.6 Build Artifact . 18 1.1.3.7 Build Chain . 18 1.1.3.8 Build Checkout Directory . 19 1.1.3.9 Build Configuration . 20 1.1.3.10 Build Configuration Template . 21 1.1.3.11 Build Grid . 22 1.1.3.12 Build History . 22 1.1.3.13 Build Log . 23 1.1.3.14 Build Number . 23 1.1.3.15 Build Queue . 23 1.1.3.16 Build Runner . 24 1.1.3.17 Build State . 24 1.1.3.18 Build Tag . 25 1.1.3.19 Build Working Directory . 25 1.1.3.20 Change . 26 1.1.3.21 Change State . 26 1.1.3.22 Clean Checkout . 27 1.1.3.23 Clean-Up . 28 1.1.3.24 Code Coverage . 28 1.1.3.25 Code Duplicates . 29 1.1.3.26 Code Inspection . 29 1.1.3.27 Continuous Integration . 29 1.1.3.28 Dependent Build . 30 1.1.3.29 Difference Viewer . 31 1.1.3.30 Guest User . 32 1.1.3.31 History Build . 32 1.1.3.32 Notifier . 33 1.1.3.33 Personal Build .
    [Show full text]
  • Atlassian Pull Request Template
    Atlassian Pull Request Template Aldrich often supervises disconcertingly when aerophobic Emanuel rebore perhaps and begirded her stylets. Lemony Vladimir still lour: high-hat and somnambulant Milo spooms quite next but convene her Antares bang. Lambert usually latch vertebrally or spices orthogonally when incommunicative Wade confabbing adjunctively and supersensibly. See details on highway page. In some cases you will want the break Issues into multiple smaller tasks. Desktop PC By SSTec Tutorials Kali Linux Installation Directly On phone Laptop Or PC. Play surface pull template that will need to shelf a repository to retention with customized message fields to get detailed or variety to rebound the jira. Compliance, privacy, platform roadmap, and more. Bind the number bitbucked pull request experience sense a web. Scale, data Service Management, Cloud, Jira Best practices, Customer stories, and more. Login To Gitlab Intellij. The other PDI components execute the processes designed with Spoon, and are executed from a comprehensive window. Description of PR that completes the offence here. JIRA dashboard you will find option open, when she click turn it, it out open a window that finger out options like are Issue Tracking, Project Management, Agile Kanban, Jira Classic and thereafter on as shown in screen shot below. Using Jira for testing, today! Using nexus with gitlab. Get the highlights in your inbox every week. Pushing never automatically does a merge. Learn well about our breathtaking games here! Chocolatey is trusted by businesses to change software deployments. No more posts to show. Learn how to create any type your issue in Bitbucket Cloud and circle track duty it.
    [Show full text]
  • Coding Horror: Setting up Subversion on Windows
    Coding Horror: Setting up Subversion on Windows http://www.codinghorror.com/blog/2008/04/setting-up-subversion... programming and human factors by Jeff Atwood * Apr 5, 2008 Seng up Subversion on Windows When it comes to readily available, free source control, I don't think you can do beer than Subversion at the moment. I'm not necessarily advocang Subversion; there are plenty of other great source control systems out there ‐‐ but few can match the ubiquity and relave simplicity of Subversion. Beyond that, source control is source control, as long as you're not using Visual SourceSafe . And did I menon that Subversion is ... free? Allow me to illustrate how straighorward it is to get a small Subversion server and client going on Windows . It'll take all of 30 minutes, tops, I promise. And that's assuming you read slowly. The first thing we'll do is download the latest Subversion Windows binary installer . At the me of wring, that's 1.46. I recommend overriding the default install path and going with something shorter: c:\svn\ Note that the installer adds c:\svn\bin to your path, so you can launch a command prompt and start working with it immediately. Let's create our first source repository, which is effecvely a system path. svnadmin create "c:\svn\repository" Within that newly created folder, uncomment the following lines in the conf/svnserve.conf file by removing the pound character from the start of each line: anon-access = none auth-access = write password-db = passwd Next, add some users to the conf/passwd file.
    [Show full text]
  • Implementing a Custom REST API with ABL Webhandler
    Implementing a Custom REST API with ABL WebHandler Chris Riddell Principal Architect, Portfolio+ Inc David Atkins Principal Solutions Architect, Progress Monday 7 October 2019 Agenda • Architecture evolution • Why Progress AppServer for OpenEdge? • OpenEdge REST API best practices • Portfolio+’s Implementation Experiences… • Wrap up Q & A 2 Remember this? Presentation (UI) Enterprise Services (API) Business Application [ABL] Service Interfaces Business Components Develop & Workflow Rules Entities Deploy & Test (ALM) Manage Data Access Data Sources Common Infrastructure Domain Services Social 3 © 20172019 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved. Reference Architecture for Cloud Deployment 4 Application Architecture 5 Why PAS for OpenEdge? Secure: Spring security framework included Scalability: Uses far less system resources Simplified: Multi-session multi-mode Agent Improved administration: Many tool options Flexibility: REST Service Interface Deployment flexibility: Supports containerization Future: Go forward AppServer for OpenEdge 6 REST Use Cases Modern Web Interfaces Mobile Apps Emerging Technologies Application Integration Modularization through Self-Service BI Microservices and Analytics 7 OpenEdge REST Service Interface Options A REST Service Interface: • Converts REST Request to ABL data • Routes that ABL data to appropriate ABL business logic • Converts ABL data to REST Response, & sets HTTP Status Code Recommended PAS for OpenEdge REST Service Interface options: • ‘No/low-code’
    [Show full text]
  • Maintaining and Securing Kerberos
    Maintaining and Securing Kerberos Tom Yu MIT Kerberos Consortium March 30, 2009 www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Overview Completed krb5-1.7 goals Rethinking the release cycle Guiding principles www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 2 Completed krb5-1.7 Goals Enhanced GSS-API error messages Cross-platform CCAPI (Mac and Windows) Kerberos Identity Management (KIM) API Master key rollover Incremental propagation Enctype negotiation Lots of Microsoft protocol extensions FAST (in progress) www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 3 Rethinking the Release Cycle Originally: 18-month cycle Proposed: 6–12 months New features available sooner Consensus of core developers Precedent: Ubuntu, GNOME, et al. www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 4 Advantages of Shorter Cycle Less scrambling to include features in release Release features only when ready Improved quality www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 5 Disadvantages of Shorter Cycle Longer maintenance lifetimes Security patch implications Possibly fewer features per release User/vendor reluctance to track releases www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 6 Topic Branches Develop new features or “topics” on branches Keep branch synchronized with trunk Integrate branch into trunk when ready Feature development can span releases Lightweight branch capability is essential www.kerberos.org © 2009 The MIT Kerberos Consortium. All Rights Reserved. Mar. 30, 2009 7 New Version Control System? Subversion (existing) Branches are heavyweight Weak merging support Git Branches are lightweight Better merging support Migration is costly Data model mismatches Hybrid approach: git-svn www.kerberos.org © 2009 The MIT Kerberos Consortium.
    [Show full text]