Commit Graph

20 Commits (master)

Author SHA1 Message Date
Loïc Dachary 1c165fcea3
upgrade gitea to forgejo
ci/woodpecker/pr/woodpecker Pipeline failed Details
ci/woodpecker/push/woodpecker Pipeline failed Details
Signed-off-by: Loïc Dachary <>
2022-12-23 22:34:38 +01:00
Aravinth Manivannan cc12d1a77d
fix: hard-code CI_COMMIT_AUTHOR_* details to avoid failures in PR builds
ci/woodpecker/push/woodpecker Pipeline was successful Details
2022-07-08 19:51:06 +05:30
Loïc Dachary 6e84746a2c
git config before push
ci/woodpecker/pr/woodpecker Pipeline failed Details
2022-07-08 15:47:53 +02:00
Aravinth Manivannan 412230bd99
feat: create repo and add deploy key util 2022-07-01 19:52:10 +05:30
Aravinth Manivannan f7c0e8e296
chore: auto-cleanup ~/.ssh/known_hosts 2022-06-28 23:49:24 +05:30
Aravinth Manivannan 8640fcf449
fix: ssh deploy key perms
ci/woodpecker/push/woodpecker Pipeline was successful Details
2022-06-27 04:43:28 +05:30
Aravinth Manivannan f99420f51a
fix: ci gitea port
ci/woodpecker/push/woodpecker Pipeline failed Details
2022-06-27 04:40:41 +05:30
Aravinth Manivannan 0c0bb1bed7
feat: refactor and create commit 0 on fleet repository 2022-06-27 04:30:25 +05:30
Aravinth Manivannan 51b047fe40
fix: ssh port. server is started at 22 2022-06-27 04:30:12 +05:30
Aravinth Manivannan 6388e4de10
feat: CI loads config from env vars
ci/woodpecker/push/woodpecker Pipeline failed Details
2022-06-27 02:44:49 +05:30
Aravinth Manivannan 243880f6cc
feat: re-enable gitea service in docker-compose and CI env setup 2022-06-27 02:43:16 +05:30
Aravinth Manivannan a4a34194f3
feat: add deploy key client implementation 2022-06-26 04:51:29 +05:30
Aravinth Manivannan 0dac5121fd
feat: enable gitea service and mv vars to separate script 2022-06-26 04:19:02 +05:30
Aravinth Manivannan 442dd921a8
debug: is dashboard accessible? 2022-06-26 04:19:02 +05:30
Aravinth Manivannan 4996e33cad
debug: is maildev accessible? 2022-06-26 04:19:02 +05:30
Aravinth Manivannan 28fe03b861
fix: run wget in quiet mode and adapt MAILDEV_URL based on environment 2022-06-26 04:19:01 +05:30
Aravinth Manivannan fb5267a13b
hotfix: run gitea on host 2022-06-26 04:19:01 +05:30
Aravinth Manivannan 3c33d10ca0
fix: mv test dependency services to woodpecker config file 2022-06-26 04:19:01 +05:30
Aravinth Manivannan 798a2f03d9
feat: integration testing
    integration/ is a CLI-based HTTP client that can interact
    with Hostea Dashboard and Gitea.

    Integration tests are run via integration/, which is a
    driver for the HTTP client at integration/ The script is
    capable of spinning up a test environment consisting of services
    defined in docker-compose-dev-deps.yml and the Hostea Dashboard and
    tearing it down after a successful run.

    The credentials used to create various accounts and other parameters
    are all defined in integration/ script it self. So it is
    self contained.


	 - register user with email verification
	 - login
	 - create OIDC app
	 - visit support page

	 - Install Gitea(DB configuration, etc. The first form that's
	 presented to the visitor after a new instance is deployed)
	 - Register User
	 - Login User
	 - Create repository
	 - Configure OIDC SSO
	 - Login via SSO
2022-06-26 04:19:01 +05:30
Aravinth Manivannan 4b20f9a439
feat: Dashboard-Gitea SSO integration test script
    1. Register new user on dashboard

    2. Confirm user email, link is received from email. maildev/maildev
       is an SMTP server specifically built for testing emails locally.
       It comes with a REST API[0], which is used to access emails

    3. Sign in to Dashboard

    4. Visit /support/new/ on dashboard to raise new support request

    5. Redirection to Hostea Gitea support repository is done via
       JavaScript, so we simply test to see if the support repository's
       new issue page is present in the Dashboard response

    6. Go to support repository's new issue page. Gitea will redirect to
       sign in page

    7. Parse sign in page, find OIDC SSO link in sign in page

    8. Visit OIDC SSO link in sign in page, to be redirected to
       authorization page

    9. If OIDC integration on Dashboard is setup via `create_oidc`
       management command, then auto-authorization will be enabled for
       the integration. So user will be redirected to Gitea

    10. For new OIDC logins, Gitea will present a form to choose
	preferred username and enter email address. So fill that form
	and submit it.

	Please note the form submits to a different URL than the one at
	which the form is available. See `Gitea.__link_acount` and
	`Gitea.__link_acount_signup` and its usage in `Gitea._sso_login`

    11. Verify user creation by GET /{username}, should respond HTTP 200

    12. Visit new issue on support repository, should respond HTTP 200

2022-06-26 04:19:01 +05:30