├── .gitignore ├── .github ├── comment-ops.yml ├── ISSUE_TEMPLATE │ ├── 2-feature-request.yml │ ├── config.yml │ ├── 3-documentation.yml │ └── 1-report-bug.yml └── release-drafter.yml ├── FUNDING.yml ├── README.md ├── CODE_OF_CONDUCT.md ├── SUPPORT.md ├── CONTRIBUTING.md ├── SECURITY.md └── profile └── README.md /.gitignore: -------------------------------------------------------------------------------- 1 | .idea 2 | -------------------------------------------------------------------------------- /.github/comment-ops.yml: -------------------------------------------------------------------------------- 1 | commands: 2 | reviewer: 3 | enabled: true 4 | -------------------------------------------------------------------------------- /FUNDING.yml: -------------------------------------------------------------------------------- 1 | community_bridge: jenkins 2 | custom: ["https://jenkins.io/donate/#why-donate"] 3 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # .github 2 | Global configurations for the Jenkins Infrastructure organization on GitHub 3 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Jenkins Code of Conduct 2 | 3 | You can find the Jenkins Code of Conduct [on jenkins.io](https://jenkins.io/project/conduct/). 4 | 5 | It applies to the entire `jenkins-infra` GitHub organization, among other community spaces. 6 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/2-feature-request.yml: -------------------------------------------------------------------------------- 1 | name: '🚀 Feature request' 2 | labels: ['enhancement'] 3 | description: I have a suggestion 4 | 5 | body: 6 | - type: textarea 7 | attributes: 8 | label: What feature do you want to see added? 9 | description: A clear and concise description of your feature request. 10 | validations: 11 | required: true 12 | 13 | - type: textarea 14 | attributes: 15 | label: Upstream changes 16 | description: Link here any upstream changes that might be relevant to this request 17 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/config.yml: -------------------------------------------------------------------------------- 1 | blank_issues_enabled: true 2 | contact_links: 3 | - name: Infrastructure issue 4 | url: https://github.com/jenkins-infra/helpdesk/issues 5 | about: Check if there isn't already an issue open in the Jenkins Infrastructure Help Desk first 6 | - name: Community forum 7 | url: https://community.jenkins.io/tag/sig-infra 8 | about: Please ask and answer questions here 9 | - name: Mailing lists 10 | url: https://www.jenkins.io/mailing-lists/#jenkins-infra-googlegroups-com 11 | about: You can also raise a question in Jenkins Infrastructure mailing list 12 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/3-documentation.yml: -------------------------------------------------------------------------------- 1 | name: '📝 Documentation' 2 | labels: ['documentation'] 3 | description: 'Let us know if any documentation is missing or could be improved' 4 | 5 | body: 6 | - type: textarea 7 | attributes: 8 | label: Describe your use-case which is not covered by existing documentation. 9 | description: If it is easier to submit a documentation patch instead of writing an issue, just do it! 10 | validations: 11 | required: true 12 | 13 | - type: textarea 14 | attributes: 15 | label: Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration. 16 | -------------------------------------------------------------------------------- /SUPPORT.md: -------------------------------------------------------------------------------- 1 | # Jenkins Infrastructure Support 2 | 3 | Our infrastructure is an open project made by and for the Jenkins community. 4 | It is maintained and supported by the [Jenkins Infrastructure team](https://jenkins.io/projects/infrastructure/). 5 | This team consists of Jenkins contributors and volunteers who provide a best-effort support depending on their availability and other commitments. 6 | There is no guarantee of immediate response or issue resolution. 7 | Contributions are welcome and much appreciated, see the [contributing guidelines](https://jenkins.io/projects/infrastructure/#contributing)! 8 | 9 | ## Support Contacts 10 | 11 | * Mailing list: [jenkins-infra@googlegroups.com](https://groups.google.com/g/jenkins-infra) 12 | * Chat: [#jenkins-infra:matrix.org](https://jenkins.io/chat/#jenkins-infra) 13 | * Bugtracker: [Jenkins Infrastructure Help Desk](https://github.com/jenkins-infra/helpdesk) 14 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | Contributing to Jenkins Infrastructure 2 | ====================================== 3 | 4 | Our infrastructure is an open infrastructure project made by and for the Jenkins community. 5 | In other words, it’s a contributor driven project. 6 | While we can’t share everything publicly (like secrets), we try to be as transparent as possible so everybody can read, 7 | understand, and improve our infrastructure without having privileged accesses. 8 | If you have any idea that could help the infra or interest the community, feel free to make suggestions. 9 | 10 | See the Contributing guidelines [on jenkins.io](https://jenkins.io/projects/infrastructure/#contributing). 11 | 12 | ## Contacts 13 | 14 | * Mailing list: [jenkins-infra@googlegroups.com](https://groups.google.com/g/jenkins-infra) 15 | * Chat: [#jenkins-infra:matrix.org](https://jenkins.io/chat/#jenkins-infra) 16 | * Bugtracker: [Helpdesk](https://github.com/jenkins-infra/helpdesk/) repository on the jenkins-infra organization 17 | 18 | ## Newcomers 19 | 20 | If you are a newcomer contributor and have any questions, please do not hesitate to ask in the `#jenkins-infra` IRC channel as explained [here](https://jenkins.io/chat/#jenkins-infra) or in the [Newcomers Gitter channel](https://app.gitter.im/#/room/#jenkinsci_newcomer-contributors:gitter.im). 21 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | The Jenkins project takes security seriously. 4 | We make every possible effort to ensure users can adequately secure their automation infrastructure. 5 | To that end, we want to guarantee that the infrastructure part of the project is as secure as possible, to keep the supply chain safe to build and deliver Jenkins components. 6 | 7 | ## Reporting Security Vulnerabilities 8 | 9 | Please report security vulnerabilities in the Jenkins issue tracker under the [SECURITY project](https://issues.jenkins.io/browse/SECURITY). 10 | This project is configured in such a way that only the reporter and the security team can see the details. 11 | By restricting access to this potentially sensitive information, we can work on a fix and deliver it before the method of attack becomes well-known. 12 | 13 | If you are unable to report using our issue tracker, you can also send your report to the private Jenkins security team mailing list: `jenkinsci-cert@googlegroups.com` 14 | 15 | The Jenkins security team will then file an issue on your behalf, and will work with the maintainers of the affected component(s) to get the issue resolved. 16 | 17 | ## Learn More 18 | 19 | For further details about our scope, issue handling process, or disclosure process, see [Reporting Security Vulnerabilities on jenkins.io](https://jenkins.io/security/reporting/). 20 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/1-report-bug.yml: -------------------------------------------------------------------------------- 1 | name: '🐛 Bug report' 2 | labels: ['bug'] 3 | description: Create a bug report to help us improve 4 | 5 | body: 6 | - type: markdown 7 | attributes: 8 | value: | 9 | **Never report security issues on GitHub or other public channels (Gitter/Twitter/etc.)** 10 | Follow these instruction to report security issues: https://www.jenkins.io/security/#reporting-vulnerabilities 11 | - type: textarea 12 | attributes: 13 | label: Reproduction steps 14 | description: | 15 | Write bullet-point reproduction steps. 16 | Be explicit about any relevant configuration, jobs, build history, etc., redacting confidential information as needed. 17 | Use screenshots where appropriate, copy textual output otherwise. When in doubt, do both. 18 | Include relevant logs, debug if needed. 19 | placeholder: | 20 | 1. Step 1: ... 21 | 2. Step 2: ... 22 | validations: 23 | required: true 24 | 25 | - type: textarea 26 | attributes: 27 | label: Expected Results 28 | description: What was your expected result? 29 | validations: 30 | required: true 31 | 32 | - type: textarea 33 | attributes: 34 | label: Actual Results 35 | description: What was the actual result? 36 | validations: 37 | required: true 38 | 39 | - type: textarea 40 | attributes: 41 | label: Anything else? 42 | description: You can provide additional context below. 43 | -------------------------------------------------------------------------------- /profile/README.md: -------------------------------------------------------------------------------- 1 | ## Jenkins Infrastructure 2 | 3 | As an independent open source project, the Jenkins project maintains most of its own infrastructure including services which help to keep the project running. The kind of things that fall into "infrastructure" can span from operating virtual machines, containers, configuring network or developing and maintaining project-specific applications to make the development of Jenkins core and plugins more efficient. 4 | 5 | Because we strongly believe in Open Source principles, we also apply them to our infrastructure. As such we consider ourself as an open infrastructure project where everybody is invited to learn, share, contribute. 6 | 7 | **Want to contribute?** 8 | Like for Jenkins, there is also a community behind its Infrastructure, and we invite you to join us and participate. 9 | Connect to the Community on social media and in [chats](https://www.jenkins.io/chat/#jenkins-infra/), [mailing lists](https://www.jenkins.io/mailing-lists/#infralists-jenkins-ci-org/) and [meetings](https://www.jenkins.io/projects/infrastructure/#meetings) 10 | [participate and contribute](https://www.jenkins.io/projects/infrastructure/#contributing). 11 | 12 | See also Jenkins [Project Governance and Values](https://www.jenkins.io/project/governance/) and [Code of Conduct](https://www.jenkins.io/project/conduct/). 13 | 14 | **About this GitHub org** 15 | This is the main GitHub organization of the Jenkins Infrastructure, with [its help desk dedicated to infrastructure issues](https://github.com/jenkins-infra/helpdesk) and [status website](https://status.jenkins.io/) 16 | 17 | You can learn more about this subproject on the [website](https://www.jenkins.io/projects/infrastructure/). You're encouraged to submit pull requests, propose features and discuss issues! 18 | 19 | The GitHub organization of the main Jenkins community including repositories of the [Jenkins core](https://github.com/jenkinsci/jenkins), plugins, libraries and developer tools is here: 20 | https://github.com/jenkinsci/ 21 | -------------------------------------------------------------------------------- /.github/release-drafter.yml: -------------------------------------------------------------------------------- 1 | # Configuration for Release Drafter: https://github.com/toolmantim/release-drafter 2 | name-template: '$RESOLVED_VERSION 🌈' 3 | tag-template: '$RESOLVED_VERSION' 4 | 5 | version-resolver: 6 | major: 7 | labels: 8 | - 'major' 9 | minor: 10 | labels: 11 | - 'minor' 12 | - 'feature' 13 | - 'enhancement' 14 | patch: 15 | labels: 16 | - 'patch' 17 | - 'fix' 18 | - 'bugfix' 19 | - 'bug' 20 | - 'chore' 21 | - 'dependencies' 22 | default: patch 23 | 24 | # Emoji reference: https://gitmoji.carloscuesta.me/ 25 | categories: 26 | - title: ":boom: Breaking changes" 27 | labels: 28 | - breaking 29 | - title: 🚨 Removed 30 | labels: 31 | - removed 32 | - title: ":tada: Major features and improvements" 33 | labels: 34 | - major-enhancement 35 | - major-rfe 36 | - title: 🐛 Major bug fixes 37 | labels: 38 | - major-bug 39 | - title: ⚠️ Deprecated 40 | labels: 41 | - deprecated 42 | - title: 🚀 New features and improvements 43 | labels: 44 | - enhancement 45 | - feature 46 | - rfe 47 | - title: 🐛 Bug Fixes 48 | labels: 49 | - bug 50 | - fix 51 | - bugfix 52 | - regression 53 | - title: ":construction_worker: Changes for plugin developers" 54 | labels: 55 | - developer 56 | - title: 📝 Documentation updates 57 | labels: 58 | - documentation 59 | - title: 👻 Maintenance 60 | labels: 61 | - chore 62 | - internal 63 | - title: 🚦 Tests 64 | labels: 65 | - test 66 | - tests 67 | - title: ✍ Other changes 68 | # Default label used by Dependabot 69 | - title: 📦 Dependency updates 70 | labels: 71 | - dependencies 72 | collapse-after: 15 73 | 74 | exclude-labels: 75 | - reverted 76 | - no-changelog 77 | - skip-changelog 78 | - invalid 79 | 80 | template: | 81 | 82 | $CHANGES 83 | 84 | replacers: 85 | - search: '/\[*JENKINS-(\d+)\]*\s*-*\s*/g' 86 | replace: '[JENKINS-$1](https://issues.jenkins-ci.org/browse/JENKINS-$1) - ' 87 | - search: '/\[*HELPDESK-(\d+)\]*\s*-*\s*/g' 88 | replace: '[HELPDESK-$1](https://github.com/jenkins-infra/helpdesk/issues/$1) - ' 89 | # TODO(oleg_nenashev): Find a better way to reference issues 90 | - search: '/\[*SECURITY-(\d+)\]*\s*-*\s*/g' 91 | replace: '[SECURITY-$1](https://jenkins.io/security/advisories/) - ' 92 | - search: '/\[*JEP-(\d+)\]*\s*-*\s*/g' 93 | replace: '[JEP-$1](https://github.com/jenkinsci/jep/tree/master/jep/$1) - ' 94 | - search: '/CVE-(\d{4})-(\d+)/g' 95 | replace: 'https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-$1-$2' 96 | - search: 'JFR' 97 | replace: 'Jenkinsfile Runner' 98 | - search: 'CWP' 99 | replace: 'Custom WAR Packager' 100 | - search: '@dependabot-preview' 101 | replace: '@dependabot' 102 | 103 | autolabeler: 104 | - label: 'dependencies' 105 | title: 106 | - '/chore(deps)/i' 107 | - label: 'documentation' 108 | branch: 109 | - '/docs{0,1}\/.+/' 110 | title: 111 | - '/documentation/i' 112 | - '/docs/i' 113 | - label: 'bug' 114 | branch: 115 | - '/fix\/.+/' 116 | title: 117 | - '/fix/i' 118 | - label: 'chore' 119 | branch: 120 | - '/chore\/.+/' 121 | title: 122 | - '/chore/i' 123 | - label: 'enhancement' 124 | branch: 125 | - '/feature\/.+/' 126 | body: 127 | - '/JENKINS-[0-9]{1,4}/' 128 | title: 129 | - '/feat/i' 130 | --------------------------------------------------------------------------------