Trigger builds with custom config from our UI

[lislis]

Folks who took a close look at our docs may have already discovered the Trigger Build API.
It has already been present in our previous v2 API and is of course also present in the current v3 API.

Now we have the this functionality also available in our web client.
Read our blog post for more information.

If you have any feedback for us please let us know in this ticket!

[matthewd]

Hi! I just tried this out... I clicked More options -> Trigger build, left branch as master, and in custom config I entered:

addons:
  postgresql: "9.4"
dist: precise

But the resulting build didn't seem to do that: https://travis-ci.org/rails/rails/jobs/271323346/config

Did I do something wrong? 😕

[iriberri]

Hi @matthewd, thanks for bringing this issue to our attention! I could reproduce the behavior you describe in your comment and our team is taking a further look at this. We'll keep you posted as soon as we have more information or the issue is solved.

Thanks for your patience.

[iriberri]

@matthewd the issue has been fixed, thanks again for reporting it. Could you please give this a try and let us know how it goes? Thanks!

[matthewd]

@iriberri 👌🏻 perfect, thank you!

[gdubicki]

When is the branch list in the web ui updated? Because I have pushed a new tag (v0.17.2 in https://github.com/egnyte/gitlabform repo) about 30 minutes ago and I still don't see it there..

[bokobza]

Hi,
My list of branches in the triggering build modal only shows 'master' and an old inactive branch.
I can't see any of my new branches and I can't delete the old one (it's not even there on GitHub).
Is there any way to refresh this list?
This is my repo in case it helps: https://github.com/bokobza/StratisBitcoinFullNode
Thanks 😄

[backspace]

Hey, sorry for the delay in responding, @gdubicki. If this happens again, could you let us know if refreshing the tab causes the branch to show? It’s my suspicion that that’s not the case, but if it does help, we could trigger a refresh of branches when the dialogue opens.

I think the true problem is that we don’t currently have tracking for new branches that are created on GitHub. If you manually sync from your profile page, the UI will eventually know about the new branch, but I imagine that is a hassle. Can you describe the workflow you’re experiencing this problem with?

@bokobza, our API is returning the deleted branch with a flag indicating that it no longer exists on GitHub; I’ve changed the UI so it no longer shows those branches in the select.

As for the new branches, we’re entirely dependent on GitHub for what branches a repository has, and all I see there is master:

[cotsog]

@stephencornelius suggested as an improvement on this feature that it would be nice to be able to trigger a build on pull requests. :)

[alibitek]

Yes! It would be very nice to be able to start a rebuild on pull request triggered build jobs!

Case in point, build jobs often fail due to errors outside of the changes made in the pull request, e.g. environment setup or travis runner overload or timeouts when pulling dependencies:

• "curl: (7) Failed to connect to dl.google.com port 443: Connection timed out"
• "The job exceeded the maximum time limit for jobs, and has been terminated."
• The command "sudo -E apt-get -yq --no-install-suggests --no-install-recommends --force-yes install libstdc++6 fonts-droid clang-format-5.0" failed and exited with 100 during .

As a pull request submitter you have no control over these issues.
If the build fails you have to manually trigger another build by force pushing into the git branch and hope everything goes well this time.

https://blog.travis-ci.com/2017-08-24-trigger-custom-build mentions that you can trigger builds from the web client using the "Trigger build" option.
However, as a user with no commit access to the project and while logged in into travis-ci.org, I cannot see "Trigger build" menu option in the "More options" menu.
Example failed job: https://travis-ci.org/flutter/plugins/jobs/323672495

How can I trigger a rebuild from the web UI without doing a manual trigger again and without closing and reopening the pull request?
As mentioned in https://stackoverflow.com/questions/17606874/trigger-a-travis-ci-rebuild-without-pushing-a-commit

Tried the Travis CLI client and it doens't allow to restart build jobs outside your own fork. When I try to run travis restart 1283 it says build 1283 has been restarted but if you go and look in the web ui, there is no rebuild going on.

I think a web option should be available, where people who submit pull requests can rerun failed build jobs for their own PRs even when they do not have write/collaborator access to the project.

[allejo]

So when commits are pushed in bulk, only the latest commit will be tested in travis. It would be nice if you could trigger a build for a specific commit hash if you'd like to test one of those untested commits to see where something broke.

[fabiocarvalho777]

Hello. Could someone help me to understand why this customer build of mine failed? There are no error messages whatsoever in the console, or anywhere. By the way, it looks like the console messages just truncate, or stop, abruptly.