Heroku not implementing latest pushes from github repo in deploy - heroku

I have three different apps I have set up on heroku. When I run the apps, the apps show up in the browser, but they are very old versions of the apps.
I have configured each project to deploy a new build everytime changes are pushed to the linked github repos, and the activity feed claims the builds are successful. The logs also don't appear to show any errors.
I also know heroku is receiving the pushes because it is running new builds when I push and when I monitor the "see diff", the changes are displayed.
I am at a total loss as to what is going on and it's very frustrating. If nothing else, does anyone have any suggestions for similar services to heroku that do not have so many deploy issues?

Try and make sure heroku has the latest, from a local GitHub repo clone:
cd /path/to/my/local/clone
git remote add heroku /url/heroku/repo
git push --force heroku HEAD:master
That will make sure there is no "detached HEAD" situation on the heroku side, which would explain why the push does not update the working tree.

Related

Heroku CI status badge

Im using Heroku CI to run tests in Heroku Pipeline. I would like to add CI status as badge in the README.md file at Github, for master branch.
But so far, I have not found out-of-box solution on this request. Any tip on workarounds to get this work without building the ci-badge solution myself?
Few inspirations I have found:
https://github.com/heroku/heroku-ci: (see the status badge on top of README.md. However, image URL is specifically searching for pipelines for the Heroku CI application, and doesnt work with other applications)
https://github.com/pussinboots/heroku-badge: displays deploy badges, which is not important for me. Also, this repo/app doesn't seem to be maintained anymore (last commit 2 years ago)
I agree that a good Heroku CI badge generator is lacking! Heroku is still running one here, but the linked GitHub repo is unfortunately 404 (and, as you noted, that generator doesn't seem to work with pipelines other than Heroku's own, which makes it not that useful).
In any and all cases, inspired by your question, I went ahead and created a Heroku CI badge app that you can deploy to your Heroku account! Please find it here.
Feel free to open issues / fork it if you want to change anything.
Cheers

Parse Cloud Code development and production version control

I have a Parse application that will soon be used in production, and I need to be able to continue developing things locally without breaking things for live users when I make changes to cloud code.
I have cloned the app, and can now deploy to either the production or staging app using the parse deploy staging and parse deploy production commands, however these commands only work if I am on the master branch.
What I would like to have are two branches in git, one that can be pushed to my staging app, and the other that can be pushed to the production app.
At the moment all I can think of doing is to just tag commits in master as being pushed to production, then continue ontop of that for development, but that is going to be a nightmare if I need to patch the released app when I have all my development changes on master.
Pushing directly to the heroku git repos doesn't seem to work either, parse deploy must be doing something extra (plus it tries to build the app so I can see when things go wrong).
Another issue is that when other developers start working on this as well, we won't be able to all deploy to the development server, and as far as I know there isn't an easy way to run parse cloud code locally on windows.
What is the best way to manage all this?
You have to setup parse-server (use parse-server-example), parse-dashboard and mongoDB on a local or remote development server. You and your team can now develop everything locally, test and then deploy to production.

How to use set up Heroku Integration with PyCharm

So, I've download the Heroku Integration, with PyCharm 2.7.2. I've put in the API key, added an app with a name I chose. I want to create just a basic django app on a heroku free account. So, what do I do now? Could someone please give me some basic instructions as to how you get started with actually uploading all the stuff in your project to Heroku?
Not sure about the pycharm integration, but the easy answer is git push to heroku.
When using pycharm, I just do Menu >> VCS >> Git >> Push. Then if heroku is not your default remote (origin), check the box for push to alternate remote/branch. I choose heroku and master and away it goes!

Adding an iPhone Project to an existing Github Project

I'm working on a bit of documentation code for an API project.
Someone else already has an existing github account where some people have already submitted a few projects. I will call it {http://github.com/monkeyhouse/}
I've created a project in Xcode (iPhone app), and have that stored under my normal Xcode git, which is backed up everything is fine.
What is the right bit of git foo that I need to put Xcode Project into
{http://github.com/monkeyhouse/examples/iPhoneClient}
I've tried creating a symbolic link to the project on my machine and that didn't work.
Following is a common way to do what you're wanting to do on Github:
Fork http://github.com/monkeyhouse/ under your own Github account.
Clone your forked version of the repo to your development machine.
Make the modifications you want directly to your cloned repo (e.g., don't use a symlink), adding examples/iPhoneClient to the local repo, and commit the changes.
Push your changes to your public Github fork of http://github.com/monkeyhouse/.
Submit a pull request with http://github.com/monkeyhouse/ to have them bring in the changes you pushed to your forked version if they're happy with them.

I moved my source directory and can no longer push to Heroku

I've been happily using heroku to beta test a Rails app, and recently hit a snag. I prefer Mercurial to git and have been using hg-git to push my app to Heroku. This was working fine until I branched my repo (doing a branch by cloning in kiln, if that matters). My folder structure used to look like this:
~/Code/MyApp
And is now:
~/Code/MyApp/trunk
~/Code/MyApp/current
Where trunk is the old 'root' copy, and current is the recently created branch. I did try going back to my old directory structure (just the root MyApp folder) and that didn't change anything.
Now when I push to heroku, it does this:
pushing to git+ssh://git#heroku.com:myapp.git
importing Hg objects into Git
converting revision 7491a23b35ee405325bb7a024f3cbee047a59dcd
*snipped all the revisions*
creating and sending data
And then just stops. No errors, and when I check the site, the change didn't happen. And there's nothing in the error logs either. So what gives? I'd rather not create a separate git repo in the app; that'll get messy quickly.
It sounds to me like you're not doing the equivalent of a git push heroku master, but instead pushing your new branch.
Heroku will only deploy the master branch.
For more on topic branches, see here: http://neilmiddleton.com/deploying-topic-branches-to-heroku/

Resources