DevOps

As a developer, I’ve written code and built apps, and I realized that building apps and creating a cheesecake have a lot in common. In both cases you need to have the right ingredients, you need to trust your suppliers and have transparency in your production process. I got to go to Atlanta and meet with the Docker Meetup Group there, where we got to talk about In this talk, how you can, and why you should, know what is in the app you deploy.

It was awesome to be at DevOps Days Baltimore and engage with the amazing audience there. Together with Baruch Sadogursky I got on stage to talk about how DevOps is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA. Together with the fact that DevOps is usually driven by the change in Culture, People, and Process, the question arises how you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments.

It was awesome to be at DevOps Days Charlotte 2019 and speak about how you hear everything in DevOps is unicorns and rainbows, and you feel like you’re the last person on earth with “suboptimal” processes, tools and environment. Together with Baruch Sadogursky I got the chance to change the image bit. While most DevOps talks are like Instagram (everything is awesome and perfect), they hаve nothing to do with the real life.

In many talks, you hear how everything is DevOps unicorns and rainbows, and you feel like you’re the last person on earth with “suboptimal” processes, tools and environment. But no despair, DevOps talks are like Instagram, hаve nothing to do with real life. In this talk, we’ll reveal the truth.

This is the fourth and final post in the blog series on using GitHub Actions with the JFrog CLI and JFrog Artifactory. In this post we’ll look at building an app and uploading it, together with the BuildInfo, to Artifactory. If you have any thoughts on what the next series of posts should be, let me know here or on Twitter!

In 2016 TIBCO announced Project Flogo as an ultra lightweight integration engine. It is the lightest way to connect IoT devices being up to 20 to 50 times lighter than Node.js and Java® Dropwizard. Project Flogo was made available as Open Source Software because TIBCO believes there is a better way to integrate IoT devices. With it being Open Source and easily extensible, you want to make sure that the activities you build remain working after each check in on GitHub. These are a lot of words to say “How can I test my activities every time code is pushed to Git”?

Probably the most common version control system, used by developers today is git. Whether that is a self hosted server (like Gogs), a bare repo (git init) or with GitHub, most developers intuitively seem to choose for git as their version control system of choice. I try to store all my projects in local git repos and some of them make it to GitHub, while many of them don’t. When it comes to deployment of apps to TIBCO Cloud Integration, I do many updates per day so I wanted an easy way to not only store my latest source but deploy them right after.

As you’ve probably guessed by my previous two articles I love writing (about) Node.js. What isn’t great, however, is creating deployment artifacts every time you check something in to GitHub and want to deploy. To make that process a little easier there are many tools available, and of of those is Jenkins, the friendly butler. In this “How-to” I’ll walk you through using Jenkins with the tibcli utility to deploy Node.js apps to TIBCO Cloud Integration every time updates are pushed to GitHub.