1) The new drone tries to auto-convert the old drone format. It seems that when there are multiple variables mentioned in the when section of a step, it it doing something in the auto-conversion that causes:
linter: duplicate step names
I guess that it might be putting the step twice into the converted matrix.
The changes in this PR work-around the "feature".
2) Specify DB_NAME in every matrix entry.
db_name: ${DB_NAME=owncloud} is not being converted automatically for the new drone.
Description
1) The new drone tries to auto-convert the old drone format. It seems that when there are multiple variables mentioned in the
whensection of a step, it it doing something in the auto-conversion that causes:linter: duplicate step namesI guess that it might be putting the step twice into the converted matrix.
The changes in this PR work-around the "feature".
2) Specify
DB_NAMEin every matrix entry.db_name: ${DB_NAME=owncloud}is not being converted automatically for the new drone.Checklist: