Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BL pipeline issues - unable to complete pipeline/unable to deploy #593

Open
1 of 2 tasks
ShanaLMoore opened this issue Feb 4, 2025 · 2 comments
Open
1 of 2 tasks
Assignees

Comments

@ShanaLMoore
Copy link
Contributor

ShanaLMoore commented Feb 4, 2025

Summary

Rory is unable to deploy.

I recommended an update to replace all scientist-softserv references with notch8 in his repo but he's reported additional problems since.

I thought maybe it's because the repo's references to the actions repo is outdated. I tried updating it but now there are build issues. Due to other priorities I need to set this down for now.

Acceptance Criteria

  • BL built-test-lint pipeline should complete (There may be lint or test failures so it may not necessary be green)
  • BL should be able to deploy (See Update)

Notes

UPDATE: The deploy succeeded 🎉

I'm encouraging Rory to merge in this PR.

However the pipeline still fails:

Image

PS. I am leaving the original notes (below) just for the sake of tracking history of exploration.


Original Notes

Here's my WIP problematic PRs:

I'd recommend starting from scratch (renaming scientist-softserv=>notch8) so you can walk through each error yourself.

Below are some of my other attempts though:

I first tried keeping most things to same but renamed ss => n8 in bl and in the actions repo. You'll see branches created with old versions in the actions repo.

Then I tried moving them to a higher version of actions but other issues occurred.

Slack convos:

other Oddities - what's w the red messages in rancher?

Image

@ShanaLMoore
Copy link
Contributor Author

ShanaLMoore commented Feb 7, 2025

I believe this issue is resolved now. cc @jillpe

I've left Rory know

I can deploy and run the pipeline using the changes found in this PR.

However it requires custom branches to exist in the actions repo. We probably would want to get them off of that and only the latest actions versions eventually.

@ShanaLMoore
Copy link
Contributor Author

If maintenance still works on this, I'd say the goal is to remove them from the custom branches I made in actions, and get them aligned with the latest actions for parity with most of our other projects.

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

No branches or pull requests

1 participant