| By design, the log stream names are human-readable and map directly to Jenkins job names. Using the unique-id plugin would make them opaque, reducing ease of transition between Jenkins and external tools. (For the same reason, we decided that JCloudsArtifactManager would not encode its S3 blob name.) Remember you can change a job’s display name without actually renaming it. If JEP-207 were pushed forward, there would be a marker in a build.xml that a particular logging system were used for this build. At that point, we could also add an ItemListener that, upon seeing a job be moved or renamed, would add an extra field to all of its historical build records noting the redirect. Alternately, the log stream name could be unconditionally written when the build is started, at the cost of some redundancy in the normal case. (The log group name is system configuration, and while it might change after first use, it is not expected that the master is able to access arbitrary log groups.) |
