CircleCI Ideas

Self naming jobs

Currently I have parameterised jobs, which run multiple times, with different parameters, in one workflow. 


The only way to meaningfully tell these jobs apart (aside from numbering) is to pass a 'name ' key through. This is annoying as the 'name' key mostly just relates to the parameters I'm passing in. It would be much neater if the parametrised job itself can use the parameters to set its own name. 


At the least, it would be useful 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 19 2019
  • Not planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 19, 2019 19:00

    Unfortunately, this would make the job names arbitrarily long, and they would change if the parameters change.