<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Agents on Step Documentation</title>
    <link>https://step.dev/knowledgebase/30/categories/agents/</link>
    <description>Recent content in Agents on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 25 Jan 2024 11:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/30/categories/agents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>.NET agent</title>
      <link>https://step.dev/knowledgebase/30/plugins/dotnetagent/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/plugins/dotnetagent/</guid>
      <description>.NET Plugin Installation Installation Follow this link to install the .NET Step Agent : .NET Agent installation
Keyword Project .NET Solution To create new keywords for the .NET agent with Visual Studio Solution, you must first create a new Console Application project in Visual Studio:
You will then be able to choose between the latest .NET 5.0 framework or the legacy 4.x version (please note that only the latest 4.x version of the framework is tested before the release).</description>
    </item>
    
    <item>
      <title>Node.js agent</title>
      <link>https://step.dev/knowledgebase/30/plugins/nodejs/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/plugins/nodejs/</guid>
      <description>Agent Setup Installation Follow this link to install the NodeJS Step Agent : NodeJS Agent installation
Validation You can now test the installation by first running the following command in a shell:
You can check in Status -&amp;gt; Token Groups on the Step UI that a new agent of type &amp;ldquo;node&amp;rdquo; appears:
Troubleshooting If you forget to pass the configuration file, the following error will be displayed: If you have the following error: This can mean that:</description>
    </item>
    
    <item>
      <title>Agent configuration for Step SaaS</title>
      <link>https://step.dev/knowledgebase/30/saasdocs/agent-configuration/</link>
      <pubDate>Thu, 25 Jan 2024 11:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/saasdocs/agent-configuration/</guid>
      <description>Automation scripts are executed on Agents. Certain jobs require specific agents: Client-based automation (like browser-based testing) require UI agents. Most plugins require a specific agent type (java for most of them), we list the most relevant tasks here. Configuring this for Step SaaS in the Step Portal is an easy process and can either be done when creating a cluster or by editing an existing one.
Agent Types Here all available Agent types are listed, including information about the available resources per running agent.</description>
    </item>
    
    <item>
      <title>Agent installation</title>
      <link>https://step.dev/knowledgebase/30/setup/installation/binaries/agentinstall/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/setup/installation/binaries/agentinstall/</guid>
      <description>This page explains how to install, configure and run a Step agent.
Installation Java agent The Step agent requires at least Java 21 installed in order to run. Depending on your platform, make sure to install at least Java JDK 21 on the machine(s) running Step component(s).
The latest version of the Community Edition of the Step agent can be downloaded from our Github repository at : Step.
The latest version of the Enterprise Edition of the Step agent can be downloaded from our Nexus repository by enterprise customers at : Step Enterprise (credentials are provided upon requests)</description>
    </item>
    
  </channel>
</rss>
