Note
-hosted runners are not currently supported on Enterprise Server. You can see more information about planned future support on the public roadmap.
About automatic access to .com actions
By default, Actions workflows on Enterprise Server cannot use actions directly from .com or Marketplace. To make public actions from .com available on your enterprise instance, you can use Connect to integrate Enterprise Server with Enterprise Cloud.
To use actions from .com, both Enterprise Server and your self-hosted runners must be able to make outbound connections to .com. No inbound connections from .com are required. For more information. For more information, see Communicating with self-hosted runners.
Alternatively, if you want stricter control over which actions are allowed in your enterprise, you can manually download and sync public actions onto your enterprise instance using the actions-sync tool. For more information, see Manually syncing actions from .com.
About resolution for actions using Connect
When a workflow uses an action by referencing the repository where the action is stored, Actions will first try to find the repository on your Enterprise Server instance. If the repository does not exist on your Enterprise Server instance, and if you have automatic access to .com enabled, Actions will try to find the repository on .com.
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on .com, the repository on your enterprise will be used instead of the .com repository. For more information, see Automatic retirement of namespaces for actions accessed on .com.
Enabling automatic access to public .com actions
Before enabling access to public actions from .com for your enterprise, you must:
- Configure your Enterprise Server instance to use Actions. For more information, see Getting started with Actions for Enterprise Server.
- Enable Connect. For more information, see Enabling Connect for .com.
In the top-right corner of Enterprise Server, click your profile photo, then click Enterprise settings.
On the left side of the page, in the enterprise account sidebar, click Connect.
Under "Users can utilize actions from .com in workflow runs", use the drop-down menu and select Enabled.
After you enable Connect, you can use policies to restrict which public actions can be used in repositories in your enterprise. For more information, see Enforcing policies for Actions in your enterprise.
Automatic retirement of namespaces for actions accessed on .com
When you enable Connect, users see no change in behavior for existing workflows because Actions searches your Enterprise Server instance for each action before falling back to .com. This ensures that any custom versions of actions your enterprise has created are used in preference to their counterparts on .com.
To ensure workflows use their intended actions and to block the potential for abuse, once an action on .com is used for the first time, the namespace associated with that action is retired in your enterprise. This blocks users from creating an organization and repository in your enterprise that match the action's namespace on .com.
After using an action from .com, if you want to create an action in your Enterprise Server instance with the same name, first you need to make the namespace for that organization and repository available.
From an administrative account on Enterprise Server, in the upper-right corner of any page, click .
If you're not already on the "Site admin" page, in the upper-left corner, click Site admin.
In the left sidebar, under Site admin click Retired namespaces.
To the right of the namespace that you want use in your Enterprise Server instance, click Unretire.
Go to the relevant organization and create a new repository.
Tip
When you unretire a namespace, always create the new repository with that name as soon as possible. If a workflow calls the associated action on .com before you create the local repository, the namespace will be retired again. For actions used in workflows that run frequently, you may find that a namespace is retired again before you have time to create the local repository. In this case, you can temporarily disable the relevant workflows until you have created the new repository.