
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@roadiehq/backstage-plugin-buildkite
Advanced tools
yarn add @roadiehq/backstage-plugin-buildkite
// app-config.yaml
proxy:
'/buildkite/api':
target: https://api.buildkite.com/v2/
headers:
Authorization: 'Bearer ${BUILDKITE_API_TOKEN}'
// packages/app/src/components/catalog/EntityPage.tsx
import {
EntityBuildkiteContent,
isPluginApplicableToEntity as isBuildkiteAvailable,
} from '@roadiehq/backstage-plugin-buildkite';
// packages/app/src/components/catalog/EntityPage.tsx
export const cicdContent = (
<EntitySwitch>
<EntitySwitch.Case if={isBuildkiteAvailable}>
<EntityBuildkiteContent />
</EntitySwitch.Case>
...
</EntitySwitch>
);
Alternatively, the plugin can be configured to only display default branch
builds (However, this may be overwritten on a per-entity basis via a
buildkite.com/branch
or buildkite.com/default-branch-only: false
entity
annotations, as explained below):
// packages/app/src/components/catalog/EntityPage.tsx
export const cicdContent = (
<EntitySwitch>
<EntitySwitch.Case if={isBuildkiteAvailable}>
<EntityBuildkiteContent defaultBranchOnly />
</EntitySwitch.Case>
...
</EntitySwitch>
);
metadata:
annotations:
buildkite.com/project-slug: [exampleorganization/exampleproject]
# Optional; the buildkite.com/branch annotation can be used to configure
# the plugin to only display builds of the specified branch name.
#
# If omitted, the plugin displays builds from all branches.
#
# Note that 'buildkite.com/branch' takes precedence over a
# globally-configured <EntityBuildkiteContent defaultBranchOnly />.
buildkite.com/branch: 'main'
# Optional; the buildkite.com/default-branch-only annotation can be used to
# configure the plugin to only display builds of the default branch name,
# the value of which is dynamically determined via the Buildkite API.
#
# Note that...
# A 'buildkite.com/branch' annotation takes precedence over 'buildkite.com/default-branch-only'.
# A 'buildkite.com/default-branch-only: false' takes precedence over a
# globally-configured <EntityBuildkiteContent defaultBranchOnly />.
# "true" and "false" are the only supported values.
buildkite.com/default-branch-only: 'true'
export BUILDKITE_API_TOKEN=xxx-xxx-xxx
Roadie gives you a hassle-free, fully customisable SaaS Backstage. Find out more here: https://roadie.io.
FAQs
Unknown package
The npm package @roadiehq/backstage-plugin-buildkite receives a total of 1,962 weekly downloads. As such, @roadiehq/backstage-plugin-buildkite popularity was classified as popular.
We found that @roadiehq/backstage-plugin-buildkite demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
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.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.