jenkinsci / github-pr-comment-build-plugin Goto Github PK
View Code? Open in Web Editor NEWHome Page: https://plugins.jenkins.io/github-pr-comment-build
License: MIT License
Home Page: https://plugins.jenkins.io/github-pr-comment-build
License: MIT License
Relating to #4, is there a way to configure this plugin programmatically, as from the triggers
block?
The use case is that we would like to be able to add new repositories through the automatic scan and not need any on-server manual configuration. Instead, we could place a standard Jenkinsfile in new repositories and have the trigger configured automatically when the scan finds it.
Example: ghprbTriggerAuthorLogin
in ghprb plugin.
Hello! For starters, thank you for the excellent plugin! I've used it to good effect on my team's Jenkins server. I appreciate your work!
I have a comment / suggestion:
I think it would be great if this plugin offered a better way to configure this plugin through the Jobs DSL plugin for a GitHub organization style job.
Unless I'm missing something obvious, I don't see an easy way / dynamic syntax for configuring this plugin via Jobs DSL.
Fortunately, configuring this plugin for a GitHub organization folder is still possible, albeit a little awkward, by using the configure
block to manually add the XML:
organizationFolder('Org') {
organizations {
github {
...
}
}
// configure github-pr-comment-build-plugin
configure { organizationFolder ->
def strategy = organizationFolder << strategy(class: 'jenkins.branch.DefaultBranchPropertyStrategy') {
properties(class: 'java.util.Arrays$ArrayList') {
a(class: 'jenkins.branch.BranchProperty-array') {
"com.adobe.jenkins.github__pr__comment__build.TriggerPRCommentBranchProperty"(plugin :'github-pr-comment-build') {
commentBody('.*Do: Build.*')
}
}
}
}
}
}
Not as nice as first class support, but better than nothing :)
I'm using the github-pr-comment-build-plugin to start a build on Jenkins on a fixed commit pattern. The catch here is that, I need only few users to trigger the build via their comment.
I can't restrict authors on Github as I want all authors to make comments on the PR but only a few authors' comments to trigger the build
The approach I'm trying to use here is by retrieving the author of the comment during the build (that was triggered by the comment), I'll abort/kill the build if the author is not part of the approved list of authors.
Is there a way I can pull the author information using this plugin?
I use Scripted Pipeline.
Thanks for your time!
I installed the plugin, restarted Jenkins, however, the configuration of GitHub Pull Request Comment Build Plugin doesn't show up in Configure page
Jenkins: 2.346.3
OS: Linux - 4.14.326-245.539.amzn2.x86_64
Java: 11.0.16 - Eclipse Adoptium (OpenJDK 64-Bit Server VM)
.....
branch-api:2.1071.v1a_188a_562481
git:4.14.3
git-client:3.13.1
github:1.34.5
github-api:1.303-400.v35c2d8258028
github-branch-source:1696.v3a_7603564d04
github-checks:1.0.19
github-pr-comment-build:96.v9ff13b69dd66
......
OS: Linux - 4.14.326-245.539.amzn2.x86_64
The expected result would be that a build is triggered only in the repository in which the comment was posted
Builds are triggered for every "repository" in Jenkins that matches the PR number which sent the Github event
In the image above, a comment with the expected keyword was posted on first PR in the sw-prj-repo3 repository
Is this the intended behavior?
Jenkins: 2.319.3
OS: Linux - 3.10.0-1160.53.1.el7.x86_64
generic-webhook-trigger:1.83
ghprb:1.36.2
git:4.10.3
git-client:3.11.0
git-server:1.10
github:1.34.2
github-api:1.301-378.v9807bd746da5
github-branch-source:2.11.4
github-pr-comment-build:61.v49f749d31d98
github-scm-trait-notification-context:1.1
.
.
.
pipeline-build-step:2.15
pipeline-github:2.8-138.d766e30bb08b
pipeline-github-lib:36.v4c01db_ca_ed16
pipeline-graph-analysis:188.v3a01e7973f2c
pipeline-input-step:446.vf27b_0b_83500e
pipeline-milestone-step:100.v60a_03cd446e1
pipeline-model-api:1.9.3
pipeline-model-definition:1.9.3
pipeline-model-extensions:1.9.3
pipeline-multibranch-defaults:2.1
pipeline-rest-api:2.21
pipeline-stage-step:291.vf0a8a7aeeb50
pipeline-stage-tags-metadata:1.9.3
pipeline-stage-view:2.21
RHEL 7.9
Multi-branch Job Configuration:
Multi-branch Job build should be triggered if a PR comment matching the regular expression configured is issued
Multi-branch job isn't getting triggered when a comment that matches the configured regular expression is issued, And here is the log,
Calling registerHooks() for test-multi-branch
Feb 20, 2022 12:37:54 PM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run GitHub webhooks activated for job test-multi-branch with [GitHubRepositoryName[host=github.enterprise.com,username=org-name,repository=repo-name]] (events: [PULL_REQUEST, PUSH, PULL_REQUEST_REVIEW, ISSUE_COMMENT])
Feb 20, 2022 12:38:02 PM FINE org.jenkinsci.plugins.github.webhook.WebhookManager repoWithWebhookAccess None of the github repos configured have admin access for: GitHubRepositoryName[host=github.enterprise.com,username=org-name,repository=repo-name]
Feb 20, 2022 12:55:59 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply
Feb 20, 2022 12:57:42 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply
Calling registerHooks() for test-org/repo-name
Feb 20, 2022 12:57:42 PM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run
GitHub webhooks activated for job test-org/repo-name with [GitHubRepositoryName[host=github.ibm.com,username=org-name,repository=repo-name]] (events: [PULL_REQUEST, PUSH, PULL_REQUEST_REVIEW, ISSUE_COMMENT])
Feb 20, 2022 12:57:43 PM FINE org.jenkinsci.plugins.github.webhook.WebhookManager repoWithWebhookAccess
None of the github repos configured have admin access for: GitHubRepositoryName[host=github.ibm.com,username=org-name,repository=repo-name]
No response
I would like only the project members to be able to trigger builds.
However, there is no way to do this with the plugin.
Anyone can make a fork / PR to the project and kick off a build with a PR comment.
Is there any way to restrict this to project members?
Thanks!
No response
Hi there,
I am trying to get this plugin to work, I have jobs configured via the GitHubSCMSource in a declarative pipeline.
While testing, I have setup for it to take any comments to trigger the build via .*
As of right now, I cannot get this to work at all. I guess my main question is if this plugin supports GithubApp authentication?
Is there currently a way to retrieve the content of the comment that started a Jenkins build? It would be useful to have in the case of performing different build steps based on the nature of the comment.
Hey Team,
We are trying to get github comment body to trigger different stages of pipeline using "when" expression and hence need commentbody to check which comment triggered this build ..like "testpr" to run tests, "deploypr" to do deployment, etc.
We have set up a multibranch pipeline and trigger build based on comments by developer.
Pipeline script:
pipeline {
agent { label 'any' }
stages {
stage('Pre-build') {
steps {
script {
dir("${WORKSPACE}") {
script {
echo "${glance_tag}"
echo "${currentBuild.buildCauses}" // [[_class:com.adobe.jenkins.github_pr_comment_build.GitHubPullRequestCommentCause, shortDescription:GitHub pull request comment]]
def buildCauses = currentBuild.buildCauses
echo "$buildCauses.getCommentBody()" // gives null
echo "$buildCauses.getCommentUrl()" // gives null
echo "$buildCauses.shortDescription" // gives GitHub pull request comment
}
}
}
}
}
}
}
Can you please tell me - what I am doing wrong to fetch required information.
Hi.
I am trying to use this plugin, but it triggers the job twice.
I found that SCMSourceOwner has duplicated jobs like
job/name_of_job and job/name_of_job/job/name_of_repository/
Could you fix the duplication? or could you let me know the way to avoid this situation?
Currently we have two options to modify plugin behaviour:
a) Trigger build after specific comment
b) Trugger build after PR is updated
I would like to have option to merge those two options in a following way:
a) User comment Pull Request and Build is triggered. Then this PR is marked
b) Marked PR is then updated automatically every time commit is done
This differ from b) in a way that not every PR is updated but those ones that are previously marked by user - this allows us to remove unnecessary load as we don't want to build all active PRs
When a build is successfully triggered following a supported event, add a thumbs up 👍 emoji to the triggering comment.
When a build was not triggered for some reason, add a thumbs down 👎 emoji to the triggering comment.
Example of how I use custom bots and this plugin:
No response
On removing wild card(*) build is getting trigerred and on having wildcard in the comment body build is not getting trigerred
Please help me with this issue
Hi I don't see much documentation regarding the review option,
i tried to test this by adding a reviewer and having them approve but no job was triggered
https://plugins.jenkins.io/github-pr-comment-build states that I should use version 1.2 with 2.x SCM API-related plugins. However, I couldn't find version 1.2 neither in https://updates.jenkins.io/stable-2.46/update-center.json nor in https://updates.jenkins.io/experimental/update-center.json. Could you publish it, or publish instructions how to install it?
P.S. Since change of dependencies is breaking, it makes sense to increment major version. I.e. release it as 2.0 instead of 1.2.
Use Case :-
I am trying to trigger my pipeline on an issue comment with deploy on dev
in body
Jenkins MultiBranch Pipeline -
Jenkins Shared Library-
triggers { issueCommentTrigger('deploy on dev') }
This prints Build was not started by a trigger -
if (triggerCause) { echo("Build was started by ${triggerCause.userLogin}, who wrote: " + "\"${triggerCause.comment}\", which matches the " + "\"${triggerCause.triggerPattern}\" trigger pattern.") } else { echo('Build was not started by a trigger') }
It is triggering on every Issue comment rather than searching for deploy on dev
. Have tried multiple of things not sure what is wrong`
Would you be open to adding a feature to initiate a build on a pull request review event?
Also, are you accepting pull requests?
Jenkins and plugins versions report:
latest
N/A
Expected result:
Creates a new build in the specific job for the specific pull request
Actual result:
Only trigger the scan with no logs from the plugin.
What this piece of code means? Perhaps is discarded for this reason, but I don't know what SCMSourceOwner implies.
@OverRide
protected boolean isApplicable(Item item) {
if (item != null && item instanceof Job) {
Job project = (Job) item;
if (project.getParent() instanceof SCMSourceOwner) {
SCMSourceOwner owner = (SCMSourceOwner) project.getParent();
for (SCMSource source : owner.getSCMSources()) {
if (source instanceof GitHubSCMSource) {
return true;
}
}
}
}
return false;
}
Hello,
I would like to ask a question if your plugin parses further jobs to run if it finds a match? I have a case where I have two separate jobs which I want to trigger with the same PR comment, but logs show it runs only the first match and does not analyze the rest of them. Is this behavior created by design or this is a bug? I am using Jenkins in ver. 2.332.1, GitHub enterprise server 3.3.7 and GitHub PR Comment Build Version: 78.v2dcf62ba199b.
RHEL 8.5 (Ootpa)
Run n-jobs triggered by the same comment
Run first match
No response
How can I use this plugin in a pipeline script?
Hi,
I am trying to use this plugin in a multibranch pipeline. I have github configured and its working with webhooks on commits in PRs. But it does not seem to work for comments,
Here is my configuration for the pipeline.
I analysed the logs for when I save the configuration. This is what I got
Calling registerHooks() for gateway-sonar
Oct 15, 2019 11:16:16 AM INFO org.jenkinsci.plugins.github.webhook.WebhookManager$1 run
GitHub webhooks activated for job gateway-sonar with [GitHubRepositoryName[host=github.com,username=xxxxx,repository=xxxxxx]] (events: [PULL_REQUEST, PUSH])
Oct 15, 2019 11:16:19 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafe
Replaced hook https://api.github.com/repos/xxxxxx/xxxxxxxx/hooks/149057 (events: [CREATE, DELETE, ISSUE_COMMENT, PULL_REQUEST, PULL_REQUEST_REVIEW, PULL_REQUEST_REVIEW_COMMENT, PUSH])
Oct 15, 2019 11:16:20 AM FINE org.jenkinsci.plugins.github.webhook.WebhookManager$3 applyNullSafe
Created hook https://api.github.com/repos/xxxxxx/xxxxxx/hooks/149090 (events: [CREATE, DELETE, ISSUE_COMMENT, PULL_REQUEST, PULL_REQUEST_REVIEW, PULL_REQUEST_REVIEW_COMMENT, PUSH])
I think here in the logs it should activate the webhooks for ISSUE_COMMENT or PULL_REQUEST_REVIEW_COMMENT which it is not.
Could you please help me find what I am doing wrong?
Hi,
As I was trying to set up the PR comment plugin on my Jenkins setup, I stumbled on the fact that (somewhat related to #20) I didn't get any triggers because I didn't use a "Discover pull request ..." behavior for my project. Instead I was using "Discover branches".
Since it seemed non-obvious to me that there was a hard requirement on the discovery behavior, I think it would be worthwhile to document this in the README file, and maybe add some more logs in that area.
Will you be open to a pull request documenting/logging this fact?
Thanks
No response
A little bit of background:
In my current project, the entire pipeline job is very time-consuming. it has Build + test. So, we decided to run the Build + Test only on specific branches. (This is achieved by "when" syntax). Also, we want to build the pipeline forcefully for a Pull request with a comment/action in the pull request. So, we ended up trying this plugin.
I have tried a few options but still not able to get the build to trigger with PR comment.
This is my Jenkins configuration:
Does it look alright?
I have also set GitHub server in administration
By basic questions:
Given that the logic is probably very similar, can we support the PR build to occur on the addition of a label? That event is sent from GH, but I don't know of any plugins that allow the build to occur when it receives that event.
It would seem that it would be pretty similar to https://github.com/jenkinsci/github-pr-comment-build-plugin/blob/master/src/main/java/com/adobe/jenkins/github_pr_comment_build/IssueCommentGHEventSubscriber.java but just subscribing to a different event action. (created: label, I think)
I'm mentioning this here because it really does seem related, and also makes things foolproof. When users need to type a certain phrase, typos can be a fact of life. Adding one (or more) of a specific predefined label removes some of that concern, and is a great way to differentiate PRs without needing to parse all the (potentially many!) comments, etc. etc.
Is that a github thing? Does the plugin have some definition of "trusted"
Context: I just installed this, think I have it configured, but builds aren't running per my PR comment. I see a section about "untrusted" users and am not sure if my user is trusted or not (which would cause the builds to not be triggered).
https://plugins.jenkins.io/github-pr-comment-build/#plugin-content-untrusted-builds
No response
Jenkins and plugins versions report:
Plugin version - 2.3
Jenkins version - 2.235.1
--
<br class="Apple-interchange-newline">
Paste here
Step 1 - Enable pull request review webhook in github (as mentioned below)
Step 2 - Configure build on pull request review - as shown below
Expected result:
it should trigger a build only once when the pr is approved.
Actual result:
its triggering the build twice everytime when the pr is approved.
I have set up the plugin for a multibranch pipeline. But the pull request comments are not triggering the build.
I was checking the plugin code.
There is a regex variable pullRequestJobNamePattern=Pattern.compile("^PR-" + pullRequestId + "\\b.*$", Pattern.CASE_INSENSITIVE)
It is being used to match with the job name.
https://github.com/jenkinsci/github-pr-comment-build-plugin/blob/master/src/main/java/com/adobe/jenkins/github_pr_comment_build/IssueCommentGHEventSubscriber.java#L136
I need help in understanding why does this pattern have to be matched with the job name. As I could understand, the job name contains pipeline name and branch name concatenated by a slash (pipelineName/jobName). I debugged the code, In my case, this pattern is not being matched and hence pipeline is not being triggered.
Thanks
Could we provide the comment text as a environment variable to the job?
No response
Jenkins Version : CloudBees Jenkins Enterprise 2.249.31.0.5-fixed.
From Jesse Glick: BranchProperty will not suffice for a GH org folder I think. You would need an AbstractFolderProperty<OrganizationFolder>.
Hi guys,
short question, does this plugin also work without webhooks configured? We use GitHub Multibranch pipeline job which periodically checks the repository, see here:
And we have the plugin configured like this:
But issuing a PR comment jenkins retest this
doesn't trigger the build.
The version of Github Branch Source Plugin used is 2.5.4 and PR Comment Build Plugin is 2.1.
I also noticed that in documentation you have this stated:
Please ensure that you have a GitHub server properly connected via the Jenkins configuration, or else the plugin will not operate correctly.
Not sure what you mean by that.
Any help apprecaited!
Thanks
I recently came across this plugin and thought it would be a really useful way to launch different tasks via PR comments. As someone who is not intimately familiar with Jenkins pipeline scripting, it would have been really useful for me to see a short snippet of code showing how I would go about retrieving the comment body from the plugin. Especially since the correct way to retrieve build causes seems to have changed over the years. Not that I even knew that I needed to retrieve build causes when I started. I got there in the end with lots of confused Googling and many many failed builds.
To save other poor souls like me from hours of frustration, please could you put a quick example in the README?
I'm thinking something like this:
script {
def triggerCause = currentBuild.getBuildCauses("com.adobe.jenkins.github_pr_comment_build.GitHubPullRequestCommentCause")
if (triggerCause) {
echo("Author: ${triggerCause.commentAuthor}, Message: " +
"\"${triggerCause.commentBody}\"")
} else {
echo("Build was not started by a PR comment")
}
}
It's quite possible that's wrong, because I (still) don't really know what I'm doing. But you probably get the idea!
No response
Hello!
First of all, thank you for the wonderful plugin, it seems the best (and it seems the only) option for MultiBranch Pipelines that need to be triggered by a comment from the pull request.
However, I can't find a way to retrieve the exact phrase that the build has been triggered with.
I've tried to use currentBuild.rawBuild.causes
and I get an array with a single object [com.adobe.jenkins.github_pr_comment_build.GitHubPullRequestCommentCause@3f698a28]
, but I'm not sure how to proceed further, https://github.com/jenkinsci/github-pr-comment-build-plugin/blob/master/src/main/java/com/adobe/jenkins/github_pr_comment_build/GitHubPullRequestCommentCause.java doesn't seem to have any methods for retrieving the comment body, even getCommentUrl()
method doesn't work. What am I doing wrong?
Ideally, it would be great to have this information already available as environment variable, similar to CHANGE_ID
, CHANGE_AUTHOR
and others.
Jenkins: [CloudBees CI Managed Controller 2.346.2.3-rolling](https://release-notes.cloudbees.com/product/141)
github-pr-comment-build version: 78.v2dcf62ba199b
Linux, Agents are all Kubernetes agents
61.v49f749d31d98
version of plugin78.v2dcf62ba199b
The plugin is expected to be working as before, triggering all the jobs that are matching the criteria of jobs that are configured to be kicked of for a PR comment
Triggering only the first job from the list of jobs configured to run on a single PR comment
This is working as expected in the older version: 61.v49f749d31d98
After we have upgraded to the new version: 78.v2dcf62ba199b
this functionality seems to be broken
I suspect, this is broken because of #48
Paste the output here
doesn't matter
execute webhoow to a multi-source job
works
excetion is thrown
No response
For private repositories people with Read
role (aka pull permission) are seen as collaborators by the GitHub API. This means, they are able to trigger builds.
In addition it would be great if there was a way to only trust users with admin permission. This way people with push permission could still collaborate on the same branches of a repo, but sensitive builds could only be triggered by authorized people.
Jenkins: 2.361.1.2
OS: Linux - 5.4.219-126.411.amzn2.x86_64
Java: 11.0.16.1 - Red Hat, Inc. (OpenJDK 64-Bit Server VM)
---
Parameterized-Remote-Trigger:3.1.6.3
ace-editor:1.1
analysis-model-api:10.16.0
antisamy-markup-formatter:2.7
apache-httpcomponents-client-4-api:4.5.13-138.v4e7d9a_7b_a_e61
async-http-client:1.7.24.3
authentication-tokens:1.4
aws-credentials:191.vcb_f183ce58b_9
aws-java-sdk:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-cloudformation:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-codebuild:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-ec2:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-ecr:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-ecs:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-efs:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-elasticbeanstalk:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-iam:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-logs:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-minimal:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-sns:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-sqs:1.12.287-357.vf82d85a_6eefd
aws-java-sdk-ssm:1.12.287-357.vf82d85a_6eefd
aws-parameter-store:1.2.2
basic-branch-build-strategies:71.vc1421f89888e
blueocean:1.25.8
blueocean-autofavorite:1.2.5
blueocean-bitbucket-pipeline:1.25.8
blueocean-commons:1.25.8
blueocean-config:1.25.8
blueocean-core-js:1.25.8
blueocean-dashboard:1.25.8
blueocean-display-url:2.4.1
blueocean-events:1.25.8
blueocean-git-pipeline:1.25.8
blueocean-github-pipeline:1.25.8
blueocean-i18n:1.25.8
blueocean-jira:1.25.8
blueocean-jwt:1.25.8
blueocean-personalization:1.25.8
blueocean-pipeline-api-impl:1.25.8
blueocean-pipeline-editor:1.25.8
blueocean-pipeline-scm-api:1.25.8
blueocean-rest:1.25.8
blueocean-rest-impl:1.25.8
blueocean-web:1.25.8
bluesteel-master:1.2.49
bootstrap4-api:4.6.0-5
bootstrap5-api:5.2.0-1
bouncycastle-api:2.26
branch-api:2.1046.v0ca_37783ecc5
build-name-setter:2.2.1
build-timestamp:1.0.3
build-token-root:151.va_e52fe3215fc
build-user-vars-plugin:1.9
caffeine-api:2.9.3-65.v6a_47d0f4d1fe
checks-api:1.7.5
cloudbees-administrative-monitors:1.0.5
cloudbees-analytics:1.42
cloudbees-assurance:2.276.0.23
cloudbees-aws-cli:1.5.20
cloudbees-bitbucket-branch-source:785.ve724eb_44e286
cloudbees-blueocean-default-theme:0.8
cloudbees-cloudfoundry-cli:2.1.10
cloudbees-folder:6.740.ve4f4ffa_dea_54
cloudbees-folders-plus:3.28
cloudbees-jsync-archiver:5.23
cloudbees-license:9.68
cloudbees-monitoring:2.15
cloudbees-nodes-plus:1.24
cloudbees-platform-common:1.18
cloudbees-platform-data:1.29
cloudbees-plugin-usage:2.17
cloudbees-quiet-start:1.8
cloudbees-slack:1.20
cloudbees-ssh-slaves:2.18
cloudbees-support:3.29
cloudbees-template:4.57
cloudbees-uc-data-api:4.50
cloudbees-unified-ui:1.22
cloudbees-workflow-template:3.18
command-launcher:84.v4a_97f2027398
commons-lang3-api:3.12.0-36.vd97de6465d5b_
commons-text-api:1.9-19.v8df45c678366
conditional-buildstep:1.4.2
config-file-provider:3.11.1
credentials:1129.vef26f5df883c
credentials-binding:523.vd859a_4b_122e6
data-tables-api:1.12.1-2
depgraph-view:1.0.5
disable-github-multibranch-status:1.2
display-url-api:2.3.6
docker-commons:1.21
docker-workflow:521.v1a_a_dd2073b_2e
durable-task:501.ve5d4fc08b0be
ec2:2.0.1
echarts-api:5.3.3-1
email-ext:2.91
envinject:2.901.v0038b_6471582
envinject-api:1.199.v3ce31253ed13
favorite:2.4.1
file-operations:1.11
font-awesome-api:6.1.2-1
forensics-api:1.15.1
form-element-path:1.12
generic-webhook-trigger:1.86.3
git:4.11.5
git-client:3.11.2
git-server:99.va_0826a_b_cdfa_d
github:1.35.0
github-api:1.303-400.v35c2d8258028
github-branch-source:1677.v731f745ea_0cf
github-oauth:0.39
github-organization-folder:1.6
github-pr-comment-build:96.v9ff13b69dd66
google-oauth-plugin:1.0.6
gradle:1.39.4
h2-api:1.4.199
handlebars:3.0.8
handy-uri-templates-2-api:2.1.8-22.v77d5b_75e6953
htmlpublisher:1.30
http_request:1.16
icon-shim:3.0.0
infradna-backup:3.38.55
instance-identity:116.vf8f487400980
jackson2-api:2.13.4.20221013-295.v8e29ea_354141
jakarta-activation-api:2.0.1-1
jakarta-mail-api:2.0.1-1
javadoc:226.v71211feb_e7e9
javax-activation-api:1.2.0-4
javax-mail-api:1.6.2-7
jaxb:2.3.6-1
jdk-tool:55.v1b_32b_6ca_f9ca
jenkins-design-language:1.25.8
jira:3.7.1
jjwt-api:0.11.5-77.v646c772fddb_0
jquery3-api:3.6.0-4
jsch:0.1.55.61.va_e9ee26616e7
junit:1119.1121.vc43d0fc45561
kube-agent-management:1.1.56
kubernetes:3697.v771155683e38
kubernetes-client-api:5.12.2-193.v26a_6078f65a_9
kubernetes-credentials:0.9.0
ldap:2.12
lockable-resources:2.18
mailer:438.v02c7f0a_12fa_4
mapdb-api:1.0.9-28.vf251ce40855d
matrix-auth:3.1.5
matrix-project:772.v494f19991984
maven-plugin:3.19
mercurial:1260.vdfb_723cdcc81
metrics:4.2.10-389.v93143621b_050
mina-sshd-api-common:2.8.0-36.v8e25ce90d4b_1
mina-sshd-api-core:2.8.0-36.v8e25ce90d4b_1
momentjs:1.1.1
multibranch-build-strategy-extension:1.0.10
nectar-license:8.41
nectar-rbac:5.76
node-iterator-api:49.v58a_8b_35f8363
nodejs:1.5.1
oauth-credentials:0.5
okhttp-api:4.9.2-20211102
openshift-cli:1.11
operations-center-agent:2.361.0.1
operations-center-analytics-config:2.222.0.1
operations-center-analytics-reporter:2.222.0.1
operations-center-client:2.361.0.1
operations-center-cloud:2.361.0.2
operations-center-context:2.361.0.1
parameterized-trigger:2.45
pipeline-aws:1.43
pipeline-build-step:2.18
pipeline-github:2.8-141.7e985db66f30
pipeline-github-lib:38.v445716ea_edda_
pipeline-graph-analysis:195.v5812d95a_a_2f9
pipeline-groovy-lib:612.v84da_9c54906d
pipeline-input-step:456.vd8a_957db_5b_e9
pipeline-maven:1205.vceea_7b_972817
pipeline-milestone-step:101.vd572fef9d926
pipeline-model-api:2.2114.v2654ca_721309
pipeline-model-declarative-agent:1.1.1
pipeline-model-definition:2.2114.v2654ca_721309
pipeline-model-extensions:2.2114.v2654ca_721309
pipeline-rest-api:2.24
pipeline-stage-step:296.v5f6908f017a_5
pipeline-stage-tags-metadata:2.2114.v2654ca_721309
pipeline-stage-view:2.24
pipeline-utility-steps:2.15.0
plain-credentials:139.ved2b_9cf7587b
plugin-util-api:2.17.0
popper-api:1.16.1-3
popper2-api:2.11.5-2
preSCMbuildstep:36.vca_61785795a_2
prism-api:1.28.0-2
pubsub-light:1.17
resource-disposer:0.20
run-condition:1.5
saml:2.333.vc81e525974a_c
scm-api:621.vda_a_b_055e58f7
script-security:1175.v4b_d517d6db_f0
slack:631.v40deea_40323b
snakeyaml-api:1.31-84.ve43da_fb_49d0b
sse-gateway:1.26
ssh-credentials:291.v8211e4f8efb_c
sshd:3.249.v2dc2ea_416e33
structs:324.va_f5d6774f3a_d
support-core:1204.v7ee88742a_53f
timestamper:1.18
token-macro:308.v4f2b_ed62b_b_16
trilead-api:2.72.v2a_3236754f73
unique-id:2.2.1
user-activity-monitoring:1.8
variant:59.vf075fe829ccb
warnings-ng:9.18.0
wikitext:3.15
windows-slaves:1.8.1
workflow-aggregator:590.v6a_d052e5a_a_b_5
workflow-api:1192.v2d0deb_19d212
workflow-basic-steps:994.vd57e3ca_46d24
workflow-cps:2759.v87459c4eea_ca_
workflow-cps-checkpoint:2.13
workflow-cps-global-lib:588.v576c103a_ff86
workflow-durable-task-step:1199.v02b_9244f8064
workflow-job:1207.ve6191ff089f8
workflow-multibranch:716.vc692a_e52371b_
workflow-scm-step:400.v6b_89a_1317c9a_
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:838.va_3a_087b_4055b
ws-cleanup:0.43
This is running in a Kubernetes deployment. The controller itself is running:
NAME="Red Hat Enterprise Linux"
VERSION="8.6 (Ootpa)"
I expect that the pipeline will be triggered when commenting on the pull request. An issue appears to be created when the job is added and removed to the multibranch pipeline.
The job is not triggered.
No response
No response
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.