English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Continuous Integration (CI) and Continuous Deployment (CD) are widely adoptedin software engineering practice. In reality, the CI/CD pipeline execution isnot yet reliably continuous because it is often interrupted by Docker buildfailures. However, the existing trial-and-error practice to detect faults istime-consuming. To timely detect Dockerfile faults, we propose a context-basedpre-build analysis approach, named DockerMock, through mocking the execution ofcommon Dockerfile instructions. A Dockerfile fault is declared when aninstruction conflicts with the approximated and accumulated running context. Byexplicitly keeping track of whether the context is fuzzy, DockerMock strikes agood balance of detection precision and recall. We evaluated DockerMock with 53faults in 41 Dockerfiles from open source projects on GitHub and 130 faults in105 Dockerfiles from student course projects. On average, DockerMock detected68.0% Dockerfile faults in these two datasets. While baseline hadolint detected6.5%, and baseline BuildKit detected 60.5% without instruction execution. Inthe GitHub dataset, DockerMock reduces the number of builds to 47,outperforming that of hadolint (73) and BuildKit (74).

DockerMock: Pre-Build Detection of Dockerfile Faults through Mocking Instruction Execution