gitea

Git server with named volumes, based on information provided in gitea docker install doc.

For ssh to work with gitea, you'll need a git user per this document. You'll also need an ssh key generated for this user, a special script, and find out the uid/gid. For example, as root on the host:

mkdir -p /app/gitea
cat <<EOF > /app/gitea/gitea
ssh -p 222 -o StrictHostKeyChecking=no git@127.0.0.1 "SSH_ORIGINAL_COMMAND=\"\$SSH_ORIGINAL_COMMAND\" \$0 \$@"
EOF
chmod +x /app/gitea/gitea
useradd --system --shell /bin/bash --comment 'Git Version Control' --user-group --create-home git
passwd --lock git
su - git
ssh-keygen -t rsa -N "" -C "Gitea git user host key"  # save to ~/.ssh/id_rsa
echo "$(cat /home/git/.ssh/id_rsa.pub)" > ~/.ssh/authorized_keys
id  # note the uid and gid
exit
# could "grep git /etc/passwd" too

Edit the docker-compose.yml file for different passwords to use. Change the UID and GID to match those from the above git user.

Also of note, ssh port is 222 unless also changed in the yml file, but if you change it, you'll need to also change it in /app/gitea/gitea script on host.

start

You'll need docker and docker-compose.

docker-compose up -d

access

Access from the host is localhost:3000. You could edit /etc/hosts and add an alias of gitea, 127.0.0.1 gitea.

If first time, access the Explore button, scan the information for correctness, and click Install at bottom to complete the installation. If no error immediately appears, give it time to install.

Access from other containers in the same network (--network=gitea_gitea) is gitea:3000.

stop

docker-compose stop

Jenkins

For integration with gitea:

• Install jenkins gitea plugin
• Configure access to gitea (manage -> configure, scroll to gitea server section) which will show up in the Server dropdowns
• Configure gitea repo webhook to jenkins (sometimes Jenkins automatically configures this)

Jenkins config

For Jenkins, install the gitea plugin, then you can configure it by scrolling to the Gitea Servers section under Manage Jenkins -> Configure System.

• Create a token in gitea for access by Jenkins, copy to clipboard for pasting next
• Create Jenkins credential to save gitea token
• Name: Local Gitea
• Server URL: http://gitea:3000
• Check Manage hooks, provide a gitea token credential
• Click Advanced
• Alias URL is http://gitea:3000

If running Jenkins and Gitea from containers, ensure both on the same network.

You'll note that one of the "New Items" you can choose from the dashboard is Gitea Organization. Choose the server to gitea, use a token as credential, enter the owner. You can enhance further by picking which branches to build when changes occur in the repo.

When using with Blue Ocean pipeline:

• create a dummy Jenkinsfile in the gitea repo of choice
• create new pipeline, choose Git as source (unless the developers have since provided a Gitea source, then choose that)
• provide the ssh url (I believe Blue Ocean requires ssh access) to the repo
• if connection errors, probably due to a key not present on gitea, so add the suggested one, and perhaps save as credential (can't remember exact order)
• find your pipeline created
• go back to classic mode and click Configure for the pipeline
• add a Gitea source in order that webhooks work (keep the Git source for Blue Ocean use if chosen at pipeline creation)
• choose a credential with username/password (since Gitea uses Git plugin)

Gitea webhook config

The webhook to Jenkins using gitea is similar to http://jenkins:8080/gitea-webhook/post (if using jenkins in a container on the same network with hostname jenkins). I generated a token in gitea, saved in Jenkins credential, and provided that to the manage jenkins -> configuration for the Gitea. A token allows full access which meant Jenkins could establish the webhook itself. A token has the added benefit of not requiring a crumb for cross-site accesses.

Troubleshooting

• ensure correct credential being used for access (user/password or user/token)
• ensure correct urls being used
• webhook issues may need advanced gitea server setup on Jenkins
• if using docker containers for gitea as well as jenkins, you may run into cross-site issues if the containers domains are not the same. You may be able to get around by checking the Enable proxy compatibility box.
• generate token for use with jenkins

starting over

Some steps if you just want to start from a clean slate. WARNING! This will destroy user accounts and stored repos!.

docker-compose stop  # ensure stopped
docker ps -a | grep gitea  # note the container ids for the gitea webserver and database (mariadb is a mysql fork)
docker rm xxxx yyyy  # remove the containers for the webserver and database
docker volume ls | grep gitea  # list gitea volumes
docker volume rm gitea_web  # use matching from above statement
docker volume rm gitea_db  # 

config

Configuration Cheat Sheet

app.ini configures gitea.

If using docker,

docker exec -it -u git gitea bash
cd /data/gitea/conf
vi app.ini

Here are changes I made:

# in [repository] section:
ENABLE_PUSH_CREATE_USER = true

# in [server] section:
DOMAIN           = gitea
SSH_DOMAIN       = gitea
ROOT_URL         = http://gitea:3000/

After changes, restart via /app/gitea/gitea manager restart or do docker-compose stop; docker-compose up -d.

Be consistent. If you changed to use url like gitea:3000, use that everywhere else where needed, like in Jenkins config too.