javax.jmdns.impl.tasks.Prober run
WARNING: run() exception
java.io.IOException: Operation not permitted
at java.net.PlainDatagramSocketImpl.send(Native Method)
at java.net.DatagramSocket.send(DatagramSocket.java:625)
at javax.jmdns.impl.JmDNSImpl.send(JmDNSImpl.java:1200)
at javax.jmdns.impl.tasks.Prober.run(Prober.java:163)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)

And when you access hudson in browser, it stays with the message “Please wait while Hudson is getting ready to work….” forever.

Initially I thought the problem might be because the ports which are required by the Hudson server i.e. 8080 and 5353, were not opened in the Firewall. I opened those, but the error remained.

After googling for sometime, I could find similar issues being reported here:

http://issues.hudson-ci.org/browse/HUDSON-7129?page=com.atlassian.streams.streams-jira-plugin:activity-stream-issue-tab

And the issue got fixed by adding

-Dhudson.DNSMultiCast.disabled=true

to the java command as follows:

java -Dhudson.DNSMultiCast.disabled=true -jar hudson.war --httpPort=8080

• Frequent Validation – Always validate with actual customers. Talk directly to them, take their feedback, implement it and soon release it. This cycle has to continue. If we don’t do this, there is no meaning in building any product with BDD/TDD, Automated tests etc.
• Limiting WIP [Work-In-Progress] – Never leave too many things untested or unreleased. Get your QA team to test as soon as the dev team is done. Release to production as soon as QA is done. When we make frequent releases, you can also get frequent validation.
• Checking vs Testing – If you’re not sure what the difference is, there’s an article on InfoQ that explains this well. The bottom line is, use automated tests for mundane tasks ["checking"] and use manual testing for exploratory testing.

There was an interesting session by Siddhartha Govindaraj, who is the founder of Silver Stripe Software. He talked about how they evolved from ad-hoc to Agile and from Agile to Kanban.  The points I felt interesting and which are worth trying out are:

1. No iterations/sprint - Always take top items from backlog – What usually happens during an iteration is, either you might finish all the items in an iteration and as there is still more time left you might have to pull some item from the backlog. The other case can be, you are not fully done with some tasks you might have to push some items to next sprint. Instead of this, always take items from backlog. The developers are supposed to work on the top items in the backlog and QA will be testing as soon as the development is done. QA need not have to wait for a certain period to test.
2. Limiting WIP (Work In Progress) - Don’t pile up stuff, never leave anything untested/unreleased. If WIP goes beyond a specific number, then change the plan like stop development make devs to test. And don’t keep tested stuff unreleased. Alway keep a maximum number of items that needs to be part of released. So even if the release is planned weekly, there can be multiple releases during the week if a lot of features are implemented during a certain week. Another advantage with this approach is, when dev team gets a chance to sit with QA, they also learn about exploratory testing.
3. Single backlog for multiple projects - This is an interesting point. He had multiple projects say A & B, both in maintenance stage. He has a team of 5. So rather than splitting the team into 2 across these 2 projects, they kept a single backlog of both projects. They prioritize the backlog and take items from that. This way both projects move in parallel more smoothly.
4. Checking vs testing - Checking should always be automated while  Manual testing effort should be reserved for exploratory testing only.

He also suggests avoiding a daily Scrum meeting. The point he had was, the team should be interacting so closely throughout the day, which avoids the need for a stand-up . But if there is an issue that needs to be discussed or if there is a requirement for having a discussion within teams, then such a stand-up is called for. I heard the same being discussed by many people – that Scrum is not really mandatory but am not sure about the same as of now. At Multunus, we still get quite a lot of value out of the stand- ups, because we do it a little differently.

It was a pretty simple presentation in which he was talking about how their company has evolved. As it was about his own experience, he had concrete examples for validating his points. There were questions from the audience like, how velocity is calculated if there were no sprints, how the team would get adjusted to context switching in case of single backlog etc. His answer was that, they are a small team – so these were mostly non-issues for them. And about velocity, productivity etc, those really will come into picture only if there is not enough trust in the team. If the team trusts the management and the management also trusts the team, then these productivity/burn down charts etc are meaningless. That point really made a lot of sense to me. If the team always perform/deliver well and if the management has trust on the team, why should they look at the burn down charts etc to see the team’s performance?

1. Export the certificate from IE by following the instructions given here: http://www.tech-pro.net/export-to-pfx.html
2. The certificate with Private key will be exported as PFX format in the above step – but this cannot be used by the jarsigner. So you need to convert it into “p12 format” which the jarsigner can understand. For that you need to use Mozilla. First import the certificate  saved in step 1 into Mozilla as follows:
   1. From the “Edit” menu select “Preferences” and open the “Privacy & Security” category and click on the “Certificates” item.
   2. In the “Manage Certificates” section, click on the “Manage Certificates” button.
   3. In the “Certificate Manager” window, the “Your Certificates” tab should automatically open. (If not, select it.)
   4. Click the “Impor”t button at the bottom of the window.
   5. It prompts you to select an existing file; select your certificate file from the location where you saved it in when you exported it.
   6. It prompts you to provide the “Master Password”; enter it, if you have set one.
   7. It prompts you to provide the password used to encrypt the certificate backup; enter it.
   8. It should say “Successfully restored your certificate(s) and private key(s).” Click OK.
3. Then export the certificate as p12 format:
   1. From the “Edit” menu select “Preferences” and open the “Privacy & Security” category and click on the “Certificates” item
   2. In the “Manage Certificates” section, click on the “Manage Certificates” button.
   3. In the “Certificate Manager” window, the “Your Certificates” tab should automatically open. (If not, select it.)
   4. To export your “DOEGrids” or “KCA Personal Certificate”, click on it to select it, and click the “Backup” button at the bottom of the window.
   5. You’ll be prompted to specify a filename and location for the “PKCS#12-format” certificate file (file extension will be “.p12″ in UNIX/Linux,  ”.pfx” in Windows).  Provide them and click OK.
   6. A dialog box requesting the Master Password may appear (the password and certificate database). If you have set a Master Password, provide it. If not, you can make one up and provide it (optional). Remember this password!
   7. You’ll be prompted to make up and (twice) enter a second password. This one is for restoring this particular backup of this certificate. Remember this password!
   8. Once the system says it’s successfully backed up your certificate and private key, click OK.
4. We also need to know the alias of the “.p12″ file so run:

    keytool -list -storetype pkcs12 -keystore <path to the cert file>

5. Then you will see output like this:

Keystore type: pkcs12 Keystore provider: SunJSSE

Your keystore contains 1 entry

xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx, Apr 26, 2006, keyEntry,

Certificate fingerprint (MD5):hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh:hh

The xxxx-xxx… number is the alias for the key

6. Change your ant script as follows to sign the certificate:

<target name="signjar" depends="jar">
 <signjar jar="yourJar.jar" storetype="pkcs12"
   keystore="yourkey.p12" alias="Your Alias"
   storepass="your password"/>
</target>