packaging 0.88.77 → 0.99.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +5 -5
- data/README.md +128 -74
- data/lib/packaging/artifactory.rb +60 -433
- data/lib/packaging/config/params.rb +7 -28
- data/lib/packaging/config.rb +50 -150
- data/lib/packaging/deb/repo.rb +19 -20
- data/lib/packaging/gem.rb +83 -41
- data/lib/packaging/ips.rb +57 -0
- data/lib/packaging/msi.rb +89 -0
- data/lib/packaging/nuget.rb +1 -1
- data/lib/packaging/osx.rb +36 -0
- data/lib/packaging/paths.rb +87 -225
- data/lib/packaging/platforms.rb +416 -443
- data/lib/packaging/repo.rb +22 -122
- data/lib/packaging/retrieve.rb +7 -36
- data/lib/packaging/rpm/repo.rb +8 -5
- data/lib/packaging/tar.rb +0 -9
- data/lib/packaging/util/date.rb +0 -5
- data/lib/packaging/util/execution.rb +2 -2
- data/lib/packaging/util/git.rb +1 -1
- data/lib/packaging/util/gpg.rb +1 -5
- data/lib/packaging/util/net.rb +37 -79
- data/lib/packaging/util/rake_utils.rb +0 -1
- data/lib/packaging/util/ship.rb +13 -142
- data/lib/packaging/util/tool.rb +1 -1
- data/lib/packaging/util/version.rb +0 -8
- data/lib/packaging/util.rb +2 -2
- data/lib/packaging.rb +3 -3
- data/spec/fixtures/config/params.yaml +2 -0
- data/spec/lib/packaging/artifactory_spec.rb +16 -66
- data/spec/lib/packaging/config_spec.rb +29 -49
- data/spec/lib/packaging/deb/repo_spec.rb +7 -16
- data/spec/lib/packaging/paths_spec.rb +56 -321
- data/spec/lib/packaging/platforms_spec.rb +21 -46
- data/spec/lib/packaging/repo_spec.rb +40 -78
- data/spec/lib/packaging/retrieve_spec.rb +8 -47
- data/spec/lib/packaging/rpm/repo_spec.rb +4 -4
- data/spec/lib/packaging/tar_spec.rb +40 -34
- data/spec/lib/packaging/util/git_tag_spec.rb +1 -1
- data/spec/lib/packaging/util/gpg_spec.rb +1 -1
- data/spec/lib/packaging/util/net_spec.rb +15 -35
- data/spec/lib/packaging/util/ship_spec.rb +63 -145
- data/spec/spec_helper.rb +14 -0
- data/tasks/00_utils.rake +6 -4
- data/tasks/apple.rake +0 -2
- data/tasks/config.rake +0 -5
- data/tasks/education.rake +5 -5
- data/tasks/fetch.rake +14 -17
- data/tasks/gem.rake +121 -134
- data/tasks/jenkins.rake +7 -51
- data/tasks/nightly_repos.rake +69 -20
- data/tasks/pe_ship.rake +11 -16
- data/tasks/retrieve.rake +6 -13
- data/tasks/ship.rake +256 -196
- data/tasks/sign.rake +135 -63
- data/tasks/tar.rake +6 -0
- data/templates/packaging.xml.erb +7 -9
- data/templates/repo.xml.erb +3 -6
- metadata +27 -80
- data/lib/packaging/archive.rb +0 -126
- data/lib/packaging/artifactory/extensions.rb +0 -94
- data/lib/packaging/config/validations.rb +0 -13
- data/lib/packaging/metrics.rb +0 -15
- data/lib/packaging/sign/deb.rb +0 -9
- data/lib/packaging/sign/dmg.rb +0 -41
- data/lib/packaging/sign/ips.rb +0 -57
- data/lib/packaging/sign/msi.rb +0 -124
- data/lib/packaging/sign/rpm.rb +0 -115
- data/lib/packaging/sign.rb +0 -8
- data/spec/lib/packaging/gem_spec.rb +0 -86
- data/spec/lib/packaging/sign_spec.rb +0 -133
- data/tasks/archive.rake +0 -69
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
|
-
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: 60597eac7cb43a07b9c9c5f2e0446eeb97741697
|
4
|
+
data.tar.gz: 4b2493e3dac7fc620c221f29207c1aac0c4628d3
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 945d03dbfe203b4ce43210494fba3da11c365064e54d014d5d2a04f1c42704295a355b0a1bd6a8b1f7b63388b4210db71d8b463b9d388a9ddc1b0d52a6f4bcce
|
7
|
+
data.tar.gz: 0f6e50d73f6d91d9666b49ff6e7a5a8019045c9cfb190a5c0ead9c04d341a5375e95d180bf2560511c404f860a6cedb10a4be4470a9cc717c5a331de61026492
|
data/README.md
CHANGED
@@ -36,12 +36,12 @@ as well as several closed-source projects, including
|
|
36
36
|
* console-auth
|
37
37
|
* console
|
38
38
|
|
39
|
-
Generally speaking, the packaging repo should be compatible with ruby
|
40
|
-
|
41
|
-
do a `
|
42
|
-
|
43
|
-
|
44
|
-
|
39
|
+
Generally speaking, the packaging repo should be compatible with ruby 1.8.7,
|
40
|
+
ruby 1.9.3 and rake 0.9.x. To pull the packaging tasks into your source repo,
|
41
|
+
do a `rake package:bootstrap`. This will clone this repo into the ext directory
|
42
|
+
of the project and make many packaging tasks available. The tasks are
|
43
|
+
generally grouped into two categories, `package:` namespaced tasks and `pl:`
|
44
|
+
namespaced tasks.
|
45
45
|
|
46
46
|
## `package:` tasks
|
47
47
|
`package:` namespaced tasks are general purpose tasks that are set up to use
|
@@ -51,8 +51,7 @@ the building host, and any dynamically generated dependencies may result in
|
|
51
51
|
packages that are only suitable for the OS/version of the build host. However,
|
52
52
|
for rolling one's own debs and rpms or for use in environments without many
|
53
53
|
OSes/versions, this may work just fine. To build an rpm using the packaging
|
54
|
-
repo, do a `
|
55
|
-
package:deb`.
|
54
|
+
repo, do a `rake package:rpm`. To build a deb, use `rake package:deb`.
|
56
55
|
|
57
56
|
## `pl:` tasks
|
58
57
|
`pl:` namespaced tasks rely on a slighly more complex toolchain for packaging
|
@@ -76,32 +75,32 @@ separating these data and tasks out is to refrain from presenting by
|
|
76
75
|
default yet more Puppet-specific tasks that aren't generally consumable by
|
77
76
|
everyone. To build a deb from a local repository using a `pl` task, ssh into a
|
78
77
|
builder (e.g., one stood up using the modules detailed below) and clone the
|
79
|
-
source repo, e.g. puppet. Then, run `
|
80
|
-
to create a deb, and `
|
81
|
-
|
78
|
+
source repo, e.g. puppet. Then, run `rake package:bootstrap` and `rake pl:deb`
|
79
|
+
to create a deb, and `rake pl:mock` to make an rpm (on a debian or redhat host,
|
80
|
+
respectively).
|
82
81
|
|
83
82
|
## `pe:` tasks
|
84
|
-
There is also a `pe:` namespace, for the building of Puppet
|
85
|
-
Enterprise packages that have been converted to using this repo.
|
86
|
-
rely heavily on PL internal infrastructure, and are not
|
87
|
-
of this environment. To create packages, in the source
|
88
|
-
|
89
|
-
the packaging
|
90
|
-
`pl:fetch` notes above).
|
91
|
-
pe:deb`, and to make an rpm, run `
|
92
|
-
`pe:deb_all` and `pe:mock_all` tasks, which build packages against all
|
93
|
-
debian/redhat targets. The `pe:deb_all` task is not generally necessary
|
94
|
-
developer use for building test packages; the `pe:deb` task creates a
|
95
|
-
that will work against virtually all supported PE debian versions.
|
96
|
-
generally true for PE internal rpms, but because of variances in
|
97
|
-
for rpm, rpms should generally be built with `pe:mock_all`, and
|
98
|
-
version installed, or by building only for a specific
|
99
|
-
accomplished by passing MOCK=<mock> to the rake call, e.g.
|
100
|
-
pe:mock MOCK=<mock>`.
|
101
|
-
`ext/build_defaults.yaml` after `final_mocks:`.
|
102
|
-
as `pupent-<peversion>-<distversion>-<arch>`, e.g.
|
103
|
-
build for a specific target, set `MOCK=<mock>` to
|
104
|
-
target.
|
83
|
+
There is also a `pe:` namespace, for the building of Puppet
|
84
|
+
Labs' Puppet Enterprise packages that have been converted to using this repo.
|
85
|
+
The `pe:` tasks rely heavily on PL internal infrastructure, and are not
|
86
|
+
generally useful outside of this environment. To create packages, in the source
|
87
|
+
repository run `rake package:bootstrap`, followed by `rake pl:fetch`. These two
|
88
|
+
commands bootstrap the packaging environment and pull in the additional data
|
89
|
+
needed for PE building (see `pl:fetch` notes above). Then, to make a debian
|
90
|
+
package, run `rake pe:deb`, and to make an rpm, run `rake pe:mock`. There are
|
91
|
+
also `pe:deb_all` and `pe:mock_all` tasks, which build packages against all
|
92
|
+
shipped debian/redhat targets. The `pe:deb_all` task is not generally necessary
|
93
|
+
for developer use for building test packages; the `pe:deb` task creates a
|
94
|
+
package that will work against virtually all supported PE debian versions.
|
95
|
+
The same is generally true for PE internal rpms, but because of variances in
|
96
|
+
build macros for rpm, rpms should generally be built with `pe:mock_all`, and
|
97
|
+
then the desired version installed, or by building only for a specific
|
98
|
+
target. This is accomplished by passing MOCK=<mock> to the rake call, e.g.
|
99
|
+
`rake pe:mock MOCK=<mock>`. The available mocks are listed in
|
100
|
+
`ext/build_defaults.yaml` after `final_mocks:`. For PE, the mocks are
|
101
|
+
formatted as `pupent-<peversion>-<distversion>-<arch>`, e.g.
|
102
|
+
`pupent-2.7-el5-i386`. To build for a specific target, set `MOCK=<mock>` to
|
103
|
+
the mock that matches the target.
|
105
104
|
|
106
105
|
## `:remote:` tasks
|
107
106
|
There are also sub-namespaces of `:pl` and `:pe` that are
|
@@ -109,24 +108,22 @@ worth noting. First, the `:remote` namespace. Tasks under `:remote` perform
|
|
109
108
|
builds remotely on internal builders from your local workstation. How they
|
110
109
|
work:
|
111
110
|
|
112
|
-
|
113
|
-
|
114
|
-
1) Run `bundle exec pl:fetch` to obtain extra data from the build-data repo. The data
|
111
|
+
1) Run `pl:fetch` to obtain extra data from the build-data repo. The data
|
115
112
|
includes the hostnames of builders to use for packaging.
|
116
113
|
|
117
114
|
2) Create a git bundle of the local workspace and tar it up.
|
118
115
|
|
119
116
|
3) Create a build parameters file. The params file includes all the information
|
120
117
|
about the build, including any values overridden with env vars, and the actual
|
121
|
-
task to run, e.g. `
|
118
|
+
task to run, e.g. `rake pl:deb`.
|
122
119
|
|
123
120
|
4) scp the git bundle and build parameters file to a temporary directory on the
|
124
121
|
builder hostname assigned to that particular package build type.
|
125
122
|
|
126
|
-
5) ssh into the builder, untar the git bundle, clone it, and run `
|
127
|
-
|
123
|
+
5) ssh into the builder, untar the git bundle, clone it, and run `rake
|
124
|
+
package:bootstrap`.
|
128
125
|
|
129
|
-
6) ssh into the builder, cd into the cloned repo, and run `
|
126
|
+
6) ssh into the builder, cd into the cloned repo, and run `rake
|
130
127
|
pl:build_from_params PARAMS_FILE=/path/to/previously/sent/file`.
|
131
128
|
|
132
129
|
7) Maintain the ssh connection until the build finishes, and rsync the packages
|
@@ -138,7 +135,7 @@ groups, e.g. to use mock on the builder, membership in the mock group. This is
|
|
138
135
|
a major hurdle, and is resolved with the `jenkins` tasks below.
|
139
136
|
|
140
137
|
## legacy `:jenkins:` workflow tasks
|
141
|
-
(Deprecated - see "
|
138
|
+
(Deprecated - see "dyamic jenkins task workflow" below)
|
142
139
|
Jenkins tasks are similar to the `:remote:` tasks, but they do not require ssh
|
143
140
|
access to the builders. They do require being on the local network - the
|
144
141
|
jenkins instance that performs package builds is an internal server only,
|
@@ -209,18 +206,18 @@ the task are:
|
|
209
206
|
|
210
207
|
cd git_repo
|
211
208
|
|
212
|
-
###
|
213
|
-
|
209
|
+
### Clone the packaging repo
|
210
|
+
rake package:bootstrap && rake pl:fetch
|
214
211
|
|
215
212
|
### Perform the build
|
216
|
-
|
213
|
+
rake pl:load_extras pl:build_from_params PARAMS_FILE=$WORKSPACE/BUILD_PROPERTIES
|
217
214
|
|
218
215
|
### Send the results
|
219
|
-
|
216
|
+
rake pl:jenkins:ship["artifacts"]
|
220
217
|
|
221
218
|
### If a downstream job was passed, trigger it now
|
222
219
|
if [ -n "$DOWNSTREAM_JOB" ] ; then
|
223
|
-
|
220
|
+
rake pl:jenkins:post["$DOWNSTREAM_JOB"]
|
224
221
|
fi
|
225
222
|
|
226
223
|
#################
|
@@ -261,18 +258,18 @@ analysis. Contents of this string are items which cannot be obtained from within
|
|
261
258
|
the Jenkins job itself. Note that the Groovy postbuild script needed for metrics
|
262
259
|
gathering is dynamically passed to each job.
|
263
260
|
|
264
|
-
This first job clones the git bundle passed in as a parameter, then
|
265
|
-
packaging
|
266
|
-
package build for a specific target (e.g.
|
261
|
+
This first job clones the git bundle passed in as a parameter, then clones the
|
262
|
+
packaging repo (rake package:bootstrap) and for every cell in its matrix
|
263
|
+
performs a package build for a specific target (e.g. rake pl:deb
|
267
264
|
COW=base-lucid-i386.cow). Once all cells in the matrix complete (either succeed
|
268
|
-
or fail), this job automatically triggers the second of the new jobs
|
269
|
-
downstream job.
|
265
|
+
or fail), this job automatically triggers the second of the new jobs
|
266
|
+
as a downstream job.
|
270
267
|
|
271
268
|
To receive an email notification from jenkins about the status of the packaging
|
272
269
|
job, pass NOTIFY=<recipient> as an environment variable to the uber_build
|
273
270
|
invocation, e.g.:
|
274
271
|
|
275
|
-
|
272
|
+
rake pl:jenkins:uber_build NOTIFY="foo@puppet.com bar@puppet.com"
|
276
273
|
|
277
274
|
The second job is an automatic repository creation task for this git repo.
|
278
275
|
Specifically, the job copies the git bundle from the packaging job and clones
|
@@ -361,6 +358,10 @@ side of this packaging repo. The rpm-side module,
|
|
361
358
|
[puppetlabs-rpmbuilder](https://github.com/puppetlabs/puppetlabs-rpmbuilder),
|
362
359
|
will set up an rpm builder.
|
363
360
|
|
361
|
+
## Clean up
|
362
|
+
To remove the packaging repo, remove the ext/packaging directory or run `rake
|
363
|
+
package:implode`.
|
364
|
+
|
364
365
|
##Setting up projects for the Packaging Repo
|
365
366
|
|
366
367
|
The packaging repo requires many project-side artifacts inside the ext
|
@@ -376,9 +377,48 @@ spec file, and an osx preflight and plist.
|
|
376
377
|
|
377
378
|
The top level Rakefile or a separate task file in the project should have the following added:
|
378
379
|
|
380
|
+
(this assumes RAKE\_ROOT is defined in the top-level Rakefile using something like the following)
|
381
|
+
```ruby
|
382
|
+
RAKE_ROOT = File.expand_path(File.dirname(__FILE__))
|
383
|
+
```
|
384
|
+
|
379
385
|
```ruby
|
380
|
-
|
381
|
-
|
386
|
+
build_defs_file = File.join(RAKE_ROOT, 'ext', 'build_defaults.yaml')
|
387
|
+
if File.exist?(build_defs_file)
|
388
|
+
begin
|
389
|
+
require 'yaml'
|
390
|
+
@build_defaults ||= YAML.load_file(build_defs_file)
|
391
|
+
rescue Exception => e
|
392
|
+
$stderr.puts "Unable to load yaml from #{build_defs_file}:"
|
393
|
+
raise e
|
394
|
+
end
|
395
|
+
@packaging_url = @build_defaults['packaging_url']
|
396
|
+
@packaging_repo = @build_defaults['packaging_repo']
|
397
|
+
raise "Could not find packaging url in #{build_defs_file}" if @packaging_url.nil?
|
398
|
+
raise "Could not find packaging repo in #{build_defs_file}" if @packaging_repo.nil?
|
399
|
+
|
400
|
+
namespace :package do
|
401
|
+
desc "Bootstrap packaging automation, e.g. clone into packaging repo"
|
402
|
+
task :bootstrap do
|
403
|
+
if File.exist?(File.join(RAKE_ROOT, "ext", @packaging_repo))
|
404
|
+
puts "It looks like you already have ext/#{@packaging_repo}. If you don't like it, blow it away with package:implode."
|
405
|
+
else
|
406
|
+
cd File.join(RAKE_ROOT, 'ext') do
|
407
|
+
%x{git clone #{@packaging_url}}
|
408
|
+
end
|
409
|
+
end
|
410
|
+
end
|
411
|
+
desc "Remove all cloned packaging automation"
|
412
|
+
task :implode do
|
413
|
+
rm_rf File.join(RAKE_ROOT, "ext", @packaging_repo)
|
414
|
+
end
|
415
|
+
end
|
416
|
+
end
|
417
|
+
|
418
|
+
begin
|
419
|
+
load File.join(RAKE_ROOT, 'ext', 'packaging', 'packaging.rake')
|
420
|
+
rescue LoadError
|
421
|
+
end
|
382
422
|
```
|
383
423
|
|
384
424
|
Also in ext should be two files, build_defaults.yaml and project_data.yaml (optional).
|
@@ -404,9 +444,9 @@ deb_build_mirrors:
|
|
404
444
|
# Who is packaging. Turns up in various packaging artifacts
|
405
445
|
packager: 'puppetlabs'
|
406
446
|
# GPG key ID of the signer
|
407
|
-
gpg_key: '
|
447
|
+
gpg_key: '7F438280EF8D349F'
|
408
448
|
# Whether to require tarball signing as a prerequisite of other package building
|
409
|
-
sign_tar:
|
449
|
+
sign_tar: FALSE
|
410
450
|
# a space separated list of mock configs. These are the rpm distributions to package for. If a noarch package, only one arch of each is needed.
|
411
451
|
final_mocks: 'pl-el-5-i386 pl-el-5-x86_64 pl-el-6-i386 pl-el-6-x86_64 pl-fedora-16-i386 pl-fedora-16-x86_64 pl-fedora-17-i386 pl-fedora-17-x86_64'
|
412
452
|
# The host that contains the yum repository to ship to
|
@@ -422,10 +462,10 @@ apt_repo_path: '/opt/repository/incoming'
|
|
422
462
|
# The host that stores the tarballs for downloading
|
423
463
|
tar_host: 'downloads.puppetlabs.com'
|
424
464
|
# Whether to present the gem and apple tasks
|
425
|
-
build_gem:
|
426
|
-
build_dmg:
|
465
|
+
build_gem: TRUE
|
466
|
+
build_dmg: TRUE
|
427
467
|
# Whether to execute the rdoc rake tasks prior to composing the tarball
|
428
|
-
build_doc:
|
468
|
+
build_doc: FALSE
|
429
469
|
# Whether to kick of a dynamic msi build job along side the uber_build
|
430
470
|
# If present, a dynamically generated jenkins job will be kicked off.
|
431
471
|
# The automation in puppet_for_the_win is used to build the msi with the
|
@@ -447,9 +487,9 @@ build_msi:
|
|
447
487
|
repo: 'git://github.com/puppetlabs/puppet-win32-ruby.git'
|
448
488
|
# Whether to present the Solaris 11 IPS packaging tasks
|
449
489
|
# This requires suitable IPS packaging artifacts in the project in ext/ips
|
450
|
-
build_ips:
|
490
|
+
build_ips: FALSE
|
451
491
|
# Whether this project is a PE project or not
|
452
|
-
build_pe:
|
492
|
+
build_pe: FALSE
|
453
493
|
# An optional task to execute pre-tarball composition. See the tasks in
|
454
494
|
# the 'pretasks' directory
|
455
495
|
pre_tar_task: 'package:vendor_gems'
|
@@ -462,7 +502,7 @@ author: 'Puppet'
|
|
462
502
|
email: 'info@puppet.com'
|
463
503
|
homepage: 'https://github.com/puppetlabs/hiera'
|
464
504
|
summary: 'Light weight hierarchical data store'
|
465
|
-
description: 'A pluggable data store for
|
505
|
+
description: 'A pluggable data store for hierarcical data'
|
466
506
|
# file containing hard coded version information, if present
|
467
507
|
version_file: '/lib/hiera.rb'
|
468
508
|
# A string indicating the version strategy for the project (one of 'odd_even' or 'rc_final'), defaults to rc_final
|
@@ -617,11 +657,18 @@ files:
|
|
617
657
|
* **package:apple**
|
618
658
|
|
619
659
|
Use `PackageMaker` to create a pkg package inside a dmg. Requires 'sudo'
|
620
|
-
privileges. `build_dmg:
|
660
|
+
privileges. `build_dmg: TRUE` must be set in `ext/build_defaults.yaml`.
|
621
661
|
Packages are staged in ./pkg/apple. See the Mac packaging section of
|
622
662
|
[Setting up projects for the Packaging
|
623
663
|
Repo](https://github.com/MosesMendoza/packaging/tree/more_documentation#setting-up-projects-for-the-packaging-repo).
|
624
664
|
|
665
|
+
* **package:bootstrap**
|
666
|
+
|
667
|
+
Clone the packaging repo into this project. This task isn't actually in the
|
668
|
+
packaging repo itself, but resides in the project. See [Setting up projects
|
669
|
+
for the Packaging
|
670
|
+
Repo](https://github.com/puppetlabs/packaging#setting-up-projects-for-the-packaging-repo).
|
671
|
+
|
625
672
|
* **package:deb**
|
626
673
|
|
627
674
|
Use `debbuild` to create a deb package and associated debian package
|
@@ -630,10 +677,17 @@ files:
|
|
630
677
|
|
631
678
|
* **package:gem**
|
632
679
|
Use the `rubygems/package_task` library to create a rubygem from the
|
633
|
-
repository. Requires `build_gem:
|
680
|
+
repository. Requires `build_gem: TRUE` and gem-related parameters be set in
|
634
681
|
`ext/build_defaults.yaml` and `ext/project\_data.yaml`. The gem is staged
|
635
682
|
in `./pkg`.
|
636
683
|
|
684
|
+
* **package:implode**
|
685
|
+
|
686
|
+
Remove the packaging repo entirely from the project. This task isn't
|
687
|
+
actually in the packaging repo itself, but resides in the project. See
|
688
|
+
[Setting up projects for the Packaging
|
689
|
+
Repo](https://github.com/puppetlabs/packaging#setting-up-projects-for-the-packaging-repo).
|
690
|
+
|
637
691
|
* **package:ips**
|
638
692
|
|
639
693
|
Use Solaris 11 pkg* tools to create a IPS package from the project.
|
@@ -663,8 +717,8 @@ files:
|
|
663
717
|
* **pl:build_from_params**
|
664
718
|
|
665
719
|
Invoke a build from a build parameters yaml file. The parameters file
|
666
|
-
should be created with `
|
667
|
-
|
720
|
+
should be created with `rake pl:write_build_params`. The settings in the
|
721
|
+
build parameters file will override all values contained in
|
668
722
|
`./ext/build_defaults.yaml` and `./ext/project_data.yaml`.
|
669
723
|
|
670
724
|
* **pl:deb**
|
@@ -679,10 +733,10 @@ files:
|
|
679
733
|
|
680
734
|
* **pl:deb_all***
|
681
735
|
|
682
|
-
The same as `
|
683
|
-
|
684
|
-
|
685
|
-
|
736
|
+
The same as `rake pl:deb`, but a package is built for every cow listed in
|
737
|
+
`ext/build_defaults.yaml` on the line `cows:<cows>`. The packages and
|
738
|
+
associated source artifacts are staged in `./pkg/deb/$distribution`, where
|
739
|
+
$distribution is the Debian/Ubuntu codename of the cow that was used to
|
686
740
|
build the package, e.g. "wheezy" or "precise."
|
687
741
|
|
688
742
|
* **pl:ips**
|
@@ -851,11 +905,11 @@ files:
|
|
851
905
|
|
852
906
|
* **pl:mock_all**
|
853
907
|
|
854
|
-
The same as `
|
855
|
-
|
856
|
-
|
857
|
-
|
858
|
-
|
908
|
+
The same as `rake pl:mock`, but a package is built for every mock listed in
|
909
|
+
`ext/build_defaults.yaml` on the line `mocks:<mocks>`. Packages are staged
|
910
|
+
in `./pkg/<repo_name>/(el | fedora)/$version/(i386 | x86_64 |
|
911
|
+
SRPMS)`. The subdirectories are dependent on the mock that is used. The
|
912
|
+
task assumes that the mock configurations are the standard Puppet mock
|
859
913
|
configurations that are generated by the
|
860
914
|
[puppetlabs-rpmbuilder](https://github.com/puppetlabs/puppetlabs-rpmbuilder)
|
861
915
|
module.
|