Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend new dogfooding ci job to linux and macos #7742

Closed
jneira opened this issue Oct 11, 2021 · 4 comments · Fixed by #8045
Closed

Extend new dogfooding ci job to linux and macos #7742

jneira opened this issue Oct 11, 2021 · 4 comments · Fixed by #8045

Comments

@jneira
Copy link
Member

jneira commented Oct 11, 2021

  • The motivation is clear: cabal HEAD should be able to install istself including its dependencies. It wuld cover the build of important libs for the ecosystem like network
  • The job was initially added for windows by @Mikolaj

test-windows-8_6_5-dogfood:

test-windows-8_10_4-dogfood:

  • Ideally those jobs should reuse the cabal excutable buils in the previous step. The usual way is upload and download it as a workflow artifact
@Mikolaj
Copy link
Member

Mikolaj commented Oct 11, 2021

Actually, as @hasufell rightly points out, we'd benefit from extending this to all architectures suppported by cabal, either on GHA or gitlab CI or whenever else we can set it up.

@hasufell
Copy link
Member

hasufell commented Oct 11, 2021

IMO, development, including the majority of CI should happen on gitlab, but that's just my opinion.

Right now the gitlab repo is a mirror and there are no tests run by default. When the next release is imminent, we'll have to fix a bazillion of issues again, because the gitlab CI part isn't actively maintained.

@jneira
Copy link
Member Author

jneira commented Oct 18, 2021

ci plumbing is not very popular but i think it would not be difficult to extend and clean those jobs

@andreabedini
Copy link
Collaborator

andreabedini commented Feb 22, 2022

After #7952 we are now testing dogfooding on linux, macos and windows. I belive this can be closed.

Sorry, I was grossly mistaken. We still need to do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants