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

nicolas de loof nicolas.deloof at gmail.com
Fri Oct 21 16:28:30 UTC 2016


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

> (replies inline)
>
> On Fri, 21 Oct 2016, nicolas de loof wrote:
>
> > current proposed implementation uses a simple file to log each vote
> event.
> > so my question : can we get some persistent filesystem on infra ?
>
>
> "Persistent filesystem" doesn't explain anything to me as far as
> requirements
> for infrastructure is concerned.
>
>
>
> Files don't just disappear in Jenkins infrastructure
>

Filesystem on any cloud service is considered ephemeral until there's some
specific infra to ensure it's replicated and distributed. But according to
your comment I assume Azure does it right, so will now focus on
implementing STV base on such a log file.


>
>
>
> >
> > 2016-10-21 18:15 GMT+02:00 R. Tyler Croy <tyler at monkeypox.org>:
> >
> > > (replies inline)
> > >
> > > On Thu, 20 Oct 2016, nicolas de loof wrote:
> > >
> > > > 2016-10-20 17:45 GMT+02:00 Daniel Beck <ml at beckweb.net>:
> > > >
> > > > >
> > > > > > On 20.10.2016, at 17:03, nicolas de loof <
> nicolas.deloof at gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > I prefer to use jenkins.io ID vs arbitrary string, so one can
> link
> > > to
> > > > > profile, github, gravatar, etc.
> > > > >
> > > > > No real need for any of this as there'll be a blog post or similar
> > > > > introduction articles on each candidate.
> > > > >
> > > > > Besides,
> > > > > * You won't get around the need to have a custom URL as just
> linking to
> > > > > the GitHub profile or wiki profile will be pretty much useless in
> > > informing
> > > > > voters about the candidates.
> > > > > * Since we're placing so much emphasis on company affiliation that
> we
> > > need
> > > > > a custom counting algorithm, we really should show this in the
> voting
> > > UI as
> > > > > well.
> > > > >
> > > >
> > > > ack
> > > >
> > > >
> > > > >
> > > > > > just as a side note, writing votes log to a plain file doesn't
> make
> > > this
> > > > > solution "simpler", until we can ensure this file is persisted and
> has
> > > > > backups. IIUC we don't have such a guarantee with current hosting
> > > solution,
> > > > > do we ?
> > > > >
> > > > > To clarify, the voting log can be a database or whatever else you
> want.
> > > > > It's just that there's no need to add the result computation to the
> > > account
> > > > > app.
> > > > >
> > > >
> > > > right, but we don't have any safe storage but LDAP iiuc. Maybe Tyler
> can
> > > > provide more details ?
> > >
> > >
> > >
> > > I am strongly against using LDAP as a general-purpose data storage tier
> > > for the
> > > account-app, which is why I suggested adding an actual DB behind the
> > > account-app to help with this.
> > >
> > >
> > >
> > > - R. Tyler Croy
> > >
> > > ------------------------------------------------------
> > >      Code: <https://github.com/rtyler>
> > >   Chatter: <https://twitter.com/agentdero>
> > >
> > >   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> > > ------------------------------------------------------
> > >
>
> - 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/20161021/3bb863eb/attachment-0001.html>


More information about the Jenkins-infra mailing list