Yes it is a known problem.

It occurred when internal jenkins instance was updated and is not compatible with public one anymore.

Jenkins CI guys are aware of the problem and are working on it.
see ticket 311347 for more

--
tomaz


On Wed, Aug 20, 2014 at 11:23 PM, Arun Gupta <arun.gupta@gmail.com> wrote:
WildFly CI at https://ci.jboss.org/hudson/job/WildFly-latest-master/
is stamped Aug 6th.

Can somebody please fix it ?

Arun

--
http://blog.arungupta.me
http://twitter.com/arungupta
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev