I would recommend running jenkins just once every 24 hours or something to that effect.
Yes, that's my plan. The download links appear to require Jenkins running though, but this should be fixable.
Before Jenkins, we had some directory listing (h5ai) and a cron job that ran daily. It did the job well, but a nicer interface is tempting as well.
A1ex, I've got a simple Python script running now, that reads a generic template file, takes the URL of the latest nightly build from Jenkins and write everything into a new HTML file.
Sounds good!
Too bad currently Jenkins is not reachable here. So I couldn't test out things.
Just restarted it, hope it's fine now. It used to lock up within minutes after starting, but since I've disabled the builds page, it's a little better. Not sure how to diagnose it - the symptom is very high CPU usage with no apparent reason (and no obvious increase in website traffic - it's actually pretty quiet).
Do you plan to use one Python script that generates multiple HTML file or do you need to call it with parameters for each camera model?
I don't mind, either way should be fine.
> There's some extra functionality I'd like to add, too.
Could you tell me what you like to add in future?
Sure, most of it should be obvious from the extra menu items from the example HTML, but I'll give some details below.
Here's what I'd like to address:
* design: OK to keep it along the same lines as the old one?
* compatibility with Windows or Mac browsers: does my HTML template look fine there?
* validation: I'm not good at web development, so other than the w3c validator, I'm not sure what to look for.
* top menu:
- main builds: ports merged to mainline
- early ports: ports that are still in progress and can be compiled from their own branches (e.g. 1200D)
- additional modules:
- here I'm thinking to list the modules that are not widely used, or still experimental (e.g. io_crypt, tiltcalc, raw_diag)
- I can compile from user repos as well
- todo: a list with what's worth including here
- what about naming this just Modules, moving the modules section from the features page here, and listing additional modules below?
- utilities
- things like mlv_dump, raw2dng, cr2hdr, with both win/mac builds
- todo: a list with what's worth including here
- experiments
- builds from branches like new_sound_system, crop_rec, iso-research
- what about compiling pull requests automatically, so users can give feedback easier?
- other stuff worth including?
* buttons:
- change log
- this used to be a popup box, which looks nice, but requires javascript, which I'd rather avoid
- I'm open to suggestions on how to make them more obvious
- what about displaying the changes for latest build right below the buttons?
- the changes for old builds could be in a large HTML page; maybe only show the last month or so?
- build log: plain text is fine for me; better suggestions?
- old builds: large HTML page?
- screenshots and tests:
- proof of concept
here - we may start with some menu screenshots from qemu (should already work on some cameras like 60D, 5D3, 500D, 1200D), and do the rest later.
- a simple test would be to start each binary in QEMU and check whether ML config file gets created (this should also work on models with SD card that cannot boot the GUI yet)
- this section has huge potential IMO (automated burn-in tests and such), but let's start with something easy, just to get the ball rolling.
- discussion: just links to the forum (for each camera)
We don't need to finish all of these in order to get it back online; just the basics (previous functionality). I'm just thinking in advance, what would be nice to have over the next few months.
That's it for now, thanks for helping on any of those items. I expect to have some more time next week, to work on it; meanwhile, I'm mostly available during evenings (European time). We may discuss on IRC as well if you prefer.
