[JIRA] (JENKINS-42270) GithubSCMFile should expose file attributes exposed by GitHub api

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title

Vivek Pandey created an issue   Jenkins / JENKINS-42270 GithubSCMFile should expose file attributes exposed by GitHub api Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2017/Feb/22 11:53 PM Priority: Major Reporter: Vivek Pandey GitHubSCMFile does not expose attributes that GitHub content API provides via it's API. Some of these are important in order to use it to talk to GitHub APIs. For example pipeline editor can only update Jenkinsfile on Github if it has access to 'sha' of the file. Its also good idea to expose whats coming from GitHub over to consumer. Most these attributes are already present in GHContent wrapped inside GitHubSCMFile, its matter of exposing these attributes. sha - we need to to use GitHub content API to update Jenkinsfile from pipeline editor size - good to have it known to client encodedContent - File content should be encoded, for example if its binary file. Github by default gives base64 encoded content encoding - GitHub API by default does base64 encoding path - file path relative to root name - name of this file Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.