[I] ci: Make it easier to reproduce CI jobs with local scripts [sedona-db]

["paleolimbot (via GitHub)" <gi...@apache.org>]

paleolimbot opened a new issue, #1201:
URL: https://github.com/apache/sedona-db/issues/1201

   Yes that sounds good.
   
   Here is some additional information: my final goal is to have an easy way to reproduce the full CI locally, so for small fixes we don’t have to go back and forth checking the GitHub CI runner status.
   
   I usually use plain shell scripts for this purpose, as I find them much more flexible than pre-commit configuration files.
   
   How about maintaining CI jobs like:
   
   ```
   cargo-fmt.sh
   cargo-clippy.sh
   test.sh
   ```
   
   Each one can support different options, for example:
   
   ```
   ./cargo-clippy.sh          # check only
   ./cargo-clippy.sh --fix    # auto-fix and then check
   ./test.sh --fast           # quick tests, finish in minutes
   ./test.sh                  # full test suite, takes longer
   ```
   
   Then local CI scripts, GitHub CI configuration, and pre-commit hooks can all call these shared scripts, while still allowing us to customize our local development workflow based on personal preferences.
   
   I’m trying to set this up and hopefully sync it with upstream later.
   
   _Originally posted by @2010YOUY01 in https://github.com/apache/sedona-db/issues/580#issuecomment-3882020292_
               


-- 
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: issues-unsubscribe@sedona.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] ci: Make it easier to reproduce CI jobs with local scripts [sedona-db]

["2010YOUY01 (via GitHub)" <gi...@apache.org>]

2010YOUY01 commented on issue #1201:
URL: https://github.com/apache/sedona-db/issues/1201#issuecomment-5487544019

   Update, some time after the original comment: we've been using bash for DataFusion's CI scripts, but given how complex they've grown, they're becoming hard to maintain. Writing the CI scripts directly in Rust looks like the better choice.
   
   We've just started on this — if it works out, we can follow the same pattern here later.
   - https://github.com/apache/datafusion/issues/24487


-- 
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: issues-unsubscribe@sedona.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org