Questions tagged with AWS CodeCommit
Sort by most recent
Browse through the questions and answers listed below or filter and sort to narrow down your results.
CodeCommit merge-pull-request-by-three-way merges by commit-id rather than branch
We are trying to use CodeCommit and CodeBuild to implement a process by which when a developer creates a pull request to merge changes from his/her branch, rather than merging into master, he/she requests the changes be merged into an integration branch. Before the merge, the integration and master branches reference the same commit id. After the merge of the developer's changes into the integration branch, integration is now ahead of master and the corresponding CodeBuild job builds the integration branch. Once all the unit and integration tests have been verified, the integration branch is then merged into master branch and integration and master will once again reference the same commit id. What I have observed is that when I execute a merge-pull-request-by-three-way (cli) specifying the pull request that was created to merge from the developer branch into integration, the end result is that the code is merged into both the integration and master branches. Unlike merge-branches-by-three-way, merge-pull-request-by-three-way does not give you an option to specify the target branch, but it shouldn't since the pull request already specifies the target branch into which changes are to be merged. It is unclear to me if this is happening because the commit id's are the same and the merge is doing it based on that, or if CodeCommit thinks master is the "current" branch (referring to the git-merge behavior), but regardless, the result was not what I was expecting. Is this behavior of ignoring the pull requests target branch when merging using merge-branches-by-three-way, a bug or is this expected behavior/"feature" of merge-pull-request-by-three-way (and possibly the other merge-pull-request-* commands) and I should instead use merge-branches-by-three-way.
Lambda API Calls duration
I have a lambda function that makes calls to different aws services. For example: DynamoDB, CodeCommit, SES. My problem is the one call's duration. codecommit.getMergeOptions() for some reason ( I want to know which ) this call last too much compared with others. For example codecommit.getDifferences last 300 ms but codecommit.getMergeOptions() 900 ms. Why that happen?
Can I connect a Sagemaker "Studio" instance to a private github repository?
I've successfully connected a Sagemaker "notebook" to a private github repository, but wondering if it isn't possible for a studio instance? Failing that is there an easy way to get the remote codecommit git url for an existing "studio" instance so that code there can at least be pulled to my local machine?
Is it possible to connect CodeBuild to CodeCommit over PrivateLink ?
I am able to connect CodeBuild with CodeCommit via NAT gateway in public subnet -> Internet Gateway. As both CodeCommit & CodeBuild are on AWS, I am trying to avoid using Internet Gateway. Here's what I have done so far - Created endpoint for CodeCommit - Attached it to private subnet - Configured CodeBuild to use the same subnet I am curious on what can be done here to avoid using Internet Gateway.
use study link embedded in the same window of amazon mturk (iframe)
Hello, I am trying to create a study that opens in the mturk webpage instead of a new window. In the study we are using webcam and I got this message when publish the study in sandbox (so I could try it out). Warning message says: Unable to connect to your webcam, please try again. Perhaps it is being used by another application. So what should I edit in the HTML format so I can give access to webcam using the same page? Is that the solution or should I try to search something else?
is there a service role that needs to be attached to AWSCodeCommitPowerUser policy for codecommit , we are integrating with Jenkins and with only policy the code /repo is not getting checked out
Got started with creating a repo using codecommit , respective users (IAM) with needed policy AWSCodeCommitPowerUser. Also have integrated Jenkins in aws ec2instance using the security credentials of the IAM user. The issue is that code is not getting checked out. There is a old post on code commit integration with jenkins https://aws.amazon.com/blogs/devops/integrating-aws-codecommit-with-jenkins/ (mentions service role tagging with policy) however there is no mention of the same in the current info center