Developing for Remote Bamboo Agents, AtlasCamp US 2012Atlassian
Brydie McCoy, Java Developer
As more and more peoples' building demands grow, they expand from building everything locally to a distributed building system or the elastic cloud. And for OnDemand the elastic cloud is the only option. Unfortunately developing plugins for remote/elastic agents has its own set of gotchas. Most plugins written for Bamboo do not work properly on remote agents. This talk will cover the core principles of developing for remote agents, what you can and can't do, as well as more advanced topics such as data transfer and communication between the agent and the server.
Expose Yourself! How to Leverage Plugin Extensibility to Delight your Users, ...Atlassian
The document discusses how developing plugins for Atlassian products can leverage extensibility to benefit users. It encourages plugin developers to expose APIs and build integrations between plugins to provide additional functionality. The talk will cover examples of integrations GreenHopper has built, best practices for developing APIs, and techniques for building integrations that play nicely with the plugin system while maintaining backwards compatibility.
The document summarizes the key lessons learned from building the Google Plugin for Eclipse (GPE). It discusses challenges around installation, creating new web applications, running/debugging apps, supporting multiple SDK versions, and features for GWT like JSNI. Lessons included the need for stability, ease of use, classpath management, and supporting various configurations and developer needs.
Building an Eclipse plugin to recommend changes to developerskim.mens
1) The document summarizes a master's thesis defense about building an Eclipse plugin called Mendel to recommend code changes to developers based on regularities extracted from existing code.
2) Mendel uses a "genetic metaphor" to find family members of a selected code entity according to different family definitions, extract dominant traits from the family, and recommend traits for the entity that are not already implemented.
3) The thesis validates Mendel's recommendations by analyzing multiple versions of projects and checking if recommended changes were later implemented by developers. The results showed some family definitions were better suited than others for different recommendation types.
The document is a presentation by Amir Barylko on continuous integration using TeamCity. It introduces CI and its benefits, how to get started with CI using TeamCity, and provides an overview of key TeamCity concepts like source control, build agents, and notifications. The presentation concludes with a discussion on next steps and a question period.
Designing for User Experience (UX) with Atlassian ToolsAtlassian
The document discusses integrating design and development. It outlines 5 steps to solve challenges: 1) braindump to brief, 2) brief to wireframes, 3) wireframes to design, 4) design to implementation, and 5) implementation to validation. Key points include using tools like JIRA and Confluence for collaboration, bringing designs to life with prototypes, and validating designs through internal and external testing.
Continuous integration and delivery for java based web applicationsSunil Dalal
This document discusses continuous integration and delivery for Java web applications using Jenkins, Gradle, and Artifactory. It defines continuous integration and delivery and explains why they are important. It outlines the workflow and steps involved, including using source control, building and testing with Jenkins and Gradle, storing artifacts in Artifactory, running code analysis with tools like SonarQube, and deploying to test and production. Finally, it addresses some common questions around plugins, versioning, rollbacks, and build frequency.
Developing for Remote Bamboo Agents, AtlasCamp US 2012Atlassian
Brydie McCoy, Java Developer
As more and more peoples' building demands grow, they expand from building everything locally to a distributed building system or the elastic cloud. And for OnDemand the elastic cloud is the only option. Unfortunately developing plugins for remote/elastic agents has its own set of gotchas. Most plugins written for Bamboo do not work properly on remote agents. This talk will cover the core principles of developing for remote agents, what you can and can't do, as well as more advanced topics such as data transfer and communication between the agent and the server.
Expose Yourself! How to Leverage Plugin Extensibility to Delight your Users, ...Atlassian
The document discusses how developing plugins for Atlassian products can leverage extensibility to benefit users. It encourages plugin developers to expose APIs and build integrations between plugins to provide additional functionality. The talk will cover examples of integrations GreenHopper has built, best practices for developing APIs, and techniques for building integrations that play nicely with the plugin system while maintaining backwards compatibility.
The document summarizes the key lessons learned from building the Google Plugin for Eclipse (GPE). It discusses challenges around installation, creating new web applications, running/debugging apps, supporting multiple SDK versions, and features for GWT like JSNI. Lessons included the need for stability, ease of use, classpath management, and supporting various configurations and developer needs.
Building an Eclipse plugin to recommend changes to developerskim.mens
1) The document summarizes a master's thesis defense about building an Eclipse plugin called Mendel to recommend code changes to developers based on regularities extracted from existing code.
2) Mendel uses a "genetic metaphor" to find family members of a selected code entity according to different family definitions, extract dominant traits from the family, and recommend traits for the entity that are not already implemented.
3) The thesis validates Mendel's recommendations by analyzing multiple versions of projects and checking if recommended changes were later implemented by developers. The results showed some family definitions were better suited than others for different recommendation types.
The document is a presentation by Amir Barylko on continuous integration using TeamCity. It introduces CI and its benefits, how to get started with CI using TeamCity, and provides an overview of key TeamCity concepts like source control, build agents, and notifications. The presentation concludes with a discussion on next steps and a question period.
Designing for User Experience (UX) with Atlassian ToolsAtlassian
The document discusses integrating design and development. It outlines 5 steps to solve challenges: 1) braindump to brief, 2) brief to wireframes, 3) wireframes to design, 4) design to implementation, and 5) implementation to validation. Key points include using tools like JIRA and Confluence for collaboration, bringing designs to life with prototypes, and validating designs through internal and external testing.
Continuous integration and delivery for java based web applicationsSunil Dalal
This document discusses continuous integration and delivery for Java web applications using Jenkins, Gradle, and Artifactory. It defines continuous integration and delivery and explains why they are important. It outlines the workflow and steps involved, including using source control, building and testing with Jenkins and Gradle, storing artifacts in Artifactory, running code analysis with tools like SonarQube, and deploying to test and production. Finally, it addresses some common questions around plugins, versioning, rollbacks, and build frequency.
AliExpress’ Way to Microservices - microXchg 2017juvenxu
AliExpress has transitioned to a microservices architecture from a monolithic architecture. This involved several key changes:
1. Organizing code into individual services rather than global jars to improve independence and reusability.
2. Adopting Docker to standardize environments and dependencies.
3. Integrating Alibaba cloud services like configuration (Diamond) and messaging (MetaQ) into applications using Spring starters to simplify usage.
4. Establishing practices like publishing clean API-focused jars, using Maven to manage dependencies, and applying naming standards to improve maintainability at scale.
How to explain what JRebel does to a developerBogomil Shopov
JRebel is a tool that allows developers to see changes to Java code without needing to rebuild and redeploy applications. It works by mapping the project code to the running application, and instantly reflecting any changes made in the IDE. This eliminates lengthy redeploys and restarts, saving significant time otherwise spent waiting. The document then provides technical details on how JRebel integrates with the JVM, application servers, frameworks and IDEs to enable these live updates.
The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.
Bringing Swift into your Objective-C ProjectsRené Cacheaux
Explore tips and tricks for introducing Swift source into Objective-C projects. We’ll cover where in the networking-model-UI stack to begin writing Swift, how to maximize the benefits of using Swift without re-writing your apps, and how to avoid some of the common pitfalls getting Swift and Objective-C working harmoniously together.
The document discusses the importance of developer experience (DX) and how to improve it. DX refers to the interactions and events between developers and tools/APIs, both positive and negative. Good DX matters because it leads to innovative usage and evangelism, while poor DX results in minimal usage and high turnover. The document provides tips for DX providers to consider users at each stage, from signing up and getting started to ongoing use and support. It emphasizes the importance of documentation, API design, and issue tracking/support to ensure developers enjoy and want to continue using a tool.
Introduction to the Managed Extensibility Framework in SilverlightJeremy Likness
This document provides an introduction to the Managed Extensibility Framework (MEF) using Silverlight. It discusses why MEF is useful for discovery, lifetime management, and extensibility. It also highlights 10 practical reasons to use MEF, such as providing inversion of control and allowing for multiple implementations of contracts. The document includes code demos to illustrate concepts like importing many implementations, using MEF with MVVM, dynamic XAP file loading, and filtering with metadata.
Enabling Design Reviews with JIRA and Confluence - Atlassian Summit 2012Atlassian
The presentation discusses how Moving Interactive uses Atlassian tools like JIRA and Confluence for design reviews, dashboards, meeting notes, and user acceptance testing. Specifically, it covers how they use Bonfire for collaborative design reviews, customize dashboards for different roles, implement issue and field security, integrate workflows with proprietary tools, and structure Bonfire testing into grouped sessions.
The document provides an overview of Confluence, including current usage statistics and upcoming features. It notes that Confluence currently has 142 new teams per week and 37,000 customers. The next release, Confluence 4.0, will focus on simplifying the user experience and improving reliability. It will include new features like @mentions, autoformatting, and improved tables. The release is available for testing today through an early access program.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
This document discusses using the ios-driver tool with Selenium to automate testing of iOS applications. It describes how ios-driver works by exposing the iOS element tree through the WebDriver API and allowing tests to be written using existing Selenium infrastructure and languages. It also covers testing hybrid, web, and localizing applications and discusses integrating the tools into a continuous integration pipeline using Jenkins. Future plans include adding support for running ios-driver nodes on non-Mac platforms and improvements to the inspector.
Google在2013開始導入Gradle工具作為新的Android build system,Gradle的使用正是實踐DevOps的良好利器,除了方便進行automated building外, Gradle更幫助我們消弭不同開發環境/工具間的差異問題,如同infarsture as code之於web application/service的重要性,build script as code就是幫助Android App快速發佈版本並維持品質穩定的關鍵最後一哩路。
此次主題將探討如何利用gradle進行精實良好的系統開發配置管理,建立一條下達開發者本地端上通產品發佈系統的透明化產品開發流水線。你是否常常一個App剛發佈不久,下一個idea已經生成,舊程式需要繼續維護同時又要添加新功能,你的開發方法是否能讓多方產品流水線順暢運行而且並行不悖?妥善利用Gradle並深入理解Build by convention的內涵是最好的選擇。
The document discusses creating a good developer experience when building APIs. It provides 10 steps for a great developer experience, including keeping documentation simple and up-to-date, providing quick and easy signups, code samples, interactive documentation, and being available to help developers. The overall message is that API builders should treat their developer experience as a product in its own right to inspire developers and solve their pain points.
The document describes WiredReach's process for implementing continuous deployment. It discusses how they moved from bi-weekly release cycles with large releases to releasing multiple times per day with releases containing under 25 lines of code. This was done by setting up automated testing and deployment pipelines. It also touches on some of the challenges they faced in taking this approach and strategies for incrementally building systems to support continuous deployment like adding production monitoring and building a "cluster immune system".
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
The document discusses React Native, a JavaScript framework for building mobile apps using React. It allows building iOS and Android apps using one codebase by rendering native UI components. Some key points covered include:
- React Native uses JavaScript to build mobile apps that render native components, bridging to native platforms.
- It offers native experience and performance while allowing 80% shared code between iOS and Android.
- Styling uses Flexbox layout model similar to CSS.
- JSX combines JavaScript and XML syntax to create views using single file components.
- The document provides an overview and demo of building a basic React Native app.
For enterprise projects, maintaining automation tests suite is always a challenge.
* Detailed walkthru of automation pyramid containing different types of specification driven tests layer.
* Framework built using RSpec, Spinach, Cucumber, webkit and Webdriver with examples
* Process of evolving and building specification tests
* Tips to maintain test suite and minimize test run durations
[Japan Selenium User Community in Remote] Test Automation JourneyWoohyeok Kim
This document summarizes a presentation given to the Japan Selenium User Community about optimizing end-to-end test execution time through parallel test execution. It discusses initially trying a Maven plugin to run tests in parallel threads, but this caused errors due to WebDriver not being thread-safe. The solution was to use the parallel test capabilities of TestNG, which supports WebDriver more reliably for multi-threaded test execution. With this approach, execution time was reduced significantly without issues. The presentation also provided an overview of the speaker's test automation journey and considerations for justifying test automation.
The document discusses professionalizing the front-end developer role. It covers:
1. The responsibilities of a front-end developer in bringing a designer's static design to life, separating concerns between front-end and back-end teams through an API.
2. Techniques, tools, languages, and frameworks a front-end developer uses like test-driven development, automation workflows, preprocessors, frameworks, and more.
3. Introductions to Angular and React, including their conceptual overviews, classic request flows, learning curves, and how to think in the "React way" through components, state, data flow, and more.
Atlassian builds tools for all teams... including ourselves! There's no right or wrong way to use our tools, but we've developed some best practices that a lot of our teams have adopted.
In this session you will learn how an Atlassian developer uses JIRA, Confluence, HipChat, BitBucket, and Bamboo to plan, build, test, and continuously deploy HipChat. You will also learn some tips and tricks for using the Atlassian toolset to take a project from a concept to a released application.
David Cruz, Senior Software Developer - HipChat Desktop, Atlassian
Creative Branching Models for Multiple Release StreamsAtlassian
Nuance Communications is making the move from SVN to Git! Why? To take advantage of its strong branching and merging capabilities... and to keep their developers happy. With wild variations between each product's release model, they have multiple releases of one or more components in play at a given time. So they had to get creative with a branching model. This talk will discuss choosing the right Git branching model for each of your release streams, and managing multiple releases using Bitbucket (including Stash), JIRA, Bamboo, and Maven.
AliExpress’ Way to Microservices - microXchg 2017juvenxu
AliExpress has transitioned to a microservices architecture from a monolithic architecture. This involved several key changes:
1. Organizing code into individual services rather than global jars to improve independence and reusability.
2. Adopting Docker to standardize environments and dependencies.
3. Integrating Alibaba cloud services like configuration (Diamond) and messaging (MetaQ) into applications using Spring starters to simplify usage.
4. Establishing practices like publishing clean API-focused jars, using Maven to manage dependencies, and applying naming standards to improve maintainability at scale.
How to explain what JRebel does to a developerBogomil Shopov
JRebel is a tool that allows developers to see changes to Java code without needing to rebuild and redeploy applications. It works by mapping the project code to the running application, and instantly reflecting any changes made in the IDE. This eliminates lengthy redeploys and restarts, saving significant time otherwise spent waiting. The document then provides technical details on how JRebel integrates with the JVM, application servers, frameworks and IDEs to enable these live updates.
The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.
Bringing Swift into your Objective-C ProjectsRené Cacheaux
Explore tips and tricks for introducing Swift source into Objective-C projects. We’ll cover where in the networking-model-UI stack to begin writing Swift, how to maximize the benefits of using Swift without re-writing your apps, and how to avoid some of the common pitfalls getting Swift and Objective-C working harmoniously together.
The document discusses the importance of developer experience (DX) and how to improve it. DX refers to the interactions and events between developers and tools/APIs, both positive and negative. Good DX matters because it leads to innovative usage and evangelism, while poor DX results in minimal usage and high turnover. The document provides tips for DX providers to consider users at each stage, from signing up and getting started to ongoing use and support. It emphasizes the importance of documentation, API design, and issue tracking/support to ensure developers enjoy and want to continue using a tool.
Introduction to the Managed Extensibility Framework in SilverlightJeremy Likness
This document provides an introduction to the Managed Extensibility Framework (MEF) using Silverlight. It discusses why MEF is useful for discovery, lifetime management, and extensibility. It also highlights 10 practical reasons to use MEF, such as providing inversion of control and allowing for multiple implementations of contracts. The document includes code demos to illustrate concepts like importing many implementations, using MEF with MVVM, dynamic XAP file loading, and filtering with metadata.
Enabling Design Reviews with JIRA and Confluence - Atlassian Summit 2012Atlassian
The presentation discusses how Moving Interactive uses Atlassian tools like JIRA and Confluence for design reviews, dashboards, meeting notes, and user acceptance testing. Specifically, it covers how they use Bonfire for collaborative design reviews, customize dashboards for different roles, implement issue and field security, integrate workflows with proprietary tools, and structure Bonfire testing into grouped sessions.
The document provides an overview of Confluence, including current usage statistics and upcoming features. It notes that Confluence currently has 142 new teams per week and 37,000 customers. The next release, Confluence 4.0, will focus on simplifying the user experience and improving reliability. It will include new features like @mentions, autoformatting, and improved tables. The release is available for testing today through an early access program.
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
This document discusses using the ios-driver tool with Selenium to automate testing of iOS applications. It describes how ios-driver works by exposing the iOS element tree through the WebDriver API and allowing tests to be written using existing Selenium infrastructure and languages. It also covers testing hybrid, web, and localizing applications and discusses integrating the tools into a continuous integration pipeline using Jenkins. Future plans include adding support for running ios-driver nodes on non-Mac platforms and improvements to the inspector.
Google在2013開始導入Gradle工具作為新的Android build system,Gradle的使用正是實踐DevOps的良好利器,除了方便進行automated building外, Gradle更幫助我們消弭不同開發環境/工具間的差異問題,如同infarsture as code之於web application/service的重要性,build script as code就是幫助Android App快速發佈版本並維持品質穩定的關鍵最後一哩路。
此次主題將探討如何利用gradle進行精實良好的系統開發配置管理,建立一條下達開發者本地端上通產品發佈系統的透明化產品開發流水線。你是否常常一個App剛發佈不久,下一個idea已經生成,舊程式需要繼續維護同時又要添加新功能,你的開發方法是否能讓多方產品流水線順暢運行而且並行不悖?妥善利用Gradle並深入理解Build by convention的內涵是最好的選擇。
The document discusses creating a good developer experience when building APIs. It provides 10 steps for a great developer experience, including keeping documentation simple and up-to-date, providing quick and easy signups, code samples, interactive documentation, and being available to help developers. The overall message is that API builders should treat their developer experience as a product in its own right to inspire developers and solve their pain points.
The document describes WiredReach's process for implementing continuous deployment. It discusses how they moved from bi-weekly release cycles with large releases to releasing multiple times per day with releases containing under 25 lines of code. This was done by setting up automated testing and deployment pipelines. It also touches on some of the challenges they faced in taking this approach and strategies for incrementally building systems to support continuous deployment like adding production monitoring and building a "cluster immune system".
Lean Engineering: How to make Engineering a full Lean UX partnerBill Scott
In 1999, PayPal's name was synonymous with innovation. In fact, the so called PayPal Mafia (original founders) went on to establish Tesla, SpaceX, YouTube, Skype and other startups. They also provided the early investments of many of the most innovative companies on the internet today. But over time that innovation slowed to a crawl.
In 2011 a number of things begin to come together for PayPal that started its journey back to innovation. This is the story of that reboot and how engineering has played a key role in partnering directly with product and design to move from a culture of products having a long shelf life, to one of rapid experimentation.
In this talk, Bill will outline the principles of Lean Engineering; principles for engineering that enable learning. Drawing from his experience leading User Interface Engineering at both Netflix & PayPal, Bill will walk you through the key principles your engineering team will need to adopt to be that enabler for product and design in your organization. This talk will not just inspire you, but it will also give you some hard earned advice on making this a reality in your organization.
The document discusses React Native, a JavaScript framework for building mobile apps using React. It allows building iOS and Android apps using one codebase by rendering native UI components. Some key points covered include:
- React Native uses JavaScript to build mobile apps that render native components, bridging to native platforms.
- It offers native experience and performance while allowing 80% shared code between iOS and Android.
- Styling uses Flexbox layout model similar to CSS.
- JSX combines JavaScript and XML syntax to create views using single file components.
- The document provides an overview and demo of building a basic React Native app.
For enterprise projects, maintaining automation tests suite is always a challenge.
* Detailed walkthru of automation pyramid containing different types of specification driven tests layer.
* Framework built using RSpec, Spinach, Cucumber, webkit and Webdriver with examples
* Process of evolving and building specification tests
* Tips to maintain test suite and minimize test run durations
[Japan Selenium User Community in Remote] Test Automation JourneyWoohyeok Kim
This document summarizes a presentation given to the Japan Selenium User Community about optimizing end-to-end test execution time through parallel test execution. It discusses initially trying a Maven plugin to run tests in parallel threads, but this caused errors due to WebDriver not being thread-safe. The solution was to use the parallel test capabilities of TestNG, which supports WebDriver more reliably for multi-threaded test execution. With this approach, execution time was reduced significantly without issues. The presentation also provided an overview of the speaker's test automation journey and considerations for justifying test automation.
The document discusses professionalizing the front-end developer role. It covers:
1. The responsibilities of a front-end developer in bringing a designer's static design to life, separating concerns between front-end and back-end teams through an API.
2. Techniques, tools, languages, and frameworks a front-end developer uses like test-driven development, automation workflows, preprocessors, frameworks, and more.
3. Introductions to Angular and React, including their conceptual overviews, classic request flows, learning curves, and how to think in the "React way" through components, state, data flow, and more.
Atlassian builds tools for all teams... including ourselves! There's no right or wrong way to use our tools, but we've developed some best practices that a lot of our teams have adopted.
In this session you will learn how an Atlassian developer uses JIRA, Confluence, HipChat, BitBucket, and Bamboo to plan, build, test, and continuously deploy HipChat. You will also learn some tips and tricks for using the Atlassian toolset to take a project from a concept to a released application.
David Cruz, Senior Software Developer - HipChat Desktop, Atlassian
Creative Branching Models for Multiple Release StreamsAtlassian
Nuance Communications is making the move from SVN to Git! Why? To take advantage of its strong branching and merging capabilities... and to keep their developers happy. With wild variations between each product's release model, they have multiple releases of one or more components in play at a given time. So they had to get creative with a branching model. This talk will discuss choosing the right Git branching model for each of your release streams, and managing multiple releases using Bitbucket (including Stash), JIRA, Bamboo, and Maven.
1. The document discusses running an API at scale and some of the challenges that arise. It notes that running a huge API product is different than running a web product.
2. Managing application developers and the relationships between their apps and users becomes more complex at scale. Techniques like OAuth and caching can help reduce load on APIs and internal systems.
3. As APIs and applications grow, aspects like chatty applications, application versioning, testing, and geo-distributed caching take on increased importance for managing scale and complexity. The key is to continually improve while avoiding getting stuck.
Codesion's Live Webinar: Cutting Edge Cloud Development Tools for Force.comCollabNet
Would you like to witness the industry's first end-to-end cloud development solution for Force.com? For the first time see version control, project planning, project management, and one-click deployment integrated into a single environment, designed specifically for teams building for the Force.com platform. Join Brian Matthews, the founder and CTO of BrainEngine, and Willie Wang, VP Product and Services of Codesion Cloud Services, as they introduce a new and innovative way to build and deploy cloud applications for Force.com.
The Web Development Eco-system with VSTS, ASP.NET 2.0 & Microsoft AjaxDarren Sim
This document provides an overview of the Visual Studio Team System (VSTS) for web development. It discusses common pains experienced by web development teams and how VSTS addresses them through integrated tools for source control, work item tracking, reporting, build automation, and project portals. Key features of VSTS demonstrated include change management, work item management, shared and exclusive checkouts, promotion modeling, and reports. Additional resources for learning more about VSTS are also provided.
In this webinar you will learn how to build Social Enterprise applications using Salesforce.com, Heroku, and Java. Through live coding and demonstrations you will learn how to instantly deploy and scale Java apps on the cloud with Heroku. You will also learn how to integrate those applications with Salesforce.com and Force.com through REST.
The webinar will cover:
:: An overview of Heroku
:: Best practices for integrating with Salesforce.com and Force.com apps via REST
:: How to build and deploy your Social Enterprise apps using Java on Heroku
:: Your questions about Heroku
More details: http://wiki.developerforce.com/page/Webinar:_Social_Enterprise_Java_Apps_on_Heroku_(2012-May)
AppNotch is a drag-and-drop app building platform that allows users to easily create, publish, and manage mobile apps without coding. It includes reusable modules and widgets, a live editor, app previewer, and one-click conversion to native Android and iOS apps. The platform is designed to be intuitive, collaborative, and supports real-time updates to published apps.
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA
The webinar discusses continuous integration and automation for mobile development and testing. It presents tools from Atlassian, Zephyr, and SOASTA that can help automate the mobile development and testing process. Continuous integration with Bamboo can help developers integrate code changes more frequently and fail builds faster to catch bugs earlier. Zephyr provides test management to centralize test assets and provide visibility. SOASTA offers tools for test automation, real user monitoring, and performance/load testing to help achieve test completion with quality. Together these tools can help speed up the mobile development process through continuous integration, test automation, and visibility into the testing process.
The document discusses innovations that Atlassian is launching to help unlock potential in products and help customers ship code faster. Specifically, it mentions that Atlassian is launching new plugins, a universal plugin manager, and per-user plugins that allow custom JS/CSS/Zip files. It also discusses features for distributed version control, commit graphs, builds, integration and more to help customers ship code faster through agile, lean startup and DevOps approaches.
Sign up for our beta today! http://datadipity.com/register
Datadipity reduces time to launch by promoting the “Virtualized API stack” with a set of APIs in place, there is no need to architect complex distributed systems. 3rd party APIs are leveraged so that the architecture can be reduced to one code base. This reduces development time. Usability is much easier to maintain during beta release and user acceptance changes are easier to apply.
The document discusses innovations around unlocking potential in products, shipping code faster, and launching new features. It highlights a growing plugin ecosystem with 50% more plugins, a universal plugin manager, and 120 new commercial plugins. It also covers improvements to installation, upgrades, and support including self-service tools, faster response times, and weekend support for critical issues.
AtlasCamp 2011 - Five Strategies to Accelerate Plugin Developmentmrdon
The document outlines five strategies for accelerating plugin development: 1) Use Speakeasy to validate plugin ideas before building, 2) Define interactions with page objects for testing, 3) Optimize the development loop with the SDK, 4) Reuse functionality with the Atlassian UI (AUI) framework, and 5) Encourage user feedback through tools like JIRA Mobile Connect. It also discusses the potential for "remote plugins" that could run on a server instead of requiring installation in each product.
Postman Public Workspaces: The First Massively Multiplayer API Experience | W...Postman
In this webinar Postman’s Kin Lane Nick Tran and Joyce Lin walk you through the basics of the new public workspaces functionality, and discuss the “massively multiplayer” aspect.
This document provides instructions for integrating a Java application on Heroku with Salesforce.com. The steps include:
1. Setting up OAuth in Salesforce and adding callback URLs for dev and prod
2. Updating Maven dependencies to use Force REST API and OAuth libraries
3. Switching entities to use JSON properties for fields
4. Changing the data access object (DAO) to use the Force REST API
5. Configuring Spring security and OAuth
6. Adding a servlet filter for OAuth authentication
7. Adding OAuth client key and secret as environment variables
6 Reasons Why APIs Are Reshaping Your BusinessFabernovel
A study on APIs to demonstrate the advantages of APIs for businesses in terms of scalability, flexibility, business development, product development, supply chain management...
Atlassian jira как полностью раскрыть возможностиAndrew Fadeev
Atlassian jira как полностью раскрыть возможности. Jira в базовой поставке не реализует огромное количество заложенных в нее возможностей. Возникает вопрос, прав ли был Гартнер так высоко ставя её в своих "магических квадратах". Гартнер как всегда прав, но для раскрытия потенциала Jira необходимо значительное кол-во внешних плагинов. Удобно это или нет - решать Вам.
Automated testing DrupalCamp in AshevillePromet Source
Promet Solutions specializes in developing complex web applications using open source technologies. They have over 30 solutions architects and have been in business for 10 years, contributing to over 32 open source projects. They have offices in Chicago and San Jose and have developed over 10 mobile apps in the past 12 months. They are presenting on their experience with automated testing for Drupal applications using tools like Selenium and PHPUnit.
Firefox OS allows web applications to access device capabilities through standardized web APIs. This bridges the gap between native and web applications. Mozilla is proposing and approving APIs that give web apps access to features like vibration, geolocation, and more. Web apps can also work offline through caching. Developers can create hosted or packaged apps and debug them on the Firefox OS emulator or devices.
The document provides a sneak peek at new features in SharePoint 2013. It summarizes features for sharing ideas through social networking capabilities, organizing projects and tasks, and discovering information. The document also outlines changes for developers, IT professionals, and new capabilities for designing and building sites, managing workflows, and browser support.
This session provides a “Sneak Peek” of SharePoint 2013 IT Pro / Developer perspective. The session is designed to help the audience to understand the changes architectural changes have occurred, storage considerations, browser support, social media supports, workflows and ect… This is a must attend session for leading edge SharePoint IT Pro/Developer looking to jump start their 2013 experience curve.
Similar to AtlasCamp US 2012 Keynote, Jean-Michel Lemieux (20)
We aim to celebrate women every day, but we’re taking today to give special recognition to womxn at Atlassian continue who inspire and lead.
For #InternationalWomensDay, we asked Atlassians to nominate and recognize amazing womxn at Atlassian who inspire them, challenge them, and truly represent Atlassian values.
Ever wondered what Atlassian engineers do in their 20% time? Join Forge engineering lead Tim Pettersen on a lightning tour of how Forge is being used inside Atlassian. Attendees will get a rare view into some of the apps, tools, and tweaks we’ve built internally on top of Forge in the spirit of dogfooding and innovation. Come along and be inspired with some great ideas for improving and automating your own teams' workflows!
Let's Build an Editor Macro with Forge UIAtlassian
Race out of the gate with Forge UI: a new way of building UI extensions for Atlassian products. In this session, Forge UI Developer Experience lead Peter Gleeson will demonstrate how build an Editor macro from scratch! Attendees will learn about Forge foundational concepts such as the FaaS dev loop, Forge CLI, and how to construct UIs from Forge UI components.
This session provides a great introduction to the Forge platform for any developer looking to get productive with editor apps and Forge UI.
In the words of Jeff Atwood: “JavaScript is the lingua franca of the web”. It’s also the first language we’ve chosen to support in Forge. In this session, Forge engineer Shorya Raj will walk through the Node.js isolate based runtime you’ll be using to write apps for Forge.
Attendees will learn about the unique features of the Forge JavaScript Runtime, such as automatic authentication and tenant context management. Shorya will also cover the differences between the Runtime, conventional browser, and Node.js APIs.
Developers or attendees with some programming experience will get the most out of this session.
Forge UI: A New Way to Customize the Atlassian User ExperienceAtlassian
UI extensibility is an integral part of Atlassian's ecosystem story. In cloud, traditionally this has been accomplished with the humble iframe. In this session you will learn about Forge UI, an additional and innovative way to build visual apps for Atlassian products.
Join Product Manager Simon Kubica and Senior Developer Michael Oates from the Forge team in exploring the underlying concepts and technology powering Forge UI, and learn how it will unlock exciting new opportunities in our ecosystem.
This document discusses using triggers to automate actions in Forge apps. It begins with an overview of triggers and then discusses:
- Product triggers that are triggered by events in Atlassian products like Jira, Confluence etc.
- Web triggers that are triggered by HTTP requests to a Forge function.
- How to authenticate and make requests to external services like Opsgenie from Forge functions in response to triggers.
- Demos of building a Forge app that responds to Jira issue creation by assigning the issue and notifying Opsgenie.
The document provides details on the event payload formats, making authenticated requests, and deploying/managing the Forge app lif
Observability and Troubleshooting in ForgeAtlassian
The document discusses the evolution of software development from bare metal servers to virtualization, containers, and serverless functions. It notes how debugging and observability have become more difficult as software moves to remote "somebody else's computer" environments. The author introduces Forge as Atlassian's solution for providing developers a declarative language and best-in-class experience for building user interfaces on serverless infrastructure, including features for debugging, monitoring, and security.
Trusted by Default: The Forge Security & Privacy ModelAtlassian
Security and trust have become increasingly important requirements for our customers in Cloud. We’re working to make it easier for you to build and maintain secure apps for Atlassian products.
In this session, Engineering Team Lead Dugald Morrow and Principal Product Manager Joël Kalmanowicz will explain how security and trust have been baked into the Forge framework and the benefits the platform can offer you and your users. Learn how much less work it can be to build trusted apps customers will love on Forge by going deep on the safeguards we’re putting in place.
Developers or attendees with some software security experience will get the most out of this session.
Designing Forge UI: A Story of Designing an App UI SystemAtlassian
Creating apps with Forge and its UI frontend components is now easier than ever. Join Senior Designer Allard van Helbergen and Product Manager Josephine Lee as they walk through the story of designing Forge UI.
What is a declarative UI and why did we choose this paradigm? What are all the considerations that go into defining the set of components to build apps with? And how do you make ‘creating apps’ simple? Walk away understanding the foundations of Forge, how all the different components work together, and where Forge UI is headed in the future.
After a day of learning about the exciting features of Forge, get ready for a peek under the hood to discover how it’s all implemented. Join Forge Architect Patrick Streule as he goes deep on topics such as Forge FaaS infrastructure, the internal workings of tenant isolation, and automatic authentication.
Attendees will also get a glimpse of some features we’re looking at building into the future of Forge, such as a serverless data store for apps and more!
Access to User Activities - Activity Platform APIsAtlassian
How do you stay on top of your work when it is scattered across multiple Atlassian products?
"If only there was a single place where I could see all my activity..." - sounds familiar?
We are going to provide you an insight into what lead to the creation of a new Activity API. Following last year’s Atlas Camp announcement from our CTO Sri Viswanath, Atlassian is moving onto GraphQL - new Activity API is one the first pieces of the GraphQL Atlassian Platform and is the technology behind start.atlassian.com.
Join Sergey Meshkov, Senior Developer, who will provide you a sneak peek of the new GraphQL Activity API as it will soon be available to our vendors.
Design Your Next App with the Atlassian Vendor Sketch PluginAtlassian
Our designers work 3x quicker with the Atlassian Vendor Sketch Plugin — and now we’re unleashing these superpowers to the Atlassian Ecosystem. If you mockup screens for code or marketing, we’ll help you drag and drop your way to an Atlaskit design in less than 10 minutes. And if you’re a designer, you’ll want to hear about our pixel-perfect component library and suite of seamless Sketch integrations.
Join Atlassian’s resident Sketch aficionado, Huw Evans, to learn about:
Sketch Components: If it’s in Atlaskit, it’s now in Sketch. And introducing the Symbol Palette, the quickest way to find the right component for the job.
Product Templates: Spark inspiration by building your designs inside realistic screens from Jira & Confluence — or craft hero images for your Marketplace listing!
Color and Text Styles: Heard of N75? H400? If those mean nothing to you, we’ll run through how to make your users feel at home by using Atlassian colors & typography, right inside Sketch.
Data Suppliers: Say goodbye to Lorem Ipsum. Learn how to use Sketch Data Suppliers to generate realistic copy using live data from Jira, Confluence and Bitbucket. Bonus: How we used AI to create people who don’t exist!
♀️ It's All Open Source: How we made it really easy to customise the Atlassian Vendor Sketch Plugin for your team's needs.
Tear Up Your Roadmap and Get Out of the BuildingAtlassian
The document discusses conducting customer research by tearing up existing roadmaps and getting out of the building. It recommends running a research spike with the team to define what needs to be learned. Tips are provided for recruiting participants through support, community, and sales teams. Conducting customer interviews is discussed, including roles for scribes and interviewers. Analyzing interviews by consolidating themes from transcripts is also covered. An example analysis identified themes around customer journeys, collaboration as a team sport, and overwhelming demand for participation. The document encourages being honest about whether a research spike could be run and why or why not.
Nailing Measurement: a Framework for Measuring Metrics that MatterAtlassian
When it comes to designing apps and new features, we just can't get enough of metrics. In an age where we can collect data from almost anything, how can we cut through the noise and focus on the right metrics to measure the success and failures of the apps that we’re building?
Join Atlassian Product Manager Josephine Lee as she delves through what exactly makes a good metric. Throughout the talk, we’ll walk through real Atlassian examples of good and bad metrics. By exploring a framework for measurement, we’ll cover detailed features that showcase how best to measure and choose the right set of success, supportive, and counter metrics.
You'll walk away with tips and learnings from Atlassian’s approach to measuring success, and learn how to use data and metrics to inspire action in your apps.
Building Apps With Color Blind Users in MindAtlassian
Color-blind people are using your apps. 1 in 12 men is color blind. And for women, this is 1 in 200.
Building apps that work well for color blind people is not difficult. Some simple techniques help us with the design of our interface. And some tools help us see what color blind people see.
In this talk, Maarten Arts of Avisi will look at common varieties of color blindness. We will look at apps through the eyes of a color-blind person. And we will discover what color-blind people struggle with.
Regardless of whether you're a designer or developer, this talk will equip you with the skills and the tools you need to make sure that your app works for color-blind people.
Creating Inclusive Experiences: Balancing Personality and Accessibility in UX...Atlassian
The words we choose have the power to include or alienate our users. The reality is that for many, English is spoken as a second language. And unless you're going to localize your product for those major non-English speaking markets, you'll need to thoughtfully create content that is accessible to a larger audience.
But how do we create products that maintain a sense of personality without isolating a wide audience of non-native speakers?
Join Atlassian Content Designer, Roana Bilia, as she walks you through why thoughtful, inclusive content, is key to creating well-designed user experiences. You'll walk away with foundational principles for good UX copy when optimizing your product UI, a few quick wins that you as creators and developers can incorporate into your next products, as well as a set of mistakes to avoid that companies—including Atlassian—have made, which prioritized native speakers but isolated non-native speakers.
Beyond Diversity: A Guide to Building Balanced TeamsAtlassian
We hear it all the time, and we get it. Diversity and inclusion are important! But isn't it an HR problem? HR may be able to help with diversity but inclusion or creating an inclusive environment is everyone's responsibility. So how do we create an inclusive environment that celebrates diversity and engages and supports everyone? Isabel Nyo will be sharing best practices and lessons she has learned along the way. She will also be sharing her experience as a minority, a female technical leader, in the technology industry.
The Road(map) to Las Vegas - The Story of an Emerging Self-Managed TeamAtlassian
In September 2018, K15t took its mission to go self-managed to the next-level when the entire company worked together to decide on the Next Big Thing™ to build for Atlassian users and present it at Summit in Las Vegas.
In this session, Anshuman Dash, an intern turned software engineer, turned product manager, shares his journey of professional self-discovery. In under five months, he joins a freshly assembled, self-managed team in building a new Atlassian Marketplace app.
Dash will give a quick intro to what it means for a team to be self-managed. Then, he'll share his observations and experiences on the team, as well as the best-practices, patterns, and processes K15t has discovered along the way.
Whether you are a new team with a kick-ass product idea or a big company figuring out ways to scale, this talk will provide you with practical tips and ideas your team can try out!
Designing for the enterprise comes with a unique set of challenges; ensuring readability and accessibility at scale, meeting the needs of multi-layered organizations, and building a trust when your software - used by dozens of thousands of employees - is considered mission-critical.
At Atlassian, we've spent countless hours digging deep into our enterprise customer's needs and we've gathered a vast repository of insights.
In this talk, Pawel Wodkowski, a senior designer on Jira Server, will share all that we've learned from our research (while not being shy about busting some of those wild admin myths!). You'll get a crash course in what it means to design for scale the Atlassian way.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
63. Confluence “Apps”
Three Goals:
• Show users what content they can create
• Guide them in creating it (how)
• Help them structure it
The “blank page” problem
32
64. Confluence “Apps”
Three Goals:
• Show users what content they can create
• Guide them in creating it (how)
• Help them structure it
Why should you care?
The “blank page” problem
• Still in “concept” phase - help shape the solution!
• Create add-ons which are first-class citizens of
the content creation experience.
32
65. Confluence “Apps”
Three Goals:
• Show users what content they can create
• Guide them in creating it (how)
• Help them structure it
Why should you care? Interested?
The “blank page” problem sherif@atlassian.com
• Still in “concept” phase - help shape the solution!
• Create add-ons which are first-class citizens of
the content creation experience.
32
68. Two Streams
5.0 5.1 5.2 6.0
Platform API, Integrations Perf, Scale Webhooks REST APIs
Issue Links,
Streams
User Love Quick Edit Inline Edit and New Search and Search, Nav, and
Issue Collector Issue Nav Design Refresh
69. Two Streams
5.0 5.1 5.2 6.0
Platform API, Integrations Perf, Scale Webhooks REST APIs
Issue Links,
Streams
User Love Quick Edit Inline Edit and New Search and Search, Nav,
Issue Collector Issue Nav and Design
Refresh
77. Support Testing
App App
Build Project
App Management
Webhooks
78. Support Testing
App App
When a bug is fixed in
JIRA, I want to
automatically update a
support ticket
Build Project
App Management
Webhooks
79. Support Testing
App When a bug is closed in App
When a bug is fixed in
JIRA, I want my test
JIRA, I want to
cases to reflect that fact
automatically update a
support ticket
Build Project
App Management
Webhooks
80. Support Testing
App When a bug is closed in App
When a bug is fixed in
JIRA, I want my test
JIRA, I want to
cases to reflect that fact
automatically update a
support ticket
I would like to trigger a
build when an issue
Build finishes implementation
Project
App Management
Webhooks
81. Support Testing
App When a bug is closed in App
When a bug is fixed in
JIRA, I want my test
JIRA, I want to
cases to reflect that fact
automatically update a
support ticket
I want to generate
I would like to trigger a reports once a
build when an issue milestone is
Build finishes implementation complete Project
App Management
Webhooks
82. JIRA Webhooks
Why • No plugin development required
• Push instead of poll
• Notification includes delta
83. JIRA Webhooks
Why • No plugin development required
• Push instead of poll
• Notification includes delta
What HTTP POST to the URL you designate with
information on the event that occurred
84. JIRA Webhooks
Why • No plugin development required
• Push instead of poll
• Notification includes delta
What HTTP POST to the URL you designate with
information on the event that occurred
85. What defines a webhook?
Name: "The simplest webhook"
Simple URL: http://www.myremoteapplication.com/webhookreceiver
“Give me every issue event in JIRA”
86. What defines a webhook?
Name: "The simplest webhook"
Simple URL: http://www.myremoteapplication.com/webhookreceiver
“Give me every issue event in JIRA”
Name: "A more advanced webhook"
Very URL: http://www.myremoteapplication.com/webhookreceiver
Powerful! JQL: Project = JRA AND fixVersion IN ("5.1", "5.2")
Events: issue_updated, issue_created
“Limit the events and the issues I receive”
91. HipChat Stash
Push
Workflow,
important
permissions, richest
events to chat
and complete API
rooms
92. HipChat Stash
Push
Workflow,
important
permissions, richest
events to chat
and complete API
rooms
Bamboo
Tasks,
tasks,
tasks, and
tasks
93. HipChat Stash
Push
Workflow,
important
permissions, richest
events to chat
and complete API
rooms
Bamboo Bitbucket
Tasks, Fetch code,
tasks, analyse, reports,
tasks, and and issue
tasks integrations
130. Highlights
In-process
Remote calls
Single Binary
131. Highlights
In-process
Remote calls
Single Binary
132. Highlights
In-process
Remote calls
Single Binary
...
133. When?
Today March June
Announcement! Beta 1.
0
134. Who? Where?
Tech Lead
Don Brown Google Group
don@atlassian.com
atlassian-remoteapps-dev
Issues and Doc
http://remoteapps.jira.com
Product Manager
Yon Golan
yon@atlassian.com
Welcome, I’ve got the best job at Atlassian. Preparing these slides really got me excited about all the innovation that is going on by our teams and also in our ecosystem. Sometimes you get lost in the details of each release.\n\nYou may of noticed that Scott isn’t here. He sends his regrets but he had to cancel his trip at the last minute because of ilness. He waited until the very last minute, and was terribly hard to made the decision.\n
Camp is special for us. This is not a user conference but a gathering of people who’s main mission is to deliver value to our customers. To make them awesome.\n\nTo do this, we share a lot more than we would normally with our end users. We do this because YOU have to know what’s going on behind the scenes.\n\nWe will be providing sneak peeks today, probably more than we have in the past, and would prefer if you hold off on the “tweets” and instead take notes and ask us questions during the week. \n\nAlso, roadmaps and plans may change, so the dates we are providing are our best guess at the moment and may change.\n\n\n
We flew our top shot developers from Sydney and bused another handful from SF to come and spend time with you at Camp. \n\nIn total we’ve got 38 Atlassian’s here, which means that you can gang up on us with with a 4:1 ratio. Please abuse of our knowledge, pry everything out that you can out of us, we are looking forward to being busy these two days.\n
This is our 5th Camp or 6th if we count the European event in March. We started with only 20 people at the first AtlasCamp while this year, with the mid-year event we’ve had more than 350 people attend our developer events between Sept 2011 and Sept 2012!\n\nYou are our closest friends and we invest a lot in making YOU successful which in turns makes our customers successfull by helping teams everywhere build stuff.\n\nWe also recognise that some of you have travelled from Europe and around the world for Summit which was only 3 months ago.\n
Now what about you? \n\nEveryone stand-up and let’s start the day with a bit of fun. If this is your first AtlasCamp please sit down, if this is your second sit down, etc... at the end we will have the hardcore, die-hard supporters. A huge thanks for supporting us through the years, giving all the great feedback, and building addons that help make our combined customers more productive on their teams. \n\nAnd for those that haven’t been around, you now know who to ask questions and connect with.\n
It’s challenging to give an overview when so much is happening. With almost 250 strong in our product development team now, it’s not a lack of things to highlight.\n\nWe have a lot to cover, so let’s get rolling.\n
Before we jump into the products, let’s review some of the highlights from our ecosystem.\n
So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
This year we’ve also created a dedicated team who’s mission is to help answer your development questions. \n\nWe currently get 350 questions a month on AAC related to development, 6 a day, and as you know many of them require looking at code samples and investigating and logging issues for the SDK or products. The team currently has a 80% answer rate with 40% of the questions being answered within an hour!\n\nWe are also planning the rollout of new changes to ACC to help guide and group development versus product questions. Thanks for all those have helped answer development questions on ACC!\n\nTransition & Recap: as we release more and more often so are you. we also realise that development support is critical to help us both keep up the pace and ensure that we build things together effectively.\n
This year we’ve also created a dedicated team who’s mission is to help answer your development questions. \n\nWe currently get 350 questions a month on AAC related to development, 6 a day, and as you know many of them require looking at code samples and investigating and logging issues for the SDK or products. The team currently has a 80% answer rate with 40% of the questions being answered within an hour!\n\nWe are also planning the rollout of new changes to ACC to help guide and group development versus product questions. Thanks for all those have helped answer development questions on ACC!\n\nTransition & Recap: as we release more and more often so are you. we also realise that development support is critical to help us both keep up the pace and ensure that we build things together effectively.\n
With 33 major releases this year there is definitely a lot to talk about about the products. But I’ve picked the highlights and areas that as a developer will impact how and what you build.\n
Before we jump into talking about the individual products, let’s talk about “user experience”. It’s something that we’ve been investing in a lot and are really excited about.\n\nWe’ve trippled our design team over the last year and taken a deep look at the user experience across all our products. \n\nYou haven’t seen the results just yet, but you’ll see them rolling out over the next 6 months. Given that YOU are a critical piece of the overall user experience of our products, we want to share our thinking and plans with you today.\n
We recently held an interview with a customer after which he sent us the following e-mail: \n\n“I hope your UI designer didn’t mind too much when I likened Confluence to “the config screen of my Linksys router”...?” \n\nWe have received frequent feedback like this from our customers, that our products look dated and the products are not consistent (visual and ux) between each other and even between addons.\n\nUser experience and design is not just about “pixel” pushing so we spent a lot of time reflecting about the kind of user experience we wanted to provide in our products but also the “feeling” and “character” we wanted our products to have. \n
You can recognize a BMW sports car regardless of the model or year? This is effective design at work. The design language establishes the visual vocabulary, relationships and hierarchies that allow diverse products to become recognizable and unified. \n\nThe outcome of our reflection is a set of design guidelines that include colors, fonts, common interaction patterns (how/when to user different controls and navigations for example), controls, and styling.\n\nThis still leaves the product and addon with a lot of creativity, but will help guide us and our ecosystem (eg, YOU) to take user experience into everything we build. And build out the Atlassian character commonly into our products.\n
We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It&#x2019;s single line, has all the extension points, has a &#x201C;call to action&#x201D;, and we&#x2019;ve extracted the important configuration and help menus.\n\nIt&#x2019;s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It&#x2019;s single line, has all the extension points, has a &#x201C;call to action&#x201D;, and we&#x2019;ve extracted the important configuration and help menus.\n\nIt&#x2019;s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It&#x2019;s single line, has all the extension points, has a &#x201C;call to action&#x201D;, and we&#x2019;ve extracted the important configuration and help menus.\n\nIt&#x2019;s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
But there is more... the look at feel and function will be consistent between the products. Did you notice Bitbucket in there <g> cool eh? I&#x2019;ll get back to how we did that later. \n\nThere are &#x201C;call to action&#x201D; buttons for creating key artifacts in each product when it makes sense, common interaction patterns (eg, how buttons and dropdowns work).\n
Oh, and there is one more thing.\n\nOur users navigate between products, either they&#x2019;ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe&#x2019;ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
Oh, and there is one more thing.\n\nOur users navigate between products, either they&#x2019;ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe&#x2019;ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
Oh, and there is one more thing.\n\nOur users navigate between products, either they&#x2019;ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe&#x2019;ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
Oh, and there is one more thing.\n\nOur users navigate between products, either they&#x2019;ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe&#x2019;ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
The header is just the start for a refresh and applying the design guide. Today we are launching the Atlassian Design Guidelines.\n\nhttps://developer.atlassian.com/design/\n\nWe&#x2019;d like to share a beta version of the Atlassian Design Guidelines with you today which cover controls, patterns and guidance on how to use them. It&#x2019;s live, it shows example, tips, and is built using the same code that you&#x2019;d put in our addon or product.\n\n\n
Here is an example of the vertical navigation, has usage instructions, and examples.\n
This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
... and JIRA 6.0.\n
... and JIRA 6.0.\n
... and JIRA 6.0.\n
To accompagny the design guideline is a toolkit to make your life easier. You don&#x2019;t have to use AUI, but it does make things easier. \n\nWe are really excited about the &#x201C;flat pack&#x201D; as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
To accompagny the design guideline is a toolkit to make your life easier. You don&#x2019;t have to use AUI, but it does make things easier. \n\nWe are really excited about the &#x201C;flat pack&#x201D; as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
To accompagny the design guideline is a toolkit to make your life easier. You don&#x2019;t have to use AUI, but it does make things easier. \n\nWe are really excited about the &#x201C;flat pack&#x201D; as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
The first products to ship will be in October with the new header in OnDemand and Bitbucket will implement the design guidelines using the AUI flat-pack.\n\nThere will be milestones along the way and with JIRA 6.0 and Confluence 5.0 in February the design refresh will be launched.\n\nWe want you to launch with us. Plugins can update immediately, learn the guidelines, use AUI, and follow our progress with the betas.\n
We just released Confluence 4.3 earlier this month and you probably saw us demo some of the features back at Summit. There are a TON of cool features in this release, and customers have been really excited about it. (stress: a lot of features, but as a developer this is what you can play with!)\n\nAnd what&#x2019;s cool for you guys, is that 4.3 has a lot of features to hack.\n
\n
* Shihab will talk more about the APIs for Workbox Tasks and notifications\n* I just wanted to share with you a pretty cool CLI tools that one of our developers, Sam Tardif, did on top of the new Confluence tasks API\n* he wanted a quicker way to bulk manage tasks so he built this little tool...notice the \n* Sherif can also show you some cool ways that team calendars is pluging into notifications to help make your plugin more discoverable to end users.\n\nAdd shorter link\nhttps://extranet.atlassian.com/display/~stardif/2012/09/11/WorkBox+Command+Line+Tool\n
* Here&#x2019;s another example of extending workbox notifications to make your plugin more \n* The Confluence team has been thinking of ways to make end users more aware of plugins that their admin installs for them.\n* So Team Calendars is using the workbox notifications API to notify users that their admin installed Team Calendars for them and that it&#x2019;s ready to use.\n* Again, Shihab will talk more about these API&#x2019;s in his talk.\n\n== Think about the experience of when to actually notify as the addon has to be configured. Think about feature discovery (a theme for the marketplace)\n
* We wanted to really control the mobile experience for Confluence, so we built a mobile web experience from the ground up to (i) make pages load fast, (ii) make it easy to navigate and (iii) to make content shine on a tiny screen.\n\n==> mobile rendering mode\n\n* We know that a lot of macros aren&#x2019;t designed to work on a mobile device so we tightly restricted what macros would render in mobile in Confluence 4.3. We&#x2019;re now working on mobile rendering mode for your macros so, say you output flash or something like that, you can provide a mobile render mode for your macro. That should be available in one the coming 4.3 bugfix releases.\n\n* We also know that some plugins want to hook into the left-hand navigation just like we do with notifications and tasks. Support for that is a little more experimental but come talk to me, Sherif, Shihab or Peggy if you want to learn more. Will be in 4.3.X.\n
Looking ahead, we&#x2019;ve begun work on Confluence 5.0 which will give you guys a bunch of new features and APIs to work with. It&#x2019;s implementing the design guidelines, new header, and a lot of user experience improvements. \n\nIn addition, we are also looking closely at how content is created and looking at how to make that easier...\n
Looking ahead, we&#x2019;ve begun work on Confluence 5.0 which will give you guys a bunch of new features and APIs to work with. It&#x2019;s implementing the design guidelines, new header, and a lot of user experience improvements. \n\nIn addition, we are also looking closely at how content is created and looking at how to make that easier...\n
We are calling this Apps.\n\nSo let me just dive a little bit into this &#x201C;Apps&#x201D; concept, we have planned for Confluence 5. \n\n&#x201C;Apps&#x201D; is the codename for the project - and it&#x2019;s our solution to what we&#x2019;ve been calling internally the &#x201C;Blank page problem&#x201D;. This is a common problem we often sighted as a hindrance to adoption. \n* It&#x2019;s users asking what do I use Confluence for?\n* And a subsequent question is often how? \n\nThe problem is prevalent not only for evaluators but also the &#x201C;100th&#x201D; user that might join your organisation. And today, it takes someone like a &#x201C;wiki champion&#x201D; - which I&#x2019;m sure many of you are, to show users the &#x201C;How&#x201D; and the &#x201C;What&#x201D;. \n\nSo Confluence &#x201C;Apps&#x201D; is really all about productising the use cases with the goals of showing people what they can create, how they can create it and helping them structure it. These use cases many if you are already familiar with: Using Confluence for meetings, documents, specifications, projects etc... \n\n---- CLICK\n\nSo why should you care? We&#x2019;ll if you&#x2019;re a commercial plugin developer, we&#x2019;d LOVE to hear from you. The project is still in concept phase, so you can help us shape the solution. In addition, apps presents a new opportunity for you to create add-ons that make content creation experience for your macro or even new types of content first-class in Confluence. \n\n---- CLICK\n\nWe don&#x2019;t have a talk for this as it&#x2019;s still really early stages, but Sherif Mansour is here with us - the Product Manager for &#x201C;Apps&#x201D;, and he is looking to hear from you and maybe have some one-on-ones with many of you here, so if you are interested, grab him and have chat to him or email him. \n \nSherif - do you want to stand-up so people see what you look like, this really isn&#x2019;t your photo! \n
We are calling this Apps.\n\nSo let me just dive a little bit into this &#x201C;Apps&#x201D; concept, we have planned for Confluence 5. \n\n&#x201C;Apps&#x201D; is the codename for the project - and it&#x2019;s our solution to what we&#x2019;ve been calling internally the &#x201C;Blank page problem&#x201D;. This is a common problem we often sighted as a hindrance to adoption. \n* It&#x2019;s users asking what do I use Confluence for?\n* And a subsequent question is often how? \n\nThe problem is prevalent not only for evaluators but also the &#x201C;100th&#x201D; user that might join your organisation. And today, it takes someone like a &#x201C;wiki champion&#x201D; - which I&#x2019;m sure many of you are, to show users the &#x201C;How&#x201D; and the &#x201C;What&#x201D;. \n\nSo Confluence &#x201C;Apps&#x201D; is really all about productising the use cases with the goals of showing people what they can create, how they can create it and helping them structure it. These use cases many if you are already familiar with: Using Confluence for meetings, documents, specifications, projects etc... \n\n---- CLICK\n\nSo why should you care? We&#x2019;ll if you&#x2019;re a commercial plugin developer, we&#x2019;d LOVE to hear from you. The project is still in concept phase, so you can help us shape the solution. In addition, apps presents a new opportunity for you to create add-ons that make content creation experience for your macro or even new types of content first-class in Confluence. \n\n---- CLICK\n\nWe don&#x2019;t have a talk for this as it&#x2019;s still really early stages, but Sherif Mansour is here with us - the Product Manager for &#x201C;Apps&#x201D;, and he is looking to hear from you and maybe have some one-on-ones with many of you here, so if you are interested, grab him and have chat to him or email him. \n \nSherif - do you want to stand-up so people see what you look like, this really isn&#x2019;t your photo! \n
\n\n
\n\n
\n\n
\n\n
You can think of the focus in JIRA over the last year as being along two main streams. And both are equaly important to all of you:\n\n* The Platform makes it easier and expands the ways to integrate with JIRA.\n* The user love is all about making it easier and simpler to work with issues and your team. \n\nThe &#x201C;user love&#x201D; theme is important because our goal is to provide more customer value and making it easier and faster to work with issues will be a big win for everyone. \n
Today I&#x2019;ll focus on 3 main areas.\n\nOne thing to highlight before we move on, although we are evolving the user experience with features such as &#x201C;inline edit&#x201D; and &#x201C;new search&#x201D;, we&#x2019;ve been stressing about how to make the evolution as painless for our ecosystem as possible. It&#x2019;s actually pretty freaking awesome that &#x201C;Inline&#x201D; was backwards compatible, and written as a plugin!\n
JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
We&#x2019;ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let&#x2019;s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
We&#x2019;ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let&#x2019;s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
We&#x2019;ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let&#x2019;s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
We&#x2019;ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let&#x2019;s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
We&#x2019;ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let&#x2019;s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
* REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA&#x2019;s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
* REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA&#x2019;s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
* REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA&#x2019;s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
* REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA&#x2019;s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
Highlight in the code that the changelog has the delta and generally more than enough information that doesn&#x2019;t require the receiver to have to call back to JIRA for most use-cases.\n
Highlight in the code that the changelog has the delta and generally more than enough information that doesn&#x2019;t require the receiver to have to call back to JIRA for most use-cases.\n
Highlight in the code that the changelog has the delta and generally more than enough information that doesn&#x2019;t require the receiver to have to call back to JIRA for most use-cases.\n
Highlight in the code that the changelog has the delta and generally more than enough information that doesn&#x2019;t require the receiver to have to call back to JIRA for most use-cases.\n
Webhooks should be simple. \n\nBut, the power of JQL is amazing. It means that without a single code change to JIRA a remote integration or app can register a hook, update the JQL, and get notified of the deltas. All without polling and without any changes to JIRA!\n
While JIRA 5.0 focused on the platform and new APIs, JIRA 6.0 is focused on the JIRA Experience\n\nA big reason for this is keeping JIRA thriving as the best development tool around - and attracting all new customers.\n\nThe marketplace has already been a big success for plugin developers, and with JIRA 6 we expect even more customers to flock to JIRA&#x2019;s new experience. So buckle up, and get ready for the journey.\n\nAnd we&#x2019;re doing this development in plugins! In-line edit and the new issue nav were both developed as plugins, as were issue collector and the new project administration screens.\n\n\n
There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
\n
This time last year we released two great features on top of the SDK that focused on improving development productivity. The first one is called FastDev.\n\nHow many of you here use FastDev?\n\nFor those that don&#x2019;t, FastDev will compile your code for you simply by you refreshing your browser.\n
We also introduced the plugin module generator which made it easy to generate boilerplate code for your plugin.\n\nBoth of these features added heaps to the plugin development experience.\n
Almost immediately after AtlasCamp, we released the REST API Browser and the Developer Toolbox, which bundled together some other useful development tools.\n\n\n
Earlier this Summer, we took a step back to look at how new developers got started with Atlassian plugin development. It was a bit of an eye opener. For starters, installing our SDK is a big task for many developers. Depending on the OS, you might have to alter your environment variables, install the JDK, etc. All told, our documentation on how to install the SDK was very revealing.\n\nSo, we decided to fix this problem by creating a set of installers. We now have an installer for Windows, Mac, and Linux. And on Linux, you have the choice of installing DEB or RPM files or registering our DEB or RPM repository so you can just `apt-get install` or `yum install` the SDK. For mac users, you can still use the Homebrew recipe if you wish.\n\nOur goal here is to ease the pain of getting started. We realize this may not be a big deal for all of you who already have the SDK installed and are familiar with how to set it up.\n
Earlier this Summer, we took a step back to look at how new developers got started with Atlassian plugin development. It was a bit of an eye opener. For starters, installing our SDK is a big task for many developers. Depending on the OS, you might have to alter your environment variables, install the JDK, etc. All told, our documentation on how to install the SDK was very revealing.\n\nSo, we decided to fix this problem by creating a set of installers. We now have an installer for Windows, Mac, and Linux. And on Linux, you have the choice of installing DEB or RPM files or registering our DEB or RPM repository so you can just `apt-get install` or `yum install` the SDK. For mac users, you can still use the Homebrew recipe if you wish.\n\nOur goal here is to ease the pain of getting started. We realize this may not be a big deal for all of you who already have the SDK installed and are familiar with how to set it up.\n
...and best of all it auto-upgrades now. Built into the SDK and run once a day before atlas-run or atlas-debug is a version check and it will upgrade if a new version if found. You&#x2019;ll never be behind again!\n
The developer toolbar provides easy access to all the tools you need when developing addons. In place documentation, API brower, live refresh, and more.\n
The developer toolbar provides easy access to all the tools you need when developing addons. In place documentation, API brower, live refresh, and more.\n
Best thing of all.\nBut here&#x2019;s a small preview of Live Reload... Basically, Live Reload is just that... real-time feedback as you code. Inspired by http://livereload.com/ which is a combination desktop app and browser extension that watches for file changes and auto-updates the browser page, and in the case of CSS, it doesn't even require a browser refresh!\n\nWe took their&#xA0;open-source javascript file, ditched the app and the browser extension and added that functionality into the fastdev plugin.\n\nThe Result? Live Reload can now be enabled for reloading plugin resources from the sdk. No desktop app. No browser extension. Just magic and a few pixies had to be sacrificed.\nIt currently supports live reloading the following file types: CSS, JS, LESS, VM, FTL, HTM / HTML, SOY, PNG, JPG, GIF!\n\nJonathan will have more to show tomorrow, but hopefully, I&#x2019;ve gotten you pretty excited.\n
Best thing of all.\nBut here&#x2019;s a small preview of Live Reload... Basically, Live Reload is just that... real-time feedback as you code. Inspired by http://livereload.com/ which is a combination desktop app and browser extension that watches for file changes and auto-updates the browser page, and in the case of CSS, it doesn't even require a browser refresh!\n\nWe took their&#xA0;open-source javascript file, ditched the app and the browser extension and added that functionality into the fastdev plugin.\n\nThe Result? Live Reload can now be enabled for reloading plugin resources from the sdk. No desktop app. No browser extension. Just magic and a few pixies had to be sacrificed.\nIt currently supports live reloading the following file types: CSS, JS, LESS, VM, FTL, HTM / HTML, SOY, PNG, JPG, GIF!\n\nJonathan will have more to show tomorrow, but hopefully, I&#x2019;ve gotten you pretty excited.\n
\n
It&#x2019;s been 3 months since the launch at Summit and when we first thought about launching the marketplace we had three main goals. \n
The first is goal of the marketplace was to increase the brillance of addons our customers can use - this means growing their quality, quantity, and continued support.\n
Well guess what... we currently have 112 Marketplace enabled addons! \n\nTo put this number in context and how awesome it actually is, we had 59 in June when we launched. This means we almost doubled in 3 months! And many of the new addons are brand new to Atlassian! \n\nThis has completely surpased our initial expectations!\n\nSource: Marketplace Stats Dashboard\n
The second goal was to remove the barriers for our customers to discover and purchase addons. There were many obvious barriers that we had to tackle first, such as like licensing, taxes, renewals, and evaluations. All these required a lot of grunt work in the UPM, the creation of the new Marketplace, legal, terms of use, and integration into our internal systems.\n\nBut... this is just the beginning. What is even more exciting is what this foundation is going to enable and i&#x2019;d like to share what&#x2019;s going to be shipping next that will remove even more friction and get your addons.\n
The problem is that most end-users will not randomly browse to the UPM and as a result they aren&#x2019;t exposed to the wealth of addons that are available and can make their days more productive.\n\nWe want to use the marketplace to help you reach not just your admins but the end users, and effectively turn them into your fans.\n\nSo how can we do this? First, we will start embedding links to the marketplace in key areas of the products so that end users can discover addons related to the specific areas in the product (eg, custom fields or gadgets in JIRA as another example)\n
The problem is that most end-users will not randomly browse to the UPM and as a result they aren&#x2019;t exposed to the wealth of addons that are available and can make their days more productive.\n\nWe want to use the marketplace to help you reach not just your admins but the end users, and effectively turn them into your fans.\n\nSo how can we do this? First, we will start embedding links to the marketplace in key areas of the products so that end users can discover addons related to the specific areas in the product (eg, custom fields or gadgets in JIRA as another example)\n
Clicking on the link will show an end-user view of UPM... with a big call to action. &#x201C;Request&#x201D; ab addon! Yes, we&#x2019;ve now engaged our end users directly.\n
To make the administrators life easier, please provide a really compeling reason!\n
Now switching over to the administrators view of UPM - you can see what your users have been asking for, with business justification and a rolled-up total number of requests.\n\nThis hasn&#x2019;t shipped just yet, \n\nAs you can We are really excited about the possibility that the continued removal of friction can provide for our teams.\n
The third goal was to ensure you have a thriving business that would allow you to continue to focus on providing great products for our customers.\n
Total gross dollars has surpased our forecasts, we have more addons, and more customers are evaluating and purchasing. The efforts to remove friction, although still very early, appear to be on the right track.\n\nSource: Marketplace Stats Dashboard\n
Total gross growth since launch.\n
We promised you this at Summit, and we&#x2019;re delivering today. Launching now, vendors can now get daily reports of your actual _sales_, including Renewals, Upgrades, Experts&#x2019; Discounts and Refunds. You&#x2019;ll know exactly what&#x2019;s happening in your business on a daily basis.\n\nYou can evaluate if your marketing campains, promotions, or features are making a direct difference to your customers.\n\nhttps://developer.atlassian.com/display/MARKETFAQ/Systems+and+Reporting+Provided+for+Paid-via-Atlassian+Listings\n\n<<plug dave&#x2019;s talk about techniques for making best use of the marketplace>>\n
We are building the marketplace to be the #1 enterprise marketplace in the world. \n\nBy building on this solid foundation, that you have supported and invested in, we are bullish about the massive opportunities it has opened up for us and our customers. Again, it&#x2019;s still early but we are really excited about the future.\n\nWe have two great talks this week related to the marketplace:\n\n* Dave&#x2019;s talk called &#x201C;sell, sell, sell&#x201D; provides numerous learnings on best practices for getting the most out of your addon marketing\n\n* Daniel&#x2019;s lighting talk will promote some of the untapped opportunities that we see are available for vendors to take advantage of.\n
Although we have a great platform and plugin system, the growth potential of hosted is going to require a parallel evolution of how we allow people to extend and build on our products. \n\nWe are working on some new technology that I&#x2019;d like to share with you today.\n
First, it&#x2019;s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it&#x2019;s growing. The marketplace today gives you access to all those customers. It&#x2019;s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<<click>>\n\nBut our current in-process plugin framework isn&#x2019;t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I&#x2019;m announcing plugins 3... the evolution plugins 2 for the cloud!\n
First, it&#x2019;s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it&#x2019;s growing. The marketplace today gives you access to all those customers. It&#x2019;s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<<click>>\n\nBut our current in-process plugin framework isn&#x2019;t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I&#x2019;m announcing plugins 3... the evolution plugins 2 for the cloud!\n
First, it&#x2019;s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it&#x2019;s growing. The marketplace today gives you access to all those customers. It&#x2019;s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<<click>>\n\nBut our current in-process plugin framework isn&#x2019;t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I&#x2019;m announcing plugins 3... the evolution plugins 2 for the cloud!\n
We&#x2019;ve listened to feedback from our prototyping of &#x201C;remote apps&#x201D; and are building p3. Think of plugins3 as the evolution of what we used to code-name &#x201C;remote apps&#x201D; and it&#x2019;s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It&#x2019;s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
We&#x2019;ve listened to feedback from our prototyping of &#x201C;remote apps&#x201D; and are building p3. Think of plugins3 as the evolution of what we used to code-name &#x201C;remote apps&#x201D; and it&#x2019;s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It&#x2019;s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
We&#x2019;ve listened to feedback from our prototyping of &#x201C;remote apps&#x201D; and are building p3. Think of plugins3 as the evolution of what we used to code-name &#x201C;remote apps&#x201D; and it&#x2019;s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It&#x2019;s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
We&#x2019;ve listened to feedback from our prototyping of &#x201C;remote apps&#x201D; and are building p3. Think of plugins3 as the evolution of what we used to code-name &#x201C;remote apps&#x201D; and it&#x2019;s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It&#x2019;s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
We are announcing p3 today. We will continue to be working with you over the next couple of months\n
Yon and Don are both are here - please don't hesitate to ask them any questions, express concerns or just share thoughts you may have. Don is giving a talk on p3 and will show off an example p3 addon and explain in a lot more detail the technical approach we are taking with p3.\n
Ecosystem: support is available and addons are getting better technically and getting better at UX and marketing.\n\nProducts: We are continuing make the user experience kickass and there are tons of new features to hack.\n\nThe SDK: Never update the sdk or refresh your brower again!\n\nMarketplace: It&#x2019;s growing faster than we had imagined and there are still so many untapped opportunities.\n\nThe future: BTF is still big, but we are working on the future with p3.\n
Find the guys that will help you solve your problem and if you can&#x2019;t, find me or Jonathan Nolan and we will find them for you.\n
Find the guys that will help you solve your problem and if you can&#x2019;t, find me or Jonathan Nolan and we will find them for you.\n