Skip to content

Instantly share code, notes, and snippets.

@jwadolowski

jwadolowski/doc.md

Last active April 6, 2022 10:05
Show Gist options
  • Save jwadolowski/fa7b1e1c68c4aded308628d9afd687f8 to your computer and use it in GitHub Desktop.
Save jwadolowski/fa7b1e1c68c4aded308628d9afd687f8 to your computer and use it in GitHub Desktop.
Download ZIP
DEV4 deployments
Raw
doc.md
ID Date Commit ID AEM release Reused build artifacts CM_DISABLE_BUILD_REUSE Pipeline link Dispatcher deployed?
0 2022-03-25 6:16 PM ed3c93eb 2022.3.6582 No Not set link NO 1
1 2022-03-28 3:31 PM 2a9727f3 2022.3.6582 No Not set link NO 2
2 2022-03-28 4:28 PM 2a9727f3 2022.3.6582 Yes Not set link NO 3
3 2022-03-31 12:33 PM 3a553139 2022.3.6698 No Not set link YES 4
4 2022-03-31 1:18 PM 5b8bf178 2022.3.6698 No Not set link N/A (build failure) 5
5 2022-03-31 1:39 PM d6f9a8a0 2022.3.6698 No Not set link YES 6
6 2022-03-31 3:00 PM 4030be2c 2022.3.6698 No Not set link YES 7
7 2022-04-04 12:51 PM 4030be2c 2022.3.6689 No true link YES 8
8 2022-04-04 2:22 PM 42c47d78 2022.3.6698 No true link YES 9
9 2022-04-04 3:06 PM 42c47d78 2022.3.6698 No true link YES 10
10 2022-04-05 10:17 AM 42c47d78 2022.3.6698 Yes Not set link YES 11

Footnotes

  1. Build & Unit Testing stage log says that This build generated 1 dispatcher configuration packages which will be ignored.. At that time a "Web tier" pipeline associated with DEV4 was present (that's what I said in a Gitlab MR discussion) ↩ ↩2

  2. Build & Unit Testing stage log says the same thing as in 1, however "Web tier" pipeline was deleted prior to that deployment. After a bit of investigation it turned out that Ignore Web Tier Configuration was selected (unclear how that happened) ↩ ↩2

  3. Artifacts got reused from previous pipeline execution, however the artifact set did not contain dispatcher because it was ignored due to pipeline config (see 2) ↩

  4. All the artifacts were built from scratch, including dispatcher config. Dispatcher config was deployed successfully. ↩

  5. Problem with unit tests ↩

  6. All good ↩

  7. All good ↩

  8. The same commit ID as in previous execution was used, but CM_DISABLE_BUILD_REUSE=true, hence full Maven build took place ↩

  9. New commit ID implies full Maven build and dispatcher deployment ↩

  10. The same commit ID as before, but the CM_DISABLE_BUILD_REUSE is still set to true, hence full Maven build takes place ↩

  11. CM_DISABLE_BUILD_REUSE is gone, so artifacts from previous pipeline got reused (2 other pipelines used the same Git SHA in the past, but most likely there's just 1 "cache bucket" for given commit ID, so the most recent execution always overwrites the artifact cache) ↩

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment