Hudson SVN Revisions/Changes Went Out of Sync

A project in our Hudson had been stalled for 3 weeks, for its svn revisions/changes, and I had to do a manual svn update in its workspace directory to make sure the build runs correctly. What exactly happened is that, Hudson was not checking out the HEAD revisions of these modules but the old revisions before it ran into this problem, besides, the "Changes" page showed no information other than those builds that happened 3 weeks ago.

So I thought there could be some state being held by it and I tried:

• To turn off using SVN update but SVN checkout for every build.
• To change the revision values in the svnexternals.txt.
• etc.

None of these helped 'til I changed the synchronousPolling in hudson.triggers.SCMTrigger.xml from false to true and Hudson finally polled the latest revisions and updated the "Changes" page for the newly triggered build. This reset the state and behaviour (of polling all in one go) and therefore resolved my problem.

Just a tip if any of you ever hit into this.

yc

How opportunity is given to your team members? If you are given this common scenario.

Firstly, I am not facing such a problem now. The situation came into my mind and I was thinking about what would be the best solution(s), if it happens one day that I have to make such decision.

I scrolled over my long list of MSN buddies, but I couldn't find the right people being in the right companies (true that, there's no perfect company and each company has its own culture) to answer my question. If there's any books that you can recommend, do let me know too.

Here comes the question. Say, if you are a team leader who is running a small team and there is an opportunity which can only be given to only one team member. An opportunity could be, a chance to move to another project, or to lead a new sub-project in a team.

Very common problem right? But I would like to know how differently people will handle this. Generally, the leader will short-list the potential ones from the team and make internal discussions with the superior and/or the candidates; or, instead of short-listing the guys, you make this information completely transparent to the team and let those who are interested to come back to you.

I gave two suggestions above, but each comes with its own set problems. The first one could possibly kill the opportunities of others, the second one could generate more competition in the team, so..

What will YOU do and suggest? And, what organization you are in? An open one? You may want to tell me how often do you share information with the team.

- yc

RE: Rethinking Software Development

My colleague David wrote a thoughtful blog about maximizing quality by increasing software development time, do take a look at it here.

Test-Driven development (TDD) and continuous integration (CI) are not new terms but they could be in Malaysia (generalizing based on the number of software engineers that I have met), or people (managers and developers) could just think they are something impractical in terms of meeting the project's deadline and such.

They should find out about the "Broken Iron Triangle" too.

- yc

JIRA Transport 1.0 Released

I have released my MuleForge project -- JIRA Transport yesterday. The transport enables easy integration of Mule (the leading open source ESB) with JIRA, and at this version, it has yet to support message receiving.

Click here to find out more about it.

- yc