This is an automated email from the ASF dual-hosted git repository.
jan pushed a change to branch jenkins-re-add-macos
in repository https://gitbox.apache.org/repos/asf/couchdb.git
discard 9d9b09ab1 undebug various bits
discard a9045aef4 wip: workaround brew output bug
discard e0323a186 debug: brew prefix seems to be wonky
discard 4db7f899b debug: rebar -vv throws printing badmatch
discard 4ce16e4d8 wip: maybe speed up packaging stage
discard bb73ccd31 debug: enable verbose logging for rebar compile
discard 6277bcab5 debug: print env
discard c72dcc6f0 fix: no spidermonkey for macos
discard 2667e5d43 wip: enable only mac CI
add 18d628904 feat: speed up "build release tarball" stage by compiling on
4 cores
add de65571a4 fix: re-enable macOS worker and fix homebrew regression
add 94c0e158f feat: run make eunit with -j4 parallelism
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (9d9b09ab1)
\
N -- N -- N refs/heads/jenkins-re-add-macos (94c0e158f)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
build-aux/Jenkinsfile | 268 +++++++++++++++++++++++++-------------------------
1 file changed, 133 insertions(+), 135 deletions(-)