UrbanCode CEO and co-founder, Maciej Zawadzki, explains that Continuous Integration is more than just merging code. Join him as he explains some of the fundamentals of Continuous Integration in the third installment of the uChat video series.
I've already examined how important good testing is to the health of a project, a product and an organization. There’s a lot more to good testing than running an automated test suite in Continuous Integration and forcing someone to walk through functional test scripts and check lists.
HTTPS or SSL or TLS or whatever you want to call it can be a confusing beast. Some say it’s just about protecting your password and banking info whilst the packets are flying around the web but I’ve long said that SSL is not about encryption.
Certainly I’m not the first to notice the similarity between Test Driven Development and the Scientific Method?
Today: A new fork of WebKit from Google, a big security update for Postgres, new releases for R and Rust, and some very exciting positrons.
Imagine waking up to find your site and service hacked. Everyone is running around, trying to find out what went wrong; you’re tasked with repairing the damage. But unfortunately, that automation project you’ve been promising yourself you’d get done has always taken a backburner to more pressing matters and features.
Despite the fact that I’ve been working full time in software for almost 8 years now every now and then I still need a reminder of how useful reading logs can be in helping solve problems.
Today is a great day. Everyone is now aware of the problem and truly believes that technical debt affects the velocity of teams. But when facing this mountain of technical debt that covers every single wall with post-its, many development teams renounce to continue code quality remediation projects. See in this post how to set a Dynamic Violation Filtering in Eclipse to progressively show code violations.
WANdisco submitted Bloodhound to the Apache Incubator in December 2011 and our developers have been involved in the Apache Bloodhound project since its inception. So we’re pleased that today the Apache Software Foundation (ASF) officially announced Bloodhound as a Top-Level Project (TLP).
A simple and elegant way of constructing immutable Java classes, using hints in the parameter list.
Apache TomEE is an all-Apache stack aimed at Java EE 6 Web Profile certification where Tomcat is top dog. It is the conjunction of Tomcat + Java EE.
We usually want to know what is real code coverage in our applications divided into unit and integration tests. Unfortunately Maven has no out of the box support for different test types, but there are few options to workaround those leaks and through proper setup we'll be able to achieve desired task.
Apache Subversion remembers every change committed to the repository, making it possible to revert to previous revisions of your project. Users of SmartSVN, the cross-platform client for SVN, can easily perform a revert using the built-in ‘Transactions’ window.
A couple of weeks ago Tim and I were spinning up a new service on a machine which wasn’t quite working so we were manually making changes to the /etc/nginx/nginx.conf file and restarting nginx to try and sort it out.
In an interesting piece yesterday, GigaOM reported that Netflix has an architecture built around timelines. This struck home for a guy who spends a great deal of time talking to people skeptical about the need for zero latency, real-time systems.
I depend on If This Then That (IFTTT) to move data around the cloud. I syndicate blog posts from API Evangelist to Blogger and Tumblr. This isn't just blind syndication, it is SEO and also plan B scenarios to make sure my content exists in multiple areas.
Using a version control system for software development is a standard procedure today. While things are pretty clear for ‘standard’ Eclipse projects, it is not that easy for Processor Expert projects.
On this episode of the Cloudcast, Aaron, Brian and Nick Weaver talk with Gene Kim about his new book, ‘The Phoenix Project,’ and the evolution of DevOps.
Writing unit tests for multi-threaded is not simple and could even be impossible for some scenarios – how could you test that an asynchronous method was not called?
Urbancode’s DevOps toolchain begins with a developer committing code to a source repository. Commit comments can be added so that uBuild will associate the code change to a bug report (Bugzilla, JIRA, Rally, TFS, TeamForge) or a feature story (Rally, PivotalTracker, VersionOne, Rational Team Concert).
A couple of days ago I was playing with some code to scrape data from a web page and I wanted to skip a row in a table if the row didn’t contain any text.
I know what you're thinking, “It’s just logging!” This small, yet common part of our applications, provides developers, QA and troubleshooters with information to help in determining code execution sequences, inspecting data values and trouble spots within our applications.
Investing into code improvement is a dual edged sword: on the one hand you know that if you don’t improve your code you’ll get slower over time. On the other hand improving your code does not deliver tangible value to your users. So how do you know whether you’re on track?
This talk from Sam Eaton deals with the nightmare scenario of adopting DevOps in an environment where you're working with many, many different platforms/sites.
Deploying software can be a complex endeavor. We often think of it as “getting the software to the right boxes.” But grabbing the bits and moving them out to the right place on the target servers is one of the easier and least error-prone parts.