#30414 closed Cleanup/optimization (wontfix)
Please document scripts being used on djangoci.com.
Reported by: | Daniel Hahler | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
I failed to find them, trying to figure out what the CI jobs run exactly. Are they only visible when logged in?
This should be added to the wiki then: https://code.djangoproject.com/wiki/Jenkins
Change History (2)
comment:1 by , 6 years ago
Component: | Uncategorized → Documentation |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Summary: | Please document scripts being used on djangoci.com → Please document scripts being used on djangoci.com. |
Type: | Uncategorized → Cleanup/optimization |
Version: | 2.2 → master |
comment:2 by , 6 years ago
Well, even at the referenced wiki page it only mentions my_postgres_settings
as a name, without any real example.
I've hoped that the build configuration / scripts could be just seen on Jenkins somehow (similar to .travis.yml
etc normally), and did not mean to paste them to the wiki.
Note:
See TracTickets
for help on using tickets.
There is nothing sophisticated in tests scripts run on Jenkins they have the same steps as described in documentation. I don't see much value in sharing them on wiki.