On Fri, 24 Jul 2020 at 15:07, Jiri Daněk <jda...@redhat.com> wrote: > > On Fri, Jul 24, 2020 at 2:39 PM Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > [...] > > > We must manually migrate any jobs we want to keep to the new system. > > > Are the job definitions in the new system under version control, or is > there expectation to manage jobs through the Web UI? >
The job definitions are the same in both I believe, i.e you can make do things either way. Ours have mostly been done via the UI, which is how I am keeping the ones I migrate as they are trivial, simple to port quickly without learning the Jenkinsfile stuff right now, and the config is mostly all copied from one job to another during creation anyway (for me at least, on Maven jobs). Can always change it. > [...] > > > I asked for a Qpid folder and for all committers to have access to the > > jobs, where they will live under: > > https://ci-builds.apache.org/job/Qpid/ > > > > Our old jobs are at: https://builds.apache.org/view/M-R/view/Qpid/ > > > Are there any advantages to using the Apache infra, over Travis or AppVeyor > or GitHub Actions? So far I've managed to completely ignore the Apache > Jenkins, so I am wondering; am I missing something? Maybe some Cloudbees > proprietary plugins? > -- > Mit freundlichen Grüßen / Kind regards > Jiri Daněk It's just another env really. It was there before all the other options were available, and remains so. More envs is good, helps balance availability (Things go down), and latency (everyone flocks to the shiny new thing and overloads the shared capacity, making for queues), and provides more runs (better helps see when things break, ditto when things are fixed). It hasn't used Cloudbees before now. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
