Jenkins snaps not building

I recently submitted a PR to the Jenkins snap repo, and it was merged. I had expected the merge to trigger a new build, but upon checking several hours later, it hasn’t built the new version, yet. I’m wondering if the webhook is misconfigured, not configured, or just not working?

I’ve noticed this problem on some of my own snaps and I have to manually trigger builds. I’ve not raised the issue, as I assumed I’d done something wrong, but this may be something others are seeing, too.

Here’s what I mean:

snap info jenkins
---
channels:
  latest/stable:    2.290 2021-04-29 (2126) 131MB classic
  latest/candidate: ↑                             
  latest/beta:      2.325 2021-12-19 (2767) 131MB classic
  latest/edge:      2.337 2022-03-06 (2978) 152MB classic

The version should be:

installed:          2.428              (x6) 147MB classic

Note: The version I have installed was locally built. Perhaps @galgalesh has some idea (see PR comments and actions)?

Thanks for noticing this!!

The snap is failing due to automatic reviews.

Errors
------
 - lint-snap-v2:external_symlinks
	package contains external symlinks: usr/lib/jvm/java-11-openjdk-amd64/lib/security/blacklisted.certs -> /etc/java-11-openjdk/security/blacklisted.certs
jenkins_2.428_amd64.snap: FAIL

This is a bug in the debian package. You can fix it like this:

Do you mind creating a new PR to fix this issue? You can test it locally using review-tools: https://snapcraft.io/review-tools

1 Like

Stand by for a quick local build to confirm and PR…

@galgalesh - I just submitted the PR. I’m sure you’re aware, just noting it here to close this post out.

The test builds are hit/miss. They’ll either pass or fail w/o any discernible reason. If you look at the commit history in the PR, you’ll see my comments. I’m passing this on to the @Snapcrafters team to troubleshoot. I’ve provided my last commit to the master branch and will keep building local versions for my own consumption.