Inconsistent behaviour of jenkins-plugins

[larsskj]

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

I'm preparing to split our large Jenkins server into several smaller instances.

As part of the task, we want to add Renovate to maintain and ensure proper upgrades of the new servers. For now, I have three test servers running in Kubernetes: Renovate is used to monitor the Jenkins deployments and the plugins list.

Each server has a repository in Github Enterprise, and we're using the Renovate Github app to monitor these.

On the initial test setup, things appeared to work fine: The Kubernetes deployment is monitored, and a PR is created to update Jenkins weekly. We also received a PR for each plugin update: This happens several times a day, so we limited it by grouping updates and creating a schedule. Again, this worked fine.

We then copy/pasted the renovate.json to the repos for the remaining two Jenkins servers - and was in for a surprise: The setup that worked on the first server failed to work on the two remaining servers.

For some reasons, the same Renovate app running in Github won't accept the versioning scheme used by the Jenkins plugins on the two additional hosts: It works fine on one host, but complains in the logfiles for the two others hosts and don't create a PR.

How can that be?

On the good server, we have logs like

DEBUG: branches info extended
{
  "branchesInformation": [
    {
      "branchName": "renovate/plugins",
      "prNo": 26,
      "prTitle": "Update dependency custom-folder-icon to v2.17",
      "result": "done",
      "upgrades": [
        {
          "datasource": "jenkins-plugins",
          "depName": "custom-folder-icon",
          "displayPending": "",
          "fixedVersion": "2.16",
          "currentVersion": "2.16",
          "currentValue": "2.16",
          "newValue": "2.17",
          "newVersion": "2.17",
          "packageFile": "plugins.yaml",
          "updateType": "minor",
          "packageName": "custom-folder-icon"
        }
      ]
    },
    {
      "branchName": "renovate/major-plugins",
      "prNo": 24,
      "prTitle": "Update plugins (major)",
      "result": "done",
      "upgrades": [
        {
          "datasource": "jenkins-plugins",
          "depName": "cloudbees-bitbucket-branch-source",
          "displayPending": "",
          "fixedVersion": "914.vc8c12e22f10e",
          "currentVersion": "914.vc8c12e22f10e",
          "currentValue": "914.vc8c12e22f10e",
          "newValue": "922.va_71d0e0b_7b_8d",
          "newVersion": "922.va_71d0e0b_7b_8d",
          "packageFile": "plugins.yaml",
          "updateType": "major",
          "packageName": "cloudbees-bitbucket-branch-source"
        },
        {
          "datasource": "jenkins-plugins",
          "depName": "durable-task",
          "displayPending": "",
          "fixedVersion": "577.v2a_8a_4b_7c0247",
          "currentVersion": "577.v2a_8a_4b_7c0247",
          "currentValue": "577.v2a_8a_4b_7c0247",
          "newValue": "581.v299a_5609d767",
          "newVersion": "581.v299a_5609d767",
          "packageFile": "plugins.yaml",
          "updateType": "major",
          "packageName": "durable-task"
        },
        {
          "datasource": "jenkins-plugins",
          "depName": "oss-symbols-api",
          "displayPending": "",
          "fixedVersion": "215.vc98c1787b_397",
          "currentVersion": "215.vc98c1787b_397",
          "currentValue": "215.vc98c1787b_397",
          "newValue": "235.v1a_b_7758b_3396",
          "newVersion": "235.v1a_b_7758b_3396",
          "packageFile": "plugins.yaml",
          "updateType": "major",
          "packageName": "oss-symbols-api"
        },
        {
          "datasource": "jenkins-plugins",
          "depName": "ssh-credentials",
          "displayPending": "",
          "fixedVersion": "343.v884f71d78167",
          "currentVersion": "343.v884f71d78167",
          "currentValue": "343.v884f71d78167",
          "newValue": "349.vb_8b_6b_9709f5b_",
          "newVersion": "349.vb_8b_6b_9709f5b_",
          "packageFile": "plugins.yaml",
          "updateType": "major",
          "packageName": "ssh-credentials"
        }
      ]
    }
  ]
}

whilst the other two servers log

DEBUG: Dependency durable-task has unsupported/unversioned value 577.v2a_8a_4b_7c0247 (581.v299a_5609d767) (versioning=maven)
DEBUG: Skipping durable-task because no currentDigest or pinDigests
DEBUG: Dependency email-ext has unsupported/unversioned value 1855.vd9e491cb_de1e (1861.vdb_d991590994) (versioning=maven)
DEBUG: Skipping email-ext because no currentDigest or pinDigests
DEBUG: Dependency ssh-credentials has unsupported/unversioned value 343.v884f71d78167 (349.vb_8b_6b_9709f5b_) (versioning=maven)
DEBUG: Skipping ssh-credentials because no currentDigest or pinDigests
DEBUG: Dependency workflow-durable-task-step has unsupported/unversioned value 1378.v6a_3e903058a_3 (1398.vf6c9e89e5988) (versioning=maven)
DEBUG: Skipping workflow-durable-task-step because no currentDigest or pinDigests

How can the same Renovate app with identical configurations react like this?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[github-actions[bot]]

Hi there,

A maintainer wants you to find and share a specific log message (packageFiles with updates) from your repository or environment.

If you self-host Renovate: make sure you run Renovate with LOG_LEVEL=debug to get the debug log messages! Next, open the debug-level logs and search for packageFiles with updates. This text marks the start of a structured log message that shows every package file, dependency, and update that Renovate found.

Find the relevant dependency/dependencies in the log message, and copy/paste those parts into this discussion. If you do not know which bits we need, you can copy/paste the full log message.

Read the Renovate docs, Troubleshooting to learn more about getting the docs, and getting the correct type of logs.

Thanks, the Renovate team

[larsskj]

Then let's focus on this one from the working server:

{
            "currentValue": "577.v2a_8a_4b_7c0247",
            "currentVersion": "577.v2a_8a_4b_7c0247",
            "currentVersionAgeInDays": 76,
            "currentVersionTimestamp": "2024-09-13T17:36:11.000Z",
            "datasource": "jenkins-plugins",
            "depName": "durable-task",
            "fixedVersion": "577.v2a_8a_4b_7c0247",
            "isSingleVersion": true,
            "packageName": "durable-task",
            "registryUrl": "https://updates.jenkins.io",
            "sourceUrl": "https://github.com/jenkinsci/durable-task-plugin",
            "versioning": "maven",
            "warnings": [],
            "updates": [
              {
                "bucket": "major",
                "newVersion": "581.v299a_5609d767",
                "newValue": "581.v299a_5609d767",
                "downloadUrl": "https://updates.jenkins.io/download/plugins/durable-task/581.v299a_5609d767/durable-task.hpi",
                "releaseTimestamp": "2024-11-26T14:58:10.000Z",
                "newVersionAgeInDays": 2,
                "newMajor": 581,
                "newMinor": 0,
                "newPatch": 0,
                "updateType": "major",
                "branchName": "renovate/major-plugins"
              }
            ]
          },

and from the failing server:

          {
            "datasource": "jenkins-plugins",
            "versioning": "maven",
            "depName": "durable-task",
            "currentValue": "577.v2a_8a_4b_7c0247 (581.v299a_5609d767)",
            "updates": [],
            "packageName": "durable-task",
            "warnings": [],
            "skipReason": "invalid-value"
          },

The difference is obvious - but I fail to see why this happens.

[larsskj]

These files - and a lot more - are available on developer.mend.io.

That's irrelevant because nobody here is going to look them up for you

Sorry: I have no knowledge on your working procedure.

[rarkins]

Working:

"currentValue": "577.v2a_8a_4b_7c0247",

Failing:

"currentValue": "577.v2a_8a_4b_7c0247 (581.v299a_5609d767)",

The part in brackets makes it an invalid version. If it's not obvious to you where/why it's happening, we'll need a reproduction repo (see instructions above)

[rarkins]

I have a feeling that the title of this Discussion is wrong/misleading and should be changed. These are not the same. You're seeing different behavior for different values, which is not the definition of "inconsistent"

[larsskj]

You're right: For some reason the plugins.yaml for the failing servers include the current as well as the upgrade versions in brackets. Don't know how that sneaked in: I'll remove it immediately and expect everything to work again.

A little later: Yes - that was indeed the problem. Renovate works now.

Sorry to bother you.