CNDB-16516: Jenkinsfile for multi branch support in IBM TAAS

[maheshrajamani]

Added a Jenkinsfile that will used in cc Jenkins. Cloudbees Jenkins supported in UI scripting for multibranch but IBM TAAS needs it in the repository while using Pipeline: Multi branch plugin

What is the issue

Migrating the jenkins job from Cloudbees Jenkins to IBM TAAS. IBM TAAS is open source and does not support Cloudbees provided Multibranch plugin which allowed Jenkins job directly configured with custom script. To make the job work in IBM TAAS the job need to use OS Pipeline: Multibranch plugin which need the Jenkinsfile in the repo.

Migrated Jenkins job is available in here.

[github-actions]

Checklist before you submit for review

• This PR adheres to the Definition of Done
• Make sure there is a PR in the CNDB project updating the Converged Cassandra version
• Use NoSpamLogger for log lines that may appear frequently in the logs
• Verify test results on Butler
• Test coverage for new/modified code is > 80%
• Proper code formatting
• Proper title for each commit staring with the project-issue number, like CNDB-1234
• Each commit has a meaningful description
• Each commit is not very long and contains related changes
• Renames, moves and reformatting are in distinct commits
• All new files should contain the DataStax copyright header instead of the Apache License one

[michaelsembwever]

the direction is correct, but the PR needs more work:

• commit message (see Checklist above)
• file license header (see Checklist above)
• CI (is it possible yet to share a link to the IBM Jenkins showing this branch/pr being recognised ?)

maybe the new jenkins can also validate/lint the new Jenkinsfile, like upstream also does:
https://github.com/apache/cassandra/blob/trunk/.jenkins/Jenkinsfile#L55-L56
(worth adding this is as a comment into the file, in the same manner as upstream does

[maheshrajamani]

• commit message (see Checklist above)
• file license header (see Checklist above)

I have amended the commit messages, added Datastax license to the file.

• CI (is it possible yet to share a link to the IBM Jenkins showing this branch/pr being recognised ?)

The new Jenkins CI can be checked here. The link takes directly to the job run for this PR. Note: the jobs won't be automatically triggered as yet because webhooks need to be configured.

maybe the new jenkins can also validate/lint the new Jenkinsfile, like upstream also does:
https://github.com/apache/cassandra/blob/trunk/.jenkins/Jenkinsfile#L55-L56
(worth adding this is as a comment into the file, in the same manner as upstream does

The lint provided cannot be run similar to other file because this don't have full pipeline code. So added comment to suggest where the library's repo is.

[michaelsembwever]

remember to squash both commits to one before Rebase and merge

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[cassci-bot]

❌ Build ds-cassandra-pr-gate/PR-2206 rejected by Butler

---

3 regressions found
See build details here

---

Found 3 new test failures

Test	Explanation	Runs	Upstream
o.a.c.index.sai.cql.VectorCompaction100dTest.testCompactionWithEnoughRowsForPQAndDeleteARow[dc false]	REGRESSION	🔴⚪	0 / 20
o.a.c.index.sai.cql.VectorKeyRestrictedOnPartitionTest.partitionRestrictedTest[ca false] (compression)	REGRESSION	🔵🔴	0 / 20
o.a.c.index.sai.cql.VectorSiftSmallTest.testMultiSegmentBuild[ca false]	REGRESSION	🔴⚪	0 / 20

---

Found 2 known test failures