Add protected variables with hawkbit instance location and credentials

Value

• We can start dog-fooding our HawbKit stack
• We can test stability of our tooling
• We can explore testing updates
• We can explore sharing daily builds with other developers

Description

We want the following variables:

HAWKBIT_URL - URL of the hawkbit instance (i.e. https://hawkbit.svc.ostc-eu.dev/) HAWKBIT_USERNAME - name of the hawkbit user for CI, see below HAWKBIT_PASSWORD - password of the hawkbit user for CI - this variable must be both masked and protected.

Ideally we would have a new hawkbit user for use in CI, so that rotating passwords is not interfering with other work. Credentials must be available from a scheduled job which will upload the raspberry pi update bundle, at first, before we expand the scope to other machines.

In scope

Out of Scope

Acceptance Criteria

Applicable Market Segments

Applicable Personas

assigned to @pastanki

added teamota label

changed iteration to Oniro Core Iterations May 1, 2022 - May 31, 2022

added to epic &18

added teaminfrastructure label and removed teamota label

set weight to 0

marked this issue as related to #476 (closed)

mentioned in issue #476 (closed)

Done. User "oniro"

closed

@pastanki can you look at https://gitlab.eclipse.org/eclipse/oniro-core/oniro/-/jobs/19478 and tell me what is the condition for access to the protected variables?

I think we need a branch that is designated as protected. I will need @agherzan's maintainer help to set one up for me, so that I can test this feature. Ideally before Andrei's holidays.

https://docs.gitlab.com/ee/user/project/protected_branches.html

Give me a shout when you want me to take a look at this. Unless @pastanki already handled it.