In this case we can simply copy one of the other maintenance branch builds and adapt it - if it's really required some time in the future...
Best, Christian ----------------- Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Mon, Nov 10, 2014 at 8:33 AM, Willem Jiang <[email protected]> wrote: > Hi Christian, > > I think we can keep the job there, and just disable the build. > In this way, we can keep the job configuration incase we need to run some > tests in these branches. > > Any thought? > > -- > Willem Jiang > > Red Hat, Inc. > Web: http://www.redhat.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.iteye.com (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > On November 10, 2014 at 1:16:40 AM, Christian Müller ( > [email protected]) wrote: > > Hi, > > > > because we are maintaining the trunk and the camel-2.14.x and > camel-2.13.x > > branches at present, I went ahead and removed the Camel 2.10, 2.11 and > 2.12 > > Jenkins builds. > > > > Best, > > Christian > > ----------------- > > > > Software Integration Specialist > > > > Apache Member > > V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer > > Apache Incubator PMC Member > > > > https://www.linkedin.com/pub/christian-mueller/11/551/642 > > > >
