[Jenkins-infra] Board election (INFRA-536)

nicolas de loof nicolas.deloof at gmail.com
Tue Oct 18 19:38:57 UTC 2016


2016-10-18 21:18 GMT+02:00 R. Tyler Croy <tyler at monkeypox.org>:

> (replies inline)
>
> On Tue, 18 Oct 2016, nicolas de loof wrote:
>
> > l have some cycles I can spend on INFRA-536 (implement board election
> > voting)
> > I don't know the context about Apache STeVe, IIUC there have been some
> > prior experiments to integrate with it jenkins infra.
>
>
> orrc suggested Apache Steve but it's *way* too immature IMHO, has some
> problematic infrastructure requirements (lol elasticsearch), and lacks
> integration with LDAP :/
>
>
> > I can give it a try, other option is for me to implement STV inside
> > jenkins.io account application,
> > using https://wiki.jenkins-ci.org/display/JENKINS/Board+Election+Process
> as
> > a spec.
>
>
> This is the direction I was thinking on hacking towards. The only
> persistent
> store behind the account-app is LDAP, which is certainly not where votes
> should
> go IMO. One approach I was thinking about was configuring an "election
> transaction file" which would be append-only, and then making the
> account-app
> write votes to that file.
>
> That would make the changes to the account-app minimal, and then we can
> just
> write some Groovy or Python to process the election transaction log.
>
>
Ho wis this app hosted ? I can see a Dockerfile, so wonder if we run a
docker container. In such case I guess we can get a volume with backup ?
Because replacing a database (elastic or whatever) with a flat file doesn't
seem to me a way to make this a robust solution :P


>
> The challenge I haven't given much thought to was how to present the
> election
> options, basically, how would the account-app know who the candidates
> would be?
> How would it know how long the election should run, etc.
>

Administrator UI seems to be the simplest option.


>
>
>
> I'm excited that somebody other than me might hack on this :D
>
>
> Cheers
> - R. Tyler Croy
>
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20161018/f10375df/attachment.html>


More information about the Jenkins-infra mailing list