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

Generation for CI/CD should abort on server if files changed #961

Open
matkoch opened this issue Jun 27, 2022 · 1 comment
Open

Generation for CI/CD should abort on server if files changed #961

matkoch opened this issue Jun 27, 2022 · 1 comment

Comments

@matkoch
Copy link
Member

matkoch commented Jun 27, 2022

Description

Currently, generation of CI/CD files is only enabled locally. Sometimes users forget to run nuke once more to update those files and therefore the build runs with old configuration. Instead, throw an error when files have been updated.

See https://github.com/nuke-build/nuke/blob/develop/source/Nuke.Common/CI/InvokeBuildServerConfigurationGenerationAttribute.cs

Usage Example

No response

Alternative

No response

@dansiegel
Copy link
Contributor

I've noticed that when generating on Windows/macOS these files will change even when the definition does not change. This is due to changes in the Line Endings where Windows will use \r\n and Mac will use \n.

Before this could be implemented the files would need to be compared while ignoring line endings.

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

No branches or pull requests

2 participants