Implicit bootstrapping of modules
See original GitHub issueCurrently, when using Cake Modules, if it first necessary to do something like the following:
.\build.ps1 --bootstrap
To force Cake to first check and download any Modules that are included within the Cake Script, and then you run the build as normal:
.\build.ps1
This is a minor change to the default bootstrapper to make this happen, however, it would be very nice, if possible, that Cake implicitly did this check and download for any modules added to the Cake, so that it is a single execution of Cake.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (11 by maintainers)
Top Results From Across the Web
PEP 453 – Explicit bootstrapping of pip in Python installations
Its solution involves shipping a fake pip command that when executed would implicitly bootstrap and install pip if it does not already exist....
Read more >PEP 439 – Inclusion of implicit pip bootstrap in Python ...
This PEP proposes the inclusion of a pip bootstrap executable in the Python installation to simplify the use of 3rd-party modules by Python ......
Read more >20.2 Preparing to Use the Bootstrap Binaries
These are in the %final-inputs variable of the (gnu packages commencement) module, and are implicitly used by any package that uses gnu-build-system (see ......
Read more >Bootstrapping Spot Rates - CFA, FRM, and Actuarial ...
Spot rates obtained through bootstrapping are known as implied spot rates. Example: Bootstrapping Spot Rates. Consider the following annual par ...
Read more >Chrome infrastructure - Bootstrapping infra.git
This file is a python dictionary containing the exact versions of all Python module dependencies. These versions are the standard upstream package versions...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s not a noop in the current PR or works as previously. So no breaking change there.
Only difference is that it’ll also run implicitly without extra step when you execute scripts unless you opt out.
As a side note, the same would be true for cake-build/cake-action. Existing workflows can still pass the
cake-bootstrap
parameter and it just wouldn’t be passed on to the Cake executable.