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

chore(ci): Build using Nix (Ubuntu & macOS) #20

Closed
wants to merge 365 commits into from
Closed

Conversation

srid
Copy link
Member

@srid srid commented May 2, 2024

No description provided.

Jenkins and others added 30 commits September 6, 2023 10:33
- to prevent previous build's test data poping up in another build's test
- whitelists juspay-portal origins
- Validates and authorizes users based on dashboard ACLs
- Validates tenant ID in header
- Adds an ACL guard for services
- this is needed because the application now uses git dependencies
- fixed cac tests dir as well
- variantIds brought to least priority
- toss, scope dimensions deleted
@srid srid force-pushed the patch-1 branch 2 times, most recently from 1d61e12 to 66c7d16 Compare May 2, 2024 11:51
@srid srid changed the title chore(ci): Build using Nix chore(ci): Build using Nix (Ubuntu & macOS) May 2, 2024
@srid srid marked this pull request as ready for review May 3, 2024 00:39
@srid srid requested a review from a team as a code owner May 3, 2024 00:39
name: "CI Nix"
on:
# Run only when pushing to main branch, and making PRs
push:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@srid can this be manually triggered instead of on every pull request and merge to main?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Datron CI should generally run on every PR and on commits to main. Why do you want to run it manually? The latter is risky that people may merge broken PRs into main.

Also, I think I should re-open the PR because someone seemed to have force-pushed to main branch.

Copy link
Collaborator

@Datron Datron May 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@srid You can just rebase, should get rid of the conflicts. Sorry for the trouble, I force pushed to main.

CI should generally run on every PR and on commits to main. Why do you want to run it manually? The latter is risky that people may merge broken PRs into main.

We already have a code check and build with cargo and tests, would nixci build do the same thing?

Copy link
Member Author

@srid srid May 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It builds the Rust package (via cargo), runs tests (cargo tests) and effectively makes sure that flake.nix remains not-broken for the user.

Other checks in the existing action like the one below can also be eventually moved to Nix, so that all of our checks run in CI via Nix. Just like it is in nammayatri. If there's consensus for that, I can help with doing it.

- name: Check formatting
shell: bash
run: cargo fmt --all --check

@srid
Copy link
Member Author

srid commented May 4, 2024

#27

@srid srid closed this May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.