Remove unused .github directories
They were valid until the switch to the "monorepository" when everything was merged into a single Git repository.
This commit is contained in:
Jean-Sébastien Pédron
parent
5b8dba5e2f
commit
47686ee1f0
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,404 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow
|
||||
name: "Test - Erlang 21.3"
|
||||
on:
|
||||
push:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- new-commit-to-dep-release-branch
|
||||
jobs:
|
||||
# vim:sw=2:et:
|
||||
checks:
|
||||
name: checks
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 21.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CHECK RABBITMQ COMPONENTS
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
make check-rabbitmq-components.mk base_rmq_ref=master current_rmq_ref=$branch_or_tag_name
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: RESOLVE & COMPILE DEPS
|
||||
run: |
|
||||
make deps test-deps base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
echo "Capture versions of the RabbitMQ components used in this workflow..."
|
||||
make amqp10_client-rabbitmq-deps.mk
|
||||
mv amqp10_client-rabbitmq-deps.mk deps/
|
||||
echo "Remove directories not used in the subsequent jobs..."
|
||||
rm -fr deps/*/{.git,test}
|
||||
- name: UPLOAD DEPS VERSIONS
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
with:
|
||||
name: amqp10_client-rabbitmq-deps.mk
|
||||
path: deps/amqp10_client-rabbitmq-deps.mk
|
||||
- name: CHECK CROSS REFERENCES
|
||||
run: |
|
||||
make xref base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: COMPILE FOR TEST
|
||||
run: |
|
||||
make test-build base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-21.3-rev3
|
||||
- name: PREPARE SECONDARY UMBRELLA COPIES
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
run: |
|
||||
# ----------------------------------------------------------
|
||||
# CAUTION:
|
||||
# The same script must be copied to `03-CT_SUITE.yaml`. It is used to
|
||||
# recreate the umbrellas if the cache restore fails.
|
||||
# ----------------------------------------------------------
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
# vim:sw=2:et:
|
||||
dialyzer:
|
||||
name: dialyzer
|
||||
needs: [checks]
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
if: success() && 'oldest' == 'latest'
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
if: success() && 'oldest' == 'latest'
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 21.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
if: success() && 'oldest' == 'latest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: CACHE DIALYZER PLT
|
||||
if: success() && 'oldest' == 'latest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: .amqp10_client.plt
|
||||
key: plt-amqp10_client-erlang-21.3-g${{ github.sha }}
|
||||
- name: RUN DIALYZER
|
||||
if: success() && 'oldest' == 'latest'
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make dialyze \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL=
|
||||
# vim:sw=2:et:
|
||||
eunit:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: eunit
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 21.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
! test -d ebin || touch ebin/*
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make eunit \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
# vim:sw=2:et:
|
||||
ct-msg:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-msg
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 21.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
make ct-msg \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-21.3-rev3
|
||||
- name: VERIFY SECONDARY UMBRELLA COPIES (in case of cache restore failure)
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-msg \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS=
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-msg-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
# vim:sw=2:et:
|
||||
ct-system:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-system
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 21.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
make ct-system \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-21.3-rev3
|
||||
- name: VERIFY SECONDARY UMBRELLA COPIES (in case of cache restore failure)
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && 'oldest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-system \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS=
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-system-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
# vim:sw=2:et:
|
||||
capture-tested-deps-versions:
|
||||
needs:
|
||||
- dialyzer
|
||||
- eunit
|
||||
- ct-msg
|
||||
- ct-system
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-21.3_git-${{ github.sha }}_deps
|
||||
- name: FORMAT GIT REF
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
- name: UPLOAD TO S3
|
||||
if: github.ref == 'refs/heads/master'
|
||||
# https://github.com/marketplace/actions/s3-file-upload
|
||||
uses: zdurham/s3-upload-github-action@master
|
||||
env:
|
||||
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
|
||||
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
|
||||
AWS_REGION: ${{ secrets.AWS_REGION }}
|
||||
FILE: deps/amqp10_client-rabbitmq-deps.mk
|
||||
S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
|
||||
S3_KEY: rabbitmq-amqp1.0-client/${{ steps.ref.outputs.branch_or_tag_name }}/${{ github.run_id }}/otp-21.3/amqp10_client-rabbitmq-deps.mk
|
||||
|
|
@ -1,404 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow
|
||||
name: "Test - Erlang 22.3"
|
||||
on:
|
||||
push:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- new-commit-to-dep-release-branch
|
||||
jobs:
|
||||
# vim:sw=2:et:
|
||||
checks:
|
||||
name: checks
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 22.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CHECK RABBITMQ COMPONENTS
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
make check-rabbitmq-components.mk base_rmq_ref=master current_rmq_ref=$branch_or_tag_name
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/caching-dependencies-to-speed-up-workflows
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: RESOLVE & COMPILE DEPS
|
||||
run: |
|
||||
make deps test-deps base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
echo "Capture versions of the RabbitMQ components used in this workflow..."
|
||||
make amqp10_client-rabbitmq-deps.mk
|
||||
mv amqp10_client-rabbitmq-deps.mk deps/
|
||||
echo "Remove directories not used in the subsequent jobs..."
|
||||
rm -fr deps/*/{.git,test}
|
||||
- name: UPLOAD DEPS VERSIONS
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
with:
|
||||
name: amqp10_client-rabbitmq-deps.mk
|
||||
path: deps/amqp10_client-rabbitmq-deps.mk
|
||||
- name: CHECK CROSS REFERENCES
|
||||
run: |
|
||||
make xref base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: COMPILE FOR TEST
|
||||
run: |
|
||||
make test-build base_rmq_ref=master current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'latest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-22.3-rev3
|
||||
- name: PREPARE SECONDARY UMBRELLA COPIES
|
||||
if: success() && 'latest' == 'oldest'
|
||||
run: |
|
||||
# ----------------------------------------------------------
|
||||
# CAUTION:
|
||||
# The same script must be copied to `03-CT_SUITE.yaml`. It is used to
|
||||
# recreate the umbrellas if the cache restore fails.
|
||||
# ----------------------------------------------------------
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
# vim:sw=2:et:
|
||||
dialyzer:
|
||||
name: dialyzer
|
||||
needs: [checks]
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
if: success() && 'latest' == 'latest'
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
if: success() && 'latest' == 'latest'
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 22.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
if: success() && 'latest' == 'latest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: CACHE DIALYZER PLT
|
||||
if: success() && 'latest' == 'latest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: .amqp10_client.plt
|
||||
key: plt-amqp10_client-erlang-22.3-g${{ github.sha }}
|
||||
- name: RUN DIALYZER
|
||||
if: success() && 'latest' == 'latest'
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make dialyze \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL=
|
||||
# vim:sw=2:et:
|
||||
eunit:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: eunit
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 22.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
! test -d ebin || touch ebin/*
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make eunit \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
# vim:sw=2:et:
|
||||
ct-msg:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-msg
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 22.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
make ct-msg \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'latest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-22.3-rev3
|
||||
- name: VERIFY SECONDARY UMBRELLA COPIES (in case of cache restore failure)
|
||||
if: success() && 'latest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && 'latest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-msg \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS=
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-msg-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
# vim:sw=2:et:
|
||||
ct-system:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-system
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: 22.3
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: 1.10.4
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
make ct-system \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && 'latest' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: secondary-umbrellas-v3.7.26-v3.8.3-erlang-22.3-rev3
|
||||
- name: VERIFY SECONDARY UMBRELLA COPIES (in case of cache restore failure)
|
||||
if: success() && 'latest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
for version in v3.7.26 v3.8.3; do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/amqp10_client" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "master"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/amqp10_client" test-dist
|
||||
rm -fr "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && 'latest' == 'oldest'
|
||||
run: |
|
||||
set -x
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-system \
|
||||
base_rmq_ref=master \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS=
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-system-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
# vim:sw=2:et:
|
||||
capture-tested-deps-versions:
|
||||
needs:
|
||||
- dialyzer
|
||||
- eunit
|
||||
- ct-msg
|
||||
- ct-system
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
- name: CACHE DEPS
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: deps
|
||||
key: otp-22.3_git-${{ github.sha }}_deps
|
||||
- name: FORMAT GIT REF
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
- name: UPLOAD TO S3
|
||||
if: github.ref == 'refs/heads/master'
|
||||
# https://github.com/marketplace/actions/s3-file-upload
|
||||
uses: zdurham/s3-upload-github-action@master
|
||||
env:
|
||||
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
|
||||
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
|
||||
AWS_REGION: ${{ secrets.AWS_REGION }}
|
||||
FILE: deps/amqp10_client-rabbitmq-deps.mk
|
||||
S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
|
||||
S3_KEY: rabbitmq-amqp1.0-client/${{ steps.ref.outputs.branch_or_tag_name }}/${{ github.run_id }}/otp-22.3/amqp10_client-rabbitmq-deps.mk
|
||||
|
|
@ -1 +0,0 @@
|
|||
.github/workflows/ @gerhard @dumbbell
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,95 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
ct-$(CT_SUITE):
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-$(CT_SUITE)
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: $(ERLANG_VERSION)
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: $(ELIXIR_VERSION)
|
||||
- name: DOWNLOAD DEPS ARCHIVE
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: deps.tar.xz
|
||||
- name: UNPACK DEPS ARCHIVE
|
||||
run: |
|
||||
tar Jxf deps.tar.xz
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
export BASE_RMQ_REF=$(base_rmq_ref)
|
||||
export ERLANG_VERSION=$(ERLANG_VERSION)
|
||||
export ELIXIR_VERSION=$(ELIXIR_VERSION)
|
||||
make ct-$(CT_SUITE) \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
CT_OPTS="-ct_hooks honeycomb_cth '[{directory,\"$PWD/honeycomb\"}]'"
|
||||
- name: DOWNLOAD SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: secondary-umbrellas.tar.xz
|
||||
- name: UNPACK SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
tar Jxf secondary-umbrellas.tar.xz
|
||||
rm secondary-umbrellas.tar.xz
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-$(CT_SUITE) \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS= \
|
||||
CT_OPTS="-ct_hooks honeycomb_cth '[{directory,\"$PWD/honeycomb\"}]'"
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-$(CT_SUITE)-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
- name: HONEYCOMB
|
||||
if: success() || failure()
|
||||
run: |
|
||||
echo "$(ls honeycomb | wc -l) events recorded"
|
||||
for f in honeycomb/*; do
|
||||
RC=$(curl --silent \
|
||||
-H 'X-Honeycomb-Team: ${{ secrets.HONEYCOMB_TEAM }}' \
|
||||
-d @${f} \
|
||||
-o /dev/null \
|
||||
-w "%{http_code}" \
|
||||
"https://api.honeycomb.io/1/events/rabbitmq-ci")
|
||||
if [ "$RC" != "200" ]; then
|
||||
echo "Honeycomb returned ${RC}"
|
||||
cat ${f}
|
||||
printf "\n\n"
|
||||
fi
|
||||
done
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow
|
||||
name: "Test - Erlang $(ERLANG_VERSION)"
|
||||
on:
|
||||
push:
|
||||
repository_dispatch:
|
||||
types:
|
||||
- new-commit-to-dep-release-branch
|
||||
jobs:
|
||||
|
|
@ -1,101 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
checks:
|
||||
name: checks
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: $(ERLANG_VERSION)
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: $(ELIXIR_VERSION)
|
||||
- name: CHECK RABBITMQ COMPONENTS
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
make check-rabbitmq-components.mk base_rmq_ref=$(base_rmq_ref) current_rmq_ref=$branch_or_tag_name
|
||||
- name: RESOLVE & COMPILE DEPS
|
||||
run: |
|
||||
make deps test-deps base_rmq_ref=$(base_rmq_ref) current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
echo "Capture versions of the RabbitMQ components used in this workflow..."
|
||||
make $(PROJECT)-rabbitmq-deps.mk
|
||||
echo "Remove directories not used in the subsequent jobs..."
|
||||
rm -fr deps/*/{.git,test}
|
||||
- name: UPLOAD DEPS VERSIONS
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: $(PROJECT)-rabbitmq-deps.mk
|
||||
path: $(PROJECT)-rabbitmq-deps.mk
|
||||
- name: CREATE DEPS ARCHIVE
|
||||
run: |
|
||||
tar cf - deps | xz > deps.tar.xz
|
||||
- name: UPLOAD DEPS ARCHIVE
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: deps.tar.xz
|
||||
path: deps.tar.xz
|
||||
- name: CHECK CROSS REFERENCES
|
||||
run: |
|
||||
make xref base_rmq_ref=$(base_rmq_ref) current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: COMPILE FOR TEST
|
||||
run: |
|
||||
make test-build base_rmq_ref=$(base_rmq_ref) current_rmq_ref=${{ steps.ref.outputs.branch_or_tag_name }}
|
||||
- name: CACHE SECONDARY UMBRELLAS
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
uses: actions/cache@v1
|
||||
with:
|
||||
path: umbrellas
|
||||
key: $(SECONDARY_UMBRELLAS_CACHE_KEY)
|
||||
- name: PREPARE SECONDARY UMBRELLA COPIES
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
for version in $(MIXED_VERSION_TESTING_WITH); do
|
||||
umbrella="umbrellas/$version"
|
||||
if ! test -d "$umbrella" ||
|
||||
! make -C "$umbrella/deps/$(PROJECT)" test-dist; then
|
||||
rm -rf "$umbrella"
|
||||
|
||||
# Fetch the master Umbrella; the final umbrellas are created from
|
||||
# the master copy.
|
||||
if ! test -d umbrellas/master; then
|
||||
git config --global advice.detachedHead false
|
||||
git clone \
|
||||
https://github.com/rabbitmq/rabbitmq-public-umbrella.git \
|
||||
umbrellas/master
|
||||
make -C umbrellas/master co # To get RabbitMQ components.
|
||||
fi
|
||||
|
||||
# We copy the master Umbrella and checkout the appropriate tag.
|
||||
cp -a umbrellas/master "$umbrella"
|
||||
git -C "$umbrella" checkout "$(base_rmq_ref)"
|
||||
make -C "$umbrella" up BRANCH="$version"
|
||||
# To remove third-party deps which were checked out when the
|
||||
# projects were on the `master` branch. Thus, possibly not the
|
||||
# version pinning we expect. We update the Umbrella one last time
|
||||
# to fetch the correct third-party deps.
|
||||
make -C "$umbrella" clean-3rd-party-repos
|
||||
make -C "$umbrella" up
|
||||
make -C "$umbrella/deps/$(PROJECT)" test-dist
|
||||
rm -rf "$umbrella"/deps/rabbitmq_website
|
||||
rm -rf "$umbrella"/deps/rabbitmq_prometheus/docker
|
||||
rm -rf "$umbrella"/deps/*/{.git,test} "$umbrella"/.git
|
||||
fi
|
||||
done
|
||||
rm -fr umbrellas/master
|
||||
- name: CREATE SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
tar cf - umbrellas | xz > secondary-umbrellas.tar.xz
|
||||
- name: UPLOAD SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
uses: actions/upload-artifact@v2
|
||||
with:
|
||||
name: secondary-umbrellas.tar.xz
|
||||
path: secondary-umbrellas.tar.xz
|
||||
|
|
@ -1,35 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
dialyzer:
|
||||
name: dialyzer
|
||||
needs: [checks]
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'latest'
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'latest'
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: $(ERLANG_VERSION)
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: $(ELIXIR_VERSION)
|
||||
- name: DOWNLOAD DEPS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'latest'
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: deps.tar.xz
|
||||
- name: UNPACK DEPS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'latest'
|
||||
run: |
|
||||
tar Jxf deps.tar.xz
|
||||
rm deps.tar.xz
|
||||
- name: RUN DIALYZER
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'latest'
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make dialyze \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL=
|
||||
|
|
@ -1,34 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
eunit:
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: eunit
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: $(ERLANG_VERSION)
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: $(ELIXIR_VERSION)
|
||||
- name: DOWNLOAD DEPS ARCHIVE
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: deps.tar.xz
|
||||
- name: UNPACK DEPS ARCHIVE
|
||||
run: |
|
||||
tar Jxf deps.tar.xz
|
||||
rm deps.tar.xz
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
! test -d ebin || touch ebin/*
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make eunit \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
|
|
@ -1,73 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
ct-$(CT_SUITE):
|
||||
needs: [checks]
|
||||
# https://help.github.com/en/actions/reference/context-and-expression-syntax-for-github-actions#contexts
|
||||
name: ct-$(CT_SUITE)
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: $(ERLANG_VERSION)
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: $(ELIXIR_VERSION)
|
||||
- name: DOWNLOAD DEPS ARCHIVE
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: deps.tar.xz
|
||||
- name: UNPACK DEPS ARCHIVE
|
||||
run: |
|
||||
tar Jxf deps.tar.xz
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
! test -d ebin || touch ebin/*
|
||||
make ct-$(CT_SUITE) \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1
|
||||
- name: DOWNLOAD SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: secondary-umbrellas.tar.xz
|
||||
- name: UNPACK SECONDARY UMBRELLAS ARCHIVE
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
tar Jxf secondary-umbrellas.tar.xz
|
||||
rm secondary-umbrellas.tar.xz
|
||||
- name: RUN TESTS [mixed-versions]
|
||||
if: success() && '$(ERLANG_VERSION_IS)' == 'oldest'
|
||||
run: |
|
||||
set -ex
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
for umbrella in umbrellas/*; do
|
||||
test -d "$umbrella"
|
||||
printf '\n\033[1;32mMixing clusters with RabbitMQ %s\033[0m' \
|
||||
$(basename "$umbrella")
|
||||
make distclean-ct ct-$(CT_SUITE) \
|
||||
base_rmq_ref=$(base_rmq_ref) \
|
||||
current_rmq_ref=$branch_or_tag_name \
|
||||
FULL= \
|
||||
FAIL_FAST=1 \
|
||||
SKIP_AS_ERROR=1 \
|
||||
SECONDARY_UMBRELLA=$PWD/$umbrella \
|
||||
RABBITMQ_FEATURE_FLAGS=
|
||||
done
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-$(CT_SUITE)-logs
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
# vim:sw=2:et:
|
||||
capture-tested-deps-versions:
|
||||
needs:
|
||||
- dialyzer
|
||||
- eunit
|
||||
- ct-$(CT_SUITES)
|
||||
runs-on: ubuntu-18.04
|
||||
steps:
|
||||
- if: github.ref == 'refs/heads/$(base_rmq_ref)'
|
||||
uses: actions/download-artifact@v2
|
||||
with:
|
||||
name: $(PROJECT)-rabbitmq-deps.mk
|
||||
- name: FORMAT GIT REF
|
||||
if: github.ref == 'refs/heads/$(base_rmq_ref)'
|
||||
# https://github.community/t5/GitHub-Actions/How-can-I-set-an-expression-as-an-environment-variable-at/m-p/41804/highlight/true#M4751
|
||||
id: ref
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
echo "::set-output name=branch_or_tag_name::$branch_or_tag_name"
|
||||
- name: UPLOAD TO S3
|
||||
if: github.ref == 'refs/heads/$(base_rmq_ref)'
|
||||
# https://github.com/marketplace/actions/s3-file-upload
|
||||
uses: zdurham/s3-upload-github-action@master
|
||||
env:
|
||||
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
|
||||
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
|
||||
AWS_REGION: ${{ secrets.AWS_REGION }}
|
||||
FILE: $(PROJECT)-rabbitmq-deps.mk
|
||||
S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
|
||||
S3_KEY: $(RABBITMQ_COMPONENT_REPO_NAME)/${{ steps.ref.outputs.branch_or_tag_name }}/${{ github.run_id }}/otp-$(ERLANG_VERSION)/$(PROJECT)-rabbitmq-deps.mk
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
# https://help.github.com/en/actions/reference/events-that-trigger-workflows#external-events-repository_dispatch
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#example-calling-the-rest-api
|
||||
# https://developer.github.com/v3/repos/#create-a-repository-dispatch-event
|
||||
name: Webhook triggers
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- master
|
||||
jobs:
|
||||
rabbitmq-server:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: New commit to rabbitmq-common master branch
|
||||
run: |
|
||||
curl --silent --fail --url https://api.github.com/repos/rabbitmq/rabbitmq-server/dispatches \
|
||||
--header "Authorization: Bearer ${{ secrets.PERSONAL_ACCESS_TOKEN }}" \
|
||||
--header "Content-Type: application/json" \
|
||||
--data '{ "event_type": "new-commit-to-dep-release-branch", "client_payload": { "dep": "rabbitmq-common" } }'
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
# https://help.github.com/en/actions/reference/events-that-trigger-workflows#external-events-repository_dispatch
|
||||
# https://help.github.com/en/actions/configuring-and-managing-workflows/authenticating-with-the-github_token#example-calling-the-rest-api
|
||||
# https://developer.github.com/v3/repos/#create-a-repository-dispatch-event
|
||||
name: Webhook triggers
|
||||
on:
|
||||
push:
|
||||
branches:
|
||||
- master
|
||||
jobs:
|
||||
rabbitmq-server:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: New commit to rabbitmq-cli master branch
|
||||
run: |
|
||||
curl --silent --fail --url https://api.github.com/repos/rabbitmq/rabbitmq-server/dispatches \
|
||||
--header "Authorization: Bearer ${{ secrets.PERSONAL_ACCESS_TOKEN }}" \
|
||||
--header "Content-Type: application/json" \
|
||||
--data '{ "event_type": "new-commit-to-dep-release-branch", "client_payload": { "dep": "rabbitmq-cli" } }'
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the RabbitMQ team
|
||||
why we should accept this pull request. If it fixes a bug or resolves a feature request,
|
||||
be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much lower chance of
|
||||
being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to communicate the problem
|
||||
you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after
|
||||
creating the PR. If you're unsure about any of them, don't hesitate to
|
||||
ask on the mailing list. We're here to help! This is simply a reminder
|
||||
of what we are going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the
|
||||
discussion by explaining why you chose the solution you did and what
|
||||
alternatives you considered, etc.
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
|
|
@ -1,7 +0,0 @@
|
|||
dialyzer:
|
||||
name: No-op Dialyzer
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: no-op
|
||||
run: |
|
||||
true
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
.github/workflows @gerhard @dumbbell
|
||||
docker/ @gerhard
|
||||
priv/schema @michaelklishin
|
||||
src/ @dcorbacho @gerhard
|
||||
test/ @dcorbacho @gerhard
|
||||
Dockerfile @gerhard
|
||||
Makefile @gerhard @dumbbell
|
||||
rabbitmq-components.mk @dumbbell @gerhard
|
||||
rabbitmq-disable-metrics-collector.conf @gerhard
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,36 +0,0 @@
|
|||
# https://help.github.com/en/actions/configuring-and-managing-workflows/configuring-a-workflow
|
||||
name: Test
|
||||
on: push
|
||||
jobs:
|
||||
test:
|
||||
name: OTP v${{ matrix.otp }} & Elixir v${{ matrix.elixir }}
|
||||
runs-on: ubuntu-latest
|
||||
strategy:
|
||||
matrix:
|
||||
otp: ["21.3", "22.3"]
|
||||
elixir: ["1.8.2"]
|
||||
steps:
|
||||
- name: CHECKOUT REPOSITORY
|
||||
uses: actions/checkout@v2
|
||||
# https://github.com/marketplace/actions/setup-elixir
|
||||
- name: CONFIGURE OTP & ELIXIR
|
||||
uses: actions/setup-elixir@v1
|
||||
with:
|
||||
otp-version: ${{ matrix.otp }}
|
||||
# https://github.com/elixir-lang/elixir/releases
|
||||
elixir-version: ${{ matrix.elixir }}
|
||||
- name: RUN TESTS
|
||||
run: |
|
||||
branch_or_tag_name=${GITHUB_REF#refs/*/}
|
||||
make ct base_rmq_ref=master current_rmq_ref=$branch_or_tag_name
|
||||
- name: ON FAILURE ARCHIVE TESTS LOGS
|
||||
if: failure()
|
||||
run: |
|
||||
make ct-logs-archive
|
||||
- name: ON FAILURE UPLOAD TESTS LOGS ARTIFACT
|
||||
# https://github.com/marketplace/actions/upload-artifact
|
||||
uses: actions/upload-artifact@v2-preview
|
||||
if: failure()
|
||||
with:
|
||||
name: ct-logs-otp-${{ matrix.otp }}-elixir-${{ matrix.elixir }}
|
||||
path: "*-ct-logs-*.tar.xz"
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Thank you for using RabbitMQ and for taking the time to report an
|
||||
issue.
|
||||
|
||||
## Does This Belong to GitHub or RabbitMQ Mailing List?
|
||||
|
||||
*Important:* please first read the `CONTRIBUTING.md` document in the
|
||||
root of this repository. It will help you determine whether your
|
||||
feedback should be directed to the RabbitMQ mailing list [1] instead.
|
||||
|
||||
## Please Help Maintainers and Contributors Help You
|
||||
|
||||
In order for the RabbitMQ team to investigate your issue, please provide
|
||||
**as much as possible** of the following details:
|
||||
|
||||
* RabbitMQ version
|
||||
* Erlang version
|
||||
* RabbitMQ server and client application log files
|
||||
* A runnable code sample, terminal transcript or detailed set of
|
||||
instructions that can be used to reproduce the issue
|
||||
* RabbitMQ plugin information via `rabbitmq-plugins list`
|
||||
* Client library version (for all libraries used)
|
||||
* Operating system, version, and patch level
|
||||
|
||||
Running the `rabbitmq-collect-env` [2] script can provide most of the
|
||||
information needed. Please make the archive available via a third-party
|
||||
service and note that **the script does not attempt to scrub any
|
||||
sensitive data**.
|
||||
|
||||
If your issue involves RabbitMQ management UI or HTTP API, please also provide
|
||||
the following:
|
||||
|
||||
* Browser and its version
|
||||
* What management UI page was used (if applicable)
|
||||
* How the HTTP API requests performed can be reproduced with `curl`
|
||||
* Operating system on which you are running your browser, and its version
|
||||
* Errors reported in the JavaScript console (if any)
|
||||
|
||||
This information **greatly speeds up issue investigation** (or makes it
|
||||
possible to investigate it at all). Please help project maintainers and
|
||||
contributors to help you by providing it!
|
||||
|
||||
1. https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
2. https://github.com/rabbitmq/support-tools/blob/master/scripts/rabbitmq-collect-env
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bugfix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
||||
- [ ] Documentation (correction or otherwise)
|
||||
- [ ] Cosmetics (whitespace, appearance)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
Thank you for using RabbitMQ.
|
||||
|
||||
**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
|
||||
|
||||
Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
|
||||
have a **specific, actionable** suggestion for our team, you must first ask
|
||||
your question or discuss your suspected issue on the mailing list:
|
||||
|
||||
https://groups.google.com/forum/#!forum/rabbitmq-users
|
||||
|
||||
Team RabbitMQ does not use GitHub issues for discussions, investigations, root
|
||||
cause analysis and so on.
|
||||
|
||||
Please take the time to read the CONTRIBUTING.md document for instructions on
|
||||
how to effectively ask a question or report a suspected issue:
|
||||
|
||||
https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
|
||||
|
||||
Following these rules **will save time** for both you and RabbitMQ's maintainers.
|
||||
|
||||
Thank you.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
## Proposed Changes
|
||||
|
||||
Please describe the big picture of your changes here to communicate to the
|
||||
RabbitMQ team why we should accept this pull request. If it fixes a bug or
|
||||
resolves a feature request, be sure to link to that issue.
|
||||
|
||||
A pull request that doesn't explain **why** the change was made has a much
|
||||
lower chance of being accepted.
|
||||
|
||||
If English isn't your first language, don't worry about it and try to
|
||||
communicate the problem you are trying to solve to the best of your abilities.
|
||||
As long as we can understand the intent, it's all good.
|
||||
|
||||
## Types of Changes
|
||||
|
||||
What types of changes does your code introduce to this project?
|
||||
_Put an `x` in the boxes that apply_
|
||||
|
||||
- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
|
||||
- [ ] New feature (non-breaking change which adds functionality)
|
||||
- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
|
||||
- [ ] Documentation improvements (corrections, new content, etc)
|
||||
- [ ] Cosmetic change (whitespace, formatting, etc)
|
||||
|
||||
## Checklist
|
||||
|
||||
_Put an `x` in the boxes that apply. You can also fill these out after creating
|
||||
the PR. If you're unsure about any of them, don't hesitate to ask on the
|
||||
mailing list. We're here to help! This is simply a reminder of what we are
|
||||
going to look for before merging your code._
|
||||
|
||||
- [ ] I have read the `CONTRIBUTING.md` document
|
||||
- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
|
||||
- [ ] All tests pass locally with my changes
|
||||
- [ ] I have added tests that prove my fix is effective or that my feature works
|
||||
- [ ] I have added necessary documentation (if appropriate)
|
||||
- [ ] Any dependent changes have been merged and published in related repositories
|
||||
|
||||
## Further Comments
|
||||
|
||||
If this is a relatively large or complex change, kick off the discussion by
|
||||
explaining why you chose the solution you did and what alternatives you
|
||||
considered, etc.
|
||||
Loading…
Reference in New Issue