Closed Bug 1378454 Opened 7 years ago Closed 7 years ago

Add predictable routes to repackage and repackage-signing tasks

Categories

(Release Engineering :: General, enhancement)

enhancement
Not set
normal

Tracking

(firefox56 fixed)

RESOLVED FIXED
Tracking Status
firefox56 --- fixed

People

(Reporter: rail, Assigned: rail)

References

Details

Attachments

(1 file, 1 obsolete file)

So we can find them as part of release promotion.
Blocks: 1354597
Attached patch routes.diff (obsolete) — Splinter Review
Not sure if this is the best approach. I don't really like the fact that I have copy-paste functions in 2 files :/
Attachment #8884041 - Flags: feedback?(bugspam.Callek)
Comment on attachment 8884041 [details] [diff] [review]
routes.diff

Review of attachment 8884041 [details] [diff] [review]:
-----------------------------------------------------------------

Kind of ugly, but I won't nitpick too much in our efforts to get these routes added. Mostly because I don't have a good alternate solution in mind atm.

::: taskcluster/taskgraph/transforms/task.py
@@ +98,5 @@
>          'job-name': basestring,
>  
>          # Type of gecko v2 index to use
> +        'type': Any('generic', 'nightly', 'l10n', 'nightly-with-multi-l10n',
> +                    'repackage', 'repackage-signing'),

no repackage-signing below, and not used elsewhere.
Attachment #8884041 - Flags: feedback?(bugspam.Callek) → feedback+
Attachment #8884041 - Attachment is obsolete: true
Comment on attachment 8884346 [details]
Bug 1378454 - Add predictable routes to repackage and repackage-signing tasks

https://reviewboard.mozilla.org/r/155270/#review160350

Some minor commentary here.

::: taskcluster/docs/attributes.rst:167
(Diff revision 2)
>  Signals that the output of this task contains signed artifacts.
> +
> +repackage_type
> +==============
> +This is the type of repackage. Can be ``repackage`` or 
> +``repacakge_signing``.

can we just use 'signed' here? (or does `repackage` emit signed?)

::: taskcluster/taskgraph/transforms/repackage_routes.py:23
(Diff revision 2)
> +def validate(config, jobs):
> +    for job in jobs:
> +        label = job['label']
> +        yield validate_schema(
> +            job_description_schema, job,
> +            "In repackage-signing ({!r} kind) task for {!r}:".format(config.kind, label))

repackage passes to `job` but repackage_signing passes directly to `task`, so I'm not sure the latter would validate as a job.
Attachment #8884346 - Flags: review?(bugspam.Callek) → review+
(In reply to Justin Wood (:Callek) from comment #5)
> > +repackage_type
> > +==============
> > +This is the type of repackage. Can be ``repackage`` or 
> > +``repacakge_signing``.
> 
> can we just use 'signed' here? (or does `repackage` emit signed?)

It depends. Some pieces are signed (dmg) and some are not (setup.exe). This is why I didn't reuse the "signed" attribute.

 
> ::: taskcluster/taskgraph/transforms/repackage_routes.py:23
> (Diff revision 2)
> > +def validate(config, jobs):
> > +    for job in jobs:
> > +        label = job['label']
> > +        yield validate_schema(
> > +            job_description_schema, job,
> > +            "In repackage-signing ({!r} kind) task for {!r}:".format(config.kind, label))
> 
> repackage passes to `job` but repackage_signing passes directly to `task`,
> so I'm not sure the latter would validate as a job.

I think they both yield `job` at the end, even though they are called `task`. It works somehow. :)
We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again.

hg error in cmd: hg rebase -s 5d540400c15c -d 407df61a6300: rebasing 405856:5d540400c15c "Bug 1378454 - Add predictable routes to repackage and repackage-signing tasks r=Callek" (tip)
merging taskcluster/ci/repackage-signing/kind.yml
merging taskcluster/ci/repackage/kind.yml
merging taskcluster/docs/attributes.rst
merging taskcluster/taskgraph/transforms/gecko_v2_whitelist.py
merging taskcluster/taskgraph/transforms/repackage.py
merging taskcluster/taskgraph/transforms/repackage_signing.py
merging taskcluster/taskgraph/transforms/task.py
warning: conflicts while merging taskcluster/taskgraph/transforms/repackage.py! (edit, then use 'hg resolve --mark')
warning: conflicts while merging taskcluster/taskgraph/transforms/repackage_signing.py! (edit, then use 'hg resolve --mark')
unresolved conflicts (see hg resolve, then hg rebase --continue)
Pushed by raliiev@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/441e4152c4b3
Add predictable routes to repackage and repackage-signing tasks r=Callek
Comment on attachment 8884346 [details]
Bug 1378454 - Add predictable routes to repackage and repackage-signing tasks

https://hg.mozilla.org/integration/mozilla-inbound/rev/441e4152c4b30c7b066edeeacbddf85852ad22ad
Attachment #8884346 - Flags: checked-in+
https://hg.mozilla.org/mozilla-central/rev/441e4152c4b3
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: