Jenkins Organization Proposal

Get Started. It's Free
or sign up with your email address
Rocket clouds
Jenkins Organization Proposal by Mind Map: Jenkins Organization Proposal

1. Views/Groups

1.1. Deploy

1.1.1. jobs to deploy artifacts to servers

1.1.2. receive artifacts to deploy as params

1.1.2.1. e.g deploy(auth, staging)

1.1.2.2. e.g deploy(gem-auth-api)

1.2. Gems

1.2.1. jobs to test and build gems artifacts

1.2.2. trigger another job

1.2.2.1. deploy-gem

1.3. Python Packages

1.3.1. tests packages

1.3.2. deploy to pypi

1.4. Golang packages

1.4.1. Test of golang packages

1.5. iOS

1.5.1. Builds of iOS apps

1.6. Android

1.6.1. Builds for Android Apps

1.6.2. Trigger the deploy-android job (?)

1.7. Core

1.7.1. Builds of jobs related stuff

1.7.1.1. Libcor3

1.8. Sysadmin

1.8.1. Builds of sysadmin stuff

1.8.1.1. Containers

1.8.1.2. Gemserver

1.9. Resources

1.9.1. Build of resources

1.9.2. Trigger another job called deploy-resource (?)

1.10. Maps

2. Conventions

2.1. Slaves names are sequencial

2.1.1. jenkins[number].ndrive.com

2.2. Slaves use labels to restrict jobs

2.2.1. e.g docker&&webservices for webservices

2.2.2. e.g docker&&maps for maps

2.3. Jobs are prefixed with the group

2.3.1. e.g gems-auth-api

3. Motivation

3.1. No conventions in naming

3.1.1. Makes hard to maintain

3.2. Jobs have too much reponsibility

3.2.1. For example, the android

3.3. We need a common language