Opened on 05/02/2014 at 06:29:44 AM

Closed on 05/02/2014 at 11:23:33 AM

#412 closed change (fixed)

Make sure release automation creates Safari builds

Reported by: trev Assignee: trev
Priority: P2 Milestone:
Module: Automation Keywords:
Cc: sebastian Blocked By:
Blocking: Platform:
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):



Currently the Chrome release automation will only create Chrome and Opera builds. As we want to release for Safari from the same repository and at the same time, it should create a Safari build as well.

What to change

Allow specifying multiple certificates in the -k parameter of the release command (different certificates will be used to sign Opera and Safari builds). Produce Safari builds and put them into the downloads repository as well.

Attachments (0)

Change History (2)

comment:1 Changed on 05/02/2014 at 07:12:13 AM by trev

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:2 Changed on 05/02/2014 at 11:23:33 AM by trev

  • Resolution set to fixed
  • Status changed from reviewing to closed

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from trev.
Note: See TracTickets for help on using tickets.