Hi,
I am trying to configure deployment to the firebase hosting using the firebase-deploy:0.3.4 pipe. Before the deployment I am trying to modify file (substitute URL in the index.html to my back-end but fails due to file system permissions:
=== Deploying to 'XXXXXX'...i deploying hosting
Running command: whoami
root
Running command: ls -lah build
total 244
K
drwxr-xr-x. 4 nobody nogroup 4.0K Nov 19 11:34 .
drwxrwxrwx. 7 nobody nogroup 4.0K Nov 19 11:34 ..
-rw-r--r--. 1 nobody nogroup 1.4K Nov 19 11:34 asset-manifest.json
drwxr-xr-x. 8 nobody nogroup 4.0K Nov 19 11:34 assets
-rw-r--r--. 1 nobody nogroup 4.6K Nov 19 11:34 index.html
-rw-r--r--. 1 nobody nogroup 1.3K Nov 19 11:34 precache-manifest.49b84e81618eb1671949030bc548f9e9.js
Running command: sed -i 's+${API_URL}+https://example.com+g' build/index.html
sed: couldn't open temporary file build/sedwtS8Jx: Permission denied
my bitbucket-pipelines.yml
image: node:10.3.0
pipelines:
default:
- step:
name: Build
caches:
- node
script:
- npm ci && npm run build
artifacts: - build/**
- step:
name: Deploy to Demo
deployment: demo
script:
- pipe: atlassian/firebase-deploy:0.3.4
variables:
FIREBASE_TOKEN: $FIREBASE_TOKEN
PROJECT_ID: $FIREBASE_PROJECT
EXTRA_ARGS: '--only hosting:demo'
DEBUG: 'true'
my firebase.json
{
"hosting": [
{
"target": "demo",
"predeploy": [
"whoami",
"ls -lah build",
"sed -i 's+${API_URL}+https://example.com+g' build/index.html"
],
"public": "build",
"ignore": [
"firebase.json",
"**/.*",
"**/node_modules/**"
],
"headers": [
{
"source": "/",
"headers": [
{
"key": "Cache-Control",
"value": "no-cache, no-store, must-revalidate"
}
]
}
]
}
]
}
can I some how change the directory and file permission before the pipe starts?
@Dmytro420 I suppose you can do chmod for build directory before you share this artifact to the next step, just after npm run build, firebase should allow this. If not , play with permissions in predeploy script.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.