[Haskell-cafe] haskell-ci problems
mikolaj at well-typed.com
Sat Nov 13 15:05:44 UTC 2021
BTW, Sven, my sources say, running `haskell-ci 'github'` as opposed to
`haskell-ci 'travis'` may give better results.
On Sat, Nov 13, 2021 at 2:39 PM Mikolaj Konarski <mikolaj at well-typed.com> wrote:
> > I can just offer testing haskell-ci patches etc.
> Thank you. I'm sure other haskell-ci contributors can use this help,
> if they read this. In general, that's a great idea, supporting our
> developers in other ways than just code contributions, e.g., via
> general positivity, appreciation, goodwill, expressions of hope,
> uplifting user stories. They are bombarded with (impersonal)
> negativity all the time via bug reports.
> > The project I used as a trial balloon for haskell-ci is really dead simple, how are other projects handling this? It must be an extremely common use case, and I doubt that everybody writes the workflows by hand: This would be silly, basically all needed information is already in the .cabal file.
> I'm afraid, since hvr stopped updating the PPA images (and other
> things), the Haskell tool ecosystem is in the very sorry and silly
> state you describe. Given that at this stage it's too late to help
> hvr, let's make sure to support Julian with ghcup (and other things)
> so that our ecosystem doesn't break up again, once we port haskell-ci
> to ghcup (if I'm guessing correctly where haskell-ci is going).
> > Other projects like e.g. lens seem to use haskell-ci successfully, see https://github.com/ekmett/lens/blob/master/.github/workflows/haskell-ci.yml. But that YAML file looks quite a bit different from what haskell-ci has generated for my project. Why?
> Because it's been edited by hand for 11 months.
> > As usual, the Haskell tool ecosystem is giving me a hard time... :´-(
> I sympathise.
> All the best,
More information about the Haskell-Cafe