Error in CDK 1.14.0: "Only a PipelineProject can be added to a CodePipeline"

I tried updating our CDK stacks to latest version but encountered a new problem with CodePipeline:

cdk/node_modules/@aws-cdk/aws-codebuild/lib/project.ts:766
      throw new Error('Only a PipelineProject can be added to a CodePipeline');
            ^
Error: Only a PipelineProject can be added to a CodePipeline
    at Project.bindToCodePipeline (cdk/node_modules/@aws-cdk/aws-codebuild/lib/project.ts:766:13)
    at CodeBuildAction.bound (cdk/node_modules/@aws-cdk/aws-codepipeline-actions/lib/codebuild/build-action.ts:117:26)
    at CodeBuildAction.bind (cdk/node_modules/@aws-cdk/aws-codepipeline-actions/lib/action.ts:30:17)
    at Pipeline._attachActionToPipeline (cdk/node_modules/@aws-cdk/aws-codepipeline/lib/pipeline.ts:346:37)
    at Stage.attachActionToPipeline (cdk/node_modules/@aws-cdk/aws-codepipeline/lib/stage.ts:136:27)
    at Stage.addAction (cdk/node_modules/@aws-cdk/aws-codepipeline/lib/stage.ts:86:29)
    at new Stage (cdk/node_modules/@aws-cdk/aws-codepipeline/lib/stage.ts:38:12)
    at Pipeline.addStage (cdk/node_modules/@aws-cdk/aws-codepipeline/lib/pipeline.ts:298:19)
    at Object.exports.addSourceAndBuildStages (cdk/pipeline-master.ts:117:12)
    at Object.exports.createBuildOnlyPipeline (cdk/pipeline-build-only.ts:27:25)

Is there something we need to change now with the latest version?

Reproduction Steps

export const addSourceAndBuildStages = (
  pipeline: codepipeline.Pipeline,
  repository: codecommit.IRepository,
  project: codebuild.Project) => {

  const source = new codepipeline.Artifact('Source');
  pipeline.addStage({
      stageName: 'Source',
      actions: [
          new codepipeline_actions.CodeCommitSourceAction({
              actionName: 'Source',
              repository,
              output: source,
              role: codeCommitRole(pipeline.stack),
          }),
      ]
  });
  const buildOutput = new codepipeline.Artifact();
// The problem is caused when adding following stage:
  pipeline.addStage({
      stageName: 'Build',
      actions: [
          new codepipeline_actions.CodeBuildAction({
              actionName: 'Build',
              input: source,
              project,
              outputs: [buildOutput],
          }),
      ]
  });
  return buildOutput;
}

Environment

• CLI Version : 1.14.0
• Framework Version: 1.14.0
• OS : Macbook
• Language : TypeScript

Other

---

This is 🐛 Bug Report

[markusl]

I see. For us this is a breaking change and require us to update our stacks and pipelines. We previously used just Project which worked fine for our use.

The nasty thing is that when updating all pipelines, we again hit the #4465 and need to manually deploy all pipelines one-by-one to avoid hitting the resource limit.

[markusl]

When we quite mechanically converted our pipelines to CDK, we weren’t aware of differences between PipelineProject and Project . TBH it still is not quite clear to me and the documentation does not help: “A representation of a CodeBuild Project” vs. “A convenience class for CodeBuild Projects that are used in CodePipeline.”.

The versioning scheme is not problematic for us, and neither is minor change in code but since #4465 this became quite much work for not a clear reason. If you need customers to move to the proper construct, would it be possible to add a some kind of warning first before enforcing build-breaking change?