Skip to content

Migrate jenkins to gha - #158

Merged
tokio-on-jupiter merged 6 commits into
mainfrom
migrate-jenkins-to-gha
Nov 17, 2025
Merged

tokio-on-jupiter merged 6 commits into
mainfrom
migrate-jenkins-to-gha

Conversation

@tokio-on-jupiter

Copy link
Copy Markdown
Contributor

QA Checklist

Insights

  • Does a related dashboard already exist, and should it be tweaked or added to instead?
  • Test each query to make sure it works
  • Look for hardcoded variables/parameter values in the query
  • Spellcheck
  • Use all caps for J1QL keywords and relationship classes
  • Make sure dashboard layout is correct, Save default layout and replace if not
  • Upload the dashboard JSON into JupiterOne to validate
  • Make sure there is a screenshot with no sensitive data
  • Update the main README.md file in the repository
  • Ensure file naming is consistent (board.json, board.png, readme.md)
  • Update index.ts file with new board
  • Update the package.json version ex: 1.7.0 -> 1.7.1 or 1.7.0 -> 1.8.0

Note: Once your changes have been merged, the owners of the insights app need to be notified

@tokio-on-jupiter
tokio-on-jupiter requested a review from a team as a code owner November 10, 2025 22:18

@mscottford mscottford left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes don't seem to line up with the PR title.

Comment thread .github/workflows/pr.yaml
Comment on lines -8 to +9
uses: jupiterone/github-internal/.github/workflows/npm-pr.yaml@v1
secrets: inherit
uses: JupiterOne/github-internal/.github/workflows/npm-pr.yaml@v1
secrets: inherit No newline at end of file

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't think this was case sensitive.

Comment thread .github/workflows/release.yaml Outdated
Comment on lines +9 to +10
npm-release:
uses: jupiterone/github-internal/.github/workflows/npm-release.yaml@v1
release:
uses: JupiterOne/github-internal/.github/workflows/npm-release.yaml@v1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this the same job name that other projects use?

@ryanmcafee

Copy link
Copy Markdown

@tokio-on-jupiter I would revert the changes to the workflow files since the workflows referenced use the exact same paths as other projects (see). I would recommend checking instead for hidden characters if you're still seeing an issue or we need to review the upstream github-internal project and analyze the npm-pr workflow to ensure it's correct.

@tokio-on-jupiter
tokio-on-jupiter merged commit 4746cda into main Nov 17, 2025
3 checks passed
@tokio-on-jupiter
tokio-on-jupiter deleted the migrate-jenkins-to-gha branch November 17, 2025 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants