Page MenuHomeDevCentral

Automate www. deployment through Alkane
ClosedPublic

Authored by dereckson on Sep 10 2024, 21:23.
Tags
None
Referenced Files
F45470539: D3439.id8871.diff
Sat, Aug 22, 08:27
F45469323: D3439.id10663.diff
Sat, Aug 22, 08:21
Unknown Object (File)
Thu, Aug 20, 14:50
Unknown Object (File)
Tue, Aug 18, 02:27
Unknown Object (File)
Mon, Aug 17, 19:06
Unknown Object (File)
Mon, Aug 17, 18:45
Unknown Object (File)
Mon, Aug 17, 16:39
Unknown Object (File)
Mon, Aug 17, 14:46
Subscribers
None

Details

Summary

Once a new commit reaches Jenkins CD, this pipeline triggers
a new deployment through Alkane HTTP API.

The API end-point is web-001, currently in IP form, as the Docker
container running the agent uses an external DNS and, as such,
ignores /etc/hosts on the Docker engine.

The context is compatible with _lib/git-clone.sh Alkane recipe.

Test Plan

Request has been checked with curl -X POST

Diff Detail

Repository
rWWW www.nasqueron.org
Lint
Lint Not Applicable
Unit
Tests Not Applicable