Skip to content
This repository was archived by the owner on Jan 11, 2019. It is now read-only.
This repository was archived by the owner on Jan 11, 2019. It is now read-only.

split config of jobs to start and those to monitor for success #38

@adriaanm

Description

@adriaanm

Read this first [edited]:
Note that I do NOT propose to have the build bot schedule anything. The only tweak is to have the build bot know which jobs are triggered by jenkins as a result of the job that it starts, so that it can monitor the result of those jobs for error reporting.

Original, poor phrasing:
I think we should make the build bot more flexible: we should be able to specify which jobs to start and which jobs to monitor for completion.

This way we can create more complex flows (such as for IDE PR validation), where we run three jobs A, B and C for validation, but where job C must run after job B (using Jenkins as a scheduler). All jobs must still complete for the PR to validate in this scenario, but you could also imagine running jobs without monitoring them.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions