Page MenuHomeDevCentral

Automate www. deployment through Alkane
AcceptedPublic

Authored by dereckson on Sep 10 2024, 21:23.
Tags
None
Referenced Files
F24999983: D3439.id8871.diff
Tue, Mar 24, 11:14
F24999431: D3439.diff
Tue, Mar 24, 10:51
F24998597: D3439.diff
Tue, Mar 24, 09:55
F24998204: D3439.diff
Tue, Mar 24, 09:26
F24998091: D3439.id8871.diff
Tue, Mar 24, 09:17
Unknown Object (File)
Sat, Mar 21, 02:04
Unknown Object (File)
Tue, Mar 17, 15:42
Unknown Object (File)
Mon, Mar 16, 07:08
Subscribers
None

Details

Reviewers
aceppaluni
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 Passed
Unit
No Test Coverage
Branch
deploy-alkane
Build Status
Buildable 5479
Build 5760: arc lint + arc unit