Since final images resulting from multi-stage are supposed to rely on artifacts from build containers, there shouldn't be any reason to copy in the application files from the build host. Once T174622: Shorthand for standard multi-stage artifact config is implemented, Blubber can additionally make the decision to copy or not based on the new variant-level config.
Description
Description
Revisions and Commits
Revisions and Commits
| rGBLBR Blubber | |||
| D769 | rGBLBR62066296380d Smarter copies/sharedvolume/default behavior | ||
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T170453 FY2017/18 Program 6: Streamlined Service delivery | |||
| Invalid | None | T170480 FY2017/18 Program 6 - Outcome 2: Developers are able to develop and test their applications through a unified pipeline towards production deployment. | |||
| Invalid | None | T170481 FY2017/18 Program 6 - Outcome 2 - Objective 2: Set up a continuous integration and deployment pipeline | |||
| Resolved | None | T157469 Mathoid CI Container Build | |||
| Resolved | dduvall | T173127 Establish blubber config in mathoid | |||
| Resolved | dduvall | T174620 Complete Blubber's support for multi-stage Dockerfiles | |||
| Resolved | dduvall | T174623 Ensure application files are not copied for final multi-stage images |