From Fedora Project Wiki

m (fix external link (it is just a placeholder for now))
m (update)
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{admon/important|If you are using a Fedora 14 HOST, there is a known issue. Use the following work-around|
* The work-around is probably '''not''' necessary for building a Fedora 14 appliances on a Fedora 15 host. If you experience problems, try the work-around.  If that fixes it, then please mention this in your notes.
* Edit boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl, comment out (or remove) line 13. Note this in your references, and see if you can build successfully from this point.}}
{{QA/Test_Case
{{QA/Test_Case
|description=Build an appliance based upon the modular appliances, which are designed to provide more comprehensive BoxGrinder Build feature coverage.
|description=Build an appliance based upon the modular appliances, which are designed to provide more comprehensive BoxGrinder Build feature coverage.
|setup=Clone the BoxGrinder test appliances into a convenient location using command <code>git clone https://github.com/msavy/boxgrinder-appliances.git</code>
|setup=
 
# [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare your environment]]
We must create a local RPM repository in order to include our custom programs, this is the most effective way of adding custom applications into a BoxGrinder appliance.  All of the hard work of dependency resolution is done via the RPMs!
# Create local repository directory <pre>mkdir -p /tmp/boxgrinder-repo</pre>
# Create a directory tree of <code>/var/repo/RPMS/noarch/</code>
# Download our test RPM <pre>wget --directory-prefix=/tmp/boxgrinder-repo http://repo.boxgrinder.org/boxgrinder/testday/ephemeral-repo-test-0.1-1.noarch.rpm</pre>
# Download the [http://www.boxgrinder.org/testday/ephemeral-test.rpm BoxGrinder test RPM file] to <code>/var/repo/RPMS/noarch/</code> (<code>wget --directory-prefix=/var/repo/RPMS/noarch http://www.boxgrinder.org/testday/ephemeral-test.rpm</code>)
# Create repodata <pre>createrepo /tmp/boxgrinder-repo</pre>
# Execute <code>createrepo /var/repo/RPMS/noarch</code>
 
|actions=
|actions=
# Navigate to directory <code>boxgrinder-appliances/testing-appliances/modular-appls/</code>
# Execute <pre>boxgrinder-build testing-appliances/modular-appls/fedora_14.appl --trace</pre>
# Execute <code>boxgrinder-build fedora_rawhide.appl</code>
|results=
|results=
The following must be true to consider this a successful test run.
The following must be true to consider this a successful test run.
# Step #2 completes without error (indicated on console)
# Step #1 completes without error (indicated on console)
# Program completes with exit code 0
# Program completes with exit code 0
}}
}}

Latest revision as of 23:57, 28 April 2011

Important.png
If you are using a Fedora 14 HOST, there is a known issue. Use the following work-around
  • The work-around is probably not necessary for building a Fedora 14 appliances on a Fedora 15 host. If you experience problems, try the work-around. If that fixes it, then please mention this in your notes.
  • Edit boxgrinder-appliances/testing-appliances/modular-appls/_test_base.appl, comment out (or remove) line 13. Note this in your references, and see if you can build successfully from this point.



Description

Build an appliance based upon the modular appliances, which are designed to provide more comprehensive BoxGrinder Build feature coverage.

Setup

  1. Prepare your environment
  2. Create local repository directory
    mkdir -p /tmp/boxgrinder-repo
  3. Download our test RPM
    wget --directory-prefix=/tmp/boxgrinder-repo http://repo.boxgrinder.org/boxgrinder/testday/ephemeral-repo-test-0.1-1.noarch.rpm
  4. Create repodata
    createrepo /tmp/boxgrinder-repo

How to test

  1. Execute
    boxgrinder-build testing-appliances/modular-appls/fedora_14.appl --trace

Expected Results

The following must be true to consider this a successful test run.

  1. Step #1 completes without error (indicated on console)
  2. Program completes with exit code 0