Search Options

Display Count
Sort
Preferred Language
Advanced Search

Results 111 - 120 of 1,010 for release (0.05 seconds)

  1. futures/failureaccess/pom.xml

            <executions>
              <execution>
                <id>default-compile</id>
                <goals>
                  <goal>compile</goal>
                </goals>
                <configuration>
                  <release>8</release>
                  <excludes>
                    <exclude>module-info.java</exclude>
                  </excludes>
                  <compilerArgs>
                    <!--
                        Make includes/excludes fully work:
    Created: Fri Apr 03 12:43:13 GMT 2026
    - Last Modified: Thu Oct 02 19:27:26 GMT 2025
    - 5.4K bytes
    - Click Count (0)
  2. helm-releases/minio-5.2.0.tgz

    .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Apr 28 10:14:37 GMT 2024
    - 21.7K bytes
    - Click Count (0)
  3. CHANGELOG.md

    [kotlin_1_7_10]: https://github.com/JetBrains/kotlin/releases/tag/v1.7.10
    [kotlin_1_9_21]: https://github.com/JetBrains/kotlin/releases/tag/v1.9.21
    [kotlin_1_9_23]: https://github.com/JetBrains/kotlin/releases/tag/v1.9.23
    [kotlin_2_1_21]: https://github.com/JetBrains/kotlin/releases/tag/v2.1.21
    [kotlin_2_2_0]: https://github.com/JetBrains/kotlin/releases/tag/v2.2.0
    Created: Fri Apr 03 11:42:14 GMT 2026
    - Last Modified: Sun Feb 15 11:57:47 GMT 2026
    - 36.2K bytes
    - Click Count (2)
  4. helm-releases/minio-5.0.2.tgz

    apiVersion: {{ template "minio.networkPolicy.apiVersion" . }} metadata: name: {{ template "minio.fullname" . }} namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }} chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} spec: podSelector: matchLabels: app: {{ template "minio.name" . }} release: {{ .Release.Name }} ingress: - ports: - port: {{ .Values.minioAPIPort }} - port: {{ .Values.minioConsolePort }} {{- if not .Values.n...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sun Dec 18 07:57:10 GMT 2022
    - 20.4K bytes
    - Click Count (0)
  5. build-tools-internal/src/main/resources/templates/breaking-changes.asciidoc

    ++++
    <titleabbrev>${majorDotMinor}</titleabbrev>
    ++++
    
    This section discusses the changes that you need to be aware of when migrating
    your application to {es} ${majorDotMinor}.
    
    See also <<release-highlights>> and <<es-release-notes>>.
    <% if (isElasticsearchSnapshot) { %>
    coming[${version}]
    <% } %>
    //NOTE: The notable-breaking-changes tagged regions are re-used in the
    //Installation and Upgrade Guide
    Created: Wed Apr 08 16:19:15 GMT 2026
    - Last Modified: Wed Jul 28 11:09:58 GMT 2021
    - 2.9K bytes
    - Click Count (0)
  6. helm/minio/README.md

    You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command:
    
    ```bash
    helm get values my-release > old_values.yaml
    ```
    
    Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using
    
    ```bash
    helm upgrade -f old_values.yaml my-release minio/minio
    ```
    
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Tue Aug 12 18:20:36 GMT 2025
    - 10.9K bytes
    - Click Count (0)
  7. helm/minio/templates/ciliumnetworkpolicy.yaml

      name: {{ template "minio.fullname" . }}
      labels:
        app: {{ template "minio.name" . }}
        chart: {{ template "minio.chart" . }}
        release: {{ .Release.Name }}
        heritage: {{ .Release.Service }}
    spec:
      endpointSelector:
        matchLabels:
          app: {{ template "minio.name" . }}
          release: {{ .Release.Name }}
      ingress:
      - toPorts:
        - ports:
          - port: "{{ .Values.minioAPIPort }}"
            protocol: TCP
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Fri Apr 26 07:50:24 GMT 2024
    - 936 bytes
    - Click Count (0)
  8. src/test/java/jcifs/smb1/smb1/BufferCacheSecurityTest.java

                buffers.add(buffer);
            }
    
            // When - Release all buffers back
            for (byte[] buffer : buffers) {
                BufferCache.releaseBuffer(buffer);
            }
    
            // Then - Should be able to get buffers again
            byte[] newBuffer = BufferCache.getBuffer();
            assertNotNull(newBuffer, "Should be able to get buffer after release");
    Created: Sun Apr 05 00:10:12 GMT 2026
    - Last Modified: Sun Aug 31 08:00:57 GMT 2025
    - 9.6K bytes
    - Click Count (0)
  9. helm-releases/minio-5.0.10.tgz

    .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Sat May 27 00:05:49 GMT 2023
    - 20.3K bytes
    - Click Count (0)
  10. helm-releases/minio-5.0.9.tgz

    .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Created: Sun Apr 05 19:28:12 GMT 2026
    - Last Modified: Wed May 03 06:23:26 GMT 2023
    - 20.2K bytes
    - Click Count (0)
Back to Top