John M. Daniel

@sfdcale -- Ugh. Good catch. Apologies for that oversight. One of us (@daveespo, @stohn777, or I) will get it cleaned up soon.

@azlam-abdulsalam, I am aware of two ways to check the version number of a 04t: 1. Check the DevHub that the package was created by 2. Check the org that...

The error message that I get is the following: ``` sfdx force:apex:test:run --testlevel RunLocalTests --outputdir target/27 --resultformat tap --json { "status": 1, "name": "InvalidAsyncTestJob", "message": "Unable to invoke async test...

Other commands that are affected by this are: - force:source:status - force:source:pull - force:source:push (yes, I listed above that it worked and it did, but now it doesn't work)

Is this an issue where the jwt connection works for a while and then the CLI needs to send a refreshtoken request and when that request occurs, it needs the...

@shetzel thanks for the update. That may be that it is working as designed, but it breaks the use case that I mentioned above about the "....Jenkins CI processes on...

@shetzel - the `force:apex:test:run` command is in a different stage. I did wrap that command with the `withCredentials` block. That did not help. Still got the same error. I **did...

@shetzel -- a couple of questions: - Have you had any success using that approach with the [pipeline -> stages -> stage syntax?](https://jenkins.io/doc/book/pipeline/syntax/). The tests that I have run thus...

@shetzel -- additional question would be: - Why is it that the `force:apex:test:run` command fails when the jwtKeyFile is not present but the `force:source:push` command works. Both make API calls...

@shetzel -- That is strange. I see now that, if you have a devhubdefault connection that was setup via JWT, then any scratch org created by that connection will also...