Change Details

While on GitHub, we deployed the branch of every pull request to Netlify. While that was initially intended for Browser testing, we ended up not using it for that purpose because we decided to use Cypress and the dev server for that purpose. However, it turned out that branch hosting is very useful in order to give UX a chance to review a Pull Request before it is merged. We should look into making this possible again. Either by creating a new Jenkins job to deploy to Netlify again or by deploying the patches to some internally hosted platform. Ideally, there would be only one deploy-target for each patch that is then subsequently updated with every patchset.

While on GitHub, we deployed the branch of every pull request to Netlify. While that was initially intended for Browser testing, we ended up not using it for that purpose because we decided to use Cypress and the dev server for that purpose. However, it turned out that branch hosting is very useful in order to give UX a chance to review a Pull Request before it is merged. We should look into making this possible again. Either by creating a new Jenkins job to deploy to Netlify again or by deploying the patches to some internally hosted platform. Ideally, there would be only one deploy-target for each patch that is then subsequently updated with every patchset. This could also be (something similar to) https://patchdemo.wmflabs.org/ if we do not want to use Netlify or verecel.

While on GitHub, we deployed the branch of every pull request to Netlify. While that was initially intended for Browser testing, we ended up not using it for that purpose because we decided to use Cypress and the dev server for that purpose. However, it turned out that branch hosting is very useful in order to give UX a chance to review a Pull Request before it is merged. We should look into making this possible again. Either by creating a new Jenkins job to deploy to Netlify again or by deploying the patches to some internally hosted platform. Ideally, there would be only one deploy-target for each patch that is then subsequently updated with every patchset. This could also be (something similar to) https://patchdemo.wmflabs.org/ if we do not want to use Netlify or verecel.