cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Semb Wever (Jira)" <>
Subject [jira] [Updated] (CASSANDRA-15496) Declarative Jenkins pipeline builds (and removing `ant test-all`)
Date Tue, 21 Jan 2020 18:16:00 GMT


Michael Semb Wever updated CASSANDRA-15496:
    Status: Ready to Commit  (was: Review In Progress)

> Declarative Jenkins pipeline builds (and removing `ant test-all`)
> -----------------------------------------------------------------
>                 Key: CASSANDRA-15496
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/unit
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>             Fix For: 2.2.x, 3.0.x, 3.11.x, 4.x
>         Attachments: Screenshot 2020-01-17 at 21.14.52.png, Screenshot 2020-01-17 at
21.16.05.png, Screenshot 2020-01-17 at 21.16.47.png, Screenshot 2020-01-17 at 21.18.49.png
> *Declarative Jenkins pipeline*
> Currently all the jenkins build jobs are generated by the DSL job from the cassandra-builds
> For a given branch, there are numerous builds: artifacts, unit tests, and dtests.
> Using a (declarative) {{Jenkinsfile}} in-tree these builds can be put together into per-branch
> Per-branch pipelines will give a nicer UI (via blue ocean) and one place to look at test
results for any branch and commit. From there we can post one complete test summary on commits
back to the related jira ticket.
> ref:
> *Removing {{`ant test-all`}}*
> Currently the test-all target does nothing but execute the test target.
> This is because the test targets finishes with unit test failures.
> As these jenkins jobs are automated here:
; it is easy enough to remove the "test-all" target, replacing it with separate jobs for 'stress-test',
'fqltool-test', and 'long-test'.

This message was sent by Atlassian Jira

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message