Use Herodevs libraries

[tasso94]

Acceptance Criteria (Required on creation)

• Bump bootstrap to a version > 3.4.1.
• Bump angular-ui-bootstrap to a version > 2.5.6.
• Bump angular-translate to a version > 2.19.0.
• Bump angular-moment to a version > 1.3.0.
• Ensure AngularJS uses Herodevs libs as well.

Update team docs: https://confluence.camunda.com/pages/viewpage.action?pageId=110241054

Hints

• Getting started instructions: https://support.herodevs.com/hc/en-us/
• Access token of private API can be found on keeper.

Links

• https://jira.camunda.com/browse/SEC-1049
• https://jira.camunda.com/browse/SUPPORT-23245
• related to: Migrate XLTS.dev to herodevs for extended support Platform versions

Breakdown

Pull Requests

Beta Give feedback

1. chore(webapps): use HeroDev libraries #4734
   ci:e2e ci:webapp-integration +2
   
2. https://github.com/camunda/camunda-bpm-platform-ee/pull/986
3. https://github.com/camunda/jenkins-job-dsl-seed-jobs/pull/427
4. https://github.com/camunda/infra-core/pull/8619
5. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1303
6. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1304
7. https://github.com/camunda/camunda-bpm-platform-maintenance/pull/1305

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment

[venetrius]

Conversion w @tasso94
We need to update to the new token in vault.
First step could be to update the secret in vault also update the xlts namespace to herodev.
And then a next step is to add bootstrap.

[venetrius]

Also update in repo:
https://github.com/camunda/jenkins-job-dsl-seed-jobs/
it might be that some update needed from infra team as well.
Can customise this build with the branch but also need to check if need to customise upstream projects
https://release.cambpm.camunda.cloud/view/Release-Test/job/7.23/job/7.23-TEST-RELEASE-start-camunda-bpm-release/build?delay=0sec
Don't merge to maintenance version before validating release test jobs work

Could also run a test release job for 7.22 to see that this is a problem (can ask Yana)

Update

Checked https://github.com/camunda/jenkins-job-dsl-seed-jobs/, it references 3 paramaters regarding this ticket:
XLTS_REGISTRY_AUTH_TOKEN
XLTS_REGISTRY
XLTS_AUTH_TOKEN
I assume XLTS_REGISTRY_AUTH_TOKEN is used to fetch the latter two.
The location where these secrets are stored changed but the keys (XLTS_REGISTRY, XLTS_AUTH_TOKEN) did not. No change is required in seed-jobs. A test will tell if any upstream projects needs an update.

[venetrius]

@tasso94 added issue to migrate remaining maintanance version to HeroDevs as well: #4784

[venetrius]

reached out to infra: https://camunda.slack.com/archives/C5AHF1D8T/p1731402410298249

[venetrius]

For our free style jobs all injected credentials are placed in this path products/cambpm/ci/jenkins.
This means XLTS.dev and HeroDevs credentials can't have the same names.
Refactored in the code:
XLTS_REGISTRY => HERODEVS_REGISTRY
XLTS_AUTH_TOKEN => HERODEVS_AUTH_TOKEN

[tasso94]

@venetrius, looks good to me. Let's merge the PRs into the master branches, run the release seed jobs (triggered automatically), and see the result of the test release job for 7.23. Afterwards, I would do the backporting