[JENKINS-61809] Include JCasC instructions in README #29
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since JCasC is now a thing, and it's not clearly mentioned somewhere how to configure a Google OAuth credential, and because somebody asked how it works, let's document it.
The config in the Jira ticket looked correct, based on what I could see from the PR which implemented JCasC support, and I was also able to get it working locally.
For info: if you want to try this out, create a
jcasc.yml
file with the contents that this PR adds to theREADME
, and run Jenkins with JCasC, e.g.:jcasc.yml
Dockerfile
You should then be able to use the Google credential in jobs to upload APKs etc..
You can also confirm that the credential was imported as expected via the Script Console, for example: