Package Exports
- @roadiehq/backstage-plugin-travis-ci
- @roadiehq/backstage-plugin-travis-ci/dist/index.esm.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@roadiehq/backstage-plugin-travis-ci) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Travis CI Plugin for Backstage

Features
- List Travis CI Builds
- Retrigger builds
How to add Travis-ci project dependency to Backstage app
If you have your own backstage application without this plugin, here are instructions how to add it:
- In the
backstage/packages/appproject add the plugin as apackage.jsondependency:
yarn add @roadiehq/backstage-plugin-travis-ci- add configuration in
app-config.yamlfile in the root directory:
In the proxy object:
proxy:
...
'/travisci/api':
target: https://api.travis-ci.com
changeOrigin: true
headers:
Authorization: ${TRAVISCI_AUTH_TOKEN}
travis-api-version: 3and as a separate configuration object:
travisci:
baseUrl: 'https://travis-ci.com/'- Import it into your Backstage application:
// packages/app/src/components/catalog/EntityPage.tsx
import {
EntityTravisCIContent,
EntityTravisCIOverviewCard,
isTravisciAvailable,
} from '@roadiehq/backstage-plugin-travis-ci';- Add plugin to the
EntityPage.tsxsource file:
// packages/app/src/components/catalog/EntityPage.tsx
export const cicdContent = (
<EntitySwitch>
<EntitySwitch.Case if={isTravisciAvailable}>
<EntityTravisCIContent />
</EntitySwitch.Case>
...
</EntitySwitch>
);- Add a recent Travis-CI builds widget/card to the overview tab to the entityPage.tsx source file:
export const cicdCard = (
<EntitySwitch>
<EntitySwitch.Case if={isTravisciAvailable}>
<Grid item sm={6}>
<EntityTravisCIOverviewCard />
</Grid>
</EntitySwitch.Case>
</EntitySwitch>
);How to use Travis-ci plugin in Backstage
Travis-ci plugin is a part of the Backstage sample app. To start using it for your component, you have to:
- Add an annotation to the yaml config file of a component:
travis-ci.com/repo-slug: <owner-name>/<project-name>Add your developer api key to the environment variables of your backstage backend server (you can find it in https://travis-ci.com/account/preferences), in the form of the word 'token' followed by your api key. So it should look like this:
TRAVISCI_AUTH_TOKEN="token <your-api-key>"
Developing the plugin locally
The easiest way is to clone the plugin repo into the plugins/ directory of your backstage code base:
git clone https://github.com/RoadieHQ/backstage-plugin-travis-ci.git travis-ciand run yarn install in the root backstage directory - it will create a symbolic link, so the dependency will be provided from the source code instead of node_modules package.
Links
- Backstage
- Get hosted, managed Backstage for your company: https://roadie.io
Roadie gives you a hassle-free, fully customisable SaaS Backstage. Find out more here: https://roadie.io.