Self-hosted GitHub actions runner installed on Linux, Windows and Mac systems.
I need to upgrade the runner version to latest on Linux, Windows and MacOS.
How to check the currently installed Runner version?
In runner log and service status side, I can't find the information.
How to upgrade the runner to latest version?
Please help me with information. Thanks in advance.
Go to the self hosted runner directory, list folders, you should see the bin and externals directory with the version suffix bin.2.288.1, externals.2.288.1 - most current should have symlink with full directory. Also you can check version of each component listener, plugin-host,worker in /bin directory json files. There's no need to force updating self hosted runner - it should update automatically to the latest. One scenario in which you will need to update the runners manually is inside docker container - you can use this script:
https://github.com/GarnerCorp/github-actions-runner/blob/cb604618a600bd5174f3dbc8d51d15eee6585c68/scripts/install-runner
Related
I've installed the latest VS Build Tools (2022), but my on-prem build agent isn't picking up the VisualStudio-related capabilities. I've been under the impression that we no longer need to install the full application in order to get these capabilities.
An example from this blog post:
I've added all workloads to my offline layout, and I've included them in my installation.
I know this is possible, because earlier I accidentally included Python and VS 2019 Build Tools in my Node.js installation configuration. The VS-related capabilities were found by the agent then.
But I'm trying to get 2022, so I uninstalled 2019.
How can I get the 2022 VS-related capabilities to be installed and detected by my build agent, without installing the full Visual Studio product?
You need to upgrade the agent to a recent enough version. You can download the agent from the azure-pipelines-agent repository's releases page. Or manually specify the capabilities.
You may need to set a special environment flag on the agent to prevent it from automatically being downgraded to whatever version shipped with your version if Azure DevOps Server or Team Foundation Server.
And then you'll also need to install the latest version of the vsbuild/msbuild and vstest tasks
Required agent version
You will need to install the most recent agent from the azure-pipelines-agent repository for it to auto-detect Visual Studio 2022, or alternatively add the capabilities to the agent manually.
You may need to force Azure DevOps Server to not downgrade back to its preferred agent version. You can do so by setting the following environment variable at the system level on your server before launching the agent:
AZP_AGENT_DOWNGRADE_DISABLED=true
These tricks will work for most tasks in the azure-pipelines-tasks repository, as long as it doesn't depend on a UI extension or service connection type that isn't available in your version of Azure DevOps Server.
https://jessehouwing.net/adding-visual-studio-2022-to-azure-devops-server-2020/
I need to deploy the agent using puppet or UCD.
We are using jProfiler Version 11.0.1.
I've tried to get the download path for that version, but all I can get via Documentation is the version for jProfiler 12.0.
Is there any way to get the download link for older versions of jDownloader Agent?
JProfiler 11.1 can be downloaded at:
https://www.ej-technologies.com/download/jprofiler/version_111
Agent-only downloads are only available starting with JProfiler 12. In previous versions you can use the remote integration wizard (Session->Integration Wizards->New Remote Integration) to create archives that only contain the agent files.
Background:
We are using the VSTS to build and Octopus integration to deploy our product. The Octopus step is configured as follows,
Issue
Today VSTS Build was throwing following error,
No supported agent found in pool Default. All agents in this pool are
using a version that is deprecated. Migrate to the latest 2.x version
of agent. For more information, see
https://go.microsoft.com/fwlink/?linkid=851067
As a result, the Agent was updated to the latest version,
After the update the octopus step stopped working with following error,
Then issue seems to be the environment variables are not replaced in the step.
I would like to know if there is a work around to fix this issue.
First, there is 2.* version available, so you can delete the old one and add the new one.
Secondly, use $(Build.BuildNumber) instead in Package Version input box, also for Output path: $(Build.ArtifactStagingDirectory).
I just updated my TeamCity server and I am suddenly getting this error message on my build agent.
I made a copy of the old installation, and the buildAgent.properties are the exact same. The Plugin folder for powershell exists aswell.
Does anyone have an idea on how to fix this?
I had the same problem when moved the build agent from windows to linux, and found the solution here.
In short:
Make sure powershell is installed on the server where the build agent is running.
You can set Platform and (Since TeamCity 2017.1) Edition properties at the PowerShell build step Edit page.
Edition: on windows Desktop, on linux Core
Platform: could be x64 or x86 based on installed version
If you set these properties correctly, it should meet the requirements, and you can use the build agent as before.
I have installed the jenkins in my mac machine through Mac Installer, my current jenkins version is 1.628 when I opens Manage Jenkins page it shown as below screen shot. I would like to update the jenkins to newer version 1.630, so can any one please suggest me how to upgrade?, If I upgrade is there any issue to my existing jenkins configuration and jobs? .
Step1
Click the download link to download the latest jenkins.war of version 1.630.
Step2
Replace the old jenkins.war (version 1.628) in your Mac to this new jenkins.war (version 1.630) and restart jenkins.