Friendly Austin is now over 1200 Members!

Friendly Austin was started almost a year ago and we recently hit 1200 members.

Some of the events I’ve particularly enjoyed are Movies in the Park, Hiking in the Greenbelt, and dancing and listening to swing and Motown music.

The Meetup group has sometimes been a challenge, but I am thankful for all of the experiences that we’ve shared together.

I have posted a few events on It’s Time Texas and am excited to see what ITT has planned for the rest of 2016.

You can join Friendly Austin at this link!

Thank you!

Getting started with Android and CircleCI

Continuous Integration provides many benefits to the software development process. Did I break the build? How many of our tests pass on the latest version? How can we distribute the latest version of our app to our testers smoothly? Continuous Integration can help answer all of these questions.

For those that have been around for a while, there have been many CI tools (CruiseControl) along the road to CircleCI and many are still relevant (Jenkins).

Yesterday, I started looking at CircleCI in depth after watching Donn Felker’s excellent video on Caster.io and here are a few simple steps to get started with CircleCI and Android.

To start, sign up for a CircleCI account here and sync your Github repositories.

Add a project that you would like to add to CircleCI. CircleCI will try to build your project automatically, but to maintain better control over your CI process you should use a circle.yml file. This file should be placed in the base directory of your project.

A sample circle.yml can be found below. Change the words CriminalIntent to the name of your project and make sure that the build-tools version in the circle.yml matches the build tools version in your build.gradle file for your app module.

https://gist.github.com/dazza5000/0a807de012c7281f14787cf30bf7be0e

Check in the circle.yml file and push it to GitHub.

CircleCI should now automatically build your project!

Screen Shot 2016-05-01 at 6.23.56 PMTo see what a passing build looks like you can check here:

https://circleci.com/gh/dazza5000/CriminalIntent

Full source for the project including the circle.yml file and build.gradle can be found here:

https://github.com/dazza5000/CriminalIntent

 

giphy

Where to put the gradle.properties file on Jenkins

TL;DR: Put your gradle.properties file in the /var/lib/jenkins/.gradle/ directory on a standard Ubuntu install.

Sometimes you need to have a gradle.properties file that is not included in your git repository. Many times this is because you need to have an api key that you would not like to be made public.

Because your gradle.properties file will not be checked into your git repository, the job will fail to build if your api key value is not able to be found.

One way to fix this is by placing your gradle.properties file in a place that jenkins will look for it. By default this location is in the .gradle directory of your Jenkins user.home directory.

To find the user.home directory open the Jenkins console in your browser, click “Manage Jenkins”, and then click the “System Information” link.

Scroll down until you find “user.home”

Screenshot_2016-02-08_17-26-12

In this example, the user.home directory is /var/lib/jenkins.

Now that we know this, we need to copy our gradle.properties file that contains our api key to /var/lib/jenkins/.gradle

For example:

sudo cp ~/source/a-caring-text/gradle.properties /var/lib/jenkins/.gradle/

Change the file permissions so that Jenkins can read the file:

sudo chown jenkins:jenkins /var/lib/jenkins/.gradle/gradle.properties

Now you can build the job that was depending on this api key!

raw

Friendly Austin hit 900 Members :)

We’re about 8 months in and this week we hit 900 members.

We are reaching a critical mass of 1000. Now we’re working on planning the rest of 2016 and enhancing our social media on Facebook and Twitter.

Lastly, Friendly Austin is now working with It’s Time Texas and is excited about what they have planned for 2016.

Thank you! <3

Click this link to join Friendly Austin!

Friendly Austin hit 500 Members :)

After starting about 4 months ago, last week we hit 500 members.

We are reaching a critical mass of 1000. Now I’m working on planning the rest of the year and getting the group setup on Facebook and Twitter.

All I have to say is thank you! <3

Friendly Austin

Austin, TX
933 Friends

Friendly Austin is a group dedicated to developing friendships and sharing healthy experiences with each other.We will be exploring all that Austin has to offer including:Hi…

Next Meetup

Hike the Violet Crown Trail (3-5 Miles)

Saturday, Feb 13, 2016, 10:00 AM
21 Attending

Check out this Meetup Group →

I started a Meetup Group – Friendly Austin!

After being an event organizer for a few Meetup groups in Austin, I decided to start my own! It’s mainly focused on outdoor activities and music events, but will probably end up having a little bit of everything!

Please join if you’d like!

Friendly Austin

Austin, TX
933 Friends

Friendly Austin is a group dedicated to developing friendships and sharing healthy experiences with each other.We will be exploring all that Austin has to offer including:Hi…

Next Meetup

Hike the Violet Crown Trail (3-5 Miles)

Saturday, Feb 13, 2016, 10:00 AM
21 Attending

Check out this Meetup Group →

First Code Contribution to Ubuntu was Approved!

Yesterday my first merge request to the Ubuntu project was approved! It is small, but feels great. It’s an automated test that tests the deletion of a playlist from the Ubuntu Music App.

Screenshot from 2015-03-24 17:59:49

Thank you to everyone who has written and published tutorials on how to get up to speed with Ubuntu QA and automating with Autopilot! The Orange Notebook was a great resource. Thank you to everyone who helped me with fix the formatting issues I had. Working on a project this size, I now realize how important it is to keep code structure and syntax consistent.

Link to the commit on launchpad:

https://code.launchpad.net/~darran-kelinske/music-app/lp_bug_1428454/+merge/253566

 

 

How to fix a few Autopilot Issues

There are changes in Autopilot and with these changes you will need to upgrade your test scripts.

Issue 1: AttributeError: type object ‘AutopilotTestCase’ has no attribute ‘register_known_application’

To fix this we need to modify the test script from something like this:

from autopilot.testcase import AutopilotTestCase
from autopilot.matchers import Eventually
from testtools.matchers import Equals, Contains

#register firefox as an application so we can call it
AutopilotTestCase.register_known_application("Firefox", "firefox.desktop", "firefox")

class FirefoxTests(AutopilotTestCase):

def setUp(self):
super(FirefoxTests, self).setUp()
self.app = self.start_app_window("Firefox")

To this:

from autopilot.testcase import AutopilotTestCase
from autopilot.matchers import Eventually
from testtools.matchers import Equals, Contains

class FirefoxTests(AutopilotTestCase):

def setUp(self):
super(FirefoxTests, self).setUp()

       if "Firefox" not in self.process_manager.KNOWN_APPS:
            self.process_manager.register_known_application("Firefox", "firefox.desktop", "firefox")

#make sure firefox is up and loaded
self.app.set_focus()
self.assertTrue(self.app.is_focused)

Issue 2: AttributeError: ‘FirefoxTests’ object has no attribute ‘start_app_window’

We need to change something like the following:

self.app = self.start_app_window("Firefox")

to

self.app = self.process_manager.start_app_window("Firefox")

 

 

 

How to Fix a Linksys EA4500 that’s not Transmitting at Wireless-N Rates

I had an issue where the EA4500 was not transmitting Wireless N rates. I did some searching and found that when you disable WMM the router will only transmit at Wireless B/G rates on 2.4 GHz.

Just re-enable WMM and you will get your Wireless-N speeds back.

To re-enable Wireless-N rates:

Login to your Administration page (typically at 192.168.0.1)

Click “Media Prioritization”

Click Settings

Finally, enable “WMM Support”

 

Screenshot from 2015-03-14 18:05:57

 

 

 

 

 

How to Fix Traktor Freezing when Plugging in a Traktor S2 (OS X)

While running the latest version of Traktor and OS X I noticed that Traktor would freeze when I plugged in the S2.

This might be obvious for some, but I had forgotten that the S2 contains an update utility that updates the firmware on the S2. After updating the firmware all my freezing issues went away!

Do the following to update the firmware on the S2.

Plug in the S2 to your PC using USB. Turn the S2 on by pressing the power button on the back of the S2.

Open the Device Updater using Spotlight (command + spacebar).

The Device Updater will inspect the version of firmware running on the S2 and the latest firmware available for the S2.

Screen Shot 2015-03-09 at 4.58.48 PM

Update the firmware and the freezing should be fixed!