Difference between revisions of "Fedora/Firefox Repository Setup for Nightly and Beta builds"

From CDOT Wiki
Jump to: navigation, search
Line 19: Line 19:
 
*Armen Zambrano Gasparnian
 
*Armen Zambrano Gasparnian
  
== Project Details ==
+
== Project News ==
  
 +
*  October 12th 2010 Notes
  
== Project Plan ==
+
* BUGZILLA - 600317
  
Goals for each release:
+
lists.fedoraproject.org/mailman/listinfo
* 0.1
 
  
setup any package to be acquired from our repository
+
Problem -->
  
Installing the repository VIA an RPM
+
When you download the nightlies you get a set of source code.  This is inconvenient and adds another step for people to start testing the nighties and Beta versions of the software.
  
* 0.2
+
WE NEED betas to co-exist with the firefox Original working package.
 
 
Manual creation of the SPEC file with the BETA Version to create a functional RPM
 
After tested and satisfied with the results TEST with NIGHTLY Packages
 
     
 
Manual creation of the SPEC file with the NIGHTLY Version to create a functional RPM
 
  
* 0.3
 
  
Automation of the creation of the SPEC File
 
 
== Project News ==
 
 
* Day One Notes - October 8th 2010
 
* Day One Notes - October 8th 2010
 
Project:
 
Project:
Line 79: Line 70:
 
--> Problem --> Getting SELinux to work with the nightlies.
 
--> Problem --> Getting SELinux to work with the nightlies.
  
'''October 12 -'''
 
 
* BUGZILLA - 600317
 
  
lists.fedoraproject.org/mailman/listinfo
 
  
Problem -->
+
== Project Details ==
 
 
When you download the nightlies you get a set of source code.  This is inconvenient and adds another step for people to start testing the nighties and Beta versions of the software.
 
 
 
WE NEED betas to co-exist with the firefox Original working package.
 
 
 
 
 
== Approach to the Problem ==
 
  
 
* Target: Current Fedora releases (right now that's  
 
* Target: Current Fedora releases (right now that's  
Line 132: Line 112:
 
* SELinux - Brett
 
* SELinux - Brett
 
* Desktop integration and testing - Tarinur
 
* Desktop integration and testing - Tarinur
 +
 +
== Project Plan ==
 +
 +
* 0.1 - Proof of concept
 +
 +
Setup any package to be acquired from our repository
 +
Installing the repository VIA an RPM
 +
 +
 +
* 0.2 - Cleaned-up release
 +
 +
Manual creation of the SPEC file with the BETA Version to create a functional RPM
 +
After tested and satisfied with the results TEST with NIGHTLY Packages
 +
 +
* 0.3 - Scripts delivered to Armen

Revision as of 15:20, 6 November 2010

Project Name

Repository Setup for Mozilla Nightlies and Betas - Firefox Versions (4, 3.6)

Project Description

Automating the process of RPM building and repository updates for Fedora systems of different architectures. Architectures such as Firefox (4, 3.6) Beta's and Nightlies.

Project Leader(s)

  • Brett van Gennip
  • Yauheni Khabian (Eugene MIA) If your still around please contact us.
  • Vitalijs Bluzmans
  • Tarinur Choudhury

Project Contributor(s)

  • Chris Tyler
  • Armen Zambrano Gasparnian

Project News

  • October 12th 2010 Notes
  • BUGZILLA - 600317

lists.fedoraproject.org/mailman/listinfo

Problem -->

When you download the nightlies you get a set of source code. This is inconvenient and adds another step for people to start testing the nighties and Beta versions of the software.

WE NEED betas to co-exist with the firefox Original working package.


  • Day One Notes - October 8th 2010

Project: Repository Setup for Mozilla Nightlies and Betas Many web developers want access to the latest Firefox pre-releases, including the nightly builds and beta releases. Mozilla's build team wants to make these accessible as parallel-installable binaries, released through a Fedora-compatible repository. This project involves setting this up.

Subprojects:

  • Build configuration for the RPM files.
  • Repository configuration RPMs.
  • Getting SELinux to work with the nightlies.


Website --> Firefox Nightlies

point 1 install repositories installing a YUM system to grab Point 2 installation of the Repositories point 3 create account on bugzilla

2 repositories for x86 and 64-bit --> producting the rpms

Creating spec files for nightlies ...

pull in nightly build and package

automate it using a script from the website

repository setup -> signing it -->

create the rpm for the repo

seperate nightlies and beta?? AND x86 and 64-bit ??

--> Problem --> Getting SELinux to work with the nightlies.


Project Details

  • Target: Current Fedora releases (right now that's

Approach to packaging:

  1. Pull from a standard URL (as of now http://nightly.mozilla.org/) (armenzg-TODO: get fixed URL to latest)
  2. Package that binary nightly/beta as an RPM
  3. Add to a repository and regenerate/update metadata

Approach to repo access:

  1. Make a repo "release" RPM that provides .repo file and public key

Approach to SELinux:

  1. Modify the RPM packaging to setup SELinux appropriately
    • File labels and policy need to be managed in the RPM package

Installation locations:

  • Must not conflict with distro-provided install locations
  • Should be in the standard path
  • Should start up with a --profile-manager
  • Should appear in the graphical menus, with a different name than the stable release
  • Make appear on the GUI menus - Minefield (Firefox nightly) - Firefox (Developer Preview)

Deployment

  • Deploy on HW in CDOT initially (which machine?)
  • Deliver scripts to Armen for deployment on Mozilla infra

Release Targets

  • 0.1 - Proof of concept
  • 0.2 - Cleaned-up release
  • 0.3 - Scripts delivered to Armen

Division of Labour

  • SPEC file - Tarinur is Taking this responsibility.
  • Repo - Vitaly
  • SELinux - Brett
  • Desktop integration and testing - Tarinur

Project Plan

  • 0.1 - Proof of concept

Setup any package to be acquired from our repository Installing the repository VIA an RPM


  • 0.2 - Cleaned-up release

Manual creation of the SPEC file with the BETA Version to create a functional RPM After tested and satisfied with the results TEST with NIGHTLY Packages

  • 0.3 - Scripts delivered to Armen