-
Notifications
You must be signed in to change notification settings - Fork 600
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
Remove obsolete files from web release deployments #3660
Labels
chore
Maintenance or non-code work
warning:stale
No recent activity within a reasonable amount of time
Comments
awentzel
added
status:triage
New Issue - needs triage
area:dev-ops
Pertains to build, CI, and other dev-ops work
labels
Aug 10, 2020
EisenbergEffect
added
chore
Maintenance or non-code work
and removed
status:triage
New Issue - needs triage
labels
Aug 10, 2020
awentzel
added
area:cloud
and removed
area:dev-ops
Pertains to build, CI, and other dev-ops work
labels
Aug 10, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
stale
bot
added
the
warning:stale
No recent activity within a reasonable amount of time
label
Dec 25, 2020
This was referenced Aug 18, 2021
This was referenced Sep 12, 2021
This was referenced Sep 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
chore
Maintenance or non-code work
warning:stale
No recent activity within a reasonable amount of time
What feature are you requesting?
New files deploy from GitHub Action's, however there is no mechanism that exists today to remove obsolete or out-of-date web files. This task would create a GitHub Action job to remove all files prior to deployment to maintain low disk space and simplify maintenance/diagnostics of wading through erroneous files.
For example, each release deployment may include 25 JavaScript files. On next build, it's another 25. Each having unique webpack generated names. Over time, this could grow unruly and thus we want to remove those old files on new deployments.
What solution would be ideal for you?
Investigate GH Actions to perform this that can be added to existing GH Action Steps.
What alternatives have you considered?
Depends if GH Actions has a solution. Will be revisited if necessary for alt-options.
The text was updated successfully, but these errors were encountered: