roadiehq/backstage-plugin-travis-ci

A Travis CI plugin for Backstage by Spotify

backstage-plugin-travis-ci's Issues

Most recent built of main branch has failed

https://github.com/RoadieHQ/backstage-plugin-travis-ci/runs/2005921131

A new version bump is needed.

Update Readme file instructions

Readme instructions had some outdated instructions so they need to be revised

Getting blank pages / javascript errors when trying to view components and resources that do not have travis configured

Expected Behavior

We have a diverse tech stack, not all repos make use of TravisCI. I would expect that if you do not have Travis configured for a component or resource that the page loads safely, could have the generic "you do not have Travis configured" message in the widget.

Current Behavior

We're getting blank pages and the following errors showing in dev tools:

Possible Solution

uncertain

Steps to Reproduce

We have version 1.0.8 of the plugin installed.

A Component with the travis tags in the annotations loads fine but all my other Components, Resources, Locations do not.

a sample Location I was using to test:
`

apiVersion: backstage.io/v1alpha1
kind: Location
metadata:
name: Dalton-Location
description: Location for Dalton components/elements
spec:
type: url
`

load it and view the page, the error shows up.

Context

We've had to disable the travis plugin to be able to demo to stakeholders to get approval to continue.

Here is the full list of errors I'm seeing:
TravisErrors.log

Your Environment

We're running our backstage instance in AWS ECS

• Plugin Version: 1.0.8
• Backstage version (e.g. 0.1.1-alpha23): 0.8.7
• NodeJS Version (e.g. v12): 14
• Operating System and Version (e.g. Ubuntu 14.04): Ubuntu ???
• Browser Information (e.g. chrome 85): Chrome 92.0.4515.107

Component extensions are not re-exported in `src/index.ts`

Found a whoopsie when "dry-running" the entity page migration. These things

backstage-plugin-travis-ci/src/plugin.ts

Line 30 in 3a77798

export const EntityTravisCIContent = travisciPlugin.provide(

should be re-exported in

backstage-plugin-travis-ci/src/index.ts

Line 7 in 3a77798

} from './plugin';

Thank you for porting all plugins btw! 😊

Some tip-top naming updates too! Helping keep things a bit more neatly separated and naming consistent, isGithubInsightsAvailable etc. 👌

Running jobs show as running for 51+ years

The Date field seems to be showing right for completed builds (passed or failed) but when they're in the started Status, they show as having started over 51 years ago sec

Expected Behavior

That the Date field would show the running time of the build

Current Behavior

it shows over 51 years ago sec

Possible Solution

not dug into the code yet

Steps to Reproduce

It happens to me on every build that's currently running, and corrects once the build is finished.

Context

We're currently evaluating Backstage, so no direct impact, but have concerns about how it will be perceived by my teams.

Your Environment

• Plugin Version (version of this software e.g. v0.4.3): 1.0.4
• Backstage version (e.g. 0.1.1-alpha23): 0.7.13
• NodeJS Version (e.g. v12): 14.17.0
• Operating System and Version (e.g. Ubuntu 14.04): OSX 10.15.7
• Browser Information (e.g. chrome 85): Chrome 91.0.4472.114

Support links to Travis Enterprise

The plugin can be used with a Travis Enterprise (on-prem) installation as the Backstage proxy configuration can be modified. The links from the UI are hardcoded to https://travis-ci.com/... though.

Expected Behavior

Links lead to the configured Travis installation, e.g. https://travis.company.com/...

Current Behavior

Links lead to https://travis-ci.com/...

Possible Solution

• To avoid the need for extra configuration, maybe the protocol and domain of the configured travis instance could be read from the proxy configuration?
• Otherwise add a configuration option for the Travis BASE_URL

Steps to Reproduce

1. Start backstage with the plugin configured (proxy config) to an enterprise travis instance
2. Browse to a service catalog entity with a travis annotation
3. The links in the travis widget links to travis-ci.com

Context

In our setup, links to travis are broken.

Your Environment

• Plugin Version (version of this software e.g. v0.4.3): latest
• Backstage version (e.g. 0.1.1-alpha23): latest
• NodeJS Version (e.g. v12): latest
• Operating System and Version (e.g. Ubuntu 14.04): latest
• Browser Information (e.g. chrome 85): latest