Change-Id: Ia7883c196c688236051a4637561c9a01be5358cb
BUG=TreeCloser
TEST=Ran with simple prefix for x86-generic and no keys
Review URL: http://codereview.chromium.org/6480085
In addition some refactoring to make this cleaner and easier.
Change-Id: I1607700d065c71aff2b2833b10acbd3ebace68ce
BUG=chromium-os:8212
TEST=Ran with Simple ... running now with full
Review URL: http://codereview.chromium.org/6482017
I was getting the error about passing along an empty string argument, and this will fix that.
Change-Id: Iffd05fe570f3a6092bbeee05abf8a1884decd644
BUG=N0ne
TEST=remote testing in progress (no VM testing)
Review URL: http://codereview.chromium.org/6465014
Change-Id: Ia5e0042250da22cebadfd48d143f21597bcada5d
BUG=chromium-os:11716
TEST=Ran vm test and vm update scripts.
Review URL: http://codereview.chromium.org/6413019
This is step 3/3, after cros_overlay_list is added to dev, and
after the ebuilds are updated to install from dev and not
crosutils, then this can go in.
Change-Id: I8ae26938fb14ccf6737acd9ca99b58aaf65a1aca
BUG=chromium-os:11507
TEST=None
Review URL: http://codereview.chromium.org/6392034
Change-Id: I7eb27ac81704de8689a65203a440303a52a01dc2
BUG=chromium-os:11171
TEST=we'll see if things explode
Review URL: http://codereview.chromium.org/6286040
from within the chroot.
It also fixes a number of style issues.
It changes the meaning of cros_workon "list-all" to list all available
packages, and adds "list-live" to list all live packages.
It changes things that load chromeos-common.sh from the installer to
load it from /usr/lib/installer.
BUG=chromium-os:4230
TEST=synced, rebuilt chroot, made packages, made images, built chrome
from source, and wrote an image to a USB stick.
Review URL: http://codereview.chromium.org/6240018
Change-Id: I90c34420af1a64020402bafef8e9e77f56837c02
It's very rarely needed anyway but enter_chroot does everything under the sun.
Avoids:
error: could not lock config file ~/.gitconfig
Change-Id: Ide72b14fd434b182a88d2fc636559b3515905509
BUG=chromium-os:11523
TEST=Ran it ... 10x
Review URL: http://codereview.chromium.org/6312069
This issue seems bigger than it first appears because we had put extra logic to "Delete" the branch if we didn't rev anything. This CL basically takes out all the Deletes and relies and cros_mark_as_stable clean to clean up any old dirs correctly. To do this, I had to fix a bug in clean so that we actually delete the stable branch as part of it (if it exists).
EOM
Change-Id: Ic1020451dc1d492d4b6e2a233d1d49cf8c1c16b3
BUG=chromium-os:11329
TEST=Ran x86-generic-pfq w/ dev options + --chrome_rev=latest_release ...built chrome,
and revved packages without error. Doing more testing still.
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=a8ac0ec
Review URL: http://codereview.chromium.org/6291013
This reverts the commit a8ac0ec8c3.
TBR the x86 PFQ buildbot fails
BUG=chromium-os:11447
TEST=
TBR=sosa
Change-Id: I019de669db13b753365e1208acc9923c4bb5c993
Review URL: http://codereview.chromium.org/6339018
This issue seems bigger than it first appears because we had put extra logic to "Delete" the branch if we didn't rev anything. This CL basically takes out all the Deletes and relies and cros_mark_as_stable clean to clean up any old dirs correctly. To do this, I had to fix a bug in clean so that we actually delete the stable branch as part of it (if it exists).
EOM
Change-Id: Ic1020451dc1d492d4b6e2a233d1d49cf8c1c16b3
BUG=chromium-os:11329
TEST=Ran x86-generic-pfq w/ dev options + --chrome_rev=latest_release ...built chrome,
and revved packages without error. Doing more testing still.
Review URL: http://codereview.chromium.org/6291013
Change-Id: I24b498fffb7e7ce54517945730c91fecd1d57586
BUG=chromium-os:10723
TEST=Ran it and killed a test
Review URL: http://codereview.chromium.org/6260023
Change-Id: If4c2852568454c2dccf09b0fc1e180ed228a1bb7
BUG=chromium-os:4230
TEST=run cros_overlay_list from both locations in the chroot and src/scripts outside the chroot.
Review URL: http://codereview.chromium.org/6293021
Change-Id: Ie1ee6554ec0973a85a11c264346295fd27f59ebf
BUG=chromium-os:11329
TEST=Ran with cbuildbot on local system.
Review URL: http://codereview.chromium.org/6384017
It also caches sudo credentials before running jobs (for devs) and
exits if any updater returns an error code != 0 with the output
of pregenerate update
BUG=chromium-os:10723
TEST=Ran it ... killed one pregeneration to make sure it did print + exit
correctly
Review URL: http://codereview.chromium.org/6381013
Change-Id: I04842211e469b3a0022cb53b78efd17fbebe7010
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=be787f3
Review URL: http://codereview.chromium.org/6277015
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=c418a8f
Review URL: http://codereview.chromium.org/6277015
As a warning, this is a pretty big change. At a high-level,
this changes the harness to move the managing of the devserver from
image_to_live into the actual test harness. Paths of the cache locations (for
archive_url) are taken when pre-generating the updates and stored
in a dictionary (maps "path_to_base->path_to_target" (or path for full updates)->
cache paths).
This change also has the tests run in parallel. Because we now start
X number of VM's at once, each VM needs it's own pid file and ssh_port.
This logic was added as well as running the actual tests in parallel.
Change-Id: I1275d79740c50c2a8028489b43dcbbcf5bbd56c4
BUG=chromium-os:10723
TEST=Ran it ... a lot with -q but without a test_prefix (so full test suite).
Review URL: http://codereview.chromium.org/6277015
image_to_live runs dev_server with sudo so old cached entries are
owned by root rather than $USER. Change to pre-generate also with
sudo.
Change-Id: I587f15953b37d4de439977e7dbac9fced175c173
BUG=chromium-os:10723
TEST=Ran it
Review URL: http://codereview.chromium.org/6380008
First CL of many. Thought I'd commit this before the others since
it sets stuff up for the other CL's (i.e. Thread Pool).
With this CL, all updates will be pre-generated before the test run.
This should improve some speeds since the two updates will be produced
at the same time rather than at the time of the sequential tests.
Change-Id: Iaf0a06f0d99c31d3d749e478fd2fb6efa0763a28
BUG=chromium-os:10723
TEST=Ran it with -q
Review URL: http://codereview.chromium.org/6264005
build problems, and will give better diagnostics if not.
Change-Id: I2f7a5d9b2e0c63a8189ad212125c7a5c0178c3c4
BUG=10567
TEST=
Review URL: http://codereview.chromium.org/6331007
Change-Id: I046d49c7002586671dc7c6707afeeeb0a0360cd5
BUG=10934
TEST=Ran it with bin/cros_mark_chrome_as_stable tot. Verified output and that it still did the right thing
Review URL: http://codereview.chromium.org/6327002
This cleanup code consolidates parsing of options, removes
globals, cleans up private vs. public functions, removes the backup full update option, and cleans up
docstrings.
Change-Id: I3eba26b3634fd87f4a36f195ab42ec7bd11e963f
BUG=chromium-os:8901
TEST=Ran with prefix SimpleTest and ran whole suite for a vm using my latest built image. Also ran normal update test using latest image against latest dev channel image for mario. Re-tested with new changes after build break.
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=2b2d7a1
Review URL: http://codereview.chromium.org/6015013
Clobbering the builder uncovered a bug that was lurking.
Change-Id: Ieb487d2112a7048438943aa96fba23e9c8412a13
BUG=chromium-os:8693
TEST=Running now
Review URL: http://codereview.chromium.org/6050004
This CL also fixes the outstanding issue where to won't report progress in
image_to_live on updates.
Change-Id: I1efaf17f0fd5ebb367ae0872377b4d5d0bf5dbf6
BUG=chromium-os:8680,chromium-os:8901
TEST=Ran it with --debug on the x86 pfq locally.
Review URL: http://codereview.chromium.org/6135002
This reverts commit 2b2d7a1426.
The internal x86 buildbots have been reporting failures from
cros_au_test_harness with every build, starting with the build
that included the change being reverted.
BUG=chromium-os:8901
TEST=None
Review URL: http://codereview.chromium.org/5962019
Change-Id: Iac8c0a13d659f927b3ff61a9a894c10191432e2d
This cleanup code consolidates parsing of options, removes
globals, cleans up private vs. public functions, removes the backup full update option, and cleans up
docstrings.
Change-Id: I3eba26b3634fd87f4a36f195ab42ec7bd11e963f
BUG=chromium-os:8901
TEST=Ran with prefix SimpleTest and ran whole suite for a vm using my latest built image. Also ran normal update test using latest image against latest dev channel image for mario
Review URL: http://codereview.chromium.org/6015013
All blocking reasons for au test harness flakiness have been resolved. Removing try/catch from ctest so that we propagate the correct error code upon exit.
Change-Id: Iee1f09ade37ac7a590c2dbf4ebb96985818f1882
BUG=chromium-os:10434
TEST=Ran ctest unittests.
Review URL: http://codereview.chromium.org/5971009
Also some cleanup and fixing so we don't create unnecessary ebuilds.
I noticed that both the latest release and stable release code
were trying to rev the same branch whenever we moved to a new stable
version. It was harmless before but now that we're pushing this as
stable we want exactly to have the minimum number of revs that are
correct
Change-Id: I9f834d35be8e85c27ab0505ec81637f9a3c27b88
BUG=
TEST=Unittests and mocked in my own directory by creating new stable
branch.
Review URL: http://codereview.chromium.org/6025012
This deals with the condition where on a clobber we don't actually
re-config to use ssh:// until the second run (because git config is
called before we first sync the code).
Change-Id: Icf1a46aced633b570db9d280b10ae6866af04709
BUG=chromium-os:10545
TEST=Unit tests
Review URL: http://codereview.chromium.org/6027006
Change-Id: Ie80843a7b81a37b41ae19fc33244b5c0b8152282
BUG=chromium-os:10434
TEST=Ran it with full au test harness (still running but already showing promise).
Review URL: http://codereview.chromium.org/5988006
We had a major issue because the latest dev channel release pre-dates the virtio change. Because of this, ctest was connecting to update that channel using virtio (which is unsupported for that). This change drops a file telling the vm lib to use e1000 as before.
Also, fixed stateful change logic.
Change-Id: I394a8cece71bdd0d55efa21ba5b6d24804432c6b
BUG=chromium-os:10434
TEST=Ran it with ctest and cros_au_test_harness on images with/without the file.
Review URL: http://codereview.chromium.org/5928005
Since the package.keywords change, it's already built as part of build_packages.
With this change we don't have to needlessly build chrome twice as part of the
pfq.
Change-Id: I8dae745496a5d6f6213663b034ffe8d279d4efd3
BUG=chromium-os:8693
TEST=Ran unittests
Review URL: http://codereview.chromium.org/5973003
Change-Id: I42a6110d41e79bb0ad50817e2e76b06f7973f6c2
BUG=chromium-os:10434
TEST=Ran it with --test_prefix for delay payload test and it succeeded.
Review URL: http://codereview.chromium.org/5877007
Also add some more information output when we detect that there
is nothing to do.
Change-Id: Ia3dcf0d3c276e10d3368d6bd508f3a0d72be79cd
BUG=chromium-os:8693
TEST=Ran it with all 3 paramaters and current overlay.
Review URL: http://codereview.chromium.org/5884004
We also print to /dev/stderr directly to avoid flushing issues which have been occassionally given us broken manifests printed out
Change-Id: I97819bbc31142432aa5ef926f99f2c4f90fd50ef
BUG=chromium-os:9714
TEST=Ran cbuildbot through sync
Review URL: http://codereview.chromium.org/5888003
Change-Id: I2760e33e1473ce04f7adeda39d0db5725eaa81ae
BUG=chromium-os:7072
TEST=Replaced ./build_packages with bash and ran command; valided env var set right.
Review URL: http://codereview.chromium.org/5930002
Change-Id: I32c17e7353b420d7a895acffab4579c9b861095c
BUG=chromium-os:8693
TEST=Ran it with chrome_rev=tot, latest_release and stable_release
Review URL: http://codereview.chromium.org/5854001
This specifically gets the pfq one step closer to being completely ready to rev. We add --noprebuilts for the chrome pfq as its not ready to host prebuilts and instead we push unstable ebuilds. Anush noticed an Anush today where we are revving even when we don't change, and I've addressed this also in this CL.
Specifically:
1) Sort in cbuildbot long options by long format
2) Add --noprebuilts so that the Chrome PFQ can use this for now.
3) Fixed a unittest that had broken in a previous CL for cros_mark_chrome_as_stable.
4) Add ability for chrome to only rev if something really has changed:
-- This means, if the new ebuild either:
-- doesn't have the exact same chrome_version
-- or diff -Bu (actual diff) between last ebuild and new ebuild isn't the same (i.e. detecting a 9999 change or different CROS_SVN_COMMIT)
Change-Id: I9b289c2168d6868299573f5d7c7a676380ee497e
BUG=chromium-os:8693
TEST=Ran unittests (cbuildbot, cros_mark_*) and ran cbuildbot with new chrome pfq items.
Review URL: http://codereview.chromium.org/5783001
Change-Id: I1ac3ed12df00424ba5ba2d1c61fd6fe9716e13b9
BUG=chromium-os:9714
TEST=Ran new unittests as well as ran cbuildbot on local b/cbuild
Review URL: http://codereview.chromium.org/5689003
ability to filter or manipulate content as it's passed through.
Create two example tests using this utility that cause
updates to close early to test resumes, and to add delays
to make sure the update still completes correctly.
What other tests should be created for this?
BUG=chromium-os:8207
TEST=Run by hand
Review URL: http://codereview.chromium.org/5632002
Change-Id: Iefb8c8e223fb2ba6bad2c551f7c4403a0bec6ecf
This allows us to avoid deleting the board and still ensure our packages are
in sync with the full buildbot. This allows us to detect conflicts between
old and new packages.
BUG=chromium-os:10127
TEST=Run cbuildbot.py with emptytree feature forced to on and verify that
build_packages rebuilds all packages. Also run unit tests.
Change-Id: I83e186937e28eef44285724697895a4583910b58
Review URL: http://codereview.chromium.org/5652007
Adds verbose flag to print output while updates are running rather than on error.
Adds test_prefix to specify a prefix of tests you want to run
Flushes stderr more reliably for builders and debugging purposes
Dies when stateful_updates fail
Change-Id: I9e4289deec3688c52b92763eee9334a8868f948e
BUG=chromium-os:6910
TEST=Ran with test_prefix and verbose on and off
Review URL: http://codereview.chromium.org/5573007
Change-Id: I0dda2cfb6e11cb69a6a1a6a4bae478cab78b8947
BUG=chromium-os:8693
TEST=Ran it with cros_mark_chrome with stable_release
TBR=Config change to get chrome builder up.
I started to use /tmp, but it doesn't exist both inside and outside of the chroot. Using a consistent name like this has the advantage that the files will be cached and not redownloaded every time. Well, except on the build servers that wipe the related directories between builds.
Change-Id: I58b42d9f1bd18cc4eb44043ed2436d4ffa482767
BUG=chromium-os:10012
TEST=
Review URL: http://codereview.chromium.org/5597004
Chrome PFQ right now is uploading prebuilts which wasn't meant to happen :(
Change-Id: I502a0621a6c9f655e5a3f890dd79e00652925902
BUG=chromium-os:8693
TEST=Ran cbuildbot with --debug
Review URL: http://codereview.chromium.org/5595004
Also, fixed to honour external FEATURES for the install case.
BUG=n0ne
TEST=Built a kernel with this CL.
Change-Id: I17d50cc382b297766761f12d47a555630fedc016
Review URL: http://codereview.chromium.org/5530004
Change-Id: Ia94f1c983aec533fc2813f9c300266d394b8ee7c
BUG=chromium-os:9946
TEST=Ran ctest and saw through the download and start of the test harness
Review URL: http://codereview.chromium.org/5628002
Add two new tests that test update-engine handling of a corrupted image,
or a truncated image.
BUG=chromium-os:9502
TEST=Ran against Dell L13, Mario
Review URL: http://codereview.chromium.org/5373008
Change-Id: Ie1043004f01131ea837798c06327c486e1901c15
We also fix some of the configs for existing configurations.
Change-Id: I34baa9664ff9e91268c8bac976ab2ab0aee51bfb
BUG=chromium-os:9714
TEST=Running now with cbuildbot x86-generic-pre-flight-queue.
Review URL: http://codereview.chromium.org/5531002
BUG=chromium-os:9877
TEST=ran bin/cros_workon_now, cros_workon, set_shared_user_password
Note---this introduces another bashism to common.sh. However, despite
comments to the contrary, common.sh does not actually parse under dash
without this change
Change-Id: I1e6b9751afa8341c100f3b8e0b96284835a53d17
Review URL: http://codereview.chromium.org/5444002
If a board has a public overlay it will be used as the primary overlay. However, with this change, if a board only has a private overlay it will be used as the primary.
BUG=7339
TEST=Ran setup_board, build_packages, and build_image on a board with only a private overlay (locally created). Ran setup_board, build_packages, and build_image on a board with both public and private overlays.
Change-Id: Ic56e4951272ddb80511a213e3a2e54419267a49a
Related Issues:
http://codereview.chromium.org/3544009http://codereview.chromium.org/3571015
Review URL: http://codereview.chromium.org/3622003
Preflight prebuilts reference the last full build, so they should always be complete as long as the last full build is still there.
Also add host prebuilts to the preflight prebuilts.
BUG=chromium-os:5311
TEST=Run unit tests for cbuildbot and prebuilt.py. Test runs of cbuildbot.py with --dryrun.
Review URL: http://codereview.chromium.org/5344002
Change-Id: Id95f94c02cc2f6cbd70a029d4f8b94617b7cc071
This change updates cbuildbot.py to upload prebuilts and reference them via PREFLIGHT_BINHOST.
Also ensure make.conf ends in a newline, as it looks nicer.
BUG=chromium-os:5311
TEST=Test that prebuilt.py updates PREFLIGHT_BINHOST in right make.conf
file. Test that cbuildbot.py runs prebuilt.py with right
arguments. Run unit tests for cbuildbot and prebuilt.py. Test runs of cbuildbot.py with --dryrun. Test upload of Packages file to local web server and check that emerge works with them.
Change-Id: Iad03c6c469e05b9ee1cceff69cbe2bdd51225e25
Review URL: http://codereview.chromium.org/4969003
BUG=9717
TEST=run cros_workon_make --scrub and ensure that it only scrubs if the user types y or yes (case insensitive)
Change-Id: Ic1f8020fcca8bd57924391fcbf075d3e2adc5e4a
Review URL: http://codereview.chromium.org/5265009
cros_workon_make provides a make-style interface to incrementally building
cros_workon-enabled packages, appropriately setting up the toolchain for
the target board beforehand.
To incrementally build your package:
cros_workon_make --board <board> <package>
To re-run your package's configure steps and compile:
cros_workon_make --board <board> <package> --reconf
To incrementally build your package and tests, and run the tests:
cros_workon_make --board <board> <package> --tests
To incrementally build and install your package:
cros_workon_make --board <board> <package> --install
To remove ALL files in your package repo not known by git:
cros_workon_make --board <board> <package> --scrub
With the exception of --scrub, these flags all compose
BUG=6843
TEST=build workon packages in place
Change-Id: Ie219074127549e1e29adad6d6a03142ab74e0172
Review URL: http://codereview.chromium.org/5244001
This also removes the rw_checkout var as it's not longer changes the affect of whether we use the ssh url or not.
Note that this replaces the other CL from last night because the other CL didn't work. The other CL still pulled in the same manifest that has http: url's for each git repo. I reverted that change last night after I noticed this.
Change-Id: I3d4ad2be6887ac2cf4ed2009bad9cae6dfdf5bbf
BUG=chromium-os:9509
TEST=Ran with cbuildbot --clobber and incremental
Review URL: http://codereview.chromium.org/5278010
Other things:
Removing commit|clean|push command from cros_mark_chrome because it's unnecessary ... I'm just gonna use the same stabilizing branch as the other stable marker, so I can use the same clean / push from the other script. This makes this change fit in much more nicely to cbuildbot.
Other changes:
Add ability for cros_mark_chrome_as_stable to communicate to calling script through stdout.
Make STABLE_BRANCH in cros_mark_as_stable public for above reason.
Removed push_options from cros_mark and accompanying change to cbuildbot as it isn't used anymore.
Made it easier to debug with cbuildbot (I ran cbuildbot A LOT of times to test this change so I felt the pain)...this includes:
- only build when syncing
- allow one to explicitly disable tests
- use dryrun is options.debug is set
Change-Id: I413a2e81a99cdde2e4d9139561cd518245b9b346
BUG=chromium-os:8693
TEST=Ran cbuildbot with --notest --debug --nosync x86-pre-flight and
saw it go through correctly and dryrun push. Ran cbuildbot with same and --chrome_rev=tot. Ran with syncing and running tests too.
Review URL: http://codereview.chromium.org/5154008
This is a complement to the proposed fix for http://crosbug.com/9447, and I am getting it out first since it is a relatively simple change.
This change ensures that the rootfs on the image output by cros_make_image_bootable wasn't corrupted accidentally (for example, no boot.desc was provided and the defaults were incorrect for the image). This should catch rootfs errors that we end up discovering at delta AU time.
BUG=chromium-os:9578
TEST= Ran cros_make_image_bootable manually on an existing image with and without boot.desc. As expected, without boot.desc the output image rootfs had errors.
Also ran ./build_image - which worked fine too.
Change-Id: I4ed3a56634f37ab7d5ff2dc052ad607740356a40
Review URL: http://codereview.chromium.org/5216003
Change-Id: I680e28bcafbfeb4f19e2404e2b28761e26111f7f
BUG=chromium-os:9509
TEST=Ran cbuildbot on my local builder checkout with both clobber and without.
It sync'd and built.
Review URL: http://codereview.chromium.org/5312002
added --test option
removed superfluous output (e.g. from dd) unless --verbose given
added --debug option for when you really want that output
added use of pv for a nice progress bar
TEST=(run script several times)
BUG=chromium-os:9563
Change-Id: Ib9d89ad5649b6cb6d5db35f66f6a3fda1ada0c53
Review URL: http://codereview.chromium.org/5176002
Change-Id: I6744aac09fb075f91f710f16343fab45b8dc8af9
BUG=chromium-os:7283
TEST=Ran it with cbuildbot through the unit tests phase and looked
at the file and saw it get parsed correctly.
Review URL: http://codereview.chromium.org/5124006
Have subsequent review for cbuildbot that calls this for the pfq.
This module has 3 modes ... TOT, latest_release, sticky_release that describe the three different types of revs for chrome we will be supporting.
For tot, we grab the latest svn revision # from the chrome src tree, and rev to the corresponding ebuild i.e. 9.0.553.0_alpha-r1 with CROS_SVN_COMMIT=svn revision number.
For latest_release, we grab the latest release from the releases page, and create an ebuild (or rev a previously existing on with same version) and use the release candidate suffix _rc.
For sticky_release, we use much of the same logic as latest_release, however, we specifically look to rev _rc's in the sticky branch.
This change depends on http://codereview.chromium.org/5172003 for the cros_mark_as_stable changes.
Change-Id: Idc1f4cd905cc1dcb4c44422f6104760077a24b8d
BUG=chromium-os:8693
TEST=Ran cros_mark_as_stable with --packages="chromeos-base/chromeos-chrome" --chrome_version=0.8.65.0 --chrome_revision=67890 commit. Re-ran unit-tests as well (though thinking about adding another unit test for chrome revving)
Review URL: http://codereview.chromium.org/4798001
This would not have been a problem if "--no_graphics" is used.
Change-Id: I3645391d25d4bb8618109ff5be0ca2fbe8e96a60
BUG=chromium-os:9373
TEST=Ran by hand
Review URL: http://codereview.chromium.org/5104006
Preflight clean needs to wait until after the checkout happens before
it asserts that all of our overlays exist.
BUG=chromium-os:9197
TEST=Ran cbuildbot.py with missing chromiumos-overlay dir
Change-Id: If66574f01d1e85741e971919a9fa2da34f85872d
Review URL: http://codereview.chromium.org/5069001
Change-Id: I34e9d64656e04d4f5c477914512219d9b8563b78
BUG=chromium-os:9137
TEST=Ran with both wrong and right versions against a Google Chrome and
Chromium build
Review URL: http://codereview.chromium.org/4942001
What's new?
- cros_mark_as_stable now exits with errors if directories are specified
that don't exist.
- cbuildbot.py always explicitly specifies overlay directories so
cros_mark_as_stable can rely on them existing.
- Package names and paths are now separated with colons instead of
spaces, so as to allow for us using the same syntax with
enter_chroot.sh as we use without the same script. (enter_chroot.sh
mucks with command-lines that contain spaces or quotes.)
- cbuildbot.py now ensures its build path is a absolute path. This ensures we don't kill the wrong processes, if, for instance, the buildpath is '../..'
- All buildbots now explicitly specify what overlays they want to rev. Public buildbots only rev public ebuilds and private buildbots now only rev private ebuilds.
BUG=chromium-os:8647
TEST=Ran unit tests. Manually marked packages as stable. Ran cbuildbot.py test run.
Change-Id: I1df6d428973d91329c4f5159e2886889a3ebb7c7
Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=795bd30
Review URL: http://codereview.chromium.org/4442001
What's new?
- cros_mark_as_stable now exits with errors if directories are specified
that don't exist.
- cbuildbot.py always explicitly specifies overlay directories so
cros_mark_as_stable can rely on them existing.
- Package names and paths are now separated with colons instead of
spaces, so as to allow for us using the same syntax with
enter_chroot.sh as we use without the same script. (enter_chroot.sh
mucks with command-lines that contain spaces or quotes.)
- cbuildbot.py now ensures its build path is a absolute path. This ensures we don't kill the wrong processes, if, for instance, the buildpath is '../..'
- All buildbots now explicitly specify what overlays they want to rev. Public buildbots only rev public ebuilds and private buildbots now only rev private ebuilds.
BUG=chromium-os:8647
TEST=Ran unit tests. Manually marked packages as stable. Ran cbuildbot.py test run.
Change-Id: I1df6d428973d91329c4f5159e2886889a3ebb7c7
Review URL: http://codereview.chromium.org/4442001
