You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kevin Buntrock (Jira)" <ji...@apache.org> on 2023/08/02 21:12:00 UTC

[jira] [Created] (MBUILDCACHE-67) Any error in restoring from the cache should resume the non cache build

Kevin Buntrock created MBUILDCACHE-67:
-----------------------------------------

             Summary: Any error in restoring from the cache should resume the non cache build
                 Key: MBUILDCACHE-67
                 URL: https://issues.apache.org/jira/browse/MBUILDCACHE-67
             Project: Maven Build Cache Extension
          Issue Type: Bug
    Affects Versions: 1.0.1
            Reporter: Kevin Buntrock
         Attachments: image-2023-08-02-22-55-53-476.png, image-2023-08-02-23-06-13-414.png, image-2023-08-02-23-08-25-744.png

If any error arise during the restoration of artefacts from the cache, the build should continue as it would usually do without the cache. In fact, it's even what the extension says "Cannot restore cache, continuing with normal build."

But it's a lie, the build is skipped to the saving to the cache phase.

!image-2023-08-02-22-55-53-476.png!

 

While trying to reproduce the error with a more convenient use case, it seems that erasing the artefact from the repository (local in my case) does not throw any restoration error. oO'

Here is a screenshot of a normal execution where the artefact is correctly loaded :

!image-2023-08-02-23-06-13-414.png!

And the log of an execution where the file is missing on the filesystem. We can see a missing line but no further effect on the cached build.

!image-2023-08-02-23-08-25-744.png!


I would suggest to correct / test the two bugs in the MR since it will be far easier to do so (it is why I created only one issue).

 

NB : The bugfix MR will follow.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)