Now we have: I have just installed [1] [1] https://wiki.jenkins.io/display/JENKINS/JobConfigHistory+Plugin -- With regards, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Tue, Aug 8, 2017 at 7:18 AM, Evans Ye <evan...@apache.org> wrote: > I can only say that I didn't make any change. > While this is a bit tangential, I think it'd be great if we have edit log > on Jenkins jobs ;) > > 2017-08-07 23:37 GMT+08:00 Kevin Monroe <kevin.mon...@canonical.com>: > >> Hey folks, >> >> I've been using the workspace of a Bigtop-trunk-repos job as an apt >> repository to test new packages, e.g.: >> >> https://ci.bigtop.apache.org/job/Bigtop-trunk-repos/OS= >> ubuntu-16.04,label=docker-slave/ws/output/apt/ >> >> Up until a week or two ago, I could use the same technique on ppc64le >> systems with the following repo url (note 'ppc64le' in the url): >> >> https://ci.bigtop.apache.org/job/Bigtop-trunk-repos/OS= >> ubuntu-16.04-ppc64le,label=docker-slave/ws/ >> >> The above doesn't have a job workspace anymore. Was that intentional? I >> went poking around at my first link above and saw 'binary-arch' dirs, so >> perhaps the trunk repo is the one source of truth for all architectures: >> >> https://ci.bigtop.apache.org/job/Bigtop-trunk-repos/OS= >> ubuntu-16.04,label=docker-slave/ws/output/apt/dists/bigtop/contrib/ >> >> It's really cool if that's the case -- just wanted to confirm whether or >> not Bigtop-trunk-repos jobs for arm and ppc were now handled in 1 repo >> location. >> >> Thanks! >> -Kevin >>
