Is this CI only need to run during the release preparing period? like, between the time of creating branch "branch-4.6", and creating release tag "release-4.6.0".
On Sun, Dec 3, 2017 at 5:45 AM, Enrico Olivelli <eolive...@gmail.com> wrote: > As we are supporting only a limited number of releases, say 3, we just have > to keep 3 jobs. > Currently we should have for at least 4.5, 4.6 and master. I am not saying > 4.4 because I am sure it will be full of flakes so it won't be useful > > +1 for jenkins job builder, it can be easily integrated with the release > process as for yhe website, at least for the config files, then an user who > has permissions ro edit config will apply the config after the release > > Enrico > > Il gio 30 nov 2017, 12:12 Ivan Kelly <iv...@apache.org> ha scritto: > > > With jenkins job builder, you can define templates, and then fill in > > variables for those templates. > > > > We already use jjb for the nightly job (see the jenkins directory), we > > should put all jobs into it. Then we can create parameterized jobs for > > 4.6, master etc. > > > > -Ivan > > > > On Thu, Nov 30, 2017 at 5:19 AM, Sijie Guo <guosi...@gmail.com> wrote: > > > We don't have a CI for a release branch. for example we created > > branch-4.6 > > > a month ago, but there is no CI covers branch-4.6. > > > > > > I don't know what would be the best solution. for now, I clone a > > > `bookkeeper-release-branch` from `bookkeeper-master` to run CI over > > > `branch-4.6`. so we at least have a CI job running for current release > > > branch. > > > > > > https://builds.apache.org/view/B/view/BK/job/bookkeeper-release-branch > > > > > > We need to think about a solution for this and how to manage this. > > > > > > - Sijie > > > -- > > > -- Enrico Olivelli >
