Hi there,
I've got three questions on some of our GitHub actions (for example for
tomcat-native):
- CodeQL: it seems we combine CodeQL steps with steps that compile the
native code in the same Job. I have used the same pattern for
tomcat-connectors but since I am going to add further steps to allow
making test requests I wonder, whether there is a reason for this
combination. I haven't really read in detail on CodeQL but it seems it
does not make use of the build steps. Wouldn't it be cleaner to separate
the build part of the action and the CodeQL part into separate actions
(and workflows)?
- Is there an easy pattern to follow, if one would like to use uploaded
artefacts from another workflow eg. by downloading and using for tests?
Even if the artefact comes from another project? Like using
tomcat-native lib or Tomcat build in tomcat-connector test. I can live
without that and download latest released artefacts, but it might be
nice to use the snapshot builds.
- Windows runners allow different shells, like cmd (cmd.exe), pwsh
(Powershell) and bash (git bash). I'd prefer using git bash for the
steps to set up an environment where I can run simple test requests
against Apache with mod_jk (needs config patching with sed or similar).
Until now mostly Powershell is being used. Are there strong preferences
not to use git bash? Would people prefer to keep the PowerShell steps
used for ExpandArchive or sed-like Get-Content / Set-Content pipes or
should I migrate those to git bash (with unzip and sed)?
Thanks a bunch for any input.
Best regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
