[
https://issues.apache.org/jira/browse/CASSANDRA-15496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018244#comment-17018244
]
David Capwell edited comment on CASSANDRA-15496 at 1/17/20 7:11 PM:
--------------------------------------------------------------------
I am new to Jenkinsfile but the docs look like its groovy. What I see in the
test section is each test is copy/paste with a change in the build target name,
I am wondering if this could be extracted into a function which then lets you
define the target to generate for?
With that, I think the body of test could be
{code}
stage('Test') {
parallel {
runBuild("stress-test")
runBuild("fqltoo-testl")
runBuild("test-jvm-dtest-forking")
...
}
}
{code}
was (Author: dcapwell):
I am new to Jenkinsfile but the docs look like its groovy. What I see in the
test section is each test is copy/paste with a change in the build target name,
I am wondering if this could be extracted into a function which then lets you
define the target to generate for?
> Declarative Jenkins pipeline builds (and removing `ant test-all`)
> -----------------------------------------------------------------
>
> Key: CASSANDRA-15496
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15496
> 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
>
>
> *Declarative Jenkins pipeline*
> Currently all the jenkins build jobs are generated by the DSL job from the
> cassandra-builds repository.
> 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 pipelines.
> 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:
> https://lists.apache.org/thread.html/rc8d5a55142ea3bfb742e3347b8ea924946796bad03a1e089c8fb9ee7%40%3Cdev.cassandra.apache.org%3E
> *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:
> https://github.com/apache/cassandra-builds/blob/master/jenkins-dsl/cassandra_job_dsl_seed.groovy#L44
> ; 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
