The Apache Jenkins build system has built Camel.trunk.notest (build #2490)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2490/
to view the results.
Hi Raul,
This is a good idea and we can work on a solution.
Speed up tests can be also useful to automate builds related to Pull Requests
submitted and for releases too.
There are several Apache Projects using this approach for PR first tests.
Actually I don't have experience with tests parallelis
Hi Raúl
Great, thanks for the help, JIRA issue got updated...
Cheers, Sergey
On 28/08/15 17:43, Raul Kripalani wrote:
Sergey,
Done.
Cheers,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://w
Sergey,
Done.
Cheers,
*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Fri, Aug 28, 2015 at 5:11 PM, Sergey Beryoz
Sorry can someone please add a new component to JIRA, camel-http-common ? I
had to list camel-http in CAMEL-9105
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Re-2-3-git-commit-CAMEL-7856-camel-cxf-producer-HttpAPI-should-not-send-the-message-body-when-using-d-tp575
I've created
https://issues.apache.org/jira/browse/CAMEL-9105.
Thinking more about it, DefaultHttpDestination is the best place to get Date
(and Locale) conversions handled, as noted though the existing code where
global TypeConverters are used would still work.
I'll create a patch next week and
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/601
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Hi team,
Our tests are taking around 4 - 5 hours to execute on Jenkins CI.
I think we can reduce this time by making use of the maven-surefire-plugin
parallelisation [1]. Not sure if the partitioning is able to span tests in
multiple projects, though. I've used it in the context of a single Maven
