You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the Jenkins CI server went away, we moved the CI build to Github Actions, but it has never actually fully worked, because the scripts expect to get AWS credentials from a profile named pfb but there's no such profile configured for the runner.
I'm not sure if it's possible to configure a profile for a Github Actions runner. If so, doing that, and providing it with a key pair, would be the simplest solution to this. If not, we'll have to provide credentials some other way and adjust the cipublish and infra scripts accordingly.
The text was updated successfully, but these errors were encountered:
When the Jenkins CI server went away, we moved the CI build to Github Actions, but it has never actually fully worked, because the scripts expect to get AWS credentials from a profile named
pfb
but there's no such profile configured for the runner.I'm not sure if it's possible to configure a profile for a Github Actions runner. If so, doing that, and providing it with a key pair, would be the simplest solution to this. If not, we'll have to provide credentials some other way and adjust the
cipublish
andinfra
scripts accordingly.The text was updated successfully, but these errors were encountered: