Mmuzaf commented on code in PR #2852:
URL: https://github.com/apache/cassandra/pull/2852#discussion_r1541552552


##########
.jenkins/Jenkinsfile:
##########
@@ -11,762 +11,518 @@
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
 // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-// Se# Licensed to the Apache Software Foundation (ASF) under onee the License 
for the specific language governing permissions and
+// See the License for the specific language governing permissions and
 // limitations under the License.
 //
 //
-// Jenkins declaration of how to build and test the current codebase.
-//  Jenkins infrastructure related settings should be kept in
-//    
https://github.com/apache/cassandra-builds/blob/trunk/jenkins-dsl/cassandra_job_dsl_seed.groovy
+// Jenkins CI declaration.
+//
+// Scripting defs and the declarative pipeline is presented first.
+// The stepsMap array describes the pipeline stages to what CI-agnostic 
scripts they map to.
+// All `type: test` use the script `.build/docker/run-tests.sh`
+//
+// These CI-agnostic scripts are used as an intermediate dockerized layer 
above the ant build.xml
+//
+//
+// This Jenkinsfile is expected to work on any ci-cassandra.a.o clone.
+// Functionality that depends upon ASF Infra and the canonical 
ci-cassandra.a.o setup (e.g. post-commit builds)
+//  is required to quietly fail when run on other environments.
+//
 //
 // Validate/lint this file using the following command
 // `curl -X POST  -F "jenkinsfile=<.jenkins/Jenkinsfile" 
https://ci-cassandra.apache.org/pipeline-model-converter/validate`
 
+

Review Comment:
   Should we use 4 spaces for a tab or 2 spaces? The code varies from one style 
to another, I think it should be consistent (4 tabs?).



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to