Skip to content

Further optimizations for Jenkins #5

Description

@Cervator

In the past with the Cloudbees flavored Jenkins one step was making an SSD storage class for faster masters - which we may well need again, especially for archiving of analytics which happens on the master and involves lots of little files.

There are other low hanging fruits at this point like simply disabling analytics we do not need (like PMD) - it isn't like we're using much of the analytics at all anyway. They can always be re-enabled later.

Initial resource config was applied but could probably need more tweaking over time.

See the TECHNICAL.md file for more details

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions