On Fri, Nov 10, 2017 at 6:03 PM, Pascal Schumacher
wrote:
> I have updated the jobs to use Maven 3.5.0.
Awesome, thank you :)
zoran
--
Zoran Regvart
Hi Zoran,
I have updated the jobs to use Maven 3.5.0.
-Pascal
Am 07.11.2017 um 01:01 schrieb Zoran Regvart:
Hi Cameleers,
I'm running a Jenkins instance to build Camel, and we have been
experiencing memory issues similar to those we have on
builds.apache.org. I've analysed a heapdump and trace
Hi Gregor,
awesome! I think you can use the Jenkinsfile from my fork[1] as a
starting point. Looking at it I remembered that I wanted to have Java
8/9 build run in parallel, and that complicates the build as two
checkouts are needed (for two nodes).
If you'd like to start from a fresh, that's also
Hi Zoran,
It would be great if we could switch to the Jenkinsfile approach soon.
I'd be available to help with this. :)
Thanks,
Gregor
On Tue, Nov 7, 2017 at 10:16 AM, Zoran Regvart wrote:
> Hi Gregor & Cameleers,
> yeah I think we should add Maven Wrapper, I think it's good to have as
> much
I have created a PR for the Maven wrapper [1] targeting the master
branch and using Maven 3.5.2.
Thanks,
Gregor
[1] https://github.com/apache/camel/pull/2083
On Tue, Nov 7, 2017 at 10:16 AM, Zoran Regvart wrote:
> Hi Gregor & Cameleers,
> yeah I think we should add Maven Wrapper, I think it's
Hi Gregor & Cameleers,
yeah I think we should add Maven Wrapper, I think it's good to have as
much project related tools/scripts within source control.
Some time ago I started experimenting on how to make the build faster
on Jenkins and I created a branch[1] to experiment with on my GitHub
fork. I
Hi Zoran,
Thanks for digging into this.
What do you think about using the Maven Wrapper for Camel going
forward? This way we could manage the Maven version from within the
project itself and even use the correct Maven version per branch /
Camel release (via the maven-wrapper.properties file).
T
I believe it should be fine, but first we need access to the CI.
--
Andrea Cosentino
--
Apache Camel PMC Member
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Tuesday, November 7, 2017, 1:0
Hi Cameleers,
I'm running a Jenkins instance to build Camel, and we have been
experiencing memory issues similar to those we have on
builds.apache.org. I've analysed a heapdump and traced it back to
Maven issue MNG-6030[1].
I see that Camel.2.19.x.fulltest and Camel.2.19.x.notest jobs are
running
