[Feature request] Add support for self-hosted Gitlab(CE) or GitHub Enterprise

[daannijkamp]

Feature request: add support for the self-hosted version of Gitlab (CE).

Currently the Amplify console has support for Gitlab.com, but not for the self-hosted variant. At this moment it is unfortunately a dealbreaker why we do not yet use Amplify Console for all projects/sites. As a workaround we now use the S3 and CodeCommit (by using the mirror repository function of Gitlab).

[ltickett]

Hey guys, does anyone have a workaround for deploying to AWS Amplify from a self-managed GitLab Pipeline?

Yes, I built a CI pipeline to do it- see https://github.com/aws-amplify/amplify-hosting/issues/14#issuecomment-1207938529

[johnenderson]

6. usando a confirmação de código da AW

The big problem is not being able to create a site display equal to functionality released only for Github. This is really sad. In addition to having to deploy the site at Gitlab Auto hosted, I would also like to be able to have the site preview at AWS Amplify via Pipeline de CI/CD.

[Gayathriec512]

+1

[moigonzalez]

+1

[mzhafez]

+1

[gsi-chao]

+1

[Bradley-Cooley]

+1

[MrMegaNova]

Probably one of the most requested feature, I don't understand why any AWS engineers doesn't respond to this issue. At least to give us information about possibilities / priority of this topic. Any information or explanation would be appreciated :pray:

[jesusr00]

+1

[advoria]

+1

[maunzCache]

Probably one of the most requested feature, I don't understand why any AWS engineers doesn't respond to this issue. At least to give us information about possibilities / priority of this topic. Any information or explanation would be appreciated 🙏

@Jay2113 you are the most active person here. Can you give us any insights?

[matt-wood-ct]

Probably one of the most requested feature, I don't understand why any AWS engineers doesn't respond to this issue. At least to give us information about possibilities / priority of this topic. Any information or explanation would be appreciated 🙏

I think AWS have given up on this service like so many before it.... look how dead the actual repo is, 1 active dev around 6 commits in the last 30 days.

Feels disappointing being ignored/abandoned by the AWS team again (I've been through the below cycle twice now).

1. AWS half implement an interesting service/workflow system
2. Market and push it onto devs
3. Developers adopt it for their active project(s)
4. AWS provide highly active support for approximately 6 months
5. AWS move on to a new unrelated system, abandon the project leaving hundreds/thousands of devs high and dry
6. ????
7. Profit

[elabbarw]

I guess this is dead...

[maunzCache]

@calavera would you be able to give feedback on the topic? I'd still love to.move this forward or have a definitve "Won't do".

[swaminator]

Hi folks, we appreciate all the requests here. Unfortunately this feature has not been prioritized this year. We will consider this when we do our 2025 planning.

[benydc]

+1