-
Bug
-
Resolution: Fixed
-
Major
DownstreamPassCondition.jobs is in some places (e.g. getJobList) interpreted as a list of paths relative to the current job, yet in other places as a list of absolute paths (e.g. contains). Also there is no form validation on this field. The result is that you may be tempted to use a relative path to a downstream job in the same folder, but the promotion will silently never occur unless you use an absolute path.
PromotionTrigger also seems flawed. jobName is interpreted in appliesTo as a fullDisplayName, i.e. Folder Display Name » Job Display Name; but in the DescriptorImpl as a fullName, i.e. folder/job.