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

From CDOT Wiki
Jump to: navigation, search
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Project Name ==
 
== Project Name ==
  
Repository Setup for Mozilla Nightlies and Betas - Firefox Versions (4, 3.6)
+
Repository Setup for Mozilla Nightly and Beta builds
  
 
== Project Description ==
 
== 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.
+
Automating the process of RPM building and repository updates for 32 Bit and 64 Bit Firefox beta and nightly builds on Fedora systems.
  
== Project Leader(s) ==
+
== Project Leaders ==
  
*Brett van Gennip
+
*Brett van Gennip - bvangennip@learn.senecac.on.ca
*Yauheni Khabian (Eugene MIA) If your still around please contact us.
+
*<s>Eugene Khabian</s> - Removed
*Vitalijs Bluzmans
+
*Vitalijs Bluzmans - vbluzmans@learn.senecac.on.ca
*Tarinur Choudhury
+
*Tarinur Choudhury - trchoudhury@learn.senecac.on.ca
 +
 
 +
== Responsibilities ==
 +
 
 +
* SPEC File Formation & Desktop Integration - Tarinur
 +
* Repository Configuration - Vitaly
 +
* Testing Minefield with SELinux and Fedora 13  - Brett
  
 
== Project Contributor(s) ==
 
== Project Contributor(s) ==
Line 21: Line 27:
 
== Project Details ==
 
== Project Details ==
  
point 1
+
* Target: Current supported Fedora releases (Fedora 13 and Fedora 14)
- install repositories
 
- installing a YUM system to grab
 
  
 +
Approach to packaging:
 +
# Pull from a standard URL (as of now http://nightly.mozilla.org/)
 +
# Package that binary nightly/beta as an RPM
 +
# Add to a repository and regenerate/update metadata
  
Point 2
+
Approach to repo access:
- installation of the Repositories
+
# Make a repo "release" RPM that provides .repo file and public key
  
 +
Approach to SELinux:
 +
# Modify the RPM packaging to setup SELinux appropriately
 +
#* File labels and policy need to be managed in the RPM package
  
point 3
+
Installation locations:
- create account on bugzilla
+
* 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)
  
== Project Plan ==
+
== Deployment ==
  
Goals for each release:
+
* Deploy on HW in CDOT initially (Chile)
* 0.1
+
* Deliver scripts to Armen for deployment on Mozilla infrastructure
  
setup any package to be acquired from our repository
+
== Release Targets ==
  
Installing the repository VIA an RPM
+
* 0.1 - Proof of concept
 +
* 0.2 - Cleaned-up release
 +
* 0.3 - Scripts delivered to Armen
  
* 0.2
+
== Project Plan ==
  
Manual creation of the SPEC file with the BETA Version to create a functional RPM
+
* 0.1 - Proof of concept
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
+
Fully working proof of concept including early mock up of nightly RPM and repository installation RPM.
  
Automation of the creation of the SPEC File
+
=== Progress made on 0.1 Milestone ===
  
== Project News ==
+
Please see our latest blog posts on the status of milestone 0.1. This wiki will feature a brief overview of how the project is progressing.
* 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:
+
==== Brett van Gennip - Testing Minefield with SELinux and Fedora 13 ====
  
* Build configuration for the RPM files.  
+
Brett had downloaded Minefield and attempted to replicate the error message that was coming up for people.  Overall, he had no success making the error message show up which proved to be a bit of an issue to how he can understand the issue. Certain things came up such as: while running firefox, Minefield would not open. While running Minefield, firefox would not open.  At no point was he able to run both at the same time.  Overall, he plans to speak with people on IRC to try to make some sense of these issues.  
* Repository configuration RPMs.
 
* Getting SELinux to work with the nightlies.  
 
  
 +
Please see blog for more details:
  
Website -->  [http://nightly.mozilla.org/ Firefox Nightlies]
+
[http://brettvangennip.wordpress.com/2010/11/05/0-1-repository-setup-for-firefox-nightly-and-betas/ Minefield and Firefox]
  
point 1 install repositories
+
==== Tarin - RPM Building and Repository Setup ====
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 -->
+
Tarin had setup the Repository and made it so that you are able to download the nightly via iraq.proximity.on.ca repository. He has also packaged the nightlies in an RPM format.  Which means that he has created a SPEC file for the RPM to work with Fedora 1x machines in both 32 bit and 64 bit architectures.  Our repository is located at [http://iraq.proximity.on.ca/ffrepo/ Nightly Repository].
producting the rpms
 
  
Creating spec files for nightlies ...
+
Please see blog for more details:
  
pull in nightly build and package
+
[http://tarinc.wordpress.com/2010/11/05/milestone-1-continued/ Milestone 1 Continued]
 
automate it using a script from the website
 
  
repository setup -> signing it -->
+
==== Vitaly - Building Firefox/Fedora Repository ====
  
create the rpm for the repo
+
Vitaly had setup the Repository on one of the servers in Seneca's open source room locations.  He had proceeded in creating a script that will automate the process of setting up the repo's into the directory for which they are to be downloaded from.
  
seperate nightlies and beta??  AND x86 and 64-bit ??
+
Our repository is located at [http://iraq.proximity.on.ca/ffrepo/ Nightly Repository].
  
--> Problem --> Getting SELinux to work with the nightlies.
+
Please see blog for more details:
  
'''October 12 -'''
+
[http://vbluzmans.wordpress.com/2010/11/05/in-quest-of-building-firefoxfedora-repository/ Building Firefox/Fedora Repo]
  
* BUGZILLA - 600317
+
* 0.2 - Cleaned-up release
  
lists.fedoraproject.org/mailman/listinfo
+
Finalize spec files and implement automation.
  
Problem -->
+
=== Progress made on 0.2 Milestone ===
  
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.
+
Please see our latest blog posts on the status of milestone 0.2.  This wiki will feature a brief overview of how the project is progressing.
  
WE NEED betas to co-exist with the firefox Original working package.
+
==== Tarin ====
 +
[http://tarinc.wordpress.com/2010/11/25/release-0-2-update/ Release 0.2 Update]
  
Solution -->
+
* 0.3 - Scripts delivered to Armen
  
Add a system (RPM and Repository Setup) for streamlined setup for users to test the firefox software Nightlies and Betas.
+
=== Progress made on 0.3 Milestone ===
  
'''project plan'''
+
Please see our latest blog posts on the status of milestone 0.3.  This wiki will feature a brief overview of how the project is progressing.
  
what we need to learn -
+
== Project News ==
  
    --> REPOSITORY SETUP - WHAT IS IT ?HOW DO WE SET IT UP
+
''' November 12th, 2010 '''
    --> SPEC FILE CREATION FOR THE NIGHLTLIES
 
    --> SELINUX <-- HOW IT WORKS AND HOW WE CAN
 
  
resources --
+
- EUGENE IS Back -
  
    --> EBOOK
+
STATUS:
    --> WIKI
 
    --> PLANETS
 
        --> FIND PEOPLE THAT MAY BE OF HELP OF SELINUX
 
  
* Milestone 1 -
+
(BRETT)
 
 
    -> setup any package to be acquired from our repository
 
  
* Milestone 2 - RPM Fusion -- a separate reposit
+
setup a different profile for
  
    ->installing the repository VIA an RPM
+
That i run firefox and minefield together the way i just describe it.
  
 +
what does he want ?  can we do it or is the builders Responsibility to figure it out...  or does it even matter
  
* Milestone 3 -
+
TARIN > It sounds like it is related to profiles
  
    -> Manual creation of the SPEC file with the BETA Version to create a functional RPM
+
TARIN IS Compiling 32 bit minefield on Chile
    -> After tested and satisfied with the results TEST with NIGHTLY Packages
+
TARIN IS Compiling 64 bit minefield on IRAQ
    -> Manual creation of the SPEC file with the NIGHTLY Version to create a functional RPM
 
  
* Milestone 4 -
+
Problems :
  
    -> Automation of the creation of the SPEC File
+
REVISIT SPEC FILE - Figure out how to make it more
  
 +
Vitaly -  Figure out signing of public keys - password:  senecaCdot
 +
Eugene - make a spec file by the end of the day
  
Steps needed to take -
 
  
    -Need to setup 2 repos - x86 and x86_64 of beta and Nightlies
+
'''October 12th 2010 Notes'''
    -Experimentation with the nightly build and how it works with SELinux
 
  
 +
* BUGZILLA - 600317
  
Project sections and Assignments  -
+
lists.fedoraproject.org/mailman/listinfo
  
    Repository Setup -->                                                       Vitalijs
+
Problem -->
  
    SPEC File Building for Nightlies and Beta's For 64bit and x86 Packages --> Eugene , Tarinur
+
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.
  
    Nightly compatibility with SELinux -->                                    Brett , Tarinur
+
WE NEED betas to co-exist with the firefox Original working package.
  
Nightlies are located at [http://nightly.mozilla.org/ Firefox Nightlies]
 
  
 +
'''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.
  
== Approach to the Problem ==
+
Subprojects:
  
* Target: Current Fedora releases (right now that's
+
* Build configuration for the RPM files.
 +
* Repository configuration RPMs.
 +
* Getting SELinux to work with the nightlies.
  
Approach to packaging:
 
# Pull from a standard URL (as of now http://nightly.mozilla.org/) (armenzg-TODO: get fixed URL to latest)
 
# Package that binary nightly/beta as an RPM
 
# Add to a repository and regenerate/update metadata
 
  
Approach to repo access:
+
Website -->  [http://nightly.mozilla.org/ Firefox Nightlies]
# Make a repo "release" RPM that provides .repo file and public key
 
  
Approach to SELinux:
+
point 1  install repositories
# Modify the RPM packaging to setup SELinux appropriately
+
installing a YUM system to grab
#* File labels and policy need to be managed in the RPM package
+
Point 2  installation of the Repositories
 +
point 3  create account on bugzilla
  
Installation locations:
+
2 repositories for x86 and 64-bit -->
* Must not conflict with distro-provided install locations
+
producting the rpms
* 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 ==
+
Creating spec files for nightlies ...
  
* Deploy on HW in CDOT initially (which machine?)
+
pull in nightly build and package
* Deliver scripts to Armen for deployment on Mozilla infra
+
 +
automate it using a script from the website
  
== Release Targets ==
+
repository setup -> signing it -->
  
* 0.1 - Proof of concept
+
create the rpm for the repo
* 0.2 - Cleaned-up release
 
* 0.3 - Scripts delivered to Armen
 
  
== Division of Labour ==
+
seperate nightlies and beta??  AND x86 and 64-bit ??
  
* SPEC file - Tarinur is Taking this responsibility.
+
--> Problem --> Getting SELinux to work with the nightlies.
* Repo - Vitaly
 
* SELinux - Brett
 
* Desktop integration and testing - Tarinur
 

Latest revision as of 06:15, 12 December 2010

Project Name

Repository Setup for Mozilla Nightly and Beta builds

Project Description

Automating the process of RPM building and repository updates for 32 Bit and 64 Bit Firefox beta and nightly builds on Fedora systems.

Project Leaders

  • Brett van Gennip - bvangennip@learn.senecac.on.ca
  • Eugene Khabian - Removed
  • Vitalijs Bluzmans - vbluzmans@learn.senecac.on.ca
  • Tarinur Choudhury - trchoudhury@learn.senecac.on.ca

Responsibilities

  • SPEC File Formation & Desktop Integration - Tarinur
  • Repository Configuration - Vitaly
  • Testing Minefield with SELinux and Fedora 13 - Brett

Project Contributor(s)

  • Chris Tyler
  • Armen Zambrano Gasparnian

Project Details

  • Target: Current supported Fedora releases (Fedora 13 and Fedora 14)

Approach to packaging:

  1. Pull from a standard URL (as of now http://nightly.mozilla.org/)
  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 (Chile)
  • Deliver scripts to Armen for deployment on Mozilla infrastructure

Release Targets

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

Project Plan

  • 0.1 - Proof of concept

Fully working proof of concept including early mock up of nightly RPM and repository installation RPM.

Progress made on 0.1 Milestone

Please see our latest blog posts on the status of milestone 0.1. This wiki will feature a brief overview of how the project is progressing.

Brett van Gennip - Testing Minefield with SELinux and Fedora 13

Brett had downloaded Minefield and attempted to replicate the error message that was coming up for people. Overall, he had no success making the error message show up which proved to be a bit of an issue to how he can understand the issue. Certain things came up such as: while running firefox, Minefield would not open. While running Minefield, firefox would not open. At no point was he able to run both at the same time. Overall, he plans to speak with people on IRC to try to make some sense of these issues.

Please see blog for more details:

Minefield and Firefox

Tarin - RPM Building and Repository Setup

Tarin had setup the Repository and made it so that you are able to download the nightly via iraq.proximity.on.ca repository. He has also packaged the nightlies in an RPM format. Which means that he has created a SPEC file for the RPM to work with Fedora 1x machines in both 32 bit and 64 bit architectures. Our repository is located at Nightly Repository.

Please see blog for more details:

Milestone 1 Continued

Vitaly - Building Firefox/Fedora Repository

Vitaly had setup the Repository on one of the servers in Seneca's open source room locations. He had proceeded in creating a script that will automate the process of setting up the repo's into the directory for which they are to be downloaded from.

Our repository is located at Nightly Repository.

Please see blog for more details:

Building Firefox/Fedora Repo

  • 0.2 - Cleaned-up release

Finalize spec files and implement automation.

Progress made on 0.2 Milestone

Please see our latest blog posts on the status of milestone 0.2. This wiki will feature a brief overview of how the project is progressing.

Tarin

Release 0.2 Update

  • 0.3 - Scripts delivered to Armen

Progress made on 0.3 Milestone

Please see our latest blog posts on the status of milestone 0.3. This wiki will feature a brief overview of how the project is progressing.

Project News

November 12th, 2010

- EUGENE IS Back -

STATUS:

(BRETT)

setup a different profile for

That i run firefox and minefield together the way i just describe it.

what does he want ? can we do it or is the builders Responsibility to figure it out... or does it even matter

TARIN > It sounds like it is related to profiles

TARIN IS Compiling 32 bit minefield on Chile TARIN IS Compiling 64 bit minefield on IRAQ

Problems :

REVISIT SPEC FILE - Figure out how to make it more

Vitaly - Figure out signing of public keys - password: senecaCdot Eugene - make a spec file by the end of the day


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.