updates builder shouldn't fail when config files have been bumped



8 years ago
3 years ago


(Reporter: bhearsum, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [releases][automation])

the updates builder currently fails if it has no update verify bumping to do. as long as the update-verify-bump.pl script exited successfully, it should continue even if there's onthing to commit. I think we can do this by:
- setting flunkOnFailure/haltOnFailure=True for the bumping
- setting haltOnFailure=False for the commit/push

Not sure what to do about the builder turning red still in those cases. Maybe we need to use doStepIf?


8 years ago
Blocks: 627271
Whiteboard: [releases][automation]
Priority: -- → P4
Hardware: x86_64 → All
Mass move of bugs to Release Automation component.
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: 714371
Duplicate of this bug: 746607
This is a bit tougher than I thought because a) there's no way I can find to create a commit without any changes on a modern hg, and b) "hg push" returns non-zero when there's nothing to push.

The best I can come up with is adding supporting for skipping bumping when a certain property is set. This isn't quite as good, because it means you need to know upfront that there won't be any changes necessary, but it's better than the current state. (Worst case scenario, you try rerunning updates, it fails because it didn't bump anything, you rerun it again with the property set). To implement this, we need to:
* Add a method that checks to see if "skipBump" exists (see https://github.com/mozilla/buildbotcustom/blob/master/process/factory.py#L2224 for a similar method), and returns False if it does.
* Pass that method to all of the BuildStep's in the bumpConfigs method: https://github.com/mozilla/buildbotcustom/blob/72d08bd748b9d71a85a1fbef2e0a06b1d488824b/process/factory.py#L4187
Product: mozilla.org → Release Engineering

Comment 4

3 years ago
fixed in release promotion
Last Resolved: 3 years ago
QA Contact: bhearsum
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.