Evans beat to me it ;) 

+1.  I believe one of the reasons we have dropped the idea is a
semi-baked state of the plugin in question (at least at the time). Perhaps it
is time to let it go.

I still like the idea to have all the jobs to be version controlled, and in a
sense we are getting there by making CI jobs more "stateless" in a sense. Say,
the core functionality of a job sits in a script in git and gets invoked (with
necessary parameters) by the job to perform what is needed. Not all of them
are like that, but that's the direction I hope ;)

Cheers,
  Cos

On Wed, Jun 12, 2019 at 04:52PM, Evans Ye wrote:
> You're right. That's outdated. I'd like to remove them.
> The original thought was to have CI settings committed as code, however
> we're not getting there yet.
> 
> If you'd like to know the CI setting, go to Bigtop CI guide[1] and you'll
> find some more up-to-date info.
> To cope with our environment, we still have some workaround in our
> production CI jobs, which I think mine not be necessary for users who just
> target one single OS and Arch.
> 
> Let me know if you have any questions.
> 
> - Evans
> 
> [1] https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide
> 
> Xiyuan Wang <wangxiyuan1...@gmail.com> 於 2019年6月12日 週三 下午4:31寫道:
> 
> > Hi team,
> > I'm a new newbie to BigTop, after read some offical docs, I have a
> > question about bigtop-ci,
> >
> > BigTop has a CI system: https://ci.bigtop.apache.org/ Then I tried to
> > find the definition of the job that running on this Jenkins systemd.
> > But I failed.
> > I finde a Jenkins DSL plugin file at the location
> > "bigtop/bigtop-ci/jenkins/jobsCreator.groovy". While after reading the
> > code, it seems that the jobs which are defined in this file is not the
> > same with the jobs runs on the website.
> >
> > Is the file `jobsCreator.groovy` out of date already? Or my
> > understanding about BigTop-CI is totally wrong?
> >
> > Hope someone could help me or is there any link can give me more
> > information?
> >
> > Thanks very much
> >

Attachment: signature.asc
Description: PGP signature

Reply via email to