Use sane bundle names on result page. #120
Comments
@seman i don't think you could be less descriptive if you tried! What's the insane thing you're seeing, and what's the sane thing you want? |
I'm not a fan of that because what if you want to test
So you'd know exactly what the charm and bundle context is being executed by the job name.
Agreed. How does |
I, too, really dislike the underscore-heavy presentation in the reports, but between the collision issue that @kwmonroe mentioned and the need to be able to match jobs up to the output directory in a consistent manner, I couldn't come up with a better way to have them be presented nicely without the underscores and namespacing. Things to consider: being able to see a job in the CWR report and being able to easily match that job up in Jenkins, being able to reference said job in the API, being able to distinguish jobs that use the same bundle but are building and testing different specific charms within the bundle, avoiding corner cases where special characters in the title leak out and break things on the file system, avoiding a lot of duplicate logic throughout the codebase for normalizing titles to jobs names, etc. But if we can come up with a solution that improves the presentation while addressing those issues, I'm all for it. |
No description provided.
The text was updated successfully, but these errors were encountered: