Skip to content

Not working behind proxy #49

@addisonautomates

Description

@addisonautomates

When trying to run the github action behind a proxy it does not use it and instead goes out the firewall. This is despite setting the proxy env vars in the actions step prior which works for every other action step we've used to date. Could we get a code change to allow this action step as well as the rest of the jira actions steps just to use the proxy if proxy setting are set in env vars?

Error:
Error: Jira API error
at Jira.fetch (/var/lib/ghactions/actions-runner/_work/_actions/pri-actions/gajira-login/v3/webpack:/@atlassian/gajira-login/common/net/Jira.js:111:1)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at module.exports.execute (/var/lib/ghactions/actions-runner/_work/_actions/pri-actions/gajira-login/v3/webpack:/@atlassian/gajira-login/action.js:17:1)
at exec (/var/lib/ghactions/actions-runner/_work/_actions/pri-actions/gajira-login/v3/dist/index.js:29732:20) {
req: {
method: 'GET',
body: undefined,
url: '***/rest/api/2/myself'
},
originError: FetchError: request to ***/rest/api/2/myself failed, reason: connect ETIMEDOUT 104.192.142.19:443
at ClientRequest. (/var/lib/ghactions/actions-runner/_work/_actions/pri-actions/gajira-login/v3/webpack:/@atlassian/gajira-login/node_modules/node-fetch/lib/index.js:1491:1)
at ClientRequest.emit (node:events:527:28)
at TLSSocket.socketErrorListener (node:_http_client:454:9)
at TLSSocket.emit (node:events:527:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
type: 'system',
errno: 'ETIMEDOUT',
code: 'ETIMEDOUT'
},
source: 'jira'
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions