Permission problems with firebase-deploy:0.3.4

Dmytro420 November 19, 2019

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 244K
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?

1 answer

0 votes
Halyna Berezovska
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 24, 2020

@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.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events