5

Build trigger should wait untill the previous trigger for a same repos finishes its execution.

If i push twice to the repo, trigger executed twice at same time. I don't want this to be happen.

How to make the cloud trigger to wait for the previous trigger job?

Thanks in advance!

Shashikumar KL
  • 1,007
  • 1
  • 10
  • 25
  • circleCI's free plan did this and it was awesome! We use both right now but are really missing that feature ourselves in GCP. – Dean Hiller Jul 27 '20 at 22:52

3 Answers3

2

Use a build server like Jenkins that has all the basic functionality cloudbuild is missing. Then use the cloudbuild jenkins plugin so that the build jobs are still actually run on cloudbuild.

dan carter
  • 4,158
  • 1
  • 33
  • 34
1

You would have to implement this configuration and logic. It would have to evaluate if the build has been triggered and running and then wait for it to finish.

Maybe something can be done in order to check with the buildSteps and a waitFor or with a custom builder.

A combination between a call to the API and listing the Cloud Builds and they're statuses, implementing maybe waitFor in your config so it checks and then proceed with the build once the other is finished.

The thing is depending on how many builds you are submitting I don't have a clear idea on how you can assign a priority in the queue as it would go FIFO.

Someone else added a similar question here

Hope this helps.

Stefan G.
  • 890
  • 5
  • 10
  • waitFor can used inside a trigger steps and works between steps. but my issue is with different build triggers. – Shashikumar KL Jan 17 '20 at 15:10
  • I push a Code changes to repo, build get trigger and during build if i again push then it also start building. – Shashikumar KL Jan 17 '20 at 15:12
  • 1
    The only way of getting a "queue" in Cloud Run I can think of is by evaluating the status of the builds as I previously mentioned with an API and reacting according to that. As I mentioned in my answer. I have not seen any way of doing this by default. – Stefan G. Jan 17 '20 at 15:19
0

There's nothing "out of box" for this as stated above.

The only two things I could think of are:

  1. adding an initial step that queries the builds using gcloud builds list and filtering by trigger-id (you'd have to set this manually as I don't think you can get this from the build itself as a variable). Then check if there is more than 1 build running, sleep for whatever, and check again. The only thing you have to watch out for is after the checking again, if a new build starts you need to have a way of distinguishing that (again since we don't know the build-id) and your build... or you will end up with a continuous loop and no builds.

  2. The idea would be to have a storage bucket and each build to create a file with some sort of naming convention so we can build a "queue" system. At the beginning of each build, we would mount the storage, search for any other files, and then create ours.

Example:

  • First build -- no other builds, we create file 'build-name-1" ... we then start building, and at the end, we delete that file.
  • Second build (while the first is running), we mount the storage, check for other files, we see that there is one file, so we create a new file incrementing the last number (build-name-2) and sleep... we wait until this file is not there, and then we can start our build, and at the end, delete the file again.
  • (and so on for three, four, etc)
Lance Sandino
  • 316
  • 1
  • 4