Supporting Bitbucket and Gitea, not only GitHub via Repository URL

[stevenanthonyrevo]

Is your feature request related to a problem? Please describe

I've recently tried connecting a bitbucket repository to Portainer and then a Gitea repository to Portainer with the authentication toggle and it seems the connection Repository URL only supports GitHub.

Thanks for making GitHub work so nicely!

Although, I did not get to test out, the official feature "GitOps updates" yet on the Github Repository connection.

The issue I've come across is "I have a few other repositories in different providers which I cannot connect..." and "I can't automate rebuilding stacks and containers based on new commits easily"

It would be great to support all types of Repository URLs from Bitbucket and Gitea with a peace of mind that my containers or stacks will be updated accordingly and connected to any repository available.

The main concern is when "docker-compose.yaml" does not have access to a repository the stack can't be created.

In the "Add a Stack Section" I noticed the "Upload Section" only allows a single file.

I originally thought I would be able to upload a full private repository with a few Docker files.

Only to later realize, it needs a docker-compose.yaml file pointing to a registry. This limits the ability to deploy local Docker files not found in a public or private registry.

Describe the solution you'd like

If "GitOps Updates" does not already do this, I hope the stacks and containers are rebuilt based on commits via any repository url in which I've connected via authentication.

Ideally, I'd like to see Portainer be able to do a "push on commit" from any type of Repository URL via Bitbucket, Gitea or Github.

When developing with Git, its always nice to have access to the latest code committed and see the images or containers be refreshed with the latest changes and a great peace of mind.

Describe alternatives you've considered

I've considered using a private registry or even DockerHub with the GitOps feature.

These are extra steps for me, because the private repository would have the correct Docker files to build into images on the hard drive.

Additional context

Could the feature be updated to allow private codebases to be manually uploaded via zip and locate the "docker-compose.yaml" file inside the zip?

This could be helpful when a repository URL fails to authentic because you can simply upload a zip and rebuild your codebase.

[stevenanthonyrevo]

Hey Portainer Devs,

After further testing, I'm still new to portainer.

I discovered "Portainer does connect to Bitbucket".

You must setup a an "app password" as more details are mentioned - https://portal.portainer.io/knowledge/how-do-i-configure-portainers-gitops-features-to-authenticate-to-a-bitbucket-repository

Would it be possible update the UI in Portainer for it to be easier to set different repositories?

I'd suggest another option similar to the Github formatting but instead simply the bitbucket repo URL and app password.

As an avid user, I still had a difficult time trying to get Bitbucket to connected.

It would be great to support "Gitea" too.

Not to mention, automatic rebuilding of stacks on a new "commits".

Thanks!