🚨 Shai-Hulud Strikes Again:834 Packages Compromised.Technical Analysis →
Socket
Book a DemoInstallSign in
Socket

@kalamazoo/branch-deploy-product-integrator

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@kalamazoo/branch-deploy-product-integrator

Installs branch deployed atlaskit packages into products to run product CI.

latest
Source
npmnpm
Version
1.0.2
Version published
Maintainers
1
Created
Source

@kalamazoo/branch-deploy-product-integrator

This is a CLI for automatically creating branches installing Atlaskit branch deploys in products.

CLI Flags

--branchPrefix Prefix for the generated branch [default=atlaskit-branch-deploy/]

--workingPath Working path of the product repo installing a branch in [default=./]

--atlaskitCommitHash Atlaskit commit hash of the branch deploy that needs to be installed

--atlaskitBranchName The branch with which to compare the current branch, when git reporting is enabled can detect PR target branch. [default=master]

--packageEngine The package manager to use, currently only tested with Bolt and yarn [default=yarn]

--packages comma delimited list of packages to install branch deploy of

--dedupe !yarn only! run yarn deduplicate at the end to deduplicate the lock file

Bamboo example implementation:

  • Create a build plan that is linked to the Atlaskit repo AND the product repo.
  • Check out Atlaskit repo in the root
  • Check out the product repo in a sub-dir and make sure it has write-rights.
  • Then run the following shell script in the sub-dir of the product checkout:
branch_name=${bamboo_planRepository_branch}
if [ "$branch_name" != "master" ]; then

yarn global add atlaskit-branch-deploy-product-integrator

branch-deploy-product-integrator --atlaskitBranchName ${bamboo_planRepository_branch} --atlaskitCommitHash ${bamboo_planRepository_revision}
else
echo "Current branch is master. Not going to branch deploy."
fi

Note: There's a protection against accidentally pushing to the wrong repo. If that throws most likely the order of the repo's on the build plans is incorrect. Also sometimes the repo will not have a remote setup, if that is the case add this to the start of the build script:

git remote set-url origin ssh://git@my.stash.instance.com/productproject/productrepo.git

FAQs

Package last updated on 24 Jan 2020

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts