Bug #15321
[workbench2] Test run, package building & deploy integration
0%
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
History
#1
Updated by Ward Vandewege almost 3 years ago
- Related to Story #15333: Workbench2 feature parity with Workbench added
#2
Updated by Lucas Di Pentima almost 3 years ago
- Subject changed from [workbench2] the docker build container doesn't currently build workbench2 to [workbench2] Test run, package building & deploy integration
- Description updated (diff)
#3
Updated by Peter Amstutz almost 3 years ago
- Related to Story #15335: [Workbench2] Integration testing added
#4
Updated by Lucas Di Pentima almost 3 years ago
- Blocked by Story #14659: Merge Workbench2 repo into Arvados repo added
#5
Updated by Peter Amstutz over 2 years ago
- Release set to 20
- Target version deleted (
To Be Groomed)
#6
Updated by Peter Amstutz over 2 years ago
- Status changed from New to Resolved