-
Epic
-
Resolution: Won't Do
-
Major
-
2.0.1.GA
-
None
-
Prepare CRW build system for CPaaS integration
-
To Do
-
0% To Do, 0% In Progress, 100% Done
As of CRW 2.2.0 not all upstream to downstream repos are automatically synced or have places we can improve.
- operator-metadata: TODO: sync crd & csv from upstream 7.y.z -> 2.y.z, apply changes via sed DONE
- update deploy/operator*.yaml with specific tags (:2.y-zzz instead of :2.y) -
CRW-828DONE
- update deploy/operator*.yaml with specific tags (:2.y-zzz instead of :2.y) -
- plugin registry: tech debt: update Jenkinsfile to new devfile style w/ cleaner sed transforms & more close alignment to upstream DONE
- crw-theia:
- tech debt: build sometimes runs out of disk. Add naginator to retrigger? not a problem anymore; cleaning up between container builds so as to save space MITIGATED
- ensure dev, then theia, then endpoint are built IN ORDER (not in parallel): DONE
- crw-server:
- tech debt: merge build & sync jobs into a single job: DONE
- others / overall:
- All code in pkgs.devel should have a matching GH repo that is simply a 1:1 sync. That would allow us to see/share/PR code more easily.
CRW-797DONE - All existing sync jobs would of course need to be updated to sync to new midstream GH repo(s) rather than pushing directly to pkgs.devel - followup in
CRW-1275
- All code in pkgs.devel should have a matching GH repo that is simply a 1:1 sync. That would allow us to see/share/PR code more easily.
Overall status tracker: