A little general purpose documentation on using Jenkinsfiles

Hi all, As I have been setting up the builds for several Apache projects, I usually encountered the same problems and used the same solutions. Thinking that this might help other projects, I documented recipes for some of the typical problems I encountered over time: https://cwiki.apache.org/c

Re: workspace cleanups needed on jenkins master

Hi all, seeing PLC4X consuming 6 GB ... being a quite small project, that's clearly too much. Even if I have an idea why this is probably the reason. Could you please also share what's consuming that much space? Chris Am 27.12.18, 20:05 schrieb "Karl Heinz Marbaise" : Hi Chris,

Re: workspace cleanups needed on jenkins master

work. Chris Am 28.12.18, 12:22 schrieb "Olivier Lamy" : Looking at https://builds.apache.org/job/PLC4X/job/PLC4X/job/develop/ the history is 30 builds for only one branch (same for others) this history is consuming space On Fri, 28 Dec 2018 at 19:58,

PRJenkins builds for Projects

Hi all, the IoTDB Team would like to have PRs automatically built. When using the Multibranch Pipeline plugin it already would validated PRs from a branch, but not from a fork. Now I was guided here and to this page: https://cwiki.apache.org/confluence/display/INFRA/GitHub+Pull+Request+Builder

Re: PRJenkins builds for Projects

hen I look at the "GitHub-Projekt" plugins description ... this doesn't seem to handle PRs. Chris Am 03.01.19, 16:07 schrieb "Allen Wittenauer" : > On Jan 3, 2019, at 7:01 AM, Christofer Dutz wrote: > > Hi all, > > the

Re: Please pick up after yourself

Is there a way to check the status of a project? I would like to help improve and have done some things, but I need a way to see that what I'm doing is helping. Chris Am 03.01.19, 16:10 schrieb "Allen Wittenauer" : > On Jan 3, 2019, at 3:11 AM, Bertrand Delacretaz wrote:

Re: PRJenkins builds for Projects

eb "Allen Wittenauer" : > On Jan 3, 2019, at 7:14 AM, Christofer Dutz wrote: > > I can't see that ... where can we find that ... and we don't want to automatically push everything that works. > > From the description of "Enable Git validated

Re: PRJenkins builds for Projects

h.MultiBranchProject$BranchIndexing.run(MultiBranchProject.java:1025) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE Chris Am 03.01.19, 16:34 schrieb "Christofer Dutz" : Hi Allen,

Re: PRJenkins builds for Projects

thing that wouldn't harm the ASF. Chris Am 03.01.19, 16:37 schrieb "Allen Wittenauer" : > On Jan 3, 2019, at 7:34 AM, Christofer Dutz wrote: > > Hi Allen, > > thanks for that ... if I had known that simply selecting the "Gi

Re: PRJenkins builds for Projects

rent topic. Chris Am 04.01.19, 15:20 schrieb "Allen Wittenauer" : > On Jan 4, 2019, at 2:00 AM, Christofer Dutz wrote: > > Hmmm, > > thinking about it ... this is not quite "safe" is it? Just imagining someone starting PRs with mav

Re: Can we package release artifacts on builds.a.o?

Just adding my thoughts to the problem: Whenever I did a Maven training in the past, the core mantra I tried my students to understand was: "If it's hard to do with Maven, you're probably doing it wrong." Ok ... if you're working on builds for non-java, things do get quite a lot trickier, but s

Re: Can we package release artifacts on builds.a.o?

Hi Alex, Ways to do bad stuff with just a pom.xml: - simply adding a dependency to a vulnerable library, even an intentionally staged malicious one. - Adding an evec-maven-plugin to execute anything on the host machine - Generate code - Like I introduced into the FlexJS maven build: Patch/Modify

Re: PRJenkins builds for Projects

Hi, In The Edgent project we were using Travis. But the integration mode has changed. The legacy way worked, but you can no longer set it up and the new way requires privileges we can't give. At least I was told from infra when I asked to change the integration version to the new one. Regard

Re: Can we package release artifacts on builds.a.o?

Chris, Thank you for providing Carlos with instructions. Was that on or off list? Regards, Dave Sent from my iPhone > On Jan 7, 2019, at 1:18 PM, Christofer Dutz wrote: > > Hi Alex, > > Ways to do bad stuff with just a pom.xml: > - simply adding a dependency to a vul

Re: Can we package release artifacts on builds.a.o?

Just have a look at the Jenkinsfile of the PLC4X projects develop branch. The build has an additional Parameter: -DaltDeploymentRepository=snapshot-repo::default::file:./local-snapshots-dir clean deploy The deploy step then use the wagon plugin to upload. You'll figure it out the rest ... Chri

RAT not working equally on all platforms?

Hi all, I have spent the last few days hardening the PLC4X build by running it on loads of different systems, operating-systems, library versions and even network infrastructures. One thing I noticed that a build on a windows machine may fail by rat complaining a file (particularly a Wireshark

Fair use policy for build agents?

Hi all, we now had one problem several times, that our build is cancelled because it is impossible to get an “ubuntu” node for deploying artifacts. Right now I can see the Jenkins build log being flooded with Hadoop PR jobs. Would it be possible to enforce some sort of fair-use policy that one p

Re: Fair use policy for build agents?

, Integration Tests, Sonar Analysis, Website generation and then waits to get access to a node that can deploy and here the job just times-out :-/ Chris Von: Uwe Schindler Datum: Donnerstag, 22. August 2019 um 17:40 An: "builds@apache.org" , Christofer Dutz , "builds@apache.or

Re: Fair use policy for build agents?

Hi all, well I agree that we could possibly split up the job into multiple separate builds. However this makes running the Jenkins Multibranch pipeline plugin quite a bit more difficult. And the thing is, that our setup has been working fine for about 2 years and we are just recently having

Re: Jenkins

Hi Gabriel, I just have to jump in here ... as I saw you were only getting feedback from one side. I did see that Cloudstack generally seems to be built with Maven, so I can give some input There is absolutely nothing wrong with building dev snapshots on a CI server ... that's one of the thin

Re: [IMPORTANT] - Migration to ci-builds.a.o

Hi, could you please create the folder for the Apache PLC4X project? Thanks, Chris Am 18.07.20, 20:04 schrieb "Stefan Seelmann" : Done: https://issues.apache.org/jira/browse/INFRA-20545 On 7/18/20 7:25 PM, Gavin McDonald wrote: > Thanks Stefan, > > Can you create an INFR

Re: [ci-builds] - New Project Folder requests

Please create a folder for "PLC4X" Thanks, Chris Am 18.07.20, 12:12 schrieb "Gavin McDonald" : Hi All, The Migrations thread is getting a bit large, so please any new requests for Project Folder requests please either open a new INFRA jira ticket or reply to this new thread

Re: [IMPORTANT] - Migration to ci-builds.a.o

17 schrieb "Christofer Dutz" : Hi, could you please create the folder for the Apache PLC4X project? Thanks, Chris Am 18.07.20, 20:04 schrieb "Stefan Seelmann" : Done: https://issues.apache.org/jira/browse/INFRA-20545 On 7/18/20

AW: Reproducible builds [Airflow] -> done

In PLC4X we’re also working on enabling fully reproducible builds. As PLC4X contains Java, C, C#, Go, Python, … it was a bit of a challenge, but I think we’ll cross the finishing lines with our upcoming release. We basically gave up on the idea of configuring our tooling to produce the same outp

[jira] [Commented] (BUILDS-34) SSL Handshake errors on jenkins build

[ https://issues.apache.org/jira/browse/BUILDS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244119#comment-14244119 ] Christofer Dutz commented on BUILDS-34: --- Ping? > SSL Handshake errors on