Let me guess what you’re going to say in 3… 2… 1…
Right?
Some of us don’t have the luxury of a local NPM repository, while some others have their delivery pipeline tightly integrated to an Ivy repository.
So, for those few who are stuck with the unholy union of Node.js and Apache Ivy, you can publish your Node.js module to an Ivy repository using Bob. Here’s how:
Look what I found at my dad’s home office in Jakarta?
Apple Facts 8.95 - a concise guide to Apple products offered worldwide.
I didn’t know Apple used to have gazillion of products. Apple printers?
Why Macintosh? I started using an Apple MacBook Pro about 2 years ago, and after 6 months I was convinced that it was by far the most productive environment I had ever used. It’s cool to know that it was also the case back in the 90s.
I’m a fan of NodeUp, a podcast of all things Node.js-related, and a great source of thoughts/opinions from the who’s who in Node.js community.
Putting the serious stuff aside, the show has a running joke where the hosts put on their best effort to prop up Bislr, one of the show’s sponsors, by saying hilarious things about Australia. And it actually worked, us Australians (at least myself and those I know) love it, and I sure won’t forget the name Bislr for at least the next couple of years.
I went to Canberra this week to attend Open Source Developers Conference 2011 and also to give a talk titled Continuous Delivery Using Jenkins. OSDC ran for 3 days, and was held at Australian National University.
OSDC 2011 was very well organised, much thanks to the organisers: Evan Leybourn, Gavin Jackson, and the volunteers squad. It was an interesting grass roots conference with lots of passionate open source geeks, definitely learned a lot.
I was watching I, Robot the other day, and thought how great it would be to use voice to control Jenkins.
So last night I did a quick read, and then recorded this video. This used Mac Speech Recognition, so in theory I talked to my Mac, which then opened Jenkins pages on Firefox. Here are the commands:
It all started because at one point I was using a rather resource-challenged machine running Windows and an Ubuntu VM at the same time, and Firefox froze every so often, rendering Jenkins BuildMonitor and Jenkins web interface useless most of the time. So I looked for an alternative and gave Jenkins CLI a go.
Like most Java applications, Jenkins built-in CLI also suffers from slow start up time (flame suit: ON) due to core Java libraries loading (Kohsuke later told me on #jenkins that there’s also a handshaking process involved). This led me to try Jenkins Remote Access API with curl, which performed significantly faster than Jenkins CLI.
My earliest memory of real photography was this Mamiya camera my dad used for his work. My dad was an entrepreneur and started a small advertising company in the 80s, which means I grew up surrounded by tons of printing, design, photography, and various other creative works.
The above pictures were taken at the garage of my parents’ house back in Jakarta, Indonesia, sometime in the 90s.
I gave two Node.js-related talks within the past week.
The first one was titled “From Java To Node.js”, at Shine Technologies’ developers meeting on August 5th, 2011.
The second one was titled “JavaScript Everywhere From Nose To Tail”, at Melbourne JavaScript usergroup on August 10th, 2011, with Carl Husselbee from Sensis.
Happy with the positive feedback from the audience of both talks, thanks folks, much appreciated!
I’ve just added a new feature to Nestor to discover Jenkins on the network, and as it turned out, it’s pretty simple to do thanks to Node.js Datagram sockets API (hat tip Paul Querna).
Jenkins has a discovery feature as part of its remote access API where it listens on UDP port 33848, and whenever it receives a message, Jenkins will respond with an XML containing the instance’s URL, version number, and slave port information.
I still have 80 pages to go on Skunk Works, but this book has been one of the best I’ve ever read.
The story revolves around an elite group within Lockheed Martin called Skunk Works, who worked on top secret projects and engineered some of the most famous aircraft in the history of aviation. The book was authored by Ben Rich, Skunk Works second director, and central to the story was Clarence ‘Kelly’ Johnson, the founder of Skunk Works who was a genius on both technical and management fronts.