Page MenuHomeDevCentral

Automate www. deployment through Alkane
AcceptedPublic

Authored by dereckson on Sep 10 2024, 21:23.
Tags
None
Referenced Files
F25091034: D3439.id8871.diff
Sun, Mar 29, 11:57
F25086024: D3439.id8871.diff
Sun, Mar 29, 08:50
F25084082: D3439.id.diff
Sun, Mar 29, 06:16
F25075697: D3439.id8871.diff
Sat, Mar 28, 19:05
Unknown Object (File)
Thu, Mar 26, 16:07
Unknown Object (File)
Thu, Mar 26, 10:45
Unknown Object (File)
Tue, Mar 24, 16:25
Unknown Object (File)
Tue, Mar 24, 16:24
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