Jenkins Approval stage links doesn't work

Using Jenkins Ask a question
1

I have an Approve stage in the Jenkinsfile.

stage () {

steps {
script { input “DeployToTest”, message: “Deploy to TEST?”, ok: ‘Deploy’) }
}
}

This would prompt Deploy or Abort links in the Jenkins console. This works in v2.414. I recently upgraded to 2.452. The approval links doesn’t work anymore. Nothing happened after clicked on Deploy or Abort link. What could be the issue?

2

The issue you’re encountering with the approval links not working after upgrading Jenkins from version 2.414 to 2.452 could be due to several reasons, including changes in Jenkins core, plugin incompatibilities, or security settings that were introduced or modified between these versions. :person_shrugging:

Here are a few ideas to hopefully help you diagnose the problem:

  1. Review the release notes for Jenkins versions between 2.414.1 and 2.452.3. Look for any changes related to pipeline execution, input steps, or security that might affect the behavior of approval links.
  2. Ensure all plugins, especially the Pipeline and related plugins, are updated to their latest versions compatible with Jenkins 2.452. Sometimes, functionality breaks due to outdated plugins not being fully compatible with newer Jenkins versions.
  3. Check if there are any new security settings introduced in Jenkins or in plugins that might be blocking the execution of scripts or the input step specifically.
  4. Look into the Jenkins logs for any errors or warnings that occur when you click the Deploy or Abort link. This can provide clues to what might be going wrong.
  5. Create a minimal pipeline script that only contains an input step to see if the issue persists. This can help isolate the problem.
  6. Sometimes, the issue might be client-side. Check the browser console for any JavaScript errors that might be preventing the links from working.
  7. Revert to a Known Good Configuration: As a last resort, if the issue severely impacts your CI/CD process and cannot be resolved promptly, consider reverting Jenkins to the previous version where the functionality worked, until a solution is found.
  8. Upgrade gradually, by going to 2.424.3, and then 2.440.3, and so on.

Remember to perform these steps in a testing or staging environment if possible, to avoid impacting your production CI/CD pipelines.

1 Like
3

I already updated the plugins before even I post here. It didn’t help. I also created a dummy pipeline and tried. Jenkins logs doesn’t have any clue.

4

As far as I can tell, there is a syntax error in the snippet of Pipeline script that you posted. I can’t find any way to make the Pipeline Snippet Syntax Generator create that syntax. When I run a Pipeline with that syntax, it fails with a message about named arguments.

I ran the following declarative Pipeline successfully with 2.452.3 and current releases of all plugins:

pipeline {
    agent any

    stages {
        stage('Hello') {
            steps {
                echo 'Hello World'
                input id: 'DeployToTest', 
                         message: 'Deploy to TEST?', 
                         ok: 'Deploy'
                echo 'Goodbye World'
            }
        }
    }
}

Note that DeployToTest is preceded by id:

1 Like
5

Thanks. I upgraded Jenkins from v 2.452.1 to 2.452.3 and updated all the plugins. It works now.