Page MenuHomeDevCentral

Allow arbitrary images to provision Jenkins agent
ClosedPublic

Authored by dereckson on Sep 11 2018, 18:50.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 26, 18:27
Unknown Object (File)
Sun, Nov 24, 12:05
Unknown Object (File)
Sun, Nov 24, 11:37
Unknown Object (File)
Sun, Nov 24, 08:53
Unknown Object (File)
Sat, Nov 23, 13:02
Unknown Object (File)
Wed, Nov 20, 04:37
Unknown Object (File)
Tue, Nov 19, 21:53
Unknown Object (File)
Tue, Nov 19, 21:51
Subscribers
None

Details

Summary

Jenkins execution nodes can be tagged, so a Jenkins job runs on a server
ready for that.

Instead to create a unique 'jack of all trades' Jenkins images, we want to
be able to create more specialized images, for different needs or set of
configurations.

For example, we need to provision an agent with Rust capability.

Ref T1422
Ref T1406

Test Plan

Check the state is no op as far as Jenkins agents for CD are concerned.

Diff Detail

Repository
rOPS Nasqueron Operations
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

dereckson created this revision.

Not convinced by YAML alias, but works fine.

This revision is now accepted and ready to land.Sep 11 2018, 18:52
This revision was automatically updated to reflect the committed changes.
dereckson retitled this revision from Allow arbitrary images to provision Jenkins slave to Allow arbitrary images to provision Jenkins agent.Sep 12 2021, 08:49
dereckson edited the summary of this revision. (Show Details)
dereckson edited the test plan for this revision. (Show Details)