Comments for Software is too expensive to build cheaply.... http://twasink.net Robert's Rambling Ruminations Regarding Reality... Tue, 29 May 2012 00:48:29 +0000 hourly 1 http://wordpress.com/ Comment on Git, Feature Branches, and Jenkins – or how I learned to stop worrying about broken builds by Joe McDonagh http://twasink.net/2011/09/20/git-feature-branches-and-jenkins-or-how-i-learned-to-stop-worrying-about-broken-builds/#comment-621 Tue, 29 May 2012 00:48:29 +0000 http://twasink.net/blog/?p=778#comment-621 Good to know that it is not my insanity.

]]> Comment on Making Parallel Branches meet regularly with Git and Jenkins by Robert Watkins http://twasink.net/2011/09/16/making-parallel-branches-meet-regularly-with-git-and-jenkins/#comment-619 Mon, 28 May 2012 12:07:26 +0000 http://twasink.net/blog/?p=763#comment-619 In that case, I’d suggest merging it into some sort of candidate-for-stable branch. The biggest problem you’ll have with long-lived branches is that they will get harder and harder to merge and integrate together; keeping a candidate-for-stable branch around will make it easier to identify that.

]]> Comment on Git, Feature Branches, and Jenkins – or how I learned to stop worrying about broken builds by Robert Watkins http://twasink.net/2011/09/20/git-feature-branches-and-jenkins-or-how-i-learned-to-stop-worrying-about-broken-builds/#comment-618 Mon, 28 May 2012 12:05:33 +0000 http://twasink.net/blog/?p=778#comment-618 Yes – there’s a bug in the Git plugin where if it can’t merge a branch it gets stuck. That’s a bug, and it’s bloody annoying.

The behaviour I describe is when the branch merges cleanly, but doesn’t pass – at this point, the feature branch will not get monitored anymore. You may need to clean the workspace out between builds.

]]> Comment on Making Parallel Branches meet regularly with Git and Jenkins by Jon Lachelt http://twasink.net/2011/09/16/making-parallel-branches-meet-regularly-with-git-and-jenkins/#comment-617 Mon, 21 May 2012 23:00:33 +0000 http://twasink.net/blog/?p=763#comment-617 We’re planning to implement something like this, but we don’t want the build server to automatically merge a feature into the stable branch just because the build passed the tests. The developer may not be finished with the feature, or we may need product manager approval before we decide to merge the feature into the stable branch. So we want some additional action to trigger the merge (but still want it to happen only if the build/test were successful).

]]> Comment on Git, Feature Branches, and Jenkins – or how I learned to stop worrying about broken builds by Joe McDonagh http://twasink.net/2011/09/20/git-feature-branches-and-jenkins-or-how-i-learned-to-stop-worrying-about-broken-builds/#comment-616 Mon, 21 May 2012 15:35:49 +0000 http://twasink.net/blog/?p=778#comment-616 We have the same settings AFAICT and a broken topic branch that can’t be merged causes the build to fail, and remain broken until the branch is fixed so it will merge cleanly… so I’m having trouble understanding specifically what you mean when you reference a ‘feature’ to stop this from happening… would be a god-send to have this feature.

]]> Comment on Podcasts that I listen to by Nate http://twasink.net/2012/02/04/podcasts-that-i-listen-to/#comment-591 Thu, 12 Apr 2012 16:31:52 +0000 http://twasink.net/?p=896#comment-591 This Developer Life, not as technical but developer focused. It seems to be formatted like This American Life.

]]> Comment on On the private health insurance rebate means test… by Robert Watkins http://twasink.net/2012/02/14/on-the-private-health-insurance-rebate-means-test/#comment-562 Thu, 23 Feb 2012 21:20:45 +0000 http://twasink.net/?p=907#comment-562 The stated policy is that the means test will cut in at $160,000 (for families – $80,000 for individuals), with the benefit being phased out entirely at $250,000 (or $125,000 for individuals). This implies that the benefit is reduced as income goes up, which would be normal for most means-tested benefits. As a rule, Australian government subsidies try (but don’t always succeed) to avoid hard cutoffs.

]]> Comment on On the private health insurance rebate means test… by Carol Leary (caleary@picknowl.com.au http://twasink.net/2012/02/14/on-the-private-health-insurance-rebate-means-test/#comment-561 Thu, 23 Feb 2012 03:59:59 +0000 http://twasink.net/?p=907#comment-561 You have captured the inequalities in the Health System but like me you feel the need to have a backup. I sometimes wonder if these medical specialist are over charging because we have a private fund. Technology is great but the great costs come with it. I don’t know the answer as I think we can’t win. We pay a high premium for our families – hoping it gives us health security but the member is nearly always out of pocket after the exorbitant fees charged by the medical profession. I hope those on $160,000 will not lose their whole rebate and we need this to be explained. Those on $250,000 and over I believe do not need a government rebate.

]]> Comment on Git, Feature Branches, and Jenkins – or how I learned to stop worrying about broken builds by Stig Kleppe-Jørgensen http://twasink.net/2011/09/20/git-feature-branches-and-jenkins-or-how-i-learned-to-stop-worrying-about-broken-builds/#comment-559 Tue, 21 Feb 2012 16:19:11 +0000 http://twasink.net/blog/?p=778#comment-559 Yes, you will have to manually merge the integration branch into your branch to get _your_ commits to build if there is a merge error. But, as he says, if another developer pushes changes and they merge ok, the build will be green again.

]]> Comment on My heart bleeds for Karen Gee… by Robert Watkins http://twasink.net/2012/01/29/my-heart-bleeds-for-karen-gee/#comment-556 Mon, 20 Feb 2012 22:42:35 +0000 http://twasink.net/?p=891#comment-556 Yeah, I worked that out later. Still picked it out randomly, though. ;) The other public school in the same area also outperformed the Catholic school, though.

]]>