change - nouveau jenkinsfile

feature/testing
unknown 4 years ago
parent 1485bd0b52
commit 57d1bac326

91
Jenkinsfile vendored

@ -1,41 +1,80 @@
rm -rf $WORKSPACE/the_tip_top echo "
git clone git@172.17.0.3:cedric/The_Tip_Top.git $WORKSPACE/the_tip_top NEXTAUTH_URL='https://devops.dsp-archiwebo21-ad-ec-cb-mt.fr'
DATABASE_URL="postgres://postgres:dandanalaa@212.227.206.140:5454/thetiptop"
cd $WORKSPACE/the_tip_top
git checkout master
yarn install
yarn build
mkdir the_tip_top GITHUB_ID=YOUR_GITHUB_CLIENT_ID
GITHUB_SECRET=YOUR_GITHUB_CLIENT_SECRET
mv public/ the_tip_top/
NEXT_BUILD_ID=$(cat build/BUILD_ID)
LAST_COMMIT=$(git rev-parse HEAD)
# That's just for debugging purposes GOOGLE_CLIENT_ID=965228443747-049kq59pm43bd23aplfu9ja2333dpo5s.apps.googleusercontent.com
echo "{git: ${LAST_COMMIT}, ci: ${BUILD_ID}, next: ${NEXT_BUILD_ID}}" > the_tip_top/CI GOOGLE_CLIENT_SECRET=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
# trim package.json and leave only things that you need in production
cat package.json | jq '. | {name: .name, private: true, version: .version, scripts: {start: .scripts.start}, dependencies: .dependencies}' > the_tip_top/package.json
# I'm using next-compose-plugins, so here we need to dump config. If you have next.config.js as an object then just copy config file
NEXT_CONFIG=$(node -e 'var configFile = require("./next.config.js"); var config = configFile([], {}); delete config.webpack; console.log(JSON.stringify(config));')
echo "module.exports = ${NEXT_CONFIG}" > the_tip_top/next.config.js # result => {distDir: "build", poweredByHeader: false}
mv build the_tip_top/ EMAIL_SERVER_USER=contact@dsp-archiwebo21-ad-ec-cb-mt.fr
EMAIL_SERVER_PASSWORD=Acem@2022a
EMAIL_SERVER_HOST=mail50.lwspanel.com
EMAIL_SERVER_PORT=587
EMAIL_FROM=contact@dsp-archiwebo21-ad-ec-cb-mt.fr
cd the_tip_top
yarn install
cd $WORKSPACE/the_tip_top SECRET=thetiptop123
# dump folder tree structure just for Jenkins console output logs
tree -h -L 1 build/
tar czf $WORKSPACE/the_tip_top.tar.gz the_tip_top
cd $WORKSPACE
rm -rf $WORKSPACE/the_tip_top API_KEY=1234
" > ./.env
cat ./.env
npm -v
npm install
npm run build
npm run start
// rm -rf $WORKSPACE/the_tip_top
// git clone git@172.17.0.3:cedric/The_Tip_Top.git $WORKSPACE/the_tip_top
// cd $WORKSPACE/the_tip_top
// git checkout master
// yarn install
// yarn build
// mkdir the_tip_top
// mv public/ the_tip_top/
// NEXT_BUILD_ID=$(cat build/BUILD_ID)
// LAST_COMMIT=$(git rev-parse HEAD)
// # That's just for debugging purposes
// echo "{git: ${LAST_COMMIT}, ci: ${BUILD_ID}, next: ${NEXT_BUILD_ID}}" > the_tip_top/CI
// # trim package.json and leave only things that you need in production
// cat package.json | jq '. | {name: .name, private: true, version: .version, scripts: {start: .scripts.start}, dependencies: .dependencies}' > the_tip_top/package.json
// # I'm using next-compose-plugins, so here we need to dump config. If you have next.config.js as an object then just copy config file
// NEXT_CONFIG=$(node -e 'var configFile = require("./next.config.js"); var config = configFile([], {}); delete config.webpack; console.log(JSON.stringify(config));')
// echo "module.exports = ${NEXT_CONFIG}" > the_tip_top/next.config.js # result => {distDir: "build", poweredByHeader: false}
// mv build the_tip_top/
// cd the_tip_top
// yarn install
// cd $WORKSPACE/the_tip_top
// # dump folder tree structure just for Jenkins console output logs
// tree -h -L 1 build/
// tar czf $WORKSPACE/the_tip_top.tar.gz the_tip_top
// cd $WORKSPACE
// rm -rf $WORKSPACE/the_tip_top

Loading…
Cancel
Save