This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Apache Gitbox Self Service Requirements

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Record fixed issues

...

FeatureNotes
Update GitHub repository topicsWe want to make it easier for our users filtering for groups of repositories belonging together.
Repository topics would solve this.
Update GitHub repository description and URL
Archive/Unarchive a GitHub repositoryFrom time to time we deprecate modules. We do not want to delete their repositories but rather lock them down and make it clear that they are no longer maintained. The GitHub archive feature would fulfill this.
Disable JIRA Integration

By default GitHub pull request creation/closing and any comments are added as comments to the linked Jira issues. Since this is also sent to the mailing list there is lots of unwanted noise. We have asked infra once to change this setting (

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyINFRA-16219
) but this only had effect for existing repositories.

(tick) Jenkins Github hook configuration

We are moving to a Github-centric Jenkins model (

Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keySLING-7245
) which would issue a large number of GitHub API requests to check for branches to build. Enabling hooks would solve this problem, but it would have to happen for all existing repos and automatically for new ones as well. Fixed with
Jira
serverASF JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyINFRA-17660