| What's the timeline on this? This is pretty inconvenient. We use different color schemes to signal to users which environment Jenkins is running in. e.g., a Jenkins running in 'dev' has different colors to that running in 'prod'. This helps prevent issues where a user thinks they are running a job on their local 'dev' Jenkins instance but instead they are running it on the actual production instance. Implementing a field in the global configuration that lets us define our own CSS file to load from the 'userContent' directory of Jenkins would be straightforward and allow us to change things as needed. This doesn't need to be complicated, we just need some way to inject some minor CSS into the page. |
