[no-relnotes] Use reusable workflows for CI #1154
Conversation
elezar
force-pushed
the
update-ci
branch
27 times, most recently
from
bb73cfb to
ea8b77c
Compare
| if: false | ||
| uses: slackapi/[email protected] |
There was a problem hiding this comment.
@ArangoGutierrez the upgrade to v2.0.0 has broken this step. I believe the API has changed.
There was a problem hiding this comment.
Let me check and take action for our repos
.github/workflows/code_scanning.yaml
Outdated
| jobs: | ||
| analyze: | ||
| name: Analyze Go code with CodeQL | ||
| if: always() |
There was a problem hiding this comment.
I think this can be removed
Signed-off-by: Evan Lezar <[email protected]>
|
I'm still not 100% about the naming of the steps, but I suppose we can iterate on that at a later point. |
Signed-off-by: Evan Lezar <[email protected]>
same here, not 100% on "basic" but I can't think of a better name |
| }) | ||
| It("it should run GPU jobs", func(ctx context.Context) { | ||
| By("Creating a GPU job") | ||
|
|
There was a problem hiding this comment.
@ArangoGutierrez just a note. There is an issue with the tests uninstalling the plugin between stanzas. This "fixes" them, but we should follow up at some point.
2 participants
This PR propses a more agressive split of the CI steps to reusable workflows. We now have the following high-level workflows:
mainandrelease-*branches (as well as PR copy bot branches)