richkuz

This is my scratch pad of GitHub graph QL queries I run with the Graphiql app.

Make sure to "Edit HTTP Headers" in Graphiql and set the header with your GitHub Personal Dev API Token: Authorization Bearer ghp_ubRfl1F4...

query FindRepo {
  repository(owner: "richkuz", name: "repo2") {
    id
  }

richkuz

An easy way to run a GitHub GraphQL API call is to use the GraphiQL app:

brew install --cask graphiql

Run GraphiQL and click "Edit Headers". Add a header with the name Authorization and value Bearer ghp_REPLACEME where ghp_REPLACEME is the value of a GitHub Access Token. You can create a GitHub Access Token under https://github.com/settings/tokens.

Then type a GraphQL query and run it.

richkuz

To find a GitHub label ID, such as for use in a labelIds parameter when creating an issue with the createIssue API, run this graphql API:

query FindLabelId {
  repository(owner: "richkuz", name: "repo1") {
    label(name:"bug") {
      id
    }
  }
}

richkuz

def message = """{
  "query": "query {
    organization(login: \\"elastic\\") {
        samlIdentityProvider {
            externalIdentities(first: 100) {
                pageInfo {
                    endCursor
                    hasNextPage
                }
                edges {

richkuz

Notes on GitHub ProjectV2 API

GitHub Projects Beta aka GitHub Projects Next aka GitHub ProjectNext is now known as GitHub ProjectV2 in the API.

It's not immediately obvious how to use the new API, especially if you're coming from the old beta API.

You no longer need to set the HTTP header: GraphQL-Features: projects_next_graphql.

You still need to add your GitHub personal access token to the Authorization header, e.g. Authorization: Basic ghp_...

richkuz

"use strict";

var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.warnMismatchedVersions = exports.callEnterpriseSearchConfigAPI = void 0;

var _abortController = _interopRequireDefault(require("abort-controller"));

richkuz

"use strict";

var _interopRequireDefault = require("@babel/runtime/helpers/interopRequireDefault");

Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.EnterpriseSearchRequestHandler = void 0;

var _defineProperty2 = _interopRequireDefault(require("@babel/runtime/helpers/defineProperty"));

richkuz

Install custom plugins and custom Jenkins version in Jenkinsfile-runner (JFR)

To specify your own set of plugins and use a specific version of Jenkins with Jenkinsfile-runner, build a modified Jenkinsfile-runner image that overrides the plugins and installs a specific Jenkins into it.

Use the attached Dockerfile and plugins.txt to build your own Jenkinsfile-runner image.

In plugins.txt, it's a best practice to pin your plugins to specific versions, e.g.

git-server:1.11

richkuz

"analysis" : {
  "filter" : {
    "front_ngram" : {
      "type" : "edge_ngram",
      "min_gram" : "1",
      "max_gram" : "12"
    },
    "bigram_joiner" : {
      "max_shingle_size" : "2",
      "token_separator" : "",

richkuz

{
  ".ent-search-engine-documents-sample" : {
    "mappings" : {
      "dynamic" : "true",
      "dynamic_templates" : [
        {
          "permissions" : {
            "match" : "_*_permissions",
            "mapping" : {
              "type" : "keyword"