NO-ISSUE: Trigger jitexecutor-native Github workflow as part of the Kogito Apps weekly job #2052
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
tiagobento
approved these changes
May 16, 2024
tiagobento
changed the title
jstastny-cz
approved these changes
May 21, 2024
rodrigonull
force-pushed
the
trigger-jit-executor-workflow
branch
from
93a3d09 to
5ed5da4
Compare
|
getGitAuthor and getRepoName will always return |
|
Or it returns whatever is configured in the Jenkins job "Configuration"? |
|
It returns what is in the job configuration, which is |
tiagobento
approved these changes
May 21, 2024
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.
This PR is part of the effort for the Apache 10 release and it adds a new trigger for the jitexecutor-native workflow to run as part of the Kogito Apps weekly job.
Depends on: #2049