What's up with DRONE_* envs? #4098

zc-devs · 2024-09-08T09:48:05Z

zc-devs
Sep 8, 2024

I would add DRONE_* to the list.

We keep the drone vars to be compatible to drone plugins.

0.15

Dropped support for DRONE_* environment variables. The according WOODPECKER_* variables must be used instead.

Dropped support for DRONE_* environment variables in pipeline steps. Pipeline meta-data can be accessed with CI_* variables.

So, where is the truth?

Is there some docs, stating, that it was brought back for compatibility?

Answered by 6543

We dropped the DRONE_ vars as official build-in vars.
But we never removed them completely so drone plugins worked as the did.

nowadays we have a dedicated "compatibility" function that do provide this feature and also works with quirks we know of:

As for the docs we intentionally don't mention them, as users should not use them. But we do document that drone plugins can be used just natively.

I hope that covers all questions?

6543 · 2024-09-08T22:45:11Z

We dropped the DRONE_ vars as official build-in vars.
But we never removed them completely so drone plugins worked as the did.

nowadays we have a dedicated "compatibility" function that do provide this feature and also works with quirks we know of:

As for the docs we intentionally don't mention them, as users should not use them. But we do document that drone plugins can be used just natively.

I hope that covers all questions?

0 replies