A step-by-step tutorial for continuous integration with Jenkins for a Red Hat Mobile Native Android application: Part 1

nakfour
By Juana Nakfour

The dramatic influx of mobile application development has driven many new innovations that make it easier than ever to create compelling, flexible, and secure  applications. This two-part series details my work done at Red Hat’s Open Innovation Labs to capture these mobile innovations in a useful, repeatable way. In part one of this two-part series, I break down the steps to create and unit test a native android application using Red Hat’s Mobile Application Platform. In part two, I show how Jenkins can be used to automate  continuous integration and unit testing of that Mobile app.

This post was originally published on the Red Hat Services blog.

PART 1

Part 1 of this series covers the creation of a native Gradle Android application, shows how to add unit and instrumentation tests specific to Android.

Pre-requisites for this tutorial:

  1. Red Hat Mobile Application Platform Instance
  2. Android Studio set up on a development machine.

The following are the topics covered in today’s post and the video below:

  1. Creating an Android Application using RHMAP
  2. Creating an Android Unit test and Instrumented test
  3. Adding an Android Unit Test
  4. Adding an Android Instrumented Unit Test

Continue reading “A step-by-step tutorial for continuous integration with Jenkins for a Red Hat Mobile Native Android application: Part 1”

Share

Are “Web Components” in the future for PatternFly?

dgutride
By Dana Gutride

Web development has become increasingly complicated in recent years.  The questions of which framework to use often can eat up much time at the start of a project.  I can’t remember the number of times people have asked me while working on a Knockout project if I’ve heard of Durandal, or when considering Angular 2 – what about React/Flux or Aurelia?

Patternfly is a community project that promotes design commonality and improved user experience. Its offerings include open source code, patterns, style guides and an active community that helps support it all. But, this complexity, choosing web frameworks, also affects PatternFly.  Our goal is “to build a UI framework for enterprise web applications”.  That requires that we remain outside of the discussion of which framework is best and provide a solid set of patterns and designs for developers to rely on.

How can you build a UI framework when there are so many choices and so many strong feelings about the different choices?  In my opinion, it’s important for developers to choose the framework that is best for the project and fits their skill set.  There isn’t one choice that works for everybody and it’s important that we support all developers that want the benefit of well-designed components that can be used in enterprise applications.

Continue reading “Are “Web Components” in the future for PatternFly?”

Share