Re: packer and vagrant and virtualbox

their example not work? On 10/03/2022 04:38, Gavin McDonald wrote: Hi Joan. On Thu, Mar 10, 2022 at 10:01 AM Joan Touzet wrote: Try something like: https://gist.github.com/mak3r/3f05c9d4f6f46d24d99bcfa4ac33 I think you need vagrant. yeah I have that. What I am doing is creating an AMI

Re: packer and vagrant and virtualbox

Try something like: https://gist.github.com/mak3r/3f05c9d4f6f46d24d99bcfa4ac33 I think you need vagrant. On 2022-03-10 3:40 a.m., Gavin McDonald wrote: > Hi All, > > docs are failing me. > > I have packer currently outputting an aws type .box file > > I would like to have that opened in

Re: Better stability with docker authenticated jenkins agents

On 14/04/2021 13:05, Mick Semb Wever wrote: >> Then it is easy to use our own Jenkins-stored creds >>

Re: Better stability with docker authenticated jenkins agents

On 07/04/2021 07:43, Mick Semb Wever wrote: >> >> My understanding is that pulls of all images from the apache/* namespace >> are not subject to rate limiting. Thus, the recommendation to move >> everything you need inside of it. >> > As >95% of our CI docker commands are pulls from apache/

Re: Bintray Deprecation

Hi Gavin, any updates? We need to do a release and get our documentation/external references updated. I tried pinging you on IRC twice, but no response. -Joan On 28/03/2021 12:49, Joan Touzet wrote: > Thanks Gavin. I know this couldn't have been an easy task. Looking > forward to th

Re: Better stability with docker authenticated jenkins agents

On 06/04/2021 18:09, Mick Semb Wever wrote: >> >>> Has anyone experience with such issues before? >> >> Yes. See https://issues.apache.org/jira/browse/INFRA-20795 for detail. >> >> In short, once Infra agrees to create the images for us, we'll move all >> our CI dependencies into those containers,

Re: Better stability with docker authenticated jenkins agents

Hi Mick, On 06/04/2021 06:34, Mick Semb Wever wrote: > tl;dr > Can and should all jenkins agents be (automatically) docker authenticated, > for improved stability around docker commands? > > > This past week the ci-cassandra.apache.org CI fell over because a fair > percentage of docker pulls

Re: Bintray Deprecation

Thanks Gavin. I know this couldn't have been an easy task. Looking forward to the info. On 28/03/2021 11:00, Gavin McDonald wrote: > Hi All, > > As advertised in [1] Bintray is closing down. > > We have secured a replacement for bintray, which is JFrogs more extensive > software offering

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

20 at 11:08 PM Gavin McDonald wrote: Hi , Just to note I have emailed DockerHub, asking for clarification on our account and what our benefits are. On Thu, Oct 29, 2020 at 6:34 PM Allen Wittenauer wrote: On Oct 29, 2020, at 9:21 AM, Joan Touzet wrote: (Sidebar about the script's details)

Re: Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

On 2020-10-29 11:37 a.m., Allen Wittenauer wrote: On Oct 28, 2020, at 11:57 PM, Chris Lambertus wrote: Infra would LOVE a smarter way to clean the cache. We have to use a heavy hammer because there are 300+ projects that want a piece of it, and who don’t clean up.. We are not build

Docker rate limits likely spell DOOM for any Apache project CI workflow relying on Docker Hub

Got your attention? Here's what arrived in my inbox around 4 hours ago: > You are receiving this email because of a policy change to Docker products > and services you use. On Monday, November 2, 2020 at 9am Pacific Standard > Time, Docker will begin enforcing rate limits on container pulls

Re: GitHub PR comment build trigger

And to add to this, with the Blue Ocean UI for Multibranch Pipeline, it is a single click to rebuild a build. It's not as friendly as commenting, but it's a single button on the results view for your build, which is linked right from the PR. Of course, this is limited to only people who have

Re: Controlling the images used for the builds/releases

ot even true for e.g. Node.JS or Python, any time there would be (potentially GNU) libc bindings. J On Mon, Sep 14, 2020 at 5:47 PM Joan Touzet wrote: Hi Jarek, I'm about to head out for 3 weeks, so I'm going to miss most of this discussion. I've done my best to leave comments in your docume

Re: Controlling the images used for the builds/releases

feel this is just continuing the double-standard I previously mentioned, albeit in a different form. Good luck with the effort, and thanks for taking on this herculean task. -Joan J. On Mon, Sep 14, 2020 at 2:57 AM Allen Wittenauer wrote: On Sep 13, 2020, at 2:55 PM, Joan Tou

Re: Controlling the images used for the builds/releases

esktop app that runs in Java or Electron (Chrome as a desktop app), as two examples. -Joan J. On Sun, Sep 13, 2020 at 11:09 PM Joan Touzet wrote: HI Jarek, Can you comment on one specific thing? In Proposal 1 you still leave the text "...MUST only add binary/bytecode files".

Re: Controlling the images used for the builds/releases

HI Jarek, Can you comment on one specific thing? In Proposal 1 you still leave the text "...MUST only add binary/bytecode files". This is not possible for convenience packages in many situations - for instance OpenOffice or other languages - where providing a full release of a product

Re: New Credentials for Github jobs

Could we get these on the ci-couchdb server for testing? Thanks. -Joan On 2020-08-14 3:37 a.m., Gavin McDonald wrote: Hi All, For those of you waiting for the 'asf-ci' credentials - this is still not resolved yet, and is waiting for Cloudbees support. However - I have created some new

Re: [ci-builds] GitHub credentials

Infra hasn't approved these in the past. If that policy changes, I'd very much like to know about it. For CouchDB we use a token on my account that I added for this purpose, limited to Apache repos only. Of course, these API calls count towards my personal limit, which affects other GitHub

Re: Controlling the images used for the builds/releases

Hey Jarek, thanks for starting this thread. It's a thorny issue, for sure, especially because binary releases are not "official" from an ASF perspective. (Of course, this is a technicality; the fact that your PMC is building these and linking them from project pages, and/or publishing them

Re: Automatically building GitHub pull requests with Jenkins

Try specifying your git repository as https://github.com/apache/guacamole-server instead of git://github.com/apache/guacamole-server.git ? Just a guess. On 09/06/2020 16:45, Mike Jumper wrote: Hello all, I've been trying to configure Jenkins jobs to automatically build pull requests for the

Re: broken builds taking up resources

On 2020-01-23 4:50, Chesnay Schepler wrote: On 23/01/2020 10:19, Thomas Bouron wrote: On Thu, 23 Jan 2020 at 08:56, Robert Munteanu wrote: On Wed, 2020-01-22 at 17:53 -0800, Chris Lambertus wrote: Additionally, orphaned docker jobs are causing major resource contention. I will be adding a

Re: Jenkins - Build docker image within a container

You may have to do a Docker sidecar running the docker daemon and pass over the docker socket, or you *might* be able to do docker-outside-of-docker. Some relevant tickets: https://github.com/fabric8io/docker-maven-plugin/issues/1005 https://github.com/fabric8io/docker-maven-plugin/issues/863 I

Re: Github Actions

Continuing the top-post trend... I'd rather see full audit logs kept ~forever for any use of credentials, including the code that was executed. If we can't stop the leak, we can at least keep the paper trail. Right now, with our aggressive build cleanup steps, I don't think this is happening.

Re: External CI Service Limitations

CI minutes/month. >>> >>> Are you currently using Git as your source code repository? >>> >>> Ray >>> >>> On Tue, Jul 16, 2019 at 8:49 AM Jarek Potiuk >>> wrote: >>> >>>> Adding Raymond Paik who is GitLab Commu

Re: External CI Service Limitations

On 2019-07-03 5:57 p.m., Greg Stein wrote: On Wed, Jul 3, 2019 at 11:36 AM Allen Wittenauer wrote: ... CouchDB keeps receiving a lot of pressure to build on aarch64, ppc64le and s390x, which keeps pushing us back to Jenkins CI (ASF or independent). And if we have to do that, then not

Re: TravisCI: various build failures - anyone else?

Looks like a known Travis CI bug: https://travis-ci.community/t/install-jdk-sh-failing-for-openjdk9-and-10/3998 On 2019-07-03 4:58 p.m., P. Ottlinger wrote: Hi *, since roughly a week ago we experience strange build failures on Travis such as

Re: External CI Service Limitations

(With my CouchDB release engineer hat on only) Anyone know if any of these external services supports platforms other than amd64/x86_64? CouchDB keeps receiving a lot of pressure to build on aarch64, ppc64le and s390x, which keeps pushing us back to Jenkins CI (ASF or independent). And if we

Re: PRJenkins builds for Projects

> > I believe this is the missing piece for Jenkins CI. > > Nope. Though configuring the behaviour for untrusted refs is a bit of > a dark magic. For one the Authorize Project plugin was implemented > without anyone paying attention to the permissions stuff in the > Credentials plugin... so there

Re: PRJenkins builds for Projects

ould you save me some time and explain > how they implement "security" so folks can't run bitcoin miners via > the PRs? > > Thanks, > -Alex > > On 1/7/19, 7:54 AM, "Joan Touzet" wrote: > > See travis-ci.org. > > This is the model we

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

> Within the Apache Subversion project, have tooling[1] to assist an RM > with > pretty much all the steps of a release. From reading this thread, it > seems > like Royale's problem is getting RMs up to speed, so maybe it can be > solved > with additional build-side tooling? > > [1]

Re: PRJenkins builds for Projects

See travis-ci.org. This is the model we could be emulating. - Original Message - From: "Alex Harui" To: builds@apache.org Sent: Sunday, January 6, 2019 6:53:44 PM Subject: Re: PRJenkins builds for Projects What other organizations are running a similar patch/pr Jenkins capability and

Re: PRJenkins builds for Projects

- Original Message - > From: "Allen Wittenauer" > This is the same model the ASF has used for JIRA for a decade+. >It’s always been possible for anyone to submit anything to Jenkins > and have it get executed. Limiting PRs or patch files in JIRAs to > just

Re: workspace cleanups needed on jenkins master

> CouchDB has 300+ builds from July taking up 100-150MB each. I’m not > sure why these wouldn’t have been removed by the ‘days to keep old > items’ parameter, so we’ll need to look into that on the infra side > as well. If the addition of the ‘max # of old items’ parameter > doesn’t purge them

Re: workspace cleanups needed on jenkins master

Hi there, - Original Message - > From: "Chris Lambertus" > As a rule of thumb, we’d like to see > projects retain no more than 1 week or 7 builds worth of historical > data at the absolute maximum. > 54 GB ./CouchDB Our config is: Discard old items: checked Days to keep old items: 7

Re: Non committer collaborators on GitHub

Allen Wittenauer wrote: >> On Dec 14, 2018, at 3:57 AM, Zoran Regvart wrote: >> And, probably the best one, is to have a ASF wide GitHub account that >> builds can use. > > I do think because of how Github works, an ASF-wide one is probably too > dangerous. But I can’t see why private@project

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

- Original Message - Allen Wittenauer wrote: > > On Dec 11, 2018, at 9:09 AM, Joan Touzet wrote: > > Perhaps I'm misunderstanding...are the Nexus-published builds not treated > > the same because they're not on dist.apache.org? Or are they not release > > ve

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

be built on another machine. -Alex On 12/8/18, 10:48 AM, "Joan Touzet" wrote: I would like to see support for something like this as well, even if it came down to individual VMs/donated HW per project, locked down by project - only project X can use build machine X'. Automa

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

I would like to see support for something like this as well, even if it came down to individual VMs/donated HW per project, locked down by project - only project X can use build machine X'. Automated repeatable builds actually *increases* trust vs. who knows what a release manager has running

Re: New Jenkins Nodes and some rolling maintenance

And just like that, it's started working again. Thanks for all your (collective) hard work on keeping Jenkins up and running for all of us. I know it's not easy. All the best, Joan - Original Message - From: "Joan Touzet" To: builds@apache.org, gmcdon...@apache.org C

Re: New Jenkins Nodes and some rolling maintenance

Thanks for the info, Gavin. I (re-)started a job about 45 minutes ago and the job is unable to find any nodes labelled 'ubuntu.' I tried restarting it again just now, and the same problem occurred. Is this related - should we expect a full Jenkins outage right now? Text from the job: "H13

Re: HBase nightly job failing forever

I'll speak to CouchDB - the donation is directly in the form of a Jenkins build agent with our tag, no money is changed hands. The donator received a letter from fundraising@a.o allowing for tax deduction on the equivalent amount that the ASF leasing the machine would have cost for a year's

Re: Jenkins Slave Workspace Retention

HI Allen, > It’s also worth pointing out that “just use Docker” only works if > one is building on Linux. That isn’t an option on Windows. Not true, you can host Windows containers inside of Windows hosts now, apparently - though I've not tried it. > … and where does this

Re: Jenkins Slave Workspace Retention

I realize our use case is a bit different than some of the big Java projects here, but I thought I'd give a few tips and tricks that have helped us along the way: Allen Wittenauer said: > > On Jul 23, 2018, at 12:45 AM, Gavin McDonald > > wrote: > > > > Is there any reason at all to keep the

Re: Jenkins build hosts filling up...needs everyone's help!

Yes - you can do this in your own Jenkinsfile or job description. In a Pipeline build (declarative or procedural), use deleteDir() : https://jenkins.io/doc/pipeline/steps/workflow-basic-steps/#-deletedir-%20recursively%20delete%20the%20current%20directory%20from%20the%20workspace In a

Jenkins build hosts filling up...needs everyone's help!

Hi there, Chris over in https://issues.apache.org/jira/browse/INFRA-16768 recommended I start a thread. We've been getting increasing numbers of failures on our builds due to nodes running out of disk space. In 16768, Chris says: "We are getting to the point where builds are running machines

Re: [DISCUSS] Deploy releases to DockerHub

Interesting. Previously, I was told we were not allowed to push snapshot builds to anywhere that the public might have access - only for our development teams. If we are now allowed to publish snapshot/nightly/checkin-based images to DockerHub, that eases a lot of CouchDB's pain. As far as

Re: Building with docker - Best practices

Hi Thomas, I can't speak to anything maven related, but on 1), you might want to look at leveraging the new Pipeline syntax, and especially the Declarative Pipeline syntax. This lets you have a Jenkinsfile right in your repo that contains the entire configuration for Jenkins. Keeping your CI

Re: Nightly build & push of Docker image(s) to bintray?

bcomponent of our project. > > Kenn > > [1] https://repository.apache.org/content/groups/snapshots/org/apache/ > [2] http://www.apache.org/legal/release-policy.html#host-rc > [3] https://www.apache.org/dev/repository-faq.html#revolutioncode > [4] https://bintray.com/apache/bea

Re: Jenkins slave able to build BED & RPM

This is what Apache CouchDB does to auto-build .deb and .rpm Linux packages. All the details are in the Jenkinsfile in our main repo, along with the companion couchdb-ci and couchdb-pkg repos for support files. Start here: https://github.com/apache/couchdb/blob/master/Jenkinsfile#L100-L112 It

Re: Nightly build & push of Docker image(s) to bintray?

Be very careful here. Making such binaries available outside of your immediate developer community is a violation of Apache policy: http://www.apache.org/dev/release-distribution.html#unreleased The middle two bullet points are the issue here. CouchDB decided to build packages and binaries

Re: INFRA-15156: problems to send mails from Jenkins

CouchDB is still getting mails, so it's not a server-wide outage. -Joan - Original Message - From: "P. Ottlinger" To: builds@apache.org Sent: Monday, 2 October, 2017 7:00:53 PM Subject: Re: INFRA-15156: problems to send mails from Jenkins Hi, ping help - can

Re: (MXNet) Testing changes to the Jenkinsfile without merging to the repo.

Multibranch pipeline builds always use the Jenkinsfile in a specific branch when testing that branch. So, your changes to the Jenkinsfile pre-merge will only affect builds on that branch. Hopefully this is enough? You can always create a new multibranch pipeline build that has a filter on which

Re: [JENKINS] - Plugins update

Yup, that's the one. I see the job is back now. Phew! Going to give it a run and see if it's successful. -Joan - Original Message - From: "Gavin McDonald" <ga...@16degrees.com.au> To: builds@apache.org Cc: "Joan Touzet" <woh...@apache.org> Sent: Saturda

Re: [JENKINS] - Plugins update

Oof, I see that ours (a multibranch pipeline job) is missing. Any clue whether the job will be restored once the plugins are restored as well? -Joan - Original Message - From: "Gavin McDonald" To: builds@apache.org Sent: Saturday, 16 September, 2017 6:36:21 PM