---
# System prepended metadata

title: Environments
tags: [Global]

---

###### tags: `Global`

# Environments

*Author: **Jérémy Habit***
*Created at: **02/03/2021***
*Last updated : **16/04/2021***

# Front's WEB environments

| Env | Url | Branch |
| -------- | -------- | -------- |
| Develop     |  https://dev.upply.com         | main     
| Quality     |  https://quality.upply.com     | main     
| Preprod     |  https://preprod.upply.com     | not a branch, but tags

As front end team, the Prod env isn't our responsability. There is a prod team to maintains this env. Our application is only for connected user, that's why it is not deployed on upply.com but on app.upply.com.

Prod : https://app.upply.com 
Prod Hubspot CMS : https://upply.com

Jenkins job for deploy quality : https://ci.upply.com/job/deploy-helm-quality/
Jenkins job for deploy preprod : https://ci.upply.com/job/deploy-helm-preprod/

## Feature environments

### For feature
As the front team, we have the possibilit to have dedicated environment to test a specific feature before it goes on main.
For example, feature A is composed of 4 US : A1, A2, A3, A4 which contains dependencies. If we were to put A2 into main (so dev and quality), it would be troubles.
To create a feature environment, we need to have a *'feature release'* branch following this pattern:
`feature-release/*-integ `
Currently, we have have one for example named 'upfront-payment'. ALl devs done for this fonctionnality will be available on this branch.
It will only be merged on main when approved by PO.
Associated url can be find at : [upfront-payment.dev.upply.com ](https://)
 
### For support
We also use the feature branch to ensure support for the production version.
We created one as soon as a version is published to use in case of hotfix.
`feature-release/support-*-integ `
Where x is the version number with - instead of .
For example: `feature-release/support-2-37-x-integ`

Jenkins job to deploy on a feature branch : https://ci.upply.com/view/Intégration/job/marketplace-integ/
If job fails, can be manually trigger on : 
https://ci.upply.com/view/Intégration/job/marketplace-integ-manual/



# Back's environments

The website make request to the middleware API only.Then the middleware has the responsability to trasnfer ours requests to the good API : user api, message api, smart api, etc.

MIDDLEWARE_ROOT_DEV : https://dev-api.upply.com
MIDDLEWARE_ROOT_QUALITY : https://quality-api.upply.com

