On Thu, Jun 16, 2016 at 01:05:26PM +0200, Michael Scherer wrote: > Le mercredi 15 juin 2016 à 21:14 +0530, Nigel Babu a écrit : > > Hello folks, > > > > We have 45 people who have access to Jenkins UI. Pretty much everyone will be > > losing this access in the next couple of weeks. > > > > At the moment, I understand that access to the UI is essential for configuring > > jobs. I’m going to change this in the near future. Jenkins Job Builder[1] will > > talk to Jenkins to create/update jobs. Job information will be managed as a > > collection of yaml files. If you want a new job, you can give us a pull request > > with the correct format. The jobs will then be updated (probably via Jenkins). > > You will then no longer need access to Jenkins to create or manage jobs. In > > fact, editing the jobs in the UI will make the YAML files out of sync. > > > > Before we start this process, I’d love to know if you use your Jenkins access. > > If you do use it, please let me know off-list what you use it for. > > Why "off-list" ? > > I kinda interested too to know the needs... > > -- > Michael Scherer > Sysadmin, Community Infrastructure and Platform, OSAS > > I was hoping to reduce noise to the list, but I see how the replies are useful. So please reply-all. I'll forward any direct replies I get. > _______________________________________________ > Gluster-infra mailing list > Gluster-infra@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-infra -- nigelb _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-devel
