CI Use single token for API

Now use a single variable to store an API token: K8S_SECRET_API_TOKEN

There is a default token supplied for orfeotoolbox/otb. If you use your own fork to make a MR, you should create a personal token (Account settings -> Access Token) and set it in a variable named K8S_SECRET_API_TOKEN (go to your forked OTB: Settings -> CI/CD -> Variables)

added ci patch labels

Does this mean that a non core developer making a contribution to OTB will not benefit from CI unless they create an access token? I'm confused if this is regarding CI on the Merge Requests submitted to the main OTB repository or on the fork.

• anyone pushing a branch on orfeotoolbox/otb will benefit from CI out-of-the-box
• a contributor pushing a branch on his own fork has to create an access token.

To answer your last question, the access token will be needed in both cases : MR from a fork to main repo, and MR/pushes on the fork itself (since the same CI script will be called).

merged

mentioned in commit dbf88cdf

changed milestone to %7.0.0