Closed rlenferink closed 1 year ago
Name | Link |
---|---|
Latest commit | 1333ea4b484d76899737bb5d14e17a29d0cc061d |
Latest deploy log | https://app.netlify.com/sites/celix-staging/deploys/64b3d9a36d5a820009190fa1 |
Deploy Preview | https://deploy-preview-26--celix-staging.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This makes the usage of Gitbox explicit for website deployments. Using Gitbox seems to be the only way for pushing branches, so make it explicit.
This because that allows us to use GitHub as branch source in Jenkins so that commits will have the build status shown in the GitHub UI (green or red check-mark).
I already took the liberty to create an additional site-gh job ans disable the site job. After merging this I'll delete the
site
job and renamesite-gh
tosite
again (to prevent broken links in e.g. documentation pointing the the Jenkins job).EDIT: The extra
git clone
is inspired by the Camel website: https://github.com/apache/camel-website/blob/fc25ff94e05f500db380bace10d6f728616c7266/Jenkinsfile#L95