build: add workflow to explicitly trigger Jenkins #56
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
paullatzelsperger
force-pushed
the
build/2234_trigger_jenkins_from_actions
branch
2 times, most recently
from
bceb4a4
to
e90ffe0
Compare
wolf4ood
approved these changes
Nov 24, 2022
paullatzelsperger
force-pushed
the
build/2234_trigger_jenkins_from_actions
branch
from
e90ffe0
to
0639720
Compare
paullatzelsperger
deleted the
build/2234_trigger_jenkins_from_actions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
Explicitly triggers Jenkins on every build on the
mainbranch.Why it does that
more reactive build
Further notes
.
Linked Issue(s)
Partly resolves eclipse-edc/Connector#2234
Checklist
no-changelog)