How to force a rebuild on Heroku without pushing using heroku-release-retry plugin

Published on March 02, 2019

Tagged: #devops

Follow me on twitter for more posts like this

I had a deploy on Heroku fail because of a database issue. The code deployed but a dependency meant that the application couldn’t start. If you try to run git push heroku master you just get “Everything is up-to-date”.

My code didn’t need to change but I wanted the “deploy” to be re run WITHOUT pushing a new commit.

The old way I would do this is to create a file called “force-rebuild.txt”, add some random text and make a commit or branch merge to master to kick off my CI/CD pipeline.

It turns out there is a neat plugin for Heroku called heroku release retry that lets you retry the last deploy without resorting to adding bad commits to your repository.

It’s pretty straight-forward to use. To install:

$ heroku plugins:install heroku-releases-retry

then just use:

$ heroku releases:retry
Retrying v48 on darragh-starter... !
 !    Release command declared: this new release will not be available until the
 !    command succeeds.
Retrying v48 on darragh-starter... done, v49
Running release command...

Sequelize CLI [Node: 10.14.2, CLI: 4.1.1, ORM: 4.42.0]

Loaded configuration file "src/datapersistence/config/config.js".
Using environment "production".
No migrations were executed, database schema was already up to date.

you can also specify the app name if you need to

$ heroku releases:retry --app darragh-starter
$ heroku releases:retry
Retrying v48 on darragh-starter... !
 !    Release command declared: this new release will not be available until the
 !    command succeeds.
Retrying v48 on darragh-starter... done, v49
Running release command...

Sequelize CLI [Node: 10.14.2, CLI: 4.1.1, ORM: 4.42.0]

Loaded configuration file "src/datapersistence/config/config.js".
Using environment "production".
No migrations were executed, database schema was already up to date.
Darragh ORiordan

Hi! I'm Darragh ORiordan.

I live and work in Sydney, Australia building supporting happy teams that create high quality software for the web.

I also make tools for busy developers! Do you have a new M1 Mac to setup? Have you ever spent a week getting your dev environment just right?

My DevShell tooling will save you 30+ hours configuring your dev environment with all the best modern tools. Get it here

https://darraghoriordan.gumroad.com/l/devshell


Read more articles like this one...

List of article summaries

#devops

Extract user profile attributes from an Azure ADB2C tenant using the Microsoft Graph API

I had to retrieve a list of users from an Azure Active Directory B2C instance today. I thought I could just go through the Azure UI but that’s limited to short pages of data and limited attributes.

There is a CSV export provided on the UI but you won’t get the required identity objects in the csv output if you need a user’s signin email address.

I had to use the Microsoft Graph Api to get what I needed. This is a bit hacky but it does the trick!

#devops

Force restart your Azure App service site and host

Sometimes your Azure App service host will need to be restarted. You can do this but it’s hidden away in the Azure resource manager site. Here’s how to find it!

#devops

Scheduling a feature toggle using no-code with Azure Logic Apps

I use launch darkly to toggle features on an app. There is one third-party dependency that has regular scheduled maintenance and I need to toggle the feature on and off on schedule.

Launch Darkly has built in scheduling to handle this scenario but you have to be on the enterprise plan to use it. The enterprise plan is too expensive to upgrade to for scheduling alone so I needed to find a different way to automate this.

#frontend-development

Avoid rebuild of React App in every CI stage

If you have a react app you can use env vars like REACT_APP_MY_ENV_VAR in your application and React will automatically pull them in to your app when you build the production application.

This is very useful but if you have variables that change for each environment and your application build takes a long time, you might want to avoid building unnecessarily in CI. For example you might have a QA environment and a Staging environment that have different configuration.

We type-check our code on each build and that was taking 5 minutes+ to build each environment so we had to make it faster. We changed our app from using REACT_APP env vars to using a configuration file that we could quickly write to using CI.

Our CI system is Azure DevOops so the CI scripts here are specifically for Azure DevOps but they apply to most CI systems with small changes.

The real work happens in a Node.js script that would work anywhere.