Mirrors/dokku
1
0
Fork 0
mirror of https://github.com/dokku/dokku.git synced 2026-08-29 10:08:53 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
96d726c43c9ffe22f69303ebf43434e8f37a2315
dokku/tests.mk

363 lines
14 KiB
Makefile
Raw Normal View History

run tests against native dokku
2019-07-12 10:05:31 -07:00
DOKKU_SSH_PORT ?= 22
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
DOKKU_DOMAIN ?= dokku.me
tests: add support for running golangci-lint automatically The plugin paths must be computed at execution because not all plugins contain golang code.
2024-01-17 02:28:11 -05:00
GO_PLUGINS := $(shell sh -c 'find plugins -type f -name "go.mod" -exec dirname "{}" \; | sort -u | sed -e "s/$$/\/.../" | xargs')
SYSTEM := $(shell sh -c 'uname -s 2>/dev/null')
bats is available in homebrew
2015-10-31 15:27:13 -05:00
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
bats:
ifeq ($(SYSTEM),Darwin)
lint: remove whitespaces before redirect
2019-02-02 13:49:24 -05:00
ifneq ($(shell bats --version >/dev/null 2>&1 ; echo $$?),0)
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
brew install bats-core
endif
else
tests: switch to upstream bats-core Bats core now has junit report formatting, so there is no need to continue using a fork.
2021-01-17 16:18:24 -05:00
git clone https://github.com/bats-core/bats-core.git /tmp/bats
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
cd /tmp/bats && sudo ./install.sh /usr/local
rm -rf /tmp/bats
endif
test with wercker
2014-12-13 18:56:31 -08:00
shellcheck:
refactor: standardize on shorthand for redirecting all output to /dev/null The shorthand is more prevalent in this codebase, and is something that bash supports, so we should just use the same thing everywhere. Note that we do not use shorthand redirect in Makefile as shell parsing is a bit different in Make and the shorthand redirect doesn't seem to be properly supported, causing CI errors.
2023-07-01 03:48:45 -04:00
ifneq ($(shell shellcheck --version >/dev/null 2>&1; echo $$?),0)
bats is available in homebrew
2015-10-31 15:27:13 -05:00
ifeq ($(SYSTEM),Darwin)
brew install shellcheck
test with wercker
2014-12-13 18:56:31 -08:00
else
refactor: standardize apt-get usage - Always put flags in same location - Always use apt-get - Add --no-install-recommends where possible
2021-01-17 16:09:58 -05:00
sudo apt-get update -qq && sudo apt-get -qq -y --no-install-recommends install shellcheck
test with wercker
2014-12-13 18:56:31 -08:00
endif
endif
tests: run mvdan/shfmt on test runs While I do not agree with _every_ style change, this will force Dokku to have consistent formatting across all shell scripts, which is arguably a Good Thing™. The command used to reprocess everything is: ```shell shfmt -l -bn -ci -i 2 -w . ```
2019-01-07 01:04:17 -05:00
shfmt:
refactor: standardize on shorthand for redirecting all output to /dev/null The shorthand is more prevalent in this codebase, and is something that bash supports, so we should just use the same thing everywhere. Note that we do not use shorthand redirect in Makefile as shell parsing is a bit different in Make and the shorthand redirect doesn't seem to be properly supported, causing CI errors.
2023-07-01 03:48:45 -04:00
ifneq ($(shell shfmt --version >/dev/null 2>&1; echo $$?),0)
fix: use SYSTEM for shfmt Darwin detection
2026-05-25 12:51:23 +04:00
ifeq ($(SYSTEM),Darwin)
tests: run mvdan/shfmt on test runs While I do not agree with _every_ style change, this will force Dokku to have consistent formatting across all shell scripts, which is arguably a Good Thing™. The command used to reprocess everything is: ```shell shfmt -l -bn -ci -i 2 -w . ```
2019-01-07 01:04:17 -05:00
brew install shfmt
else
feat: respect TARGETARCH when installing development dependencies
2022-10-12 21:53:11 -04:00
wget -qO /tmp/shfmt https://github.com/mvdan/sh/releases/download/v3.5.1/shfmt_v3.5.1_linux_${TARGETARCH}
tests: run mvdan/shfmt on test runs While I do not agree with _every_ style change, this will force Dokku to have consistent formatting across all shell scripts, which is arguably a Good Thing™. The command used to reprocess everything is: ```shell shfmt -l -bn -ci -i 2 -w . ```
2019-01-07 01:04:17 -05:00
chmod +x /tmp/shfmt
sudo mv /tmp/shfmt /usr/local/bin/shfmt
endif
endif
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
xmlstarlet:
lint: remove whitespaces before redirect
2019-02-02 13:49:24 -05:00
ifneq ($(shell xmlstarlet --version >/dev/null 2>&1 ; echo $$?),0)
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
ifeq ($(SYSTEM),Darwin)
brew install xmlstarlet
else
refactor: standardize apt-get usage - Always put flags in same location - Always use apt-get - Add --no-install-recommends where possible
2021-01-17 16:09:58 -05:00
sudo apt-get update -qq && sudo apt-get -qq -y --no-install-recommends install xmlstarlet
feat: add junit support to shellcheck output This requires us to run shellcheck twice, as the first pass doesn't output anything human readable - both because of the redirect and because shellcheck doesn't directly support it - which increases lint runtime but allows us to have both the junit information and the normal human-readable output. Note that the checkstyle output does not contain timing info.
2018-12-30 08:02:17 -05:00
endif
endif
tests: fix issue where CI cannot install docker-buildx-plugin
2024-02-05 14:31:29 -05:00
ci-dependencies: bats shellcheck xmlstarlet docker-apt-repo
fix: install docker-compose-plugin in ci This used to be installed as moby-compose in Github Runners but they switched to the docker apt repo and don't install the plugin from the apt repository as it is outdated so we have to do it ourselves.
2023-08-26 13:03:19 -04:00
tests: fix issue where CI cannot install docker-buildx-plugin
2024-02-05 14:31:29 -05:00
docker-apt-repo:
fix: install docker-compose-plugin in ci This used to be installed as moby-compose in Github Runners but they switched to the docker apt repo and don't install the plugin from the apt repository as it is outdated so we have to do it ourselves.
2023-08-26 13:03:19 -04:00
ifdef INSTALL_DOCKER_REPO
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor --yes -o /usr/share/keyrings/docker.gpg
echo "deb [arch=amd64 signed-by=/usr/share/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(shell . /etc/os-release && echo "$$VERSION_CODENAME") stable" | sudo tee /etc/apt/sources.list.d/docker.list
sudo apt update
tests: fix issue where CI cannot install docker-buildx-plugin
2024-02-05 14:31:29 -05:00
sudo apt-get -qq -y --no-install-recommends install docker-buildx-plugin docker-compose-plugin
fix: install docker-compose-plugin in ci This used to be installed as moby-compose in Github Runners but they switched to the docker apt repo and don't install the plugin from the apt repository as it is outdated so we have to do it ourselves.
2023-08-26 13:03:19 -04:00
endif
test with wercker
2014-12-13 18:56:31 -08:00
setup-deploy-tests:
make tests work
2014-12-14 14:45:49 -08:00
ifdef ENABLE_DOKKU_TRACE
test docker image
2019-07-12 11:27:20 -07:00
echo "-----> Enable dokku trace"
run tests against native dokku
2019-07-12 10:05:31 -07:00
dokku trace:on
make tests work
2014-12-14 14:45:49 -08:00
endif
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
@echo "Setting $(DOKKU_DOMAIN) in /etc/hosts"
sudo /bin/bash -c "[[ `ping -c1 $(DOKKU_DOMAIN) >/dev/null 2>&1; echo $$?` -eq 0 ]] || echo \"127.0.0.1 $(DOKKU_DOMAIN) *.$(DOKKU_DOMAIN) www.test.app.$(DOKKU_DOMAIN)\" >> /etc/hosts"
test with wercker
2014-12-13 18:56:31 -08:00
@echo "-----> Generating keypair..."
mkdir -p /root/.ssh
rm -f /root/.ssh/dokku_test_rsa*
echo -e "y\n" | ssh-keygen -f /root/.ssh/dokku_test_rsa -t rsa -N ''
fix: set correct perms on files
2020-06-08 02:09:52 -04:00
chmod 700 /root/.ssh
fix: set correct perms for ssh key files
2020-06-07 15:10:41 -04:00
chmod 600 /root/.ssh/dokku_test_rsa
chmod 644 /root/.ssh/dokku_test_rsa.pub
test with wercker
2014-12-13 18:56:31 -08:00
@echo "-----> Setting up ssh config..."
lint: remove whitespaces before redirect
2019-02-02 13:49:24 -05:00
ifneq ($(shell ls /root/.ssh/config >/dev/null 2>&1 ; echo $$?),0)
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
echo "Host $(DOKKU_DOMAIN) \\r\\n Port $(DOKKU_SSH_PORT) \\r\\n RequestTTY yes \\r\\n IdentityFile /root/.ssh/dokku_test_rsa" >> /root/.ssh/config
add sshd config for off-port testing
2015-04-25 09:54:49 -07:00
echo "Host 127.0.0.1 \\r\\n Port 22333 \\r\\n RequestTTY yes \\r\\n IdentityFile /root/.ssh/dokku_test_rsa" >> /root/.ssh/config
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
else ifeq ($(shell grep $(DOKKU_DOMAIN) /root/.ssh/config),)
echo "Host $(DOKKU_DOMAIN) \\r\\n Port $(DOKKU_SSH_PORT) \\r\\n RequestTTY yes \\r\\n IdentityFile /root/.ssh/dokku_test_rsa" >> /root/.ssh/config
add sshd config for off-port testing
2015-04-25 09:54:49 -07:00
echo "Host 127.0.0.1 \\r\\n Port 22333 \\r\\n RequestTTY yes \\r\\n IdentityFile /root/.ssh/dokku_test_rsa" >> /root/.ssh/config
test docker image
2019-07-12 11:27:20 -07:00
else
sed --in-place 's/Port 22 \r/Port $(DOKKU_SSH_PORT) \r/g' /root/.ssh/config
cat /root/.ssh/config
add sshd config for off-port testing
2015-04-25 09:54:49 -07:00
endif
run tests against native dokku
2019-07-12 10:05:31 -07:00
ifneq ($(wildcard /etc/ssh/sshd_config),)
sed --in-place "s/^#Port 22$\/Port 22/g" /etc/ssh/sshd_config
ifeq ($(shell grep 22333 /etc/ssh/sshd_config),)
sed --in-place "s:^Port 22:Port 22 \\nPort 22333:g" /etc/ssh/sshd_config
endif
fix: update ssh.socket to listen on port 22333 Newer versions of sshd respect the systemd settings for listening on ports vs just the sshd_config.
2024-09-22 20:04:32 -04:00
ifeq ($(shell grep 22333 /usr/lib/systemd/system/ssh.socket),)
sed --in-place "s:^ListenStream=22:ListenStream=22 \\nListenStream=22333:g" /usr/lib/systemd/system/ssh.socket
endif
fix: ensure testing still works in docker container environments
2024-09-23 00:32:59 -04:00
systemctl daemon-reload || true
systemctl restart ssh.socket || service ssh restart
run tests against native dokku
2019-07-12 10:05:31 -07:00
endif
test with wercker
2014-12-13 18:56:31 -08:00
@echo "-----> Installing SSH public key..."
debug: echo empty
2020-06-02 13:30:12 -04:00
echo "" > /home/dokku/.ssh/authorized_keys
run tests against native dokku
2019-07-12 10:05:31 -07:00
sudo sshcommand acl-remove dokku test
cat /root/.ssh/dokku_test_rsa.pub | sudo sshcommand acl-add dokku test
fix: set correct perms on files
2020-06-08 02:09:52 -04:00
chmod 700 /home/dokku/.ssh
chmod 600 /home/dokku/.ssh/authorized_keys
run tests against native dokku
2019-07-12 10:05:31 -07:00
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
ifeq ($(shell grep $(DOKKU_DOMAIN) /home/dokku/VHOST 2>/dev/null),)
@echo "-----> Setting default VHOST to $(DOKKU_DOMAIN)..."
echo "$(DOKKU_DOMAIN)" > /home/dokku/VHOST
run tests against native dokku
2019-07-12 10:05:31 -07:00
endif
test docker image
2019-07-12 11:27:20 -07:00
ifeq ($(DOKKU_SSH_PORT), 22)
$(MAKE) prime-ssh-known-hosts
endif
setup-docker-deploy-tests: setup-deploy-tests
ifdef ENABLE_DOKKU_TRACE
echo "-----> Enable dokku trace"
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
docker exec dokku bash -c "dokku trace:on"
test docker image
2019-07-12 11:27:20 -07:00
endif
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
docker exec dokku bash -c "sshcommand acl-remove dokku test"
docker exec dokku bash -c "echo `cat /root/.ssh/dokku_test_rsa.pub` | sshcommand acl-add dokku test"
test docker image
2019-07-12 11:27:20 -07:00
$(MAKE) prime-ssh-known-hosts
prime-ssh-known-hosts:
@echo "-----> Intitial SSH connection to populate known_hosts..."
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
@echo "=====> SSH $(DOKKU_DOMAIN)"
debug: show output from ssh attempt
2024-09-22 00:17:14 -04:00
ssh -o StrictHostKeyChecking=no dokku@$(DOKKU_DOMAIN) help
debug: more test logging
2020-06-02 12:42:54 -04:00
@echo "=====> SSH 127.0.0.1"
debug: show output from ssh attempt
2024-09-22 00:17:14 -04:00
ssh -o StrictHostKeyChecking=no dokku@127.0.0.1 help
make sure we set the default VHOST to match test env
2014-12-14 15:31:08 -08:00
fix: properly setup the tmp files necessary for the lint make target
2019-01-06 23:01:38 -05:00
lint-setup:
@mkdir -p test-results/shellcheck tmp/shellcheck
fix: remove deprecated egrep calls from codebase
2020-02-17 05:59:52 -05:00
@find . -not -path '*/\.*' -not -path './debian/*' -not -path './docs/*' -not -path './tests/*' -not -path './vendor/*' -type f | xargs file | grep text | awk -F ':' '{ print $$1 }' | xargs head -n1 | grep -B1 "bash" | grep "==>" | awk '{ print $$2 }' > tmp/shellcheck/test-files
refactor: move all shellcheck disable definitions to .shellcheckrc file This makes standard use of shellcheck work without needing to provide extra configuration anywhere. Also remove use of inline 'shellcheck disable' calls that are already defined in the .shellcheckrc and don't need to be set inline.
2023-07-01 04:21:46 -04:00
@cat .shellcheckrc | sed -n -e '/^# SC/p' | cut -d' ' -f2 | paste -d, -s > tmp/shellcheck/exclude
fix: properly setup the tmp files necessary for the lint make target
2019-01-06 23:01:38 -05:00
don't run shfmt in CI
2019-06-11 11:36:17 -07:00
lint-ci: lint-setup
test with wercker
2014-12-13 18:56:31 -08:00
# these are disabled due to their expansive existence in the codebase. we should clean it up though
refactor: move all shellcheck disable definitions to .shellcheckrc file This makes standard use of shellcheck work without needing to provide extra configuration anywhere. Also remove use of inline 'shellcheck disable' calls that are already defined in the .shellcheckrc and don't need to be set inline.
2023-07-01 04:21:46 -04:00
@cat .shellcheckrc | sed -n -e '/^# SC/p'
test with wercker
2014-12-13 18:56:31 -08:00
@echo linting...
refactor: move all shellcheck disable definitions to .shellcheckrc file This makes standard use of shellcheck work without needing to provide extra configuration anywhere. Also remove use of inline 'shellcheck disable' calls that are already defined in the .shellcheckrc and don't need to be set inline.
2023-07-01 04:21:46 -04:00
@cat tmp/shellcheck/test-files | xargs shellcheck | tests/shellcheck-to-junit --output test-results/shellcheck/results.xml --files tmp/shellcheck/test-files --exclude $(shell cat tmp/shellcheck/exclude)
test with wercker
2014-12-13 18:56:31 -08:00
tests: add support for running golangci-lint automatically The plugin paths must be computed at execution because not all plugins contain golang code.
2024-01-17 02:28:11 -05:00
lint-golang:
golangci-lint run $(GO_PLUGINS)
don't run shfmt in CI
2019-06-11 11:36:17 -07:00
lint-shfmt: shfmt
# verifying via shfmt
# shfmt -l -bn -ci -i 2 -d .
@shfmt -l -bn -ci -i 2 -d .
lint: lint-shfmt lint-ci
add codacy config and coverage targets
2017-10-02 14:19:14 -07:00
ci-go-coverage:
fix: parse cert CN and subject on OpenSSL 3.x The `certs` plugin extracted a certificate's Common Name and formatted its subject using string assumptions that only held for pre-3.x OpenSSL output, so a certificate with only a Common Name and no Subject Alternative Name reported no hostnames from `certs:report` and was not recognized during nginx config generation, while the subject report retained the `subject=` prefix and used the wrong separators. Normalizing the subject with `-nameopt` before parsing makes the extraction version independent across OpenSSL and LibreSSL.
2026-07-10 15:05:27 -04:00
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=certs
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=common
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=config
fix: match docker options by shell word when removing Options drained out of the pre-0.38.0 `DOCKER_OPTIONS_<PHASE>` files were copied verbatim rather than re-serialized the way `docker-options:add` stores them, so `docker-options:remove` compared the canonical string it builds against a stored value that could never match it and exited successfully without removing anything. Removal now matches stored options by shell word, and stored options are rewritten into the canonical form once on upgrade, which additionally splits an entry that carried several flags on a single line into one entry per flag so a single flag can be removed and so the readers that match on a flag prefix see one value per entry. The leftover `.migrated` sentinel drain is restored to running ahead of the global short-circuit that had made it unreachable, and the plugin's Go tests are added to the test target that had never run them.
2026-08-07 13:35:37 -04:00
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=docker-options
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=network
fix: remove buildpacks from dockerfile test app and add tests for app.json buildpacks The buildpacks entry in tests/apps/dockerfile/app.json caused the post-extract trigger to write a .buildpacks file during Dockerfile-based deploys, breaking builder detection. Remove the entry and add Go unit tests for getBuildpacks/validBuildpackURL, a bats integration test for deploying with app.json buildpacks, and documentation for the new feature.
2026-04-18 05:43:44 -04:00
@$(MAKE) ci-go-coverage-plugin PLUGIN_NAME=buildpacks
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
ci-go-coverage-plugin:
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
mkdir -p test-results/coverage
docker run --rm \
add codacy config and coverage targets
2017-10-02 14:19:14 -07:00
-e DOKKU_ROOT=/home/dokku \
fix: set DOKKU_LIB_ROOT in Go coverage test environment
2026-04-25 06:01:34 -04:00
-e DOKKU_LIB_ROOT=/var/lib/dokku \
add codacy config and coverage targets
2017-10-02 14:19:14 -07:00
-e CODACY_TOKEN=$$CODACY_TOKEN \
-e CIRCLE_SHA1=$$CIRCLE_SHA1 \
chore: turn on go mod
2020-06-28 01:42:09 -04:00
-e GO111MODULE=on \
add codacy config and coverage targets
2017-10-02 14:19:14 -07:00
-v $$PWD:$(GO_REPO_ROOT) \
-w $(GO_REPO_ROOT) \
$(BUILD_IMAGE) \
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
bash -c "cd plugins/$(PLUGIN_NAME) && \
feat: add debugging and use go get to grab godacov
2022-11-02 15:45:33 -04:00
echo 'installing gomega' && \
fix: switch to go install from go get This no longer works as of go 1.18: https://go.dev/doc/go-get-install-deprecation
2022-11-02 11:57:22 -04:00
go get github.com/onsi/gomega && \
feat: add debugging and use go get to grab godacov
2022-11-02 15:45:33 -04:00
echo 'installing godacov' && \
go get github.com/schrej/godacov && \
echo 'installing goverage' && \
fix: install goverage via go get
2022-11-07 00:47:06 -05:00
go get github.com/haya14busa/goverage && \
fix: switch to go install from go get This no longer works as of go 1.18: https://go.dev/doc/go-get-install-deprecation
2022-11-02 11:57:22 -04:00
go install github.com/haya14busa/goverage && \
feat: add debugging and use go get to grab godacov
2022-11-02 15:45:33 -04:00
echo 'running goverage' && \
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
goverage -v -coverprofile=./../../test-results/coverage/$(PLUGIN_NAME).out && \
feat: add debugging and use go get to grab godacov
2022-11-02 15:45:33 -04:00
echo 'running godacov' && \
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
(godacov -r ./../../test-results/coverage/$(PLUGIN_NAME).out -c $$CIRCLE_SHA1 -t $$CODACY_TOKEN || true)" || exit $$?
add codacy config and coverage targets
2017-10-02 14:19:14 -07:00
convert repo plugin to golang
2017-01-03 22:27:20 -08:00
go-tests:
fix: parse cert CN and subject on OpenSSL 3.x The `certs` plugin extracted a certificate's Common Name and formatted its subject using string assumptions that only held for pre-3.x OpenSSL output, so a certificate with only a Common Name and no Subject Alternative Name reported no hostnames from `certs:report` and was not recognized during nginx config generation, while the subject report retained the `subject=` prefix and used the wrong separators. Normalizing the subject with `-nameopt` before parsing makes the extraction version independent across OpenSSL and LibreSSL.
2026-07-10 15:05:27 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=certs
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=common
@$(MAKE) go-test-plugin PLUGIN_NAME=config
fix: retire cron containers past their active deadline Cron containers were never reaped once they exceeded their active deadline, so a hung cron task ran indefinitely instead of being retired after 24 hours as documented. `cron:run` now also accepts a `--ttl-seconds` argument, matching the one `dokku run` already takes.
2026-08-12 13:11:34 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=cron
fix: match docker options by shell word when removing Options drained out of the pre-0.38.0 `DOCKER_OPTIONS_<PHASE>` files were copied verbatim rather than re-serialized the way `docker-options:add` stores them, so `docker-options:remove` compared the canonical string it builds against a stored value that could never match it and exited successfully without removing anything. Removal now matches stored options by shell word, and stored options are rewritten into the canonical form once on upgrade, which additionally splits an entry that carried several flags on a single line into one entry per flag so a single flag can be removed and so the readers that match on a flag prefix see one value per entry. The leftover `.migrated` sentinel drain is restored to running ahead of the global short-circuit that had made it unreachable, and the plugin's Go tests are added to the test target that had never run them.
2026-08-07 13:35:37 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=docker-options
fix: apply app-label-alias to shipped events The alias was only ever used to build the `include_labels` filter on the generated vector source, while dokku labels containers with `com.dokku.app-name` unconditionally. Setting the property therefore pointed the source at a label no container carries, and log collection stopped without any error. The source now always filters the label dokku applies, and a generated remap renames the field on its way to the sink, which is what the property was documented to do. An app whose own alias differs from the global one gets a branch in the global pipeline, so a per-app value is honored even when the app ships through the global sink. Closes #8916.
2026-08-09 14:01:43 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=logs
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=network
fix: remove buildpacks from dockerfile test app and add tests for app.json buildpacks The buildpacks entry in tests/apps/dockerfile/app.json caused the post-extract trigger to write a .buildpacks file during Dockerfile-based deploys, breaking builder detection. Remove the entry and add Go unit tests for getBuildpacks/validBuildpackURL, a bats integration test for deploying with app.json buildpacks, and documentation for the new feature.
2026-04-18 05:43:44 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=buildpacks
feat: support manually managed cert issuers on k3s The `cert-issuer-name` and `cert-issuer-kind` properties point an app's generated `Certificate` at a cert-manager issuer created outside of Dokku, allowing certificates to be issued through solvers the built-in letsencrypt integration cannot use, such as `dns01` for wildcard certificates. Setting an issuer enables https on its own, as a manually managed issuer has no email for Dokku to configure. An imported certificate still takes precedence, and `letsencrypt-server false` remains the single off switch. Dokku warns before a build starts when the referenced issuer is absent from the cluster, without blocking the deploy. Wildcard domains no longer collide with their apex domain when generating ingress names, and `letsencrypt-server` values are now validated when set rather than at deploy time.
2026-08-08 15:16:12 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=scheduler-k3s
feat: add storage directory mode and removal flags `storage:create` and `storage:set` accept a `--mode` flag that sets the octal permissions of a docker-local host directory, and `storage:destroy` accepts a `--destroy-host-dir` flag that removes the directory along with its contents. A docker-local entry also honors `--reclaim-policy Delete` at destroy time now, matching how that policy governs a k3s PersistentVolume. Both are limited to the default `/var/lib/dokku/data/storage/<name>` location, the same restriction `--chown` already carries. `storage:set` applies `--chown` and `--mode` to the directory rather than only recording them.
2026-08-10 01:23:10 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=storage
fix: report traefik dns-provider env vars as global keys The dynamic `dns-provider-*` properties were reported as `--traefik-dns-provider-<env_var>`, outside the `global`/`computed` namespace every other traefik property uses, so a consumer reading the json report could not tell which of the two a key represented. They are now reported as `--traefik-global-dns-provider-<env_var>`. The `basic-auth-password` property is a credential as well and is now masked in the default report output on the same terms as the dns provider values, meaning the raw value is returned only for `--format json` or when the flag is queried by name.
2026-08-12 03:22:04 -04:00
@$(MAKE) go-test-plugin PLUGIN_NAME=traefik-vhosts
refactor: call tests while in directories They fail to be listed in go list after the gomodules move.
2020-06-28 13:59:08 -04:00
go-test-plugin:
fix: remove buildpacks from dockerfile test app and add tests for app.json buildpacks The buildpacks entry in tests/apps/dockerfile/app.json caused the post-extract trigger to write a .buildpacks file during Dockerfile-based deploys, breaking builder detection. Remove the entry and add Go unit tests for getBuildpacks/validBuildpackURL, a bats integration test for deploying with app.json buildpacks, and documentation for the new feature.
2026-04-18 05:43:44 -04:00
cd plugins/$(PLUGIN_NAME) && go get github.com/onsi/gomega && DOKKU_ROOT=/home/dokku DOKKU_LIB_ROOT=/var/lib/dokku go test -v -p 1 -race -mod=readonly || exit $$?
tests: run unit tests outside of docker by default This allows execution of unit tests within the devcontainer environment, which already has the correct golang.
2024-12-03 21:45:41 -05:00
go-test-plugin-in-docker:
convert repo plugin to golang
2017-01-03 22:27:20 -08:00
@echo running go unit tests...
tests: use github actions instead of circleci for test running
2021-01-09 16:49:18 -05:00
docker run --rm \
chore: turn on go mod
2020-06-28 01:42:09 -04:00
-e GO111MODULE=on \
convert repo plugin to golang
2017-01-03 22:27:20 -08:00
-v $$PWD:$(GO_REPO_ROOT) \
-w $(GO_REPO_ROOT) \
$(BUILD_IMAGE) \
tests: run unit tests outside of docker by default This allows execution of unit tests within the devcontainer environment, which already has the correct golang.
2024-12-03 21:45:41 -05:00
bash -c "make go-test-plugin PLUGIN_NAME=$(PLUGIN_NAME)" || exit $$?
convert repo plugin to golang
2017-01-03 22:27:20 -08:00
unit-tests: go-tests
@echo running bats unit tests...
split up unit-tests and use 4 containers (they're free)
2015-04-24 13:52:14 -07:00
ifndef UNIT_TEST_BATCH
test with wercker
2014-12-13 18:56:31 -08:00
@$(QUIET) bats tests/unit
split up unit-tests and use 4 containers (they're free)
2015-04-24 13:52:14 -07:00
else
@$(QUIET) ./tests/ci/unit_test_runner.sh $$UNIT_TEST_BATCH
endif
test with wercker
2014-12-13 18:56:31 -08:00
add tests for pre/post deploy tasks
2017-04-03 12:34:41 -07:00
deploy-test-go-fail-predeploy:
@echo deploying go-fail-predeploy app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/go-fail-predeploy $(DOKKU_DOMAIN) '' true
add tests for pre/post deploy tasks
2017-04-03 12:34:41 -07:00
deploy-test-go-fail-postdeploy:
@echo deploying go-fail-postdeploy app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/go-fail-postdeploy $(DOKKU_DOMAIN) '' true
add tests for pre/post deploy tasks
2017-04-03 12:34:41 -07:00
Add checks-root test app to tests.mk
2015-07-11 13:50:53 +02:00
deploy-test-checks-root:
@echo deploying checks-root app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/checks-root $(DOKKU_DOMAIN) '' true
Add checks-root test app to tests.mk
2015-07-11 13:50:53 +02:00
Accept first pushed branch as deploy-branch And set to DOKKU_DEPLOY_BRANCH. Idea from https://github.com/dokku/dokku/pull/4167#issuecomment-717607136
2020-12-08 23:15:11 +09:00
deploy-test-main-branch:
@echo deploying checks-root app to main branch...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/checks-root $(DOKKU_DOMAIN) '' true main
Accept first pushed branch as deploy-branch And set to DOKKU_DEPLOY_BRANCH. Idea from https://github.com/dokku/dokku/pull/4167#issuecomment-717607136
2020-12-08 23:15:11 +09:00
test clojure app
2015-02-03 16:46:04 -08:00
deploy-test-clojure:
@echo deploying config app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/clojure $(DOKKU_DOMAIN)
test clojure app
2015-02-03 16:46:04 -08:00
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-config:
@echo deploying config app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/config $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
first pass at dockerfile support
2015-02-07 10:47:04 -08:00
deploy-test-dockerfile:
@echo deploying dockerfile app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/dockerfile $(DOKKU_DOMAIN)
first pass at dockerfile support
2015-02-07 10:47:04 -08:00
support dockerfiles without expose command. closes #1083
2015-04-03 12:13:39 -07:00
deploy-test-dockerfile-noexpose:
@echo deploying dockerfile-noexpose app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/dockerfile-noexpose $(DOKKU_DOMAIN)
support dockerfiles without expose command. closes #1083
2015-04-03 12:13:39 -07:00
include dockerfile-procfile test app in Makefile
2016-04-25 18:47:33 -07:00
deploy-test-dockerfile-procfile:
@echo deploying dockerfile-procfile app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/dockerfile-procfile $(DOKKU_DOMAIN)
include dockerfile-procfile test app in Makefile
2016-04-25 18:47:33 -07:00
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-gitsubmodules:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying gitsubmodules app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/gitsubmodules $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-go:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying go app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/go $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-java:
[ci skip] fix missing strings in deploy tests output
2015-01-11 16:30:13 -08:00
@echo deploying java app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/java $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-multi:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying multi app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/multi $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-nodejs-express:
[ci skip] fix missing strings in deploy tests output
2015-01-11 16:30:13 -08:00
@echo deploying nodejs-express app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/nodejs-express $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
test deploy node app without procfile
2015-01-09 21:22:05 -08:00
deploy-test-nodejs-express-noprocfile:
[ci skip] fix missing strings in deploy tests output
2015-01-11 16:30:13 -08:00
@echo deploying nodejs-express app with no Procfile...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/nodejs-express-noprocfile $(DOKKU_DOMAIN)
test deploy node app without procfile
2015-01-09 21:22:05 -08:00
only run domains and nginx config if we have a port and ip. fixes #1355
2015-07-30 14:29:36 -07:00
deploy-test-nodejs-worker:
@echo deploying nodejs-worker app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/nodejs-worker $(DOKKU_DOMAIN)
only run domains and nginx config if we have a port and ip. fixes #1355
2015-07-30 14:29:36 -07:00
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-php:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying php app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/php $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-python-flask:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying python-flask app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/python-flask $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
ensure we have newlines around our config. closes #1025
2015-03-09 19:07:50 -07:00
deploy-test-ruby:
@echo deploying ruby app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/ruby $(DOKKU_DOMAIN)
ensure we have newlines around our config. closes #1025
2015-03-09 19:07:50 -07:00
test scala deployment
2014-12-23 23:43:11 -08:00
deploy-test-scala:
@echo deploying scala app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/scala $(DOKKU_DOMAIN)
test scala deployment
2014-12-23 23:43:11 -08:00
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
deploy-test-static:
echo out deploy test type correctly
2014-12-20 15:27:25 -08:00
@echo deploying static app...
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
cd tests && ./test_deploy ./apps/static $(DOKKU_DOMAIN)
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
fix: install logrotate in the container
2026-01-03 22:50:38 -05:00
test-ci-binaries:
docker exec dokku bash -c "whereis logrotate" || { echo "logrotate not found" ; exit 1; }
docker exec dokku bash -c "whereis rsyslog" || { echo "rsyslog not found" ; exit 1; }
test with wercker
2014-12-13 18:56:31 -08:00
deploy-tests:
@echo running deploy tests...
Add checks-root test app to tests.mk
2015-07-11 13:50:53 +02:00
@$(QUIET) $(MAKE) deploy-test-checks-root
Accept first pushed branch as deploy-branch And set to DOKKU_DEPLOY_BRANCH. Idea from https://github.com/dokku/dokku/pull/4167#issuecomment-717607136
2020-12-08 23:15:11 +09:00
@$(QUIET) $(MAKE) deploy-test-main-branch
add tests for pre/post deploy tasks
2017-04-03 12:34:41 -07:00
@$(QUIET) $(MAKE) deploy-test-go-fail-predeploy
@$(QUIET) $(MAKE) deploy-test-go-fail-postdeploy
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
@$(QUIET) $(MAKE) deploy-test-config
test clojure app
2015-02-03 16:46:04 -08:00
@$(QUIET) $(MAKE) deploy-test-clojure
first pass at dockerfile support
2015-02-07 10:47:04 -08:00
@$(QUIET) $(MAKE) deploy-test-dockerfile
support dockerfiles without expose command. closes #1083
2015-04-03 12:13:39 -07:00
@$(QUIET) $(MAKE) deploy-test-dockerfile-noexpose
include dockerfile-procfile test app in Makefile
2016-04-25 18:47:33 -07:00
@$(QUIET) $(MAKE) deploy-test-dockerfile-procfile
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
@$(QUIET) $(MAKE) deploy-test-gitsubmodules
@$(QUIET) $(MAKE) deploy-test-go
@$(QUIET) $(MAKE) deploy-test-java
enable multi buildpack test
2015-01-06 11:20:22 -08:00
@$(QUIET) $(MAKE) deploy-test-multi
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
@$(QUIET) $(MAKE) deploy-test-nodejs-express
test deploy node app without procfile
2015-01-09 21:22:05 -08:00
@$(QUIET) $(MAKE) deploy-test-nodejs-express-noprocfile
only run domains and nginx config if we have a port and ip. fixes #1355
2015-07-30 14:29:36 -07:00
@$(QUIET) $(MAKE) deploy-test-nodejs-worker
fix php test
2014-12-16 17:37:28 -08:00
@$(QUIET) $(MAKE) deploy-test-php
don't use bats for deploy tests
2014-12-14 18:11:17 -08:00
@$(QUIET) $(MAKE) deploy-test-python-flask
test scala deployment
2014-12-23 23:43:11 -08:00
@$(QUIET) $(MAKE) deploy-test-scala
fix static site test
2014-12-20 16:37:41 -08:00
@$(QUIET) $(MAKE) deploy-test-static
test with wercker
2014-12-13 18:56:31 -08:00
make tests work
2014-12-14 14:45:49 -08:00
test: setup-deploy-tests lint unit-tests deploy-tests
use circleci 2.0
2017-08-29 10:14:33 -07:00
test-ci:
refactor: use a python script to translate from shellcheck output to junit The checkstyle xslt wasn't quite good enough, resulting in missing/malformatted output. Note that this now excludes _passing_ tests, which also isn't quite right, but a fair bit closer to the xsd here: https://github.com/windyroad/JUnit-Schema
2019-01-05 19:56:23 -05:00
@mkdir -p test-results/bats
tests: split by classname instead of filename
2019-01-21 21:57:03 -05:00
@cd tests/unit && echo "executing tests: $(shell cd tests/unit ; circleci tests glob *.bats | circleci tests split --split-by=timings --timings-type=classname | xargs)"
tests: switch to upstream bats-core Bats core now has junit report formatting, so there is no need to continue using a fork.
2021-01-17 16:18:24 -05:00
cd tests/unit && bats --report-formatter junit --timing -o ../../test-results/bats $(shell cd tests/unit ; circleci tests glob *.bats | circleci tests split --split-by=timings --timings-type=classname | xargs)
test docker image
2019-07-12 11:27:20 -07:00
feat: retry failing and skipped tests once Plugn is fairly brittle since the upgrade to bash 5, so this might help decrease the need to retry the whole circleci job.
2020-12-20 01:57:00 -05:00
tests-ci-retry-failed:
tests: update junit test files when a bats retry is successful
2020-12-20 15:35:15 -05:00
wget -qO /tmp/bats-retry.tgz https://github.com/josegonzalez/go-bats-retry/releases/download/v0.2.1/bats-retry_0.2.1_linux_x86_64.tgz
feat: retry failing and skipped tests once Plugn is fairly brittle since the upgrade to bash 5, so this might help decrease the need to retry the whole circleci job.
2020-12-20 01:57:00 -05:00
tar xzf /tmp/bats-retry.tgz -C /usr/local/bin
tests: update junit test files when a bats retry is successful
2020-12-20 15:35:15 -05:00
bats-retry --execute test-results/bats
feat: retry failing and skipped tests once Plugn is fairly brittle since the upgrade to bash 5, so this might help decrease the need to retry the whole circleci job.
2020-12-20 01:57:00 -05:00
fix: install logrotate in the container
2026-01-03 22:50:38 -05:00
test-ci-docker: setup-docker-deploy-tests deploy-test-checks-root deploy-test-config deploy-test-multi deploy-test-go-fail-predeploy deploy-test-go-fail-postdeploy test-ci-binaries
fix: use correct path within the ssl tarballs Also add a command to help automate the generation of the certificates in the future.
2023-01-16 01:50:52 -05:00
generate-ssl-tars: generate-ssl-tar generate-ssl-sans-tar generate-ssl-wildcard-tar
generate-ssl-tar:
rm -rf /tmp/dokku-server_ssl
mkdir -p /tmp/dokku-server_ssl
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
openssl req -x509 -newkey rsa:4096 -sha256 -nodes -keyout /tmp/dokku-server_ssl/server.key -out /tmp/dokku-server_ssl/server.crt -subj "/CN=$(DOKKU_DOMAIN)" -days 3650
fix: use correct path within the ssl tarballs Also add a command to help automate the generation of the certificates in the future.
2023-01-16 01:50:52 -05:00
rm tests/unit/server_ssl.tar
cd /tmp/dokku-server_ssl && tar cvf $(PWD)/tests/unit/server_ssl.tar server.key server.crt
tar -tvf tests/unit/server_ssl.tar
generate-ssl-sans-tar:
rm -rf /tmp/dokku-server_ssl_sans
mkdir -p /tmp/dokku-server_ssl_sans
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
openssl req -x509 -newkey rsa:4096 -sha256 -nodes -keyout /tmp/dokku-server_ssl_sans/server.key -out /tmp/dokku-server_ssl_sans/server.crt -subj "/CN=test.$(DOKKU_DOMAIN)" -days 3650 -addext "subjectAltName = DNS:www.test.$(DOKKU_DOMAIN), DNS:www.test.app.$(DOKKU_DOMAIN)"
fix: use correct path within the ssl tarballs Also add a command to help automate the generation of the certificates in the future.
2023-01-16 01:50:52 -05:00
rm tests/unit/server_ssl_sans.tar
cd /tmp/dokku-server_ssl_sans && tar cvf $(PWD)/tests/unit/server_ssl_sans.tar server.key server.crt
tar -tvf tests/unit/server_ssl_sans.tar
generate-ssl-wildcard-tar:
rm -rf /tmp/dokku-server_ssl_wildcard
mkdir -p /tmp/dokku-server_ssl_wildcard
tests: make it possible to specify an alternative base domain for tests When developing Dokku, it is useful to use a real domain to test actual functionality. This is impossible if the domain is hardcoded to dokku.me in testing.
2023-08-05 16:32:58 -04:00
openssl req -x509 -newkey rsa:4096 -sha256 -nodes -keyout /tmp/dokku-server_ssl_wildcard/server.key -out /tmp/dokku-server_ssl_wildcard/server.crt -subj "/CN=*.$(DOKKU_DOMAIN)" -days 3650
fix: use correct path within the ssl tarballs Also add a command to help automate the generation of the certificates in the future.
2023-01-16 01:50:52 -05:00
rm tests/unit/server_ssl_wildcard.tar
cd /tmp/dokku-server_ssl_wildcard && tar cvf $(PWD)/tests/unit/server_ssl_wildcard.tar server.key server.crt
tar -tvf tests/unit/server_ssl_wildcard.tar
Reference in New Issue Copy Permalink