- Issue created by @justafish
- 🇺🇸United States drumm NY, US
As the Drupal Association, we don’t really want to be in the business of being integrated into individual site deployments. That’s not something we’re prepared to provide support for, or guarantee availability, especially for free. As far as I can tell, the primary use of environments is the continuous deployment part of CI/CD.
Enabling for test environments on clusters which the Drupal Association does not manage or provide could be interesting. I’d like a bit more context on the use case here.
GitLab’s UI doesn’t have a way to add explanations around supported uses of environments, so we’d have to weigh this against the inevitability that it might be used in ways we don’t really want to support.
- 🇬🇧United Kingdom justafish London, UK
we don’t really want to be in the business of being integrated into individual site deployments. That’s not something we’re prepared to provide support for, or guarantee availability
Absolutely! This is just enabling the exposure of links to environments in the UI that you can already deploy to with GitLab CI - the expectation isn't that the DA would be hosting environments, it's just a nice way to link to external ones. You can already see it partially working on this job here with the "This job is deployed to" banner: https://git.drupalcode.org/project/experience_builder/-/jobs/5936806
A couple of things we're using it for in Experience Builder which would be useful to surface on the MR itself:
1. Pages deployments, which are already surfaced here https://git.drupalcode.org/project/experience_builder/pages
2. Showing test result reports which are richer than JUnit, for example: https://project.pages.drupalcode.org/-/experience_builder/-/jobs/5906499...
3. It'd also be useful to display Tugboat environment links if we ever set that up again. - 🇺🇸United States drumm NY, US
Right now we’re thinking we want to stay with the current behavior, since we do not want to encourage deployments from git.drupalcode.org. We have seen what looks like people trying to deploy production sites using the community infrastructure a few times before.
If I understand correctly, for experience builder, it sounds like things are working, but some links and quality of life features are not accessible.