Project

General

Profile

Actions
Copy link

Bug #1919

closed

Jenkins: ABORTED when publishing draft patchset

Added by Junxiao Shi about 11 years ago. Updated almost 9 years ago.

Status:
Abandoned
Priority:
Low
Assignee:
-
Category:
Base
Target version:
-
Start date:
08/23/2014
Due date:
% Done:

0%

Estimated time:

Description

Steps to reproduce:

  1. push a patchset to refs/drafts/* branch
  2. wait for Jenkins to start the build job
  3. click Publish on the patchset

Expected: build job continues

Actual: build job is aborted, and a new build job for the same patchset is created

Actions
Copy link
 #1

Updated by Alex Afanasyev about 11 years ago

I doubt it is solvable without any changes in jenkins plugin itself. Any specific reason to use "drafts" and not normal patchsets?

Actions
Copy link
 #2

Updated by Junxiao Shi about 11 years ago

A draft patchset is useful for the Change Owner to review the patchset, before allowing others to review.

To fix this bug, either allow the build job to continue, or don't build a draft patchset until it's published.

If neither is possible without changing the plugin, file a feature request on the plugin's site, and let this Bug block on that feature request.

Actions
Copy link
 #3

Updated by Junxiao Shi about 11 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

The Bug disappeared on its own as of Oct 12. There wasn't any system upgrades or configuration changes.

If no new occurrence is observed in 7 days, this Bug can close.

Actions
Copy link
 #4

Updated by Junxiao Shi almost 11 years ago

  • Status changed from Resolved to Closed
Actions
Copy link
 #5

Updated by Junxiao Shi almost 11 years ago

  • Project changed from NFD to ndn-cxx
  • Category changed from Build to Base
  • Status changed from Closed to New
  • Target version deleted (v0.3)
  • % Done changed from 100 to 0

Reopening this Bug in ndn-cxx, because it appears again in ndn-cxx.

I suspect there's some configuration difference between ndn-cxx and NFD: NFD does not build a draft patchset until it's published, but ndn-cxx builds draft patchsets.

Build 1482 is triggered by a draft patchset.

When the draft patchset is published, 1482 is aborted and a new Build 1483 is triggered.

Actions
Copy link
 #6

Updated by Alex Afanasyev almost 11 years ago

I don't see a difference in configuration. Both configs has two triggers: draft published and patchset submitted.

WHy are you worrying about building of a draft?

Actions
Copy link
 #7

Updated by Junxiao Shi almost 11 years ago

Try delete "draft published" and see how it goes.

Building twice wastes resources, and posts "Verified-1" message which makes Change Owner worry.

Actions
Copy link
 #8

Updated by Yi Huang almost 11 years ago

I downloaded config file in xml format from Jenkins. And I get <triggers> node from both config file. Basically there is no difference between them except the name of project.

yi-osx:jenkins yihuang$ diff NFD-trigger.xml ndn-cxx-trigger.xml
7c7
<         <pattern>NFD</pattern>
---
>         <pattern>ndn-cxx</pattern>
Actions
Copy link
 #9

Updated by Alex Afanasyev almost 11 years ago

  • Assignee deleted (Yi Huang)

Nobody is working on this issue and it is not known what needs to be done. I would abandon this task.

Actions
Copy link
 #10

Updated by Alex Afanasyev almost 9 years ago

  • Status changed from New to Abandoned
Actions
Copy link

Also available in: Atom PDF