Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Allow deploy-exclude-additions.txt to be defined #1246

Closed
4 tasks
grasmash opened this issue Mar 22, 2017 · 0 comments
Closed
4 tasks

Allow deploy-exclude-additions.txt to be defined #1246

grasmash opened this issue Mar 22, 2017 · 0 comments
Assignees
Labels
Enhancement A feature or feature request

Comments

@grasmash
Copy link
Contributor

In addition to allowing deploy-exclude.txt to be replaced with a custom file, we should allow an additional deploy-exclude-additions.txt file to be defined. This will allow projects to add additional lines to be excluded from deployment artifacts without the need to frequently rebase from upstream.

  • Add new deploy.exclude_additions_file property to build.yml with default value ${repo.root}/blt/deploy-exclude-additions.txt
  • Create empty template/blt/deploy-exclude-additions.txt file.
  • Document new setting here
  • Modify deploy:copy target such that it:
    • Checks for the existence of ${deploy.exclude_additions_file}
    • If it exists, munge ${deploy.exclude_additions_file} and ${deploy.exclude_file} together into a third temporary file.
    • Use the temporary file in the rsync command
@grasmash grasmash added Enhancement A feature or feature request ready labels Mar 22, 2017
@grasmash grasmash added in progress and removed ready labels Apr 6, 2017
grasmash pushed a commit that referenced this issue Apr 7, 2017
* Allow deploy-exclude-additions.txt to be defined.

* Add unit test for new text:munge command.

* Update docs to include new exclude additions feature.

* Add deploy-exclude-additions.txt to ignore-existing.txt.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement A feature or feature request
Projects
None yet
Development

No branches or pull requests

2 participants