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

best practice configuring SPA application using Bamboo

What is the best practice to continuously build and deploy a static javascript/css/html application (SPA)?

Coming from a backend development world, normally we build once and then deploy to various targets where the configuration sits in the environment. So for a basic Java web app, we'd just setup one build in Bamboo, but link it to various deployments.

However, we're moving towards more SPA type applications and these all run in the client browser. So, there is no environment to get configuration from. In this case I'm using a React/Redux app that is bundled/wrapper using Webpack and it's build using npm/node.

The only way I have found to be able to configure this correctly is by having the environment/configuration injected during the npm build phase. Because, basically, after that, you're left with a folder of minified and uglified and hashed javascript files so it's virtually impossible to do post-build variable updates.

So, now I have one project that has as many builds as that it has deployment targets and then for each I have to create one single deployment task.

Given that I'm surely not the only one building SPA type applications, I was wondering what the best practice for this is?

Are you perhaps doing the npm build during the deployment task? And instead of having the build folder as artifact, use the entire source tree?

1 answer

0 votes
devpartisan Atlassian Team Aug 30, 2017

To restate your problem, Bamboo's deployment model depends upon the notion of a fixed "artifact" (like a Java jar), while Webpack's build model is about binding configuration into the web files (like URLs). The "difference of opinion" is confusing.

One thing that I would recommend is taking more of a continuous deployment approach. Namely, don't worry about deploying into multiple environments, just deploy straight to production. That doesn't necessarily mean that every deployment is immediately visible to your users. Rather, use Webpack's understanding of the whole dependency tree to create "versions" of your SPA. Then use your web server/load balancer to point to the version that you want to reveal.

Use Bamboo's deployment projects to manage the "pointer". For example, users access "app.example.com" but it points to "app.example.com/1/". Testers access "test.app.example.com" but it points to "app.example.com/2/". When you want to "deploy", Bamboo changes the configuration of the web server, rather than moving any real artifacts.

It feels like this approach would avoid too much conflict between the tools. That said, there are many ways to solve this one.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

220 views 4 6
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