1.2 KiB

Raw Blame History

<html lang="en"> <head> </head>

Evergreen Use Cases

Table of Contents

1. Priority 1 Cases: Risk analysis
2. Priority 2 Cases
- 2.1. First startup should be done in less than 5 clicks and 5 minutes

This document summarizes the Priority 1 use cases for Jenkins Evergreen.

Note	This is still early work. To help the thought process, the cases definition and analysis was done by thinking about what a demonstration would need to go through.

1. Priority 1 Cases: Risk analysis

1.1. I can start an instance from scratch and it’s available

Registration & authentication service need to be available:
- An Internet connection is required
- Bandwidth needs to be enough to download things in a reasonable time. (It can probably be more than 5 minutes, if there is an issue.)
Binaries repository must be available.

1.2. Jenkins is constantly upgraded safely

If the backend becomes unavailable:
- Check the evergreen-client does reconnect automatically when back.
it the unavailability happens just after a failed upgrade, can we rollback offline?

1.3. Starting in a given cloud environment, Evergreen is auto-configured and ready to build with it

Concrete examples:

auto-configuring the docker-plugin if the Docker socket is available,
auto-configuring with ec2-plugin if AWS.

2. Priority 2 Cases

2.1. First startup should be done in less than 5 clicks and 5 minutes

Last updated 2024-05-19 20:59:28 UTC

</html>