1654759865
Gitea 1.19 is here. Release notes can be found at: https://github.com/go-gitea/gitea/blob/v1.19.3/CHANGELOG.md I've highlighted the breaking changes entries in this commit message with notes on whether or not this affects us. * 1.19.0 * Add loading yaml label template files (#22976) (#23232) * I think this is for auto applying labels to PRs? Shouldn't affect us. * Make issue and code search support camel case for Bleve (#22829) * We don't rely on code search in gitea yet, but this seems like a good addition. * Repositories: by default disable all units except code and pulls on forks (#22541) * We don't allow forks so this shouldn't affect us. * Support template for merge message description (#22248) * We don't do merging via gitea so this shouldn't affect us. * Remove ONLY_SHOW_RELEVANT_REPOS setting (#21962) * We don't set this flag in our app.ini config file. * Implement actions (#21937) * They are disabled by default, but I've explicitly disabled them as we use Zuul. * Remove deprecated DSA host key from Docker Container (#21522) * Our installatins were all created prior to this update which generated DSA keys. We can go and manually clean them up with gitea disabled if we like. * Improve valid user name check (#20136) * As long as our CI job is able to create the necessary accounts we should be fine. * 1.19.1 * Rename actions unit to repo.actions and add docs for it (#23733) (#23881) * app.ini.j2 updated to use repo.actions to disable the repo unit. * 1.19.2 * No breaking changes listed. * 1.19.3 * No breaking changes listed. In addition to the breaking changes upstream has updated to golang 1.20 and nodejs 18. We update our image to match. In 1.19.0 and 1.19.1 org listing required authentication which was a new change/regression in [0] gitea. I have updated the logo update role to drop authentication details to make it clear this API should be publicly accessible. In earlier patchsets I was forcing basic auth due to another bug [1] which is not correct as we expect this API to be public. Updating the role this way makes that more clear. Finally the usual template updates are applied to keep our forked templates in line with upstream. There were no template changes between 1.19.0, 1.19.1, 1.19.2, and 1.19.3 according to git diff. [0] https://github.com/go-gitea/gitea/issues/24159 [1] https://github.com/go-gitea/gitea/issues/24160 Change-Id: I5570deaf505a27c8c90c58896de990a4d2d44530 |
||
|---|---|---|
| assets | ||
| doc | ||
| docker | ||
| hiera | ||
| inventory | ||
| kubernetes | ||
| launch | ||
| manifests | ||
| modules/openstack_project | ||
| playbooks | ||
| roles | ||
| roles-test | ||
| testinfra | ||
| tools | ||
| zuul.d | ||
| .gitignore | ||
| .gitreview | ||
| COPYING.GPL | ||
| Gemfile | ||
| README.rst | ||
| Rakefile | ||
| bindep.txt | ||
| install_modules.sh | ||
| install_puppet.sh | ||
| modules.env | ||
| run_k8s_ansible.sh | ||
| run_puppet.sh | ||
| setup.cfg | ||
| setup.py | ||
| tox.ini | ||
README.rst
OpenDev System Configuration
This is the machinery that drives the configuration, testing, continuous integration and deployment of services provided by the OpenDev project.
Services are driven by Ansible playbooks and associated roles stored
here. If you are interested in the configuration of a particular
service, starting at playbooks/service-<name>.yaml
will show you how it is configured.
Most services are deployed via containers; many of them are built or
customised in this repository; see docker/.
A small number of legacy services are still configured with Puppet.
Although the act of running puppet on these hosts is managed by Ansible,
the actual core of their orchestration lives in manifests
and modules.
The files in this repository are provided as an opinionated example service deployment, and to allow the OpenDev Collaboratory to use public software development workflows in order to coordinate changes and improvements to the systems it runs. This repository is not intended as a reconsumable project on its own, and anyone wishing to adjust it to suit their own needs should do so with a fork. The system-config reviewers are unable to evaluate and support use cases for the contents here other than their own.
Testing
OpenDev infrastructure runs a complete testing and continuous-integration environment, powered by Zuul.
Any changes to playbooks, roles or containers will trigger jobs to thoroughly test those changes.
Tests run the orchestration for the modified services on test nodes
assigned to the job. After the testing deployment is configured
(validating the basic environment at least starts running), specific
tests are configured in the testinfra directory to validate
functionality.
Continuous Deployment
Once changes are reviewed and committed, they will be applied
automatically to the production hosts. This is done by Zuul jobs running
in the deploy pipeline. At any one time, you may see these
jobs running live on the status page or
you could check historical runs on the pipeline
results (note there is also an opendev-prod-hourly
pipeline, which ensures things like upstream package updates or
certificate renewals are incorporated in a timely fashion).
Contributing
Contributions are welcome!
You do not need any special permissions to make contributions, even those that will affect production services. Your changes will be automatically tested, reviewed by humans and, once accepted, deployed automatically.
Bug fixes or modifications to existing code are great places to start, and you will see the results of your changes in CI testing. Please remember that this repository consists of configuration and orchestration for OpenDev Collaboratory production systems, so contributions to it will be evaluated on the basis of whether they're useful or applicable to OpenDev's services. Changes intended to make the contents more easily reusable outside OpenDev itself are not in scope, and so will be rejected by reviewers.
You can develop all the playbooks, roles, containers and testing required for a new service just by uploading a change. Using a similar service as a template is generally a good place to start. If deploying to production will require new compute resources (servers, volumes, etc.) these will have to be deployed by an OpenDev administrator before your code is committed. Thus if you know you will need new resources, it is best to coordinate this before review.
The #opendev IRC on OFTC channel is the main place for interactive discussion. Feel free to ask any questions and someone will try to help ASAP. The OpenDev meeting is a co-ordinated time to synchronize on infrastructure issues. Issues should be added to the agenda for discussion; even if you can not attend, you can raise your issue and check back on the logs later. There is also the service-discuss mailing list where you are welcome to send queries or questions.
Documentation
The latest documentation is available at https://docs.opendev.org/opendev/system-config/latest/
That documentation is generated from this repository. You can geneate
it yourself with tox -e docs.