Skip to content

Conversation

@gabrielbusta
Copy link
Contributor

This is hypothetical - but we definitely need a new ShipIt feature / framework to do something like this.

return []

def construct_name(self, attributes):
return f"merges-{attributes['version']}"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I can sort of imagine a workflow called "merges-125" but I am speculating (a lot)

- bump-central # bumps the nightly version and sends a notification.
# - bump-esr-VERSION # not sure what to do about this one yet, but we can probably read HGMO and figure out the ESR bump steps? That data is here https://searchfox.org/mozilla-central/rev/38377227b8f96fda8f418db614e6a8aa67d01c31/taskcluster/config.yml#615-627
# - update-wiki # I don't know if this is feasible any more :/ see Bug 1414278: https://bugzilla.mozilla.org/show_bug.cgi?id=1414278 can the wiki read dynamic data?
- update-shipit # This part is about updating the nightly version and release dates in shipit. To accomplish this we need to modify the app so updating these doesn't require a deployment. Maybe we can store them in a table and create APIs to manage the data.
Copy link
Contributor Author

Choose a reason for hiding this comment

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

update ShipIt/rebuild product details could be 1 step.

@gabrielbusta
Copy link
Contributor Author

#1418

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants