Launch jobs can be very generic and re-usable across projects. Right now it appears that their scope is limited to a single project. While it’s possible to select a destination project (B) when executing a job from the original project the job was created with (A), that job doesn’t become available in B when doing something like configuring a sweep or cloning a run. It would be really nice if there was support for a generic jobs project, where some CI/CD could send jobs to, and that they could then be consumed by task-specific projects.
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Job/Launch/Queue | 2 | 184 | February 21, 2024 | |
| Can I launch a job that is using an already running docker container? | 0 | 4 | October 23, 2024 | |
| Moving projects from one team to another | 4 | 748 | January 1, 2022 | |
| How can I move a whole project to a team? | 2 | 3082 | June 24, 2023 | |
| Duplicating a project? | 2 | 222 | October 10, 2022 |