Looks like the invalid "control characters from U+0000 through U+001F" are the  ANSI escape codes used by WildFly to color output. So we might be able to work around this by disabling the color output in WildFly in our integration tests.

OTOH I'm fine with removing the Blue Ocean plugin for now, because its usability is sometime worse than the default UI's. E.g. when I click on the build results link in GitHub, 99.999% of the time I want to see the test results, but Blue Ocean thinks it's much better to show me some circles with question marks and exclamation points instead, and then keep me waiting for half a minute after I click on the tests link :)

Cheers
Dan


On Fri, Apr 21, 2017 at 4:55 PM, Sebastian Laskawiec <slaskawi@redhat.com> wrote:
Hey!

As you probably have heard I'm migrating our TeamCity installation [1] into Jenkins (temporarily in [2]).

So far I've managed to migrate all Infinispan builds (with pull requests), C++/C# clients, JGroups and JGroups Kubernetes. I decided to use the new Pipeline [3] approach for the builds and keep the configuration along with the code (here's an example [4]).

The configuration builds refs/pull/<PR>/head for Pull Requests at the moment. I will switch it back to refs/pull/<PR>/merge as soon as our PR queue size is ~20. 

Current pain points are:
  • Blue Ocean UI doesn't show tests. It has been reported in [5]. The workaround is to use the old Jenkins UI.
  • Windows VM doesn't start on demand (together with Vittorio we will be working on this)
The rough plan is:
  • Apr 24th, move other 2 agents from TeamCity to Jenkins
  • Apr 24th, redirect ci.infinispan.org domain
  • May 4th, remove TeamCity
Please let me know if you have any questions or concerns.

Thanks,
Sebastian

--

SEBASTIAN ŁASKAWIEC

INFINISPAN DEVELOPER

Red Hat EMEA


_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev