Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Permission problems with firebase-deploy:0.3.4 Edited

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

@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
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

188 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you