Gulp to Github: am I missing something?


#1

This seems like it should be easy, but it’s eluding me at the moment…

How do you take the files in the filesystem from a build with Gulp and push those to a git repo?

I feel like its obvious but my brain is fried right now.

Any help would be much appreciated.


#2

Ideally, the following pipeline is what I’d like to be able to do with Buddy:

  1. When a push is made to a particular branch (let’s call it “pre-build”), it starts the pipeline actions.
  2. The first action is executing a task runner of some kind. In my case, we’re using Gulp to build some files from the “pre-build” branch.
  3. On successful completion, the build files that have been created and reside somewhere in the Pipeline Filesystem are then pushed to another branch on the same repo, and in my case, this would be the master branch.

Of the two actions that are listed under “Deliver to version control”, only the WebDAV option asks you which files to transfer. Ideally, the Git Push action would do the same, but from all appearances, it basically pushes unbuilt files which makes it effectively useless in this context.

This seems like something you should be able to do with this CD/CI tool, given all the other available options. Hopefully, it’s just me missing something entirely. I’ve played around with a few settings, but nothing seems to work.


#3

Solved my issue. The push process was utilizing the same .gitignore file throughout, and I needed to use a modified .gitignore file.


#4

Hey madrid1979, can you describe how did you solved your issue? I am having the same problem right now.


#5

Sure thing. So the last action in my pipeline is “Deliver to Version Control > Git Push” and my settings are such that I define the branch to push to, and I have “Use custom .gitignore” checked. In the Gitignore field, I set the files/paths/etc that I want removed from the build generated from the action(s) prior, which for me was a simple Gulp action (“npm install”). If you don’t use the custom gitignore option, it will use the one pulled from your starting branch, which probably has stuff you don’t actually want ignored after the build. Hopefully this makes sense. It made sense after I figured out that the gitignore is maintained throughout the pipeline until you specify using a different one.