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

Feature request: Skip production build when files unchanged #9112

Closed
karptonite opened this issue Jan 6, 2018 · 2 comments
Closed

Feature request: Skip production build when files unchanged #9112

karptonite opened this issue Jan 6, 2018 · 2 comments
Assignees
Labels
feature Issue that requests a new feature P5 The team acknowledges the request but does not plan to address it, it remains open for discussion

Comments

@karptonite
Copy link

It would be useful for us if there were a way to conditionally build the application only if any of the sources or packages have changed since the last build.

The motivation for us is that building the application is part of our deploy step (which deploys both our front end and our back end), and right now, we are rebuilding the application (which takes nearly 10 minutes) as part of every deploy, whether it needs rebuilding or not. While I could rewrite our deploy step, this seems like a feature that would be useful to other users.

I imagine that this feature would require saving a hash representing the entire pre-compiled codebase on build, then comparing that hash before the next build. An easier but less robust solution could be as simple as comparing the last changed timestamps on all the source files to the time of the last build.

@clydin clydin added P5 The team acknowledges the request but does not plan to address it, it remains open for discussion feature Issue that requests a new feature labels Jan 8, 2018
@filipesilva
Copy link
Contributor

This is mostly the same request as #7467 (a way to cache intermediate build artifacts). I agree that this is a more limited request but I think that issue captures it better, so I am closing this one as a duplicate.

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature Issue that requests a new feature P5 The team acknowledges the request but does not plan to address it, it remains open for discussion
Projects
None yet
Development

No branches or pull requests

3 participants