fakoe
opened 8 months ago
-
By default, job names here are taken from jobs defined in default branch of the project. However, you may input other job names and press ENTER to add the job as required.
-
Ok, thanks for the info.
The pull requests not working seemed to be more a problem of an very outdated branch, that still contained a very early version of the buildspec I created and therefore failed to execute the build before the merge. The developer updated the branch and I already set the branch to be the default, to get the build displayed in the branch protection recommendations.
-
So I think the issue is resolved, and can close this?
-
Yes
-
Previous Value Current Value Open
Closed
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Affected Versions |
11.9.5
|
| Labels |
No labels
|
Issue Votes (0)
Watchers (2)
Hi,
I have a branch protection rule for a specific branch, which has the following settings:
As you can see there are three builds listed (these are from the master buildspec).
But within the branch, there is a buildspec, that actually has another build:
Since the most recent update, this build can't be found or selected within the branch protection rules anymore. Which means, our Pull Requests can't set that build to be successful as mandatory for a merge anymore...
Could you help me to elaborat, what I have to do to to get this back running? I haven't changed the setup for four months now and it worked three days ago. Our developers can now merge their pull requests without having to run the build, which is... unpleasant.