Sheng, you should have admin access to Jenkins as of now.

Why wouldn't be persistent through reboots?

Pedro.

On Sat, Sep 14, 2019 at 10:07 PM Sheng Zha <zhash...@apache.org> wrote:

> Thank you, Philip. Looks like xgboost is using the same plugin for the
> timestamps.
>
> Unfortunately, I don't have admin access to the CI right now so I cannot
> add the plugin or view whether the plugin is already added. What's also
> unclear to me is how to add plugins to the CI in a persistent way that
> lasts through the next reboot.
>
> It would be great if someone could help in these aspects.
>
> -sz
>
> On 2019/09/15 04:27:47, Philip Cho <chohy...@cs.washington.edu> wrote:
> > Hi Sheng:
> >
> > Take a look at
> >
> https://github.com/dmlc/xgboost/blob/c89bcc4de5368b3f8a7fa170d8348287dab44caf/Jenkinsfile#L21
> > .
> >
> > Philip.
> >
> > On Sat, Sep 14, 2019 at 9:26 PM Sheng Zha <zhash...@apache.org> wrote:
> >
> > > Hi,
> > >
> > > There have been timeouts in the build step of CI in PRs. To help
> identify
> > > the steps where most time is taken, I suggest that we enable timestamp
> in
> > > the CI logging. With the help of a simple Jenkins plugin [1], we
> should be
> > > able to turn it on with some simple changes in our Jenkinsfiles.
> > >
> > > If you're already familiar with how to proceed, help would be much
> > > appreciated. Otherwise, I will start looking into how to proceed.
> > >
> > > -sz
> > >
> > > [1] http://wiki.jenkins.io/display/JENKINS/Timestamper
> > >
> >
>

Reply via email to