I was under the impression that one could use variables to create dynamic job names. You are using this in a way that
jobDetect:$UIDID_IPHONE_7_WHITE translates to something like this in your job list:
Wondering if that’s your intention with the
$... notation, or if I am missing some feature here.
Actually the lexer/parser for the config supports that in the background, but does not automatically do that for job names this time.
The config validation already defines a
name either as string, or as symbol which makes me thing that this could be generated automatically.
lib/gitlab/ci/config (master=) $ vim entry/job.rb
validates :config, type: Hash
validates :config, allowed_keys: ALLOWED_KEYS
validates :config, required_keys: REQUIRED_BY_NEEDS, if: :has_needs?
validates :config, presence: true
validates :script, presence: true
validates :name, presence: true
validates :name, type: Symbol
I’m still wondering why your pipeline fails. I’ve built one myself and it doesn’t fail.