Fair enough. If its just for outside contributor PRs I am agree with not owning
the risk ;-)
Stephen Connolly wrote on 2019-01-04 16:06:
> On Fri 4 Jan 2019 at 22:00, Tibor Digana wrote:
>
>> @Stephen Connolly
>> After such a big investment, especially made on your side, in Jenkins
>> plugi
Il dom 6 gen 2019, 21:04 Sylwester Lachiewicz ha
scritto:
> In Maven Resolver we have a sample Travis configuration, so someone can
> test with the forked repo.
> If we go with Travis CI I would be good to have a common configuration for
> all projects (ie to run run-it etc and have .travis.yml e
I believe my employer also offers free build services for OSS projects via
our CodeShip offering. If people are concerned about tying PR validation
exclusively to one vendor we should inspect the CloudBees CodeShip
capabilities (includes Docker build agents, which can be very nice...
though I confe
Am 2019-01-06 um 20:41 schrieb Sylwester Lachiewicz:
Hi, a small reminder - anyone to second MNG-5995 and MNG-6069?
I'd like to include both in next release.
I am fine with both, but for some comments on the MNG-6069 PR.
Michael
pt., 30 lis 2018 o 00:21 Sylwester Lachiewicz
napisał(a):
Hi
In Maven Resolver we have a sample Travis configuration, so someone can
test with the forked repo.
If we go with Travis CI I would be good to have a common configuration for
all projects (ie to run run-it etc and have .travis.yml excluded from RAT).
I saw in one Apache project (don't remember now n
disabled logs, workspace and artifacts for anonymous Jenkins users, but
available for PMC and Maven committers.
On Sun, Jan 6, 2019 at 8:41 PM Mickael Istria wrote:
> On Sun, Jan 6, 2019 at 8:32 PM Tibor Digana
> wrote:
>
> > I meant Bitcoins. Without network access bitcoins can be loaded but
>
Hi Karl,
I would like to include more [1[ in 3.6.1
MNG-6543, MNG-6522, MNG-6520, MNG-6506, MNG-6294, MNG-6071, MNG-6069,
MNG-5995, MNG-5693
please review and approve before I can merge.
BR
Sylwester
[1]
https://jira.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unres
Hi, a small reminder - anyone to second MNG-5995 and MNG-6069?
I'd like to include both in next release.
Sylwester
pt., 30 lis 2018 o 00:21 Sylwester Lachiewicz
napisał(a):
> Hi,
> branches for MNG-5995 and MNG-6069 ready in maven core - build passed
>
>
> https://builds.apache.org/view/M-R/vie
On Sun, Jan 6, 2019 at 8:32 PM Tibor Digana wrote:
> I meant Bitcoins. Without network access bitcoins can be loaded but nobody
> can use them. An access to Workspace and archived artifacts should be
> disabled for users.
That would be sad since those are actually super helpful when trying to
d
@Stephen Connolly
I meant Bitcoins. Without network access bitcoins can be loaded but nobody
can use them. An access to Workspace and archived artifacts should be
disabled for users.
On Sun, Jan 6, 2019 at 5:51 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> That is not the prob
Il dom 6 gen 2019, 18:03 Hervé BOUTEMY ha scritto:
> you mean this directory is not involved in the seed job [2]?
>
I meant only that the name of such directory was not special, it works as
you described
when I look into this job, I see a "Process Job DSLs" step that looks on
> filesystem ".tes
you mean this directory is not involved in the seed job [2]?
when I look into this job, I see a "Process Job DSLs" step that looks on
filesystem ".test-infra/jenkins/job_*.groovy"
in Maven, the "maven-box" seed job [3] is created with the ASF's Gitpubsub
Jenkins plugin that creates the mutlibran
That is not the problem you think it is. Bitcoin mining is the current
issue. And through Jenkinsfile or Process.exec you can bypass JVM
permissions
On Sun 6 Jan 2019 at 16:44, Tibor Digana wrote:
> Regarding "pull/1234/head" refs and the security, I think allowing only the
> permission to Maven
Regarding "pull/1234/head" refs and the security, I think allowing only the
permission to Maven Central IP address is needed and nowhere else.
This can be accomplished by the java policy in JRE.
WDYT?
On Sun, Jan 6, 2019 at 11:09 AM Hervé BOUTEMY wrote:
> I didn't know about these special "pull/
The Apache Maven team is pleased to announce the release of the Apache
Maven Wagon, version 3.3.1.
https://maven.apache.org/wagon/
Release Notes - Maven Wagon - Version 3.3.1
** Bug
* [WAGON-538] - Basic authentication fails if the password contains
non-ASCII characters
* [WAGON-54
Can support regex expression for maven exclusions of dependency?
I wish ingore multi dependency that has same regex , instead of write multi
exclusion.
Example:
I want to exclude all springframework dependency like as
org.springframework*
*
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Dan Tran, Tibor Digana, Robert Scholte
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file
and add this release the board report.
+1
On Thu, Jan 3, 2019 at 2:28 PM Michael Osipov wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344772
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2
+1
On Thu, 03 Jan 2019 14:28:13 +0100, Michael Osipov
wrote:
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12344772
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON
Brian,
can you pick this up?
thanks,
Robert
On Sat, 05 Jan 2019 12:11:41 +0100, Enrico Olivelli
wrote:
Can any admin create this project ?
for Maven Scripting Plugin
https://issues.apache.org/jira/browse/MSCRIPTING
Regards
Enrico
Enrico> limited to linux and osx, not windows.
Windows can be tested via AppVeyor.
The configuration is the same: one adds appveyor.yml (e.g.
https://github.com/apache/calcite/blob/master/appveyor.yml ) and asks
Infra team to enable AppVeyo-GitHub integration.
Vladimir
--
It is not a special directory, we are using Je kins DSL, and there is a
'seed job' which parses these files and creates/updates the jobs.
This way committers without direct access to Jenkins can operate on
configuration and we can work with review then commit.
Therefore it is easy to reconstruct ev
Il dom 6 gen 2019, 10:32 Hervé BOUTEMY ha scritto:
> Le samedi 5 janvier 2019, 12:34:30 CET Enrico Olivelli a écrit :
> > Travis up and running on Maven Scripting Plugin
> > this is the first build with integration tests
> >
> > mvn verify -Prun-its
> > https://travis-ci.org/apache/maven-scriptin
I didn't know about these special "pull/1234/head" refs, that are not real
branches: if these pseudo-branches were synchronized to Gitbox like any
branch, the Gitpubsub mechanism could happen at Apache
of course, the security implications of running code from these PR branches
would still have t
Le samedi 5 janvier 2019, 12:34:30 CET Enrico Olivelli a écrit :
> Travis up and running on Maven Scripting Plugin
> this is the first build with integration tests
>
> mvn verify -Prun-its
> https://travis-ci.org/apache/maven-scripting-plugin/builds/475666300
>
> This is how the PR looks like:
>
interesting
I suppose this is enabled by the content of .test-infra/jenkins directory [1]
even if I don't really understand the content and how we could add something
like this in our configuration
Regards,
Hervé
[1] https://github.com/apache/bookkeeper/tree/master/.test-infra/jenkins
Le same
26 matches
Mail list logo
