[
https://issues.apache.org/jira/browse/MBUILDCACHE-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17956958#comment-17956958
]
Olivier Lamy commented on MBUILDCACHE-98:
-----------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-build-cache-extension#325|https://github.com/apache/maven-build-cache-extension/issues/325].
Please visit the GitHub issue to view further activity, add comments, or
subscribe to receive notifications.
> Clarify literature on recommended scenarios (prod builds specifically)
> ----------------------------------------------------------------------
>
> Key: MBUILDCACHE-98
> URL: https://issues.apache.org/jira/browse/MBUILDCACHE-98
> Project: Maven Build Cache Extension (Moved to GitHub Issues)
> Issue Type: Wish
> Reporter: Pedro Javier Martos Velasco
> Priority: Major
> Labels: pull-request-available
> Attachments: screenshot.png
>
>
> Hi team,
> we're experimenting with the extension in a number of projects, both internal
> and customer facing. It's working quite fine, in fact we're so satisfied with
> the result that we're in conversations to standardise its usage throughout
> the engineering department.
> In our CI/CD implementations, any artifacts produced as part of a build are
> tested for functional correctness via post-deployment integration and/or e2e
> tests. This applies to both artifacts produced from "old style" {{mvn}}
> builds as well as artifacts produced in scope of partially or totally cached
> builds. These artifacts routinely make all the way to production with no
> issues and no impact to our customers, neither internal nor external.
> That being said, we have stumbled upon this part of the
> [documentation|https://maven.apache.org/extensions/maven-build-cache-extension/index.html]
> that has raised some concerns:
> !screenshot.png!
> Specifically, we'd like to understand the rationale behind the very last line
> of that section. It would be great if you folks could share some scenarios
> that you may have identified for which the outcome of a cached build might
> not be 100% production grade. Was that line perhaps intended as a "do your
> due diligence" kind of disclaimer, or do you foresee or have experienced
> issues that make you hesitant to showcase the build cache extension as a tool
> fit for production usage?
> We would greatly appreciate if you could elaborate a bit, as we believe that
> line, as it is stated right now, might limit the tool's adoption to the work
> done in local developer workstations, which is a bit unfortunate as we
> believe the cache extension could make a much greater difference and go much
> further than that.
> Thanks, and keep up the great work!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
