This repository has been archived by the owner on Jan 2, 2025. It is now read-only.
Problems on self-hosted runner .. idea? #97
robertklaus-bosch
started this conversation in
General
Replies: 1 comment 18 replies
-
@robertklaus-bosch sounds like you're using an encrypted password in your However, I see 2 paths forward for you:
- name: maven-settings-xml-action
uses: whelk-io/maven-settings-xml-action@v16
with:
repositories: |
[
{
"id": "some-repository",
"url": "http://some.repository.url"
}
]
servers: |
[
{
"id": "github",
"username": ${{ secrets.MY_USERNAME }},
"password": ${{ secrets.MY_PASSWORD }}
}
] |
Beta Was this translation helpful? Give feedback.
18 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am trying this action (v14, v16) on GitHub Enterprise (version 2.x) with a self-hosted runner (not under my control).
Problem is, that I never get this to work as the runner setup is different from the GitHub cloud runners.
When using
stCarolas/setup-maven@v4
the settings are never found as the maven installation does not pick up the settings from the user home.When I try to configre the settings with
--settings
I get a stacktrace as below.Only thing I can think of is that maybe it helps if this action could (optionally) generate the settings.xml in a folder specified in the workflow. Maybe that would work.
Any ideas how to solve this?
(Note replaced actual user with
<user>
)Beta Was this translation helpful? Give feedback.
All reactions