CircleCI Ideas

Relax build name rules


I'm really enjoying CircleCI 2.0.  With Circle 2.1, I'm getting a lot more inventive with my jobs, by reusing commands with various parameters.  I wanted to have a build called "2.13", but got this complaint from Circle:


2.13: string [2.13] does not match pattern ^[a-z][a-z\\d_-]*$


I then tried scala-2.13, but got the same problem.  I was able to get scala_2_13 to work, but it's unsatisfying.


Just a thought.


Thanks for Circle,


  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Nov 2 2018
  • Not planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    3 Nov, 2018 07:19pm

    Thanks for this feedback. We are hesitating to allow dots in job names because with orbs and other use-cases we can already see some pull for more granular scoping and expanding what's available during build processing. We can see a time when we'd want to allow the dot to signify some kind of scoping, so we're reserving it for now while those concepts percolate. We've also been trying to keep our data format agnostic to YAML itself as much as possible, and dots present challenges in other data formats.