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

Fix deployment --allow-dirty issue #177

Merged
merged 2 commits into from
Sep 14, 2023
Merged

Fix deployment --allow-dirty issue #177

merged 2 commits into from
Sep 14, 2023

Conversation

cottinisimone
Copy link
Contributor

The [build])https://drone-1.prima.it/primait/event_sourcing.rs/451/1/4) that failed because of dirty directory. The issue is that .cargo directory should be ignored

cpiemontese
cpiemontese previously approved these changes Sep 13, 2023
Copy link
Member

@MaeIsBad MaeIsBad left a comment

Choose a reason for hiding this comment

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

I would suggest you add a --allow-dirty flag instead

https://github.com/primait/umami/pull/1074

.cargo specifies a bunch of cargo, and it's a directory you want to commit to git

@cottinisimone
Copy link
Contributor Author

I would suggest you add a --allow-dirty flag instead

primait/umami#1074

.cargo specifies a bunch of cargo, and it's a directory you want to commit to git

Why do you think you want to commit a directory of cached things? .cargo directory is just a bunch of downloaded crates..

I think that --allow-dirty isn't that good because if something changes though all the steps (like the format, or the compilation or whatever) that should be committed in the source code, and not directly published..

Am i missing something?

@MaeIsBad
Copy link
Member

MaeIsBad commented Sep 13, 2023

I think that --allow-dirty isn't that good because if something changes though all the steps (like the format, or the compilation or whatever) that should be committed in the source code, and not directly published..

I thought allow-dirty would commit the clean state of the repo, but I was wrong, my bad.

Why do you think you want to commit a directory of cached things? .cargo directory is just a bunch of downloaded crates..

it is not, that's only a thing in the prima specific rust CI, because we set CARGO_HOME there. Normally .cargo contains the cargo config(https://doc.rust-lang.org/cargo/reference/config.html)

Copy link
Member

@MaeIsBad MaeIsBad left a comment

Choose a reason for hiding this comment

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

I'm not gonna block this on figuring out the perfect solution, since this will be fixed once we migrate to GHA, but can we just add a comment?

.gitignore Show resolved Hide resolved
Co-authored-by: MaeIsBad <26093674+MaeIsBad@users.noreply.github.com>
@cottinisimone
Copy link
Contributor Author

I think that --allow-dirty isn't that good because if something changes though all the steps (like the format, or the compilation or whatever) that should be committed in the source code, and not directly published..

I thought allow-dirty would commit the clean state of the repo, but I was wrong, my bad.

Why do you think you want to commit a directory of cached things? .cargo directory is just a bunch of downloaded crates..

it is not, that's only a thing in the prima specific rust CI, because we set CARGO_HOME there. Normally .cargo contains the cargo config(https://doc.rust-lang.org/cargo/reference/config.html)

I saw this issue: rust-lang/cargo#9398

@cottinisimone cottinisimone merged commit c392ce4 into master Sep 14, 2023
1 check passed
@cottinisimone cottinisimone deleted the fix-deploy branch September 14, 2023 08:12
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.

3 participants