Github user davsclaus closed the pull request at:
https://github.com/apache/camel/pull/2241
---
GitHub user davidkarlsen opened a pull request:
https://github.com/apache/camel/pull/2241
upgrade to release version of spring boot 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davidkarlsen/camel boot2
Alternatively you can
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2240
---
GitHub user MelissaFlinn opened a pull request:
https://github.com/apache/camel/pull/2240
FUSE-DOC-1249 include dependency for Apache Karaf
Hi - I'm contributing a fix to the ASCII-doc documentation. Can you please
review it?
You can merge this pull request into a Git repository by
On Thu, Mar 1, 2018 at 10:03 AM, Zoran Regvart wrote:
> Hello,
>
> On Thu, Mar 1, 2018 at 9:34 AM, Claus Ibsen wrote:
>> I wonder if we should not turn this off, eg remove -Pintegration for now
>
> I think that would be the best, perhaps we can have a nightly job to
> run all the integration test
Hello,
On Thu, Mar 1, 2018 at 9:34 AM, Claus Ibsen wrote:
> I wonder if we should not turn this off, eg remove -Pintegration for now
I think that would be the best, perhaps we can have a nightly job to
run all the integration tests, for Salesforce I've setup a Camel
account to be used with integ
Hi
When the test stage runs it runs with Maven profile -P integration enabled
However those can often not run on CI server as you would need to
setup testing accounts on things like twitter, box, etc.
The CI job had 100's test failures and many of these because of this.
I wonder if we should not
Hello,
On Wed, Feb 28, 2018 at 8:06 PM, Pascal Schumacher
wrote:
> I guess we should disable concurrent builds to keep load on build.apache.org
> reasonable?
I've added that in[1], I think we'll notice the difference on builds >
#96. There is another thread for skipping tests when run in paralle
Hi Andrew & Cameleers,
our builds take really long time (we have a lot of modules/tests),
it's not uncommon for a full build/test to run for ~5 hours.
I think the best course would be to never run tests in two jobs or
only run them once per day. I was experimenting with throttle[1] and
ere is what
