Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

For instructions on how to set up this architecture, see JobScheduler Universal Agent - connecting via HTTPS

...

Jira
serverSOS JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId6dc67751-9d67-34cd-985b-194a8cdc9602
keyJOE-164

Explanations

This setup needs requires 2 user accounts on the Agent host:

...

  • Communication between JobScheduler Master and Agent is initiated by the Master only and is restricted to the port that is specified for the HTTPS connection.
  • Communication between JobScheduler Master instances for remote execution make use of a number of ports in both directions, see How to configure remote execution.

References

Change Management References

Jira
serverSOS JIRA
columnstype,key,issuelinks,fixversions,status,priority,summary,updated
maximumIssues20
jqlQuerylabels in (proxy) and labels in (agent)
serverId6dc67751-9d67-34cd-985b-194a8cdc9602

See also