Am 24.10.2017 um 14:46 schrieb Joachim Breitner <mail@joachim-breitner.de>:

Is CircleCI the future now?

Yes, as per

https://ghc.haskell.org/trac/ghc/wiki/ContinuousIntegration

In general, yes. But it’s running fine for now, so I would not
prematurely throw it over.

My requirements are:

* needs to run on every commit (not just every push), including
  branches.
* needs to be able to push to a repository¹, so it needs access to
  some secret token for depolyment.
  Alternatively, the CI could simply keep track of the build log
  and the perf.haskell.org dashboard scrapes it from there.
* Occasionally, I find that I want to rebuild a fair number of commits
  that are already in the repository. So a good way to trigger
  rebuilds would be nice.

No need to mess with a working system, but as long as performance counters are the basis, I think, these constraints can all be met. In particular, CircleCI has facilities to allow deployments including managing of secrets. (That is a pretty common requirements for CIs.)

Cheers,

Manuel

Greetings,
Joachim

¹ https://github.com/nomeata/ghc-speed-logs/commits/master

Am Dienstag, den 24.10.2017, 12:18 +1100 schrieb Manuel M T
Chakravarty:
Hi Joachim,

Great! Just because you mention CI infrastructure and our effort around GHC CI at the moment, do you think, it would make sense to move this to CircleCI eventually?

Cheers,
Manuel

Am 24.10.2017 um 11:02 schrieb Joachim Breitner <mail@joachim-breitner.de>:

Hi,

after a system upgrade to avoid weird linker errors, and after some fixes in the nofib submodule, http://perf.haskell.org/ghc is running again.

I am collecting instruction counts instead of runtime, because the latter was just too often varying too wildly. I hope this will yield less false alarms.

I am also running nofib with mode=fast. This way, building GHC, running the testsuite and nofib takes a bit over one hour. I hope this can keep up with y'all's commits (when it took 2h it couldn't).

Now nothing of the setup requires a quiet dedicated machine, so if there is a need, we could move these builds into the cloud or into some CI infrastructure - but no changes are immediately planned.

Enjoy, Joachim
--
Joachim Breitner
mail@joachim-breitner.de
http://www.joachim-breitner.de/
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs