b5ef57fbc090e7e4d03189181478844e268c41fb: ansible/docker-hg-reviewboard: run syslog from supervisor
Gregory Szorc <gps@mozilla.com> - Fri, 19 Aug 2016 19:51:13 -0700 - rev 690889
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
ansible/docker-hg-reviewboard: run syslog from supervisor This is how we run all other services inside Docker containers. I think this stems from a day before we had supervisor running inside the container as pid 1. MozReview-Commit-ID: 3uI0WJzcRFt
c21c4b21ee1541d2797848d20414936e68d6ca5f: testing: pin BMO commit to work around environment bustage (bug 1298524)
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 15:01:28 -0700 - rev 690888
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
testing: pin BMO commit to work around environment bustage (bug 1298524) docker/generate_bmo_data.pl was removed by the commit after this pinned commit, breaking our Docker environment. As a temporary stop-gap to fix the environment, pin the commit. As part of this, we had to revert back to a non-shallow clone otherwise there is no guarantee the Git repo has the commit in question. I didn't want to bloat scope to change `git fetch` to "unshallow" the local clone.
db3c32a309e6fb30fd2581ba51c981f3a414bae0: docs: document how to create new Mercurial packages
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 14:25:55 -0700 - rev 690887
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
docs: document how to create new Mercurial packages As part of upgrading hg.mozilla.org to Mercurial 3.9, I'll be documenting how we perform the upgrade so people not me know how to do upgrades. We start with the process for building and uploading new Mercurial RPMs and .deb packages.
8c091e93fbe9c1f19cc54f10cdcc069f11775d8b: testing: remove support for generating Mercurial RPMs
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 13:51:05 -0700 - rev 690886
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
testing: remove support for generating Mercurial RPMs Mercurial now has make targets for building RPMs inside Docker containers. It is basically identical to what we were doing. We don't need this logic ourselves.
ad6728a23f3f06ce1ad91737296f60ea05ef542d: ansible/hg-ssh: stop populating firefox-unified-b2g repo (bug 1292333)
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 12:11:35 -0700 - rev 690885
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
ansible/hg-ssh: stop populating firefox-unified-b2g repo (bug 1292333) The b2g repos aren't being updated. Stop populating them. MozReview-Commit-ID: 1dpGqy3crPH
3a5b7a64957bfc6ea4eecee4f5024ae5571d48d6: ansible/hg-ssh: stop populating the experimental/firefox-unified repo (bug 1292333)
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 12:10:14 -0700 - rev 690884
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
ansible/hg-ssh: stop populating the experimental/firefox-unified repo (bug 1292333) mozilla-unified should be used instead. MozReview-Commit-ID: 3Y3azs7bjvf
188f7e2f4f090b0a145a5b435a2352af4eb212d2: ansible/hg-ssh: stop generating bundles for experimental/firefox-unified (bug 1292333)
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 12:07:26 -0700 - rev 690883
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
ansible/hg-ssh: stop generating bundles for experimental/firefox-unified (bug 1292333) In preparation for deleting the repo. mozilla-unified is the repo people should be using. MozReview-Commit-ID: 8G0J9PfSCOZ
8fb7ba23977ca5dc978838d5a3466ebaec879924: docs: change naming from "firefox-unified" to "firefox"
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 12:13:47 -0700 - rev 690882
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
docs: change naming from "firefox-unified" to "firefox" Some of these examples were flat out wrong. Probably a search and replace gone wrong. MozReview-Commit-ID: KbKL5OSrpS7
f23dd5a385aa099ff74e395b2b2892abbd7d78ad: hgmo: handle obsolete changesets in automationrelevance endpoint
Gregory Szorc <gps@mozilla.com> - Mon, 18 Jul 2016 16:45:08 -0700 - rev 690881
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: handle obsolete changesets in automationrelevance endpoint The json-automationrelevance endpoint is queried by automation to obtain information on changesets relevant to the current revision being built. Because automation may not start immediately after a push was made, automation may query a changeset that has since become hidden. For most APIs, this would issue a 404 because hidden changesets are, well, hidden and as good as not existing. However, for hidden changesets referenced by the pushlog, we've decided to expose their information to automation so it can make intelligent decisions. This commit allows the automation relevance endpoint to return information about hidden changesets. MozReview-Commit-ID: 3JmQT3LQU3p
5ab39b6d8119a388247ab2f17157709932b5822e: hgmo: advertise visibility of requested revision in automationrelevance
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 11:38:23 -0700 - rev 690880
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: advertise visibility of requested revision in automationrelevance In case downstream consumers want to fail fast when querying hidden changesets.
97c03930b9efe6d07b5ca9f11701782930baed2e: hgmo: assign output to variable
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 11:34:27 -0700 - rev 690879
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: assign output to variable To make upcoming commit smaller.
5437c8537b34a4f749421596a4aeb6546288dadf: hgmo: remove trailing whitespace from automationrelevance output
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 11:29:07 -0700 - rev 690878
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: remove trailing whitespace from automationrelevance output
600f6d343f7616f52c6c2638a5effffc5f29cd64: hgmo: remove unused variable
Gregory Szorc <gps@mozilla.com> - Wed, 29 Jun 2016 15:09:21 -0700 - rev 690877
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: remove unused variable Not sure how this happened. It cuts down on redundant parsing work, yay. MozReview-Commit-ID: Bo54Zldci43
b07676904c79de24c2051fddd77e9848d64d2b77: hgmo: decode description and reuse variable
Gregory Szorc <gps@mozilla.com> - Wed, 29 Jun 2016 15:08:22 -0700 - rev 690876
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgmo: decode description and reuse variable ctx.description() is a mercurial.encoding.localstr. This is a str like type that is encoded to Mercurial's active encoding (which is likely utf-8 in our server environment). By using encoding.fromlocal() we get the raw bytes of the commit message. This is what we should be using in case there are any weird character sequences that get normalized by local encoding. In addition, ctx.description() has some overhead associated with it. So we save the description into a local variable to avoid having to do redundant work. MozReview-Commit-ID: LKrHSJWo64h
ed49c31688fd692980c00660828f7d5ea89ab214: ansible: synchronize AWS IP ranges with upstream
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 10:13:08 -0700 - rev 690875
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
ansible: synchronize AWS IP ranges with upstream
fba5ad7f33db1de287e44588bda4847bfeedece3: configwizard: attempt to fix test-multiple-vct.t failure in Jenkins (bug 1295754)
Gregory Szorc <gps@mozilla.com> - Fri, 26 Aug 2016 10:03:01 -0700 - rev 690874
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
configwizard: attempt to fix test-multiple-vct.t failure in Jenkins (bug 1295754) This is a shot in the dark. Let's hope it works.
70aeab089f3cbac4b0c4a772094d550f274579e8: pushlog: add pushid(N) and pushrev(set) revsets (bug 1295780); r=glandium
Gregory Szorc <gps@mozilla.com> - Tue, 16 Aug 2016 15:42:34 -0700 - rev 690873
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
pushlog: add pushid(N) and pushrev(set) revsets (bug 1295780); r=glandium We add support for querying for changesets based on their push id (find changesets in push X) and for changesets in the same push as a changeset. MozReview-Commit-ID: 33s1zUtg7SH
94499c5c9bf7fa8697b2aa063ea87c2bcaf57c83: pushlog: extract code for obtaining a Push from a push ID; r=glandium
Gregory Szorc <gps@mozilla.com> - Thu, 25 Aug 2016 12:46:44 -0700 - rev 690872
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
pushlog: extract code for obtaining a Push from a push ID; r=glandium MozReview-Commit-ID: 5AK0Zcv6xLq
cd3ea93bb4788acf2d87a055ae8c80d3d0e35c5f: pushlog: use decorators to register revset predicates; r=glandium
Gregory Szorc <gps@mozilla.com> - Wed, 17 Aug 2016 10:46:57 -0700 - rev 690871
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
pushlog: use decorators to register revset predicates; r=glandium This is the preferred way to register revsets in Mercurial 3.7+. MozReview-Commit-ID: 5QUvVR5spWM
c27cf7ecef4bdb13677aa82a445c28d3d386bc55: hgserver: support monitoring pulse from test environment
Gregory Szorc <gps@mozilla.com> - Thu, 25 Aug 2016 16:42:37 -0700 - rev 690870
Push 87314 by gszorc@mozilla.com at Thu, 02 Nov 2017 02:08:10 +0000
hgserver: support monitoring pulse from test environment This will be used by a subsequent test.
(0) -300000 -100000 -30000 -10000 -3000 -1000 -300 -100 -50 -20 +20 +50 +100 +300 +1000 +3000 +10000 +30000 +100000 tip