Project

General

Profile

Actions

Bug #15321

closed

[workbench2] Test run, package building & deploy integration

Added by Ward Vandewege almost 5 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-
Release relationship:
Auto

Description

Test running

To be able to run future integration tests on WB2, we might need to clone its repo from the run-tests.sh execution, giving the developer the possiblity to define a custom directory when running tests locally on a specific commit.

Package building

Right now we're building workbench2 from the build-packages-workbench2 Jenkins job, that uses the workbench2-build docker image to run the package building task from the Makefile inside WB2's repo.

Not sure if that Jenkins job is triggered from somewhere automatically, so to include it on our standard package building procedure we should be modifying the build/package-build-dockerfiles/<distro_name>/Dockerfile files so that wb2's repo is cloned, and the Makefile task run from each one.

Deployment

The previously mentioned Jenkins job already run a deploy task on success(deploy-workbench2-to-4xphq and deploy-workbench2-to-c97qk), so they may be a useful example.


Related issues

Related to Arvados Epics - Idea #15333: Workbench2 feature parity with WorkbenchClosed01/01/202012/31/2021Actions
Related to Arvados - Idea #15335: [Workbench2] Integration testingResolvedActions
Blocked by Arvados - Idea #14659: Merge Workbench2 repo into Arvados repoClosedActions
Actions

Also available in: Atom PDF