What are the main syntax differences when translating a Jenkins shared library function into a composite GitHub Actions action?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
What are the main syntax differences when translating a Jenkins shared library function into a composite GitHub Actions action?
1 real search · 1 real-search pass
GitHub Actions composite actions metadata syntax inputs outputs runs steps shell documentation Jenkins shared library vars call function syntaxGoogle ↗
OBSERVEDInstruction
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
GitHub Actions composite actions metadata syntax inputs outputs runs steps shell documentation Jenkins shared library vars call function syntax Google ↗
- docs/content/actions/reference/workflows-and-actions/metadata-syntax.md at main · github/docs · github.com
- Metadata syntax reference · docs.github.com
- Metadata syntax reference · docs.github.com
- docs/content/actions/concepts/workflows-and-actions/reusing-workflow-configurations.md at main · github/docs · github.com