Am 03.07.2011 15:09, schrieb Attila Király:
I don't know about other public wicketstuff related CI server. In my experience wicketstuff hudson/jenkins was broken for most of the time during this year.
Oh cool, so Wicketstuff is the leader in Discontinuous Integration ;-)
Currently it seems it can not connect to the remote github repository (could be dns related, it had problems with that in the past).
Ok, but then it shouldn't be too difficult to fix if the Jenkins admin and the sysadmin of the box it's running on worked together.
So what's the root cause? a) At least one of these two admin roles is not assigned. b) Ping pong between the two roles. c) Admin not aware of problem. d) No time to fix it. e) No permissions to fix it. f) Does not know how to fix it. Identifying the blocker issue is the first step to remove it... Regards, Harald
