Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: blueocean-plugin, github-plugin
-
Environment:blue-ocean 1.21, jenkins 2.190.3,
GitHub API Plugin 1.95
OS: ubuntu server 18.04.3 LTS
-
Similar Issues:
Description
We use Jenkins + Blue Ocean to build our open-source projects that hosted on GitHub. Sometimes we observe very strange behavior. When we push a commit into GitHub repo, Jenkins triggers several hundreds of the same builds for this commit.
You can see it here:
http://jenkins.asneg.de:8080/blue/organizations/jenkins/OpcUaWebServer/activity?branch=master
Attachments
Activity
Aleksey Timin
created issue -
Aleksey Timin
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
We use Jenkins + Blue Ocean to build our open-source project that hosted on GitHub. Sometimes we observe very strange behavior. When we push a commit into GitHub repo, Jenkins triggered several hundreds of the same builds for this commit. You can see it here: http://jenkins.asneg.de:8080/blue/organizations/jenkins/OpcUaWebServer/activity?branch=master |
We use Jenkins + Blue Ocean to build our open-source projects that hosted on GitHub. Sometimes we observe very strange behavior. When we push a commit into GitHub repo, Jenkins triggers several hundreds of the same builds for this commit. You can see it here: [http://jenkins.asneg.de:8080/blue/organizations/jenkins/OpcUaWebServer/activity?branch=master] |