I meant the permissions thing which is dotted all around the codebase, and
looks like this:
import hudson.security.ACL;
import org.acegisecurity.Authentication;
public void doSomething(Authentication authentication) {
if (ACL.SYSTEM.equals(authentication)) {
// do something
}
}
The matr
Hi Everybody,
Considering the number of people who contacted me about
`repo.azure.jenkins.io`, makes me realize that in the hurry two weeks ago, I
didn't communicate very well about it.
To bring the context, that service was running on an old Kubernetes cluster
(v1.7) provided by a deprecated
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2020-02-26.
Please, report your findings in this thread.
Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war
Thanks!
--
oliver
--
You received this mes
I am happy that we start this discussion early enough before the current Jira
version becomes at the end of life.
It's a topic important enough to have as much feedback as possible but also
whatever we decide we won't have support from 100% of the contributors
otherwise we wouldn't have this lon
> On 11. Feb 2020, at 08:11, Tim Jacomb wrote:
>
> I feel like we can work something out for the security project, possibly
> there’s a better tool for it...
>
> I don’t think it’ll work easily in the cloud version either
Since it seems like we've managed to finally really derail this threa
Since the thread is indeed pretty well derailed by now,
On Fri, Feb 14, 2020 at 9:17 AM Daniel Beck wrote:
> The major obstacle as I see it is the mapping of users. This applies to every
> alternative not backed by our LDAP.
Right. It would be great to switch to GitHub SSO, avoiding the
confusi
ACL is in jenkins-core along with AccessControlled and the other
classes Jesse mentioned.
On Fri, Feb 14, 2020 at 4:59 AM Chris Kilding
wrote:
>
> I meant the permissions thing which is dotted all around the codebase, and
> looks like this:
>
> import hudson.security.ACL;
> import org.acegisecur
Thanks everybody!
On Thursday, February 13, 2020 at 7:16:34 PM UTC+1, Raul Arabaolaza wrote:
>
> Hello all,
>
> According to the calendar the 2.204.3 RC should be out yesterday Wednesday
> 12th, but it seems is not yet and there are no new commits in the
> stable-2.204 branch since 16 days ago.
Job Title:- AWS Data Engineer.
Location:- Charlotte, FL.
Duration:- Long Term Contract.
Job Description:-
-> Experience In Designing And Deploying An AWS-Based Application
(Native/Re-Factored), #Python, #Scala, #Spark, #Oozie, #Big Data.
-> Expertise In The #Core AWS Services, Uses #Automation And
Triple facepalm...
This one is my fault, so sorry. I went too fast and clicked the "always
approve", even worse.
Can someone with more permissions check that this user's next post doesn't
get through too please?
My apologies again.
Thanks
Le ven. 14 févr. 2020 à 19:31, Sai Kumar B a
écrit :
>
Thanks! I haven't found a way to block a user once they were allowed, but
I did reply privately to the sender asking that they not send more. I also
deleted the message from the group archive as spam. I don't think that
will ban the author, though maybe.
We've had pretty good luck with our own
I can build a super quick web app with approval support tied to
LDAP/GitHub/Google accounts.
Anyone can submit, few can approve
On Thu., Jan. 23, 2020, 4:55 a.m. Tim Jacomb, wrote:
> Why not setup required reviews?
> There can be a small group of people who can bypass if necessary but most
> pe
12 matches
Mail list logo
