Please log an issue at Azure-Pipelines-YAML. Over there we discuss YAML templates, samples for Azure Pipelines, and designs for upcoming YAML features. Also a place for the community to share best practices, ideas, and so on. File suggestions and issues here if they're specific to YAML pipelines.
Log an issue at Azure-Pipelines-Tasks. It contains all of the in-box tasks we ship with Azure-Pipelines/VSTS/TFS. If you're having issues with tasks in Build/Release jobs (e.g. unreasonable task failure) please log an issue there.
Log an issue at Hosted Agent Image Repository. It contains the VM image used in the Azure Pipelines Hosted Agent Pool. If you're having Build/Release failures that seems like they are related to software installed on the Hosted Agent (e.g. the dotnet SDK is missing or the Azure SDK is not on the latest version) please log an issue there.
Please report it on Developer Community
Version of your agent? 2.155.1
OS of the machine running the agent? OSX/Windows/Linux/...Linux, Red Hat 8
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server? dev.azure.com
If on-premises, which release? 2015.0, 2017.1, 2019 RC2, etc.
If dev.azure.com, what is your organization name? https://dev.azure.com/{organization} or https://{organization}.visualstudio.com
Please include error messages and screenshots.
when i run ./config.sh, I get
No usable version of the libssl was found
./config.sh: line 86: 6055 Aborted (core dumped) ./bin/Agent.Listener configure "$@"
Logs are located in the agent's _diag folder. The agent logs are prefixed with Agent_ and the worker logs are prefixed with Worker_. All sensitive information should already be masked out, but please double-check before pasting here.
I had the same issue, this is fixed by installing compat-openssl10 (at least on CentOS 8). I am guessing that this issue does not crop up on previous releases that natively provide older versions of OpenSSL.
Perhaps this is something that belongs in the prerequisite installer?
Most helpful comment
I had the same issue, this is fixed by installing compat-openssl10 (at least on CentOS 8). I am guessing that this issue does not crop up on previous releases that natively provide older versions of OpenSSL.
Perhaps this is something that belongs in the prerequisite installer?