On Thu, Oct 25, 2018 at 1:16 PM Matt Sicker wrote:
> I'm somewhat iffy on the admin UI since toggling feature flags is an advanced
> end user behavior
IIRC KK & Tyler were emphatic that for Evergreen at least, selection
of feature flags should not be exposed to administrators—this would be
I've been investigating what's required in order to support <
https://issues.jenkins-ci.org/browse/JENKINS-21336> (tl;dr: make
RUN_SCRIPTS the top most permission instead of ADMINISTER), and one major
requirement I've found is that such a complex change would likely only be
possible through
Thanks - I submitted another change and it seems to be back to normal.
> On 25 Oct 2018, at 13:41, Jesse Glick wrote:
>
> On Thu, Oct 25, 2018 at 4:57 AM pallen wrote:
>> Possibly one for infrastructure, but I can't post to that group.
>
> You can always file a ticket in the `INFRA` project.
On Thu, Oct 25, 2018 at 4:57 AM pallen wrote:
> Possibly one for infrastructure, but I can't post to that group.
You can always file a ticket in the `INFRA` project.
> https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/285/
>
> Please can you re-run the build and check the slaves - it
Hi Guys,
Possibly one for infrastructure, but I can't post to that group.
https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/285/
Please can you re-run the build and check the slaves - it looks like some
sort of remoting issue.
Thank you.
Kind regards,
Paul
--
You received this
