df623616c0857ee1556bcb86b7495a5f5e928715: scripts: add script to count pushes to repositories
Gregory Szorc <gps@mozilla.com> - Mon, 18 May 2015 09:39:45 -0700 - rev 360799
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
scripts: add script to count pushes to repositories Laura wanted this data. The script is hacky but gets the job done.
58298b34d99184cccdc916f0eeade9545e00c0ce: Bug 1139661 - mozreview: Fix link to BMO in error report. r=smacleod
Mark Cote <mcote@mozilla.com> - Fri, 15 May 2015 14:09:05 -0400 - rev 360798
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
Bug 1139661 - mozreview: Fix link to BMO in error report. r=smacleod
b13a2fe9629426d599f9f1f09eae5b653cf1faa8: testing: log in newly-created Bugzilla users (bug 1164688); r=smacleod
Gregory Szorc <gps@mozilla.com> - Thu, 14 May 2015 18:55:42 -0700 - rev 360797
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
testing: log in newly-created Bugzilla users (bug 1164688); r=smacleod Bugzilla recently made it so users with no activity in the past 60 days can't have review flags aimed at them. See bug 751862. We change the user creation code to log in the user by default to simulate Bugzilla activity. This is easier than modifying every test to touch newly-created users. This required a bit of refactoring to make the login code reusable.
59613029d885395890ee7b2ec46d24197d809786: ansible: add variable for djblets and review board package versions
Gregory Szorc <gps@mozilla.com> - Thu, 14 May 2015 14:11:54 -0700 - rev 360796
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
ansible: add variable for djblets and review board package versions
35943d03d552850615996491439094ff84c3c423: MozReview: Upgrade to Review Board 2.0.15 (Bug 1160176)
Steven MacLeod <smacleod@mozilla.com> - Fri, 08 May 2015 12:39:03 -0400 - rev 360795
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
MozReview: Upgrade to Review Board 2.0.15 (Bug 1160176) Review Board site upgrades print any manual steps after "Upgrade Complete!". During deploy print site upgrade stdout when "Upgrade Complete!" is not the last line of site upgrade.
9c9ca67d516e13d563811b5b41ca37a477674f72: MozReview: Disable RBTools API caching to avoid errors (Bug 1160176)
Steven MacLeod <smacleod@mozilla.com> - Fri, 08 May 2015 13:50:00 -0400 - rev 360794
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
MozReview: Disable RBTools API caching to avoid errors (Bug 1160176) RBTools 0.6.1 has known bugs in its API cache implementation. Some newer Review Board versions (e.g. 2.0.15) cause our tests to fail with errors from the RBTools API cache. Temporarily disable the API cache until we can upgrade to a newer (currently unreleased) version of RBTools and better investigate the cache problems.
ff62918a290ef6cb216f97b089d549c941e9287a: testing: add a decorator to restart MozReview between test methods
Gregory Szorc <gps@mozilla.com> - Tue, 12 May 2015 09:31:57 -0700 - rev 360793
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
testing: add a decorator to restart MozReview between test methods This was requested by mdoglio. While we were here, MozReview cluster instances now track their state and prevent simultaneous starts. This should help prevent a footgun where people could start multiple instances of a cluster, completely confusing state.
3e2bcf0d8fd5a4024df497228f529382943bddef: testing: add --use-last-tests to run-tests to make tests run faster
Gregory Szorc <gps@mozilla.com> - Tue, 12 May 2015 08:52:41 -0700 - rev 360792
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
testing: add --use-last-tests to run-tests to make tests run faster Generating Docker images on every test run adds considerable overhead, especially when developing and debugging tests. In many scenarios, the images won't have changed and generating new images just adds overhead. Add an option to recycle images from last time. This option is a footgun. A lot of files are copied to containers/images. Improper use could result in changes not taking effect in the test environment. Use with caution. On my machine, this reduces test start overhead from 20-25s to ~4s.
e586fce43a3ec4f528eb39ae2cf24ac386902bb2: Reverting accidental checkin.
Mark Cote <mcote@mozilla.com> - Mon, 11 May 2015 22:33:33 -0400 - rev 360791
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
Reverting accidental checkin.
e971c9bbe39dcc555e4a0327ae723aa756f78bcd: Bug 1055021 - mozreview: Prevent ship-its in the UI from parent review requests. r?smacleod
Mark Cote <mcote@mozilla.com> - Wed, 06 May 2015 15:38:49 -0400 - rev 360790
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
Bug 1055021 - mozreview: Prevent ship-its in the UI from parent review requests. r?smacleod The required hook isn't yet available in Review Board, so this just uses CSS rules to hide the ship-it options.
648c6c611469e3bf284511fc33f81fee03227158: Bug 1055021 - mozreview: Create attachments for all children. r?smacleod
Mark Cote <mcote@mozilla.com> - Thu, 19 Mar 2015 23:09:15 -0400 - rev 360789
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
Bug 1055021 - mozreview: Create attachments for all children. r?smacleod An attachment is now created on Bugzilla for each child. No attachment is created for the parent. Review logic has changed a bit as well. For children, a ship-it results in an r+ on the corresponding attachment from the reviewer. A review with no ship-it clears any '?' review flag with the requestee being the reviewer, and any '+' with the setter being the reviewer. For parents, reviews with ship-its are not allowed, and the corresponding UI functions have been removed. A review with no ship-it results in a comment unassociated with any attachment, and no flag changes.
3f8db281d1c63c5a55c4811efb4fe1f5b4027635: Bug 1055021 - mozreview: Include reviewer BMO ids in summary API. r?smacleod
Mark Cote <mcote@mozilla.com> - Mon, 27 Apr 2015 13:35:27 -0400 - rev 360788
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
Bug 1055021 - mozreview: Include reviewer BMO ids in summary API. r?smacleod
1b71828c5e1e13f34bbd252e21d6d2673b422fa6: mqext: make 'reviewers' and 'components' accept revisions (bug 1160440) r=gps
Xidorn Quan <quanxunzhen@gmail.com> - Fri, 01 May 2015 18:24:22 +1200 - rev 360787
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
mqext: make 'reviewers' and 'components' accept revisions (bug 1160440) r=gps
d8c81dea6ffa1191f336120d95005205426320ce: testing: support Ubuntu Ansible containers
Gregory Szorc <gps@mozilla.com> - Thu, 07 May 2015 20:29:40 -0700 - rev 360786
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
testing: support Ubuntu Ansible containers We want to use Ansible inside Ubuntu containers. Create a base image for it.
bf7af9ac79d59ea2b5970dc9d1b5b7d36fef5d4e: autoland: autoland should strip draft revisions after pushing to try (bug 1159822) r=gps
Dan Minor <dminor@mozilla.com> - Wed, 06 May 2015 16:09:06 -0400 - rev 360785
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
autoland: autoland should strip draft revisions after pushing to try (bug 1159822) r=gps If we don't strip draft revisions, we'll end up with many, many heads that will eventually make mercurial unhappy.
06a663b3df63043c87ee2fa6b042e4ba7cd14937: testing: properly unicode handling when writing xunit report (bug 1141720)
Gregory Szorc <gps@mozilla.com> - Thu, 07 May 2015 19:49:03 -0700 - rev 360784
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
testing: properly unicode handling when writing xunit report (bug 1141720) This is essentially 7b0a20cd8c95 from upstream, which is a patch I contributed to Mercurial after this was reported at Mozilla.
268c7489b8ff94ac36ad68ec3812746b1ef0f306: add explicit support for Mercurial 3.4 (bug 1162304); r=smacleod
Gregory Szorc <gps@mozilla.com> - Thu, 07 May 2015 09:57:37 -0700 - rev 360783
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
add explicit support for Mercurial 3.4 (bug 1162304); r=smacleod Mercurial 3.4 was released a few days ago on May 1. We need to advertise Mercurial 3.4 support in extensions or Mercurial may think the extension is incompatible. Do it. A test run verifies that extensions continue to work with Mercurial 3.4.
3a5abff4a80b20fc9f34c7aea2fb6a1ab3f09238: drop explicit support for Mercurial 3.0 (bug 1162304); r=smacleod
Gregory Szorc <gps@mozilla.com> - Wed, 06 May 2015 16:40:00 -0700 - rev 360782
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
drop explicit support for Mercurial 3.0 (bug 1162304); r=smacleod Mercurial 3.0 is now over a year old. People have had plenty of time to upgrade to 3.1 or newer. We're about to introduce official support for 3.4. So if nothing else, let's drop 3.0 support so we're testing on one less configuration.
bbf29965c039a9da99e63a1a44561a90db0943c8: MozReview: Stop generating parent diffs (Bug 1159860); r?gps
Steven MacLeod <smacleod@mozilla.com> - Tue, 05 May 2015 17:56:04 -0400 - rev 360781
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
MozReview: Stop generating parent diffs (Bug 1159860); r?gps MozReview requires parent diffs be generated and uploaded when the repository Review Board is configured with does not contain the commit a diff is based on. Review Board will always be pointed at the review repository itself meaning it will contain the base commit for every diff (squashed and commit) - parent diffs are not needed. Stopping the use of parent diffs has the following effects: - MozReview to use less space in the database (*Much* less in requests with many commits as every commit parent diff contains the commits before it). - Diff application and generation is faster - 1/2 to 2/3 as many applications are required and diff sizes are smaller. - MozReview requires more requests to the hg server to fetch base files. Using parent diffs the same base files are used for every request, without them each commit request has it's own base commit and files modified in several commits will not be cached (Fetched files are cached by sha/filename). Also, provide a base_commit_id with each diff. Default diffs generated by hg include information about revisions the diff is generated between but git style diffs do not. Starting in version 2.0.16, Review Board will properly parse git style diffs and take base_commit_id into account. Switching to git style diffs will require this base_commit_id be provided. Alternatively "hg export" style headers could be included in diffs to tell Review Board which commit to use as a base - this is unnecessarily complex as the same Review Board version which supports git diffs fixes base_commit_id support.
be64a5962d6e4d49617778ec12fb176c85f443f7: MozReview: Allow specifying base_commit_id and make parent_diff optional (Bug 1159860). r?gps
Steven MacLeod <smacleod@mozilla.com> - Tue, 05 May 2015 12:58:06 -0400 - rev 360780
Push 16998 by rwood@mozilla.com at Mon, 02 May 2016 19:42:03 +0000
MozReview: Allow specifying base_commit_id and make parent_diff optional (Bug 1159860). r?gps In future releases of Review Board base_commit_id will be respected by the mercurial SCMTool allowing us to properly set a diffs base. We now allow specifying the base_commit_id as part of the commits structure passed to post_reviews(). Parent diffs are also made optional. Originally they were mandatory since Review Board was going to point at the mainline repository, rather than the review repository - meaning we could not apply just the desired diff as the base was unknown to Review Board. In reality Review Board is pointing at the review repo itself, which will be mandatory going forward.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 +300000 tip