Here’s how to speed up your CI/CD pipeline and get a fast build

It’s still a relatively new area, but a CI/CD pipeline exists to be speedy. Expert Abraham Marin Perez shares his secrets for getting to a quick build.

If your builds aren’t happening fast enough, the culprit is probably your pipeline. Expert Abraham Marin Perez explains how to diagnose and treat the problem.

Abraham Marin Perez is an independent Java developer, speaker and Agile advocate. He is speaking at JavaOne 2016 in San Francisco about keeping your continuous integration and continuous delivery, or CI/CD, pipeline as fast as possible. SearchSoftwareQuality caught up with Perez right before the conference began.
In your experience, is it common for companies to lose control of their CI/CD pipeline? Is there a way to set up the pipeline from the beginning to avoid this?

Abraham Marin Perez: In a way, yes. They wouldn’t call it ‘losing control,’ but I think that, although there are some really innovative companies that have some very sophisticated CI/CD pipelines, most companies are still at the point of simply trying to get a fully functional automated build. I mean, I have seen places where they don’t even have a reproducible way to produce a deployable package — everything is still a manual compendium of independently built modules that have to be put together on site … you can imagine that amount of trial and error that this requires. For these companies, simply achieving automation, without worrying about how long the build takes, is already a huge win.

The problem with achieving a fast build is that this is a relatively new practice, and we haven’t figured out yet a standardized or normalized process for it. There are some guidelines or practices, but when you look at different CI/CD pipelines in different places, you realize everything is quite customized. But, also, even if such a way was possible, I don’t think it’s a general concern right now: The first thing is making sure you have an automated build, then you can worry about making it work fast.

CONTINUAR LEYENDO: Here’s how to speed up your CI/CD pipeline and get a fast build

Pitney Bowes: Transforming Digital Commerce with APIs | Apigee


Pitney Bowes: Transforming Digital Commerce with APIsRoger Pilc, Pitney Bowes’ chief innovation officer, discusses how the company is well on its way to digitizing legacy business and building new digital businesses by harnessing existing capabilities and leveraging modern new technologies, including APIs and Apigee’s API management platform.Read Pitney Bowes’ full case study here.

Fuente: Pitney Bowes: Transforming Digital Commerce with APIs | Apigee

How to Select App Development Frameworks: Native vs. Web vs. Hybrid

When selecting frameworks with which to build apps, the biggest consideration is what kind of apps organizations plan to deliver: native, Web, or hybrid.

As companies start to build their own mobile apps, they’ll have to choose app development frameworks.

It’s an important first step to take an existing process and make it accessible from a mobile device. But apps become transformative when they take advantage of the rich features a mobile device can provide, such as location-based services, push notifications and seamless data sharing. When selecting frameworks with which to build these apps, the biggest consideration is what kind of apps organizations plan to deliver: native, Web, or hybrid.

Native App Development

Building a native application always results in the best user experience. Mobile operating system makers invest heavily in their own development tools. They want to make sure that the apps developers write in their native languages can take advantage of all the latest OS features and perform at their best.

Companies that have no prior experience with mobile development may be hesitant to have their developers learn separate languages to write apps for both Apple iOS and Google Android, however, because of the extra effort required to support multiple OSes. In situations where a company is standardized on one OS or requires tight hardware integration — such as with embedded devices, kiosks, point of sale and other special company-issued devices — it may be more important to develop native applications.

Browser-based Web Apps

At the other end of the spectrum are Web apps that users access in mobile browsers. Developers can write these with more familiar Web technologies, such as HTML5, CSS, and JavaScript. One version of a Web app can run on multiple mobile OSes. In addition, advances in HTML5 mean Web apps can now do many of the things that native mobile apps can, such as take advantage of cameras and geolocation and launch other apps on the device from within the Web app.

They’re attractive, but browser-based apps have many drawbacks. It’s only possible to send users push notifications with a few specific browsers, and app logins and sessions can expire quickly. Plus, Web apps can’t take advantage of all the latest OS features — some of the most unique and important traits that make mobile apps so valuable.

For all these reasons, mobile browser-based Web apps have limited use cases in the enterprise.Another problem: Web apps are just less convenient than native apps. Users have to remember how to navigate them, dig into bookmark menus to find them or know how to place Web bookmarks on their home screens. IT administrators can push these bookmarks to devices with mobile device management, but they still require different management processes than other apps.

Hybrid Apps

Hybrid apps are Web apps that run inside of a native app shell. Conceptually, this approach brings the best of both worlds. Developers can write the core logic of the app in a Web-based language that’s portable across multiple mobile platforms, and the shell can use native code to interact with the device’s unique features. As a result, IT can manage and deploy a hybrid app just like any other native app.

Hybrid apps can be as simple as a Web page embedded inside a native app, or they can be much more complex. Many app development frameworks can take apps developers write in Web-based or other languages and compile them into complete native apps for different mobile OS’s. Some app development frameworks provide only the user interface for hybrid apps, using native code and all the OS-appropriate design elements.

The hybrid app concept is popular but can have drawbacks as well. Using one codebase for multiple OSes means that developers have to make some compromises. For example, iOS doesn’t have full near-field communications support, and Android and iOS apps have different navigation conventions.

In some cases, with all the extra effort needed to make the “write once, deploy anywhere” concept actually work on multiple platforms, it can be easier to just invest in native app development after all.

Other Considerations

Enterprise mobile apps also need to connect to infrastructure components for push notifications, management and security, analytics, data syncing and connections to enterprise databases and feeds.

Some people say hybrid and Web apps are good enough for enterprise apps. Others say user experience is more important these days, and apps should take advantage of the native features a mobile OS offers. But different apps and situations call for different development approaches and considerations.




Fuente: How to Select App Development Frameworks: Native vs. Web vs. Hybrid – DZone Mobile

Huge | Digital Agency | Strategy, Design, Marketing & Technology

Este dato me lo pasó Manuel. De verdad el servicio es increíble. La idea de moverse a que la tecnología preste sus servicios silenciosamente, con calidad. Buen ejemplo.

El video hay que navergar para buscarlo, pero está muy bueno.

Huge is a full service digital agency headquartered in Brooklyn with offices worldwide. We transform brands and build businesses.

Fuente: Huge | Digital Agency | Strategy, Design, Marketing & Technology