Skip to content
This repository has been archived by the owner on Feb 2, 2019. It is now read-only.

Bug 1343990 - add Fennec Release Graph 2. #219

Merged
merged 6 commits into from Mar 9, 2017

Conversation

MihaiTabara
Copy link
Contributor

@MihaiTabara MihaiTabara commented Mar 3, 2017

@rail @escapewindow @kmoir
Few observations:

  1. Shouldn't we split the release configs into "beta" and "release" or some sort? I know we're dealing with beta only now, but it'd be worth renaming those to "beta" and copy-paste later to obtain the "release" ones.

  2. I think it'd be worth chaining the checksum builder in the second graph. Currently, "push-to-releases" depends on it. We can either remove that dep or enable checksums within the second graph.

  3. I filed bugs against 1343990 to mark the changes we need to make in the second graph builders to make them work. However, right now we only need the push-to-releases builder which works fine. The rest of them can be disabled and/or run manually.

@MihaiTabara MihaiTabara self-assigned this Mar 3, 2017
@MihaiTabara MihaiTabara requested review from rail, escapewindow and kmoir and removed request for kmoir March 3, 2017 18:22
Copy link
Contributor

@escapewindow escapewindow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-expert stamp

Copy link
Contributor

@rail rail left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In overall it looks great, just a couple of issues. Almost there!


product: "fennec"
product: "mobile"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmmm, we don't usually use "mobile" for product, it's either stage_product or appName, see https://hg.mozilla.org/build/buildbot-configs/file/tip/mozilla/release-fennec-mozilla-release.py.template#l19. I'm not sure where it is used in the graph, but I'd check it. This also applies to the file renames.

-
taskId: "{{ stableSlugId(buildername) }}"
requires:
- "{{ stableSlugId('publish_release_human_decision') }}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather make this dependent on push to cdns. If push to cdns fails, we shouldn't update the bouncer aliases.

-
taskId: "{{ stableSlugId(buildername) }}"
requires:
- "{{ stableSlugId('publish_release_human_decision') }}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the same here, cdns first, then the rest

-
taskId: "{{ stableSlugId(buildername) }}"
requires:
- "{{ stableSlugId('publish_release_human_decision') }}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here, cdns first

@MihaiTabara MihaiTabara requested a review from rail March 8, 2017 17:45
@MihaiTabara
Copy link
Contributor Author

@rail Thanks again for the suggestions - I revisited my patch and was able to improve the things a bit at a second round. So here we go:

  • standardized the namings of the builders to {}-{}-_something_something
  • killed off the human decision task as it's no longer needed - all the post-release are now chained to push-to-mirrors
  • chained the post-release tasks to the push-to-releases
  • fixed tests
  • reverted the naming to address your comment. You were right, the only place I needed the stage_product was in the push-candidates-to-releases script so it knows to query the right S3 path. I've added the configs both in these release configs and in the tools repo 👍 See bug for more 1343990 details

@@ -0,0 +1,45 @@
{% set buildername = "release-{}-{}_version_bump".format(branch, product) %}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have we changed the script to make sure we don't downgrade the version? It shouldn't be too hard.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The script itself you mean? Am not sure yet. The builder is set to False anyway until I add the necessary configs within mozharness and buildbot-configs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I merge and address this later when I deal with postrelease builders anyway or should I look into it now?

@rail rail merged commit 823d0d1 into mozilla-releng:master Mar 9, 2017
@rail
Copy link
Contributor

rail commented Mar 9, 2017

Merged!

@MihaiTabara MihaiTabara deleted the 1343990 branch March 9, 2017 12:57
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
3 participants