IMPORTANT, please fill the questions
We assume you are using Bitnami to deploy your application.
Which version of the application are you using?:
Google Console Deployment Last Week - Version 2.204.5
Please choose how you got the application: Installer (Windows, Linux, macOS), cloud image (AWS, GCE, Azure, ...) or VM (VMDK, VBOX):
Google Console Jenkins Certified Bitnami. I believe it is Debian.
Have you installed any plugin or modified any configuration file?:
Installed SFDX CLI for Salesforce.com.
Describe here your question/suggestion/issue (expected and actual results):
I had to deploy new version of Jenkins. Previous deployment 10/2019. This deployment different. It seems that environment variables at OS level may be changing (or perhaps getting reset) daily based on symptoms from SFDX.
sfdx force:mdapi:deploy --wait 120 -c --deploydir /opt/bitnami/jenkins/jenkins_home/workspace/TAN-pipe_prod_validate/mdapi --targetusername email@example.com --testlevel RunLocalTests
ERROR running force:mdapi:deploy: We encountered a JSON web token error, which is likely not an issue with Salesforce CLI. Here’s the error: ENOENT: no such file or directory, open '/opt/bitnami/jenkins/jenkins_home/workspace/TAN-pipe_prod_validate@tmp/secretFiles/ef828807-fd4d-41a0-87da-554870598fce/server.key'
It's tripping up on a server.key secret credentials file. Between when it initializes this key file in a login command a few lines prior to this and this line, some how Jenkins/SFDX can no longer see the file. This is a local OS environment issue. I have only accessed Jenkins web interface post deployment for configuration outside of logging in to CLI to install SFDX.
In my Groovy script I've precluded this ahead of everything else:
This should set the environment of the local job from Jenkins perspective. Everything is pointing me to this issue being OS related right now as the application I'm using utilizes local environment variables.
Steps to reproduce the issue (if relevant):
I have to delete pipes daily in order to re-initialize. 24 hours later that same project will fail with aforementioned error. Once I delete multi-branch pipeline and recreate it, things are back to normal.
Copy the apache log (if relevant):